Driver Digital Signature error when using signed drivers (Code 52)

[ajayav]

Hi,

This is my first post on these forums, so please excuse me if anything is wrong.

Details of the problem: I have a Sony VAIO laptop that runs Windows 7 Home Premium x64. I recently downloaded the same version from digital river that has SP1 included and installed it on my laptop. I installed the drivers that I had downloaded from sony's esupport site which went fine. After I rebooted and tried to install the rest of the drivers, I started getting the Code 52 error: Windows cannot verify the signature of this driver. I've seen that every driver can be installed immediately after the system has been booted the first time (after a clean install). Once rebooted, it starts giving the code 52 error. I can't install my iPhone drivers (through iTunes) or PS3 utilities because of this. I'm wondering what changes during the first reboot. I must also say that these very same drivers were used on the previous build of Win 7 HP that I was using except that it did not have SP1 integrated.

Has anyone had a similar experience? I know that the digital signature check can be disabled using bcdedit.exe but I want Windows 7 to work the way it should: it should stop me from using unsigned drivers while installing signed drivers correctly. Does any one have any clue to what's going on with my Win7 on my laptop?

 

[archer]

Hi ajayav, Welcome to Sevenforums.

Boot into Advanced Boot Options and disable driver signing checking.

The Advanced Boot Options screen lets you start Windows in advanced troubleshooting modes. You can access the menu by turning on your computer and pressing the F8 key before Windows starts.

Disabling driver signature enforcement has helped a lot of users in fixing the issue.

You may also delete the USB "Upper Filter" & "Lower Filter" Entry and check if that helps.

Before we go any further, please first backup the Registry.

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:



1. Click “Start”, type “regedit” (without quotation marks) in the “Search” bar and press Enter.

Note: If UAC (User Account Control) pops up, please accept it.

2. Right click “Computer” (the root node) in the left pane, click “Export” under the “File” menu, choose “All” under “Export range”, and select “Desktop” in the “Save” in box and type backup in “File Name”. Click “Save”.

Note: The backup file is on the Desktop and named backup.reg. We can simply restore the registry by double-clicking the backup.reg file.

3. Click “Start”, type “regedit” (without quotation marks) in the “Search” bar and press Enter again.
4. Locate the “UpperFilters” value under the following key in the registry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{36FC9E60-C465-11CF-8056-444553540000}

5. On the “Edit” menu, click “Delete”, and then click “OK”.
6. Locate the “LowerFilters” value under the same key in the registry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{36FC9E60-C465-11CF-8056-444553540000}

7. On the “Edit” menu, click “Delete”, and then click “OK”.
8. Quit Registry Editor and restart the computer.

 

[ajayav]

Thank you archer for that detailed set of instructions!

I'll try this out and let you know how it went. I hope it will solve the issue but I'm still curious to know why the driver signature check fails when a proper digital signature is available on the driver. Windows shows the driver as digitally signed but won't install it for some reason.

Also, I've done the Advanced Boot options thing and everything works well then, it's just that I don't want to disable checking for driver signatures. let me see how your solution works.

Thank you for taking the time to go through my post and give a reply too!

 

[archer]

Reason for sign failure could be an issue with registry. The above mentioned procedure might solve the issue. But, I will suggest to be very cautious while making tweaks in registry.

 

[ajayav]

I'm sorry archer, but that didn't work...

 

[archer]

Check this Link. This might help