Also, this occurred both on my desktop HTPC with an nVidia GTX 760 and on my Surface Pro 2 with an Intel HD4600, so I'm 99% certain it's a problem inherent to the driver itself, not my particular hardware config.Ĭlick to but I still do use 32bit/x86 Windows on two computers - on a custom built PC with an old Intel board with Realtek ALC861 audio and on my mom's Dell Inspiron e1405 laptop with Sigmatel/IDT STAC9220 audio. Not complaining or anything, but this hadn't been mentioned yet in this thread, and figuring out this issue and then troubleshooting it was a bit of a nightmare for me. You have to either rollback with a restore point or reinstall Windows.
Worse, simply uninstalling this driver will not restore HDCP validation. I presume the fact that it's an unsigned driver is what is actually preventing it from qualifying as a protected HDCP signal chain. For some reason this driver is seen as an 'audio repeater' by Windows, and this seems to disrupt HDCP registration (a sort of hardware DRM that's built into the HDMI specification and is required to playback most paid video content).
I imagine it also breaks PowerDVD playback of Blu-rays, but I didn't test that.
#CANT USE DOLBY ADVANCED AUDIO V2 INSTALL#
This completely breaks your HDCP validation chain, so if you install this driver, you will no longer be able to playback Netflix, Hulu, Amazon, Vudu, iTunes, etc.
0 kommentar(er)
