Ok guys, I found a solution (temporary at least) for bypassing signature problems. This is how I did it:
1) You will need this tool: http://www.ngohq.com/home.php?page=dseo
2) Make a clean installation of 1.31 UNI Driver (https://brainbit.wordpress.com/xonar-driver-cleaning-guide/), choose any option you want (for me asio patch was most important), but disable silent installation. After installation is done, don’t reboot yet.
3) Start Driver Signature Enforcement Overrider 1.3b (as administrator) and choose “Sign a System File” and put this path C:\Windows\System32\drivers\cmudaxp.sys
4) When signing is done use Driver Signature Enforcement Overrider 1.3b again and pick Enable Test Mode. Now you can reboot system.
5) After boot driver should work perfectly, but in down-right corner will popup Test Mode whatermark, for removing this crap use this: http://deepxw.blogspot.com/2008/12/remove-watermark-v03-build-20081210.html
Run it, reboot system and it’s done. Now you can use UNI drivers without any problems. I don’t know how “safe” this method is, but its works for me 🙂
I have a Xonar D1 and none of the possible workaround works for me under Win7 x64 Ultimate SP1. I tried the test builds, this method and the DSEO method from DNL. I always get a driver signature problem.
Lastest test builds test builds (6&7) work fine for me in all modes (norma, LowLatency, C-Media, GX) except when i select ASIO patch. While normal 1.31 buld can be installed only when i select C-Media, other methods not work without DSEO
Windows 7 64-bit, ASUS Xonar Essence ST, can’t install 1.41 drivers. Gives a driver signature error every time. I’ve tried the above solution and it did not work.
I’m seeing the same issue with my Xonar DX in Win7 x64. Installer finishes without any issues, but device manager shows that the ASUS Xonar DX Audio Device is not working because “Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)”.
I tried both silent and non-silent installs, and I tried the INF file workaround on this page. Neither helped at all. I guess I’ll have to try to get an earlier version of Uni Xonar working again 😦
Windows 7 x64 Pro, UniXonar 1.41, Xonar D1. Everything installed ok except ASIO patch. Device switched off and there is a note “cannot verify the digital signature” in device properties. I tried many methods but no luck. After two hours i found solution, that works for me:
1. Remove any UniXonar driver (no need to reboot)
2. Install native ASUS driver v.7.12.8.1777 (google it), NO need to reboot
3. Install UniXonar 1.41 with ASIO Patch, DO NOT uninstall native driver
4. Reboot and enjoy.
Still having issues with the Code 52. Tried all ways described here and Test Mode, but still no solution. Xonar DX on win7 pro 64bit, newest beta build and 1.41.
Been how many months and not even the beta build fixes this.
Christ, not much of an improvement over the ASUS coders as you claim to be.
Especially if bloody Test Mode doesnt work.
The funny thing is I haven’t coded a line in the Uni xonar drivers compared to Asus ones, and had to rely on different workarounds and trial and error methods for different settings to actually fix things.
Now the bad part is that I am sick of this smart-ass kind of comments. I do this out of my own time beside having a job of my own other than trying to fix something that isn’t my responsibility to begin with. That being said please don’t try any of my work if you can’t get rid of this attitude.
Until 1.41 drivers for some of the people having issues installing, the error was kind of my fault but now with 1.41, the problem is fixed and drivers files are exactly how the Asus are. With 1.50 drivers, they don’t have a valid certificate so I needed to create a temporary/test one, which again works for most. Why isnt it working for you? Well this most probably has something to do with your Windows & Windows configuration (paranoid antivirus, security settings, modified windows files,etc.). If you would know install a clean Windows 7 from an original DVD, apply all the updates and then install UNi Xonar drivers I almost certain that both 1.41 and 1.50 would work. But better not try this and held me responsible for other problems you might encounter, I said this for your information and also for anyone else in your possition.
I had a clean win7 x64 install and 1.41 installed fine and worked for 2 weeks with my DX. I rebooted today right after installing and using speedfan (i rebooted the previous day) and i no longer see audio playback devices, and in hardware info for the dx i see the signature error. I tried system restore to before that and it didn’t work. I also tried reinstalling using the method above. I probably sound like i don’t know much but I’m just saying what’s happened to me, which may be of use to you guys.
Forgot to mention, I used the low dpc and unchecked silent install every time.
Thanks for the info, its interesting and it kinda proves my point that something happens (software wise) on some machines. But then again I don’t understand why it still works with the same version Asus drivers. I suppose it works for you with the 1794 Asus drivers?
Please try 1.50 drivers with enabling testmode and report if they work.
Edit: Can you restore to like a week ago or a couple of days more, and if it works note what updates where installed, or what other programs you have installed.
Hah, I have the same problem with the Xonar DG drivers straight off Asus’ site – PCI_DG_7_12_8_1794_W7. I only happened across this thread because I was searching for “xonar dg cannot verify digital signature code 52” on Google (sans quotes).
It does seem to have occurred around the time I installed some recent Windows updates, and the error does note that “A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.” – it doesn’t specifically say that it’s *THIS* file.
I’ll post back if I find a fix. I don’t know about resetting my BIOS (as Ian posted on Dec 30 2011) – I guess I could reconfigure it from scratch, but it seems weird that would have an effect.
brainbit 
Still getting this error on W7 x64.
Still whines about not being signed
Damm its not working still got the message of not signed driver
I’ve isolated the problem: it seems to happen when installing as standard plus the ASIO patch on the installer option.
Working on W7 x64, after multiple attempts of other methods.
Went to temp, isolated is-*****.tmp, deleted everything but the Xonar DX inf.
After restart, sound card still works – remains to be seen if it kicks the bucket in the future.
And did you tested test builds 6 and 7?
Ok guys, I found a solution (temporary at least) for bypassing signature problems. This is how I did it:
1) You will need this tool:
http://www.ngohq.com/home.php?page=dseo
2) Make a clean installation of 1.31 UNI Driver (https://brainbit.wordpress.com/xonar-driver-cleaning-guide/), choose any option you want (for me asio patch was most important), but disable silent installation. After installation is done, don’t reboot yet.
3) Start Driver Signature Enforcement Overrider 1.3b (as administrator) and choose “Sign a System File” and put this path C:\Windows\System32\drivers\cmudaxp.sys
4) When signing is done use Driver Signature Enforcement Overrider 1.3b again and pick Enable Test Mode. Now you can reboot system.
5) After boot driver should work perfectly, but in down-right corner will popup Test Mode whatermark, for removing this crap use this:
http://deepxw.blogspot.com/2008/12/remove-watermark-v03-build-20081210.html
Run it, reboot system and it’s done. Now you can use UNI drivers without any problems. I don’t know how “safe” this method is, but its works for me 🙂
I’m working on W7 Prof 64bit Xonar ST.
Hope this gonna help somebody,
Cheers.
The purpose of this workaround and for the test builds is to find another way to install the drivers without DSEO and using the system in test mode.
Anyone thanks for taking the time to write this, maybe some new users will find it useful.
Thanks 4 driver and signing is work 🙂
DNL method works, however I see “remove watermarks” from DSEO program too, did you tried that instead remove-watermark-v03-build-20081210.html ?
This will redirect you to remove-watermark-v03 website 😉
I come to say great job with the drivers.
I have W7 x64 and i dont get driver signature problem, but if i dont use this method drivers wont install.
I have a Xonar D1 and none of the possible workaround works for me under Win7 x64 Ultimate SP1. I tried the test builds, this method and the DSEO method from DNL. I always get a driver signature problem.
Lastest test builds test builds (6&7) work fine for me in all modes (norma, LowLatency, C-Media, GX) except when i select ASIO patch. While normal 1.31 buld can be installed only when i select C-Media, other methods not work without DSEO
Windows 7 64-bit, ASUS Xonar Essence ST, can’t install 1.41 drivers. Gives a driver signature error every time. I’ve tried the above solution and it did not work.
I’m seeing the same issue with my Xonar DX in Win7 x64. Installer finishes without any issues, but device manager shows that the ASUS Xonar DX Audio Device is not working because “Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)”.
I tried both silent and non-silent installs, and I tried the INF file workaround on this page. Neither helped at all. I guess I’ll have to try to get an earlier version of Uni Xonar working again 😦
Windows 7 x64 Pro, UniXonar 1.41, Xonar D1. Everything installed ok except ASIO patch. Device switched off and there is a note “cannot verify the digital signature” in device properties. I tried many methods but no luck. After two hours i found solution, that works for me:
1. Remove any UniXonar driver (no need to reboot)
2. Install native ASUS driver v.7.12.8.1777 (google it), NO need to reboot
3. Install UniXonar 1.41 with ASIO Patch, DO NOT uninstall native driver
4. Reboot and enjoy.
Still having issues with the Code 52. Tried all ways described here and Test Mode, but still no solution. Xonar DX on win7 pro 64bit, newest beta build and 1.41.
Been how many months and not even the beta build fixes this.
Christ, not much of an improvement over the ASUS coders as you claim to be.
Especially if bloody Test Mode doesnt work.
The funny thing is I haven’t coded a line in the Uni xonar drivers compared to Asus ones, and had to rely on different workarounds and trial and error methods for different settings to actually fix things.
Now the bad part is that I am sick of this smart-ass kind of comments. I do this out of my own time beside having a job of my own other than trying to fix something that isn’t my responsibility to begin with. That being said please don’t try any of my work if you can’t get rid of this attitude.
Until 1.41 drivers for some of the people having issues installing, the error was kind of my fault but now with 1.41, the problem is fixed and drivers files are exactly how the Asus are. With 1.50 drivers, they don’t have a valid certificate so I needed to create a temporary/test one, which again works for most. Why isnt it working for you? Well this most probably has something to do with your Windows & Windows configuration (paranoid antivirus, security settings, modified windows files,etc.). If you would know install a clean Windows 7 from an original DVD, apply all the updates and then install UNi Xonar drivers I almost certain that both 1.41 and 1.50 would work. But better not try this and held me responsible for other problems you might encounter, I said this for your information and also for anyone else in your possition.
I had a clean win7 x64 install and 1.41 installed fine and worked for 2 weeks with my DX. I rebooted today right after installing and using speedfan (i rebooted the previous day) and i no longer see audio playback devices, and in hardware info for the dx i see the signature error. I tried system restore to before that and it didn’t work. I also tried reinstalling using the method above. I probably sound like i don’t know much but I’m just saying what’s happened to me, which may be of use to you guys.
Forgot to mention, I used the low dpc and unchecked silent install every time.
Thanks for the info, its interesting and it kinda proves my point that something happens (software wise) on some machines. But then again I don’t understand why it still works with the same version Asus drivers. I suppose it works for you with the 1794 Asus drivers?
Please try 1.50 drivers with enabling testmode and report if they work.
Edit: Can you restore to like a week ago or a couple of days more, and if it works note what updates where installed, or what other programs you have installed.
I loaded default in bios and it’s working again 😀
Hah, I have the same problem with the Xonar DG drivers straight off Asus’ site – PCI_DG_7_12_8_1794_W7. I only happened across this thread because I was searching for “xonar dg cannot verify digital signature code 52” on Google (sans quotes).
It does seem to have occurred around the time I installed some recent Windows updates, and the error does note that “A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.” – it doesn’t specifically say that it’s *THIS* file.
I’ll post back if I find a fix. I don’t know about resetting my BIOS (as Ian posted on Dec 30 2011) – I guess I could reconfigure it from scratch, but it seems weird that would have an effect.