How to Fix USB Error Digital Signature (Code 52) Error

Error Code 52 in either the device manager or DXDiag tells you that Windows can’t verify the digital signature for the drivers for a specific device. You won’t be able to install drivers for the device, and it might just as well stop functioning.

This issue happens for a lot of users, especially with Windows 7. There is no clear root cause for the error, but some users began seeing it after installing a specific update, and the update was different, meaning there are a few of them that might have caused the issue. It basically indicates a driver failure, and Microsoft would recommend either running the troubleshooter or updating the drivers manually.

code-52

However, if you’ve ever encountered issues with drivers, you’ll know that the aforementioned solutions seldom work. Fortunately, we have several other strategies for you that should assist in resolving the issue. These have been confirmed to work for a number of users experiencing this problem. The first method is universal, catering to almost any device facing this issue, as does the second one. The final method specifically targets issues with USB drivers. Select the one that most closely aligns with your situation and proceed.

Method 1: Delete the USB Upper Filter and Lower Filter entries (only applies if the problematic devices are the USB drivers)

Here are two registry entries known as UpperFilters and LowerFilters that can cause these types of issues. Oftentimes, deleting them is the solution. However, note that editing your registry can cause numerous problems if done incorrectly, so double-check before proceeding with each step of the method.

  1. Press the Windows and R keys on your keyboard simultaneously. Type ‘regedit‘ into the Run dialogue window, and press Enter. If you receive a UAC prompt, accept it.
  2. In the Registry Editor, use the left side navigation pane to navigate to the following folder:

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

  1. Find the UpperFilters and LowerFilters. Select one, then from the Edit menu on the top toolbar, select Delete and click OK. Repeat the process for the other value.
  2. Close the Registry Editor and reboot your computer.

upper-filters

At this point, you have three possible solutions for your problem. However, not each one can be used in all situations, so it is advised that you read through all of them and see which one fits your situation best. Then, go ahead and use it to solve your Code 52 issue.

Method 2: Use an elevated command prompt to disable integrity checks

The issue appears when Windows tries to verify the digital signature and integrity of a device, and disabling that option may allow you to install the drivers for it. The steps are as follows:

  1. Press the Windows key on your keyboard, then type in. Right-click the result and choose ‘Run as administrator.’
  2. In the Command Prompt, type in the following commands, and press Enter on your keyboard after each one to execute them:

bcdedit -set loadoptions DDISABLE_INTEGRITY_CHECKS

bcdedit -set TESTSIGNING ON

  1. If you get a UAC prompt, click YES/ALLOW/OK

If this doesn’t work, there is another set of commands that you can use. Follow step 1 of the method to open the Command Prompt, and in step 2, replace the aforementioned commands with the following ones:

bcdedit /deletevalue loadoptions

bcdedit -set TESTSIGNING OFF

 

2016-11-27_022004

You shouldn’t be getting the Code 52 error at this point, but if you are, proceed with the next method.

Method 3: Disable Driver Signing Checking from the Advanced Boot Options (Windows 8 and 10) Only

This method will let you disable driver signing checking before Windows boots, which can allow you to install the drivers for the problematic devices without Windows checking for the signatures.

  1. Before Windows starts, repeatedly press F8 or ShiftF8 on your keyboard to access the Advanced Boot Options. If this doesn’t resolve your issue, begin starting your system. Interrupt the process by pressing the Power button to restart it. You may need to do this three or more times until the advanced menu appears.
  2. Click Choose an Option -> Advanced Options -> Startup Settings -> Restart. After the System Restart choose option 7.digital-signature-code-52-error
  3. When Windows boots up, you can try updating the drivers from the Device Manager. The steps to do so are as follows, and you should repeat them for each problematic device, one by one.
  4. Simultaneously press the Windows and R keys on your keyboard. In the Run dialogue box, type in ‘devmgmt.msc‘, then hit Enter.
  5. In the Device Manager, find the problematic device. You will recognize it by the yellow exclamation mark next to its name.
  6. Right-click the device and choose Update Driver Software. Follow the wizard until the driver is installed, and reboot your device if necessary.
  7. Repeat this process for every device you see an exclamation mark next to.

 

ABOUT THE AUTHOR

Kevin Arrows


Kevin Arrows is a highly experienced and knowledgeable technology specialist with over a decade of industry experience. He holds a Microsoft Certified Technology Specialist (MCTS) certification and has a deep passion for staying up-to-date on the latest tech developments. Kevin has written extensively on a wide range of tech-related topics, showcasing his expertise and knowledge in areas such as software development, cybersecurity, and cloud computing. His contributions to the tech field have been widely recognized and respected by his peers, and he is highly regarded for his ability to explain complex technical concepts in a clear and concise manner.

Comments

11
    DA
    Daniel Dec 22, 2016

    In method #2 there’s a typo with the command bcedit, should be bcdedit which is shown in the cmd graphic below it.

    Reply
      KA
      K. Arrows Author Dec 25, 2016

      Thank you for identifying. I’ve amended it.

    SS
    Soni Setiawan Sep 21, 2017

    Thank you, it’s work for me. Method #1.

    PT
    prateek tiwari May 5, 2018

    Thanks buddy it worked!!!

    PD
    Pankaj Das Sep 12, 2018

    Thanks..

    CH
    Curtis Hargreaves Nov 21, 2018

    Method #1 broke my laptop :p

    SM
    steve m Feb 19, 2019

    There is a command missing from the Method 2, instruction 1 – what needs to be typed in, and presumably with “hit Enter”?
    Also, is Method 1 done before Method 2? My reading is that M1 is done first, then either one of the two items listed under M2 or that under M3. This is confusing and inconsistent, and Step 1 would be better followed by the three Methods.
    Finally, is Method 3 only for use with Win 8 or 10? If so the word “only” should be inside the brackets.
    Without the answer to my first query I cannot make use of this guide. I thank you for doing what you have done but as it stands it is incomplete.
    steve m – Win7

      KA
      K. Arrows Author Jul 11, 2019

      Will get this updated.

    SW
    Shane Warren Author Sep 21, 2019

    The method was verified before it was published, maybe you deleted the wrong file

    AN
    Anna Jun 3, 2021

    Hi Kevin, thanks for the post on this issue. I’ve been suffering the code 52 error on my mouse for nearly 3 weeks and cannot fix it. My system is Windows 10 and my mouse is also Windows.
    Method 1 doesn’t work for me coz there’s no upperfilters/lowerfilters key in the location.
    Method 2 – I ran as administrator and got this return msg when executing the second command: “C:Windowssystem32>bcdedit -set TESTSIGNING ON
    An error has occurred setting the element data.
    The value is protected by Secure Boot policy and cannot be modified or deleted.”
    Method 3 works but it seems to be a temporary fix for my laptop gave me a blue screen afterwards and said they found something wrong and is collecting data and will reboot. After reboot, the code 52 came back.
    And I also try to update the driver in Device Manager. It said its the latest driver so no luck. Also, I cannot find the official published Windows mouse driver on Microsoft website, which is weird.
    So for now I think I’m bumping into walls. Do you have any new ideas about solving this issue?

      MZ
      Muhammad Zubyan Author Jun 13, 2021

      It seems like your Mouse’s hardware is the issue and Windows is preventing the use of a driver so your computer doesn’t get hurt. I suggest you to try a different mouse and check to see if the issue persists. Let me know how it goes.