Error Code 52 - USB ports not recognizing connected USB devices stating that "Windows cannot verify the digital signature for the drivers required for this device"

Anonymous
2010-03-07T20:11:51+00:00

Original Title: Error Code 52 - USB ports not recognizing connected USB devices

I have recently purchased a new laptop with Windows 7 and had no initial problems connecting USB devices (mouse, hard drive, camera etc.) to the ports. Since installing a number of windows updates none of my USB ports will now recognize any hardware that is connected to them.

The error code is quoted as follows **"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 have been into Device Manager and notice that each USB icon has a yellow exclamation mark icon next to it. I have uninstalled each USB port and scanned for hardware changes which has no positive affect. I have also tried to 'Update driver software' in device manager and again this tells me that the driver is up-to-date for each USB port.

Any help would be much appreciated.

Windows for home | Previous Windows versions | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2010-03-10T04:29:36+00:00

Hi slark101,

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:

How to back up and restore the registry in Windows

http://support.microsoft.com/kb/322756/

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.

  1. 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.

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

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

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

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

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

Hope this helps.


Gokul - Microsoft Support

[If this post was helpful, please click the "Vote as Helpful" (green triangle) button. If it helps in resolving your issue, click "Propose As Answer" or "Mark as Answer" button. By proposing/marking a post as Answered, or Helpful you help others find the answer faster.]

Was this answer helpful?

500+ people found this answer helpful.
0 comments No comments

42 additional answers

Sort by: Oldest
  1. Anonymous
    2011-04-13T21:43:05+00:00

    After applying the windows 7 updates (April 12th, 2011), everything was working fine. April 13th, 2011 morning when I startup the computer USB ports had this error. Did a system restore back to April 11th status, and USB ports magically worked normally. Does it mean that windows 7 updates = malicious software? Should I install the updates again?

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2011-04-17T13:01:10+00:00

    Also I had this boring problem. Today I uninstalled all Windows updates of april 13th (not Office or NET Framework ones), but problem remains. The only way is to restore back the system. I think Microsoft should release a fix for this issue. Are there news about it?

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2011-04-22T12:29:23+00:00

    I've had a similar problem, only after the update all my usb hi-speed ports are now running as very low speed and i keep getting the message to connect to hi speed ports which don't seem to exist any more?

    Stupid windows update...grrr!

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2011-04-23T08:13:31+00:00

    I'm waiting for news about this too.

    Around this time, my Zune HD stopped being able to connect, and i troubleshoot-ed my zune for days trying to figure out why it suddenly wouldn't connect. i gave up.

    then tonight i tried to connect my PSP, which wouldn't connect either. Then i realised it was my computer, and not my zune that was messed up. To check once more, i plugged in my webcam, also not working.

    After searching and trying, i finally was lead to the error 52 thing in device manager, then finally to this page. After reading what you guys said about the updates, i'm pretty sure it's not just a coincidence.

    I hope a fix is made soon. i hope they're even aware of this issue.

    Was this answer helpful?

    0 comments No comments