8.1.1 Invalid digital signature for drivers

[RyanC]

W7 is reporting invalid digital signature. It looks like the drivers aren't starting as PT throws up the no hardware connected error when it loads and digitest shows nothing.

Anyone else run into this?

[docric]

Yup!

Just yesterday... pulled out my old drive (with System & 8.1 files) and pointed the drivers to the OLD digi driver folder. Did some "under-the-hood-digital-tom-foolery" for a minute, then gave me a SWOD , but then on reboot the error message went away???

Magic? Luck? Dunno'... but our rig is working fine now.

[RyanC]

I had to disable driver signing. . .

[docric]

where can you do that at, Ryan?

[RyanC]

I found it here

[mixman4000]

Same situation here. Tried to install 8HD off the DVD but had to kill the driver installation part of the setup process from task manager in order to progress with the install. Installed 8.1.1 update over the top of that.

Get the 'Unable to locate Digidesign hardware' error on startup.

There are some devices under 'sound, video and game controllers' in Device Manager which have the yellow exclamation makr on them meaning there is a problem...the problem being no signed device driver.

Using the bcdedit commands:

bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
bcdedit.exe -set TESTSIGNING ON

I can turn off driver signing on reboot and load up Protools HD 8.1.1. However as soon as I turn off test mode the situation gpes back to as it was before.

Very annoying. I am going to look into how to fool Windows 7 into thinking the drivers are signed.

Can't believe it is this much hassle to run Protools 8HD on Windows 7.

[mixman4000]

A quick update.

I have downloaded the DSEO program to try and force Windows to accept the drivers as signed. I have identified windows\system32\drivers\dalwdm.sys as the unsigned driver file. I have used DSEO to try and sign it.

However, I am still in the same situation as before as Windows does not seem to accept the driver unless it is in test mode.

I think for the time being I'll just keep Win 7 in test mode until someone comes up with a solution.

[gandlz]

Hello,

first: I know that this thread is pretty old, but maybe there are some solutions know.

I just reinstalled my Win 7 to upgrade to the 64bit version because I need this now for some other things. Till know I was running Pro Tools HD 8.1.1 on 32bit and it worked fine. But on x64 I also got the problem with the unsigned driver, especially the dalwdm.sys. Running in test-mode works very well but I don’t want to keep my machine in this mode all the time.

On Version 8.0.3 and 8.1 the driver is digitally signed and it works without any bad workarounds.
So my question is: Did Avid forget to sign that driver? I mean I know there is no official Win7 support for Pro Tools 8 but it works and the only problem is that signature. So who do I have to pay less, Avid or Microsoft to sign that thing?

So I also read about using the 8.1 Drivers on 8.1.1 to work fine. But I also read about issues with Creative Collection in this case. What about this?
I also tested using the v10 standalone drivers but when using them I got a bluescreen (telling me some issue with dalwdm.sys) when shutting down or restarting the computer when my 192 I/O is powered on. No problem when it is powered off. Firmware is 4.9, told by DigiTest 8.0.3 – no newer version available. However, Pro Tools 8.1.1 seems to work just fine with v10 drivers, but I also read that this is not supported either and also not recommended as far as I read about one guy having problems with v10 drivers and Pro Tools HD 9.

I really would like to hear avids opinion about that problem as far as the write: “Although not officially supported, Pro Tools HD 8.1-8.1.1 can be used on Windows 7 (32 and 64-bit). No additional drivers are required for HD systems.“

Best regards!

[Abomb97]

It's so funny that I see this thread is still being commented on. I just spent hours in a studio trying to upgrade them from 8.0.3 to 8.1.1 on windows 7 x64. The system blocking the new drivers.

I ended up holding down F8 at startup and selecting to manually disable "digital driver enforcement", then installing. But this is good for the current session (bootup) only. So you have to do it every time you turn the PC on, otherwise...no PT hardware recognized.

I found this free BCD app (there are other BCD editors floating around) that might do the trick to at least automate the F8 & selection when you boot up.

https://www.dualbootpro.org/

Here is an app which purports to have a workaround:
http://www.ngohq.com/home.php?page=dseo

If anyone else wants to try one let me know, otherwise I'll give it a go and report back in a few days.

Or digi can offer up some signed drivers?

[Abomb97]

I was thinking I could take the PT9 drivers folder and copy it over the PT 8.1.1 drivers folder. Then re-install the hardware to the new drivers. Backwards compatible?

Anyone think this will work?

J