# Device Manager Code 52: Driver Signature Error > Fix Device Manager Code 52 in Windows 11. Learn why driver signatures fail, how to verify drivers, and how to install trusted replacements safely. URL: https://raincleaner.eu/guides/device-manager-code-52-driver-signature-error Short answer: Device Manager Code 52 indicates that a required driver does not satisfy Windows digital signature verification, and the recommended solution is to install a compatible, properly signed driver from a trusted source. ## What Does Device Manager Code 52 Mean? Device Manager Code 52 is a Windows driver signature verification failure. Its internal Windows problem identifier is CM_PROB_UNSIGNED_DRIVER. The full error message is: 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) Windows uses digital signatures to verify the integrity of driver packages and identify their publishers. Driver signing requirements also determine whether certain drivers are permitted to load. Code 52 commonly occurs when a kernel-mode driver does not satisfy the signing policy enforced by a 64-bit Windows installation. The error can involve an unsigned driver, an incorrectly signed package, a damaged driver file, or a signature that Windows cannot validate under its current security requirements. A signature verification failure does not automatically prove that the driver contains malware. However, Windows blocks drivers that fail applicable verification requirements because loading untrusted kernel-mode code creates security risks. Microsoft identifies the underlying error as CM_PROB_UNSIGNED_DRIVER and recommends obtaining a properly signed driver for the affected hardware. Official Microsoft documentation: https://learn.microsoft.com/en-us/windows-hardware/drivers/install/cm-prob-unsigned-driver ## Why Does Windows Require Signed Drivers? A digital signature connects a software package to signing information that Windows can evaluate for integrity and trust. Windows uses driver package signatures to verify that package contents have not been modified after signing and to establish information about the software publisher. Kernel-mode drivers operate with extensive system privileges. A faulty or malicious kernel-mode driver can affect system stability, access sensitive information, or compromise operating system security. Modern 64-bit Windows versions enforce kernel-mode driver signing requirements. Windows 11 also supports additional security mechanisms that can affect whether a driver is allowed to load. A driver package may use a signed catalog file rather than an embedded signature on every individual driver binary. For this reason, the absence of a Digital Signatures tab on an individual SYS file does not necessarily prove that the complete driver package is unsigned. A valid signature also does not guarantee that a driver is bug-free, compatible with every device, or free from security vulnerabilities. Windows evaluates driver signing according to the operating system version, applicable policies, and package characteristics. Microsoft documents driver signing requirements at https://learn.microsoft.com/en-us/windows-hardware/drivers/install/driver-signing. - Digital signatures help establish package integrity. - Signing information identifies the driver publisher or signing authority. - Kernel-mode drivers are subject to Windows signing requirements. - A properly signed driver may still contain bugs. - A driver file without an embedded signature may belong to a package signed through a catalog. - Signature verification depends on the applicable Windows security policies. - Disabling signature enforcement is not an appropriate routine repair. ## Step 1: Confirm Code 52 and Your Windows Version Before replacing a driver, confirm the exact error and identify the Windows installation. 1. Press Win + R, type winver, and press Enter. 2. Record the Windows version and OS build displayed in the About Windows dialog. 3. Press Win + X and select Device Manager. 4. Alternatively, press Win + R, enter devmgmt.msc, and press Enter. 5. Look for a device displaying a yellow warning symbol. 6. Expand the relevant device category. 7. Right-click the affected device and select Properties. 8. Open the General tab. 9. Read the Device status field and confirm that Code 52 appears. 10. Record the complete error message and device name. 11. Open the Driver tab and record the driver provider, date, and version. 12. Open the Events tab, when available, and review recent device installation events. The Device status field is the primary location for confirming the problem code. Do not assume that every yellow warning symbol indicates a driver signature problem. Other Device Manager errors require different troubleshooting procedures. Windows 10 and Windows 11 both provide Device Manager, although interface details can differ between versions. ## Step 2: Identify the Affected Hardware Correct hardware identification is essential before downloading or installing a replacement driver. 1. Open Device Manager. 2. Right-click the affected device and select Properties. 3. Open the Details tab. 4. Select Hardware Ids from the Property dropdown. 5. Copy the displayed identifiers. 6. Select Device instance path if you need to identify the exact device instance. 7. Record the device manufacturer and model when available. 8. Compare the hardware identifiers with the computer or component manufacturer's official documentation. PCI devices commonly use identifiers containing VEN and DEV fields. USB devices commonly use identifiers containing VID and PID fields. For example, a PCI identifier may begin with PCI\VEN_ and include a DEV_ value identifying the device. Hardware identifiers help match devices to compatible driver packages, but they do not prove that a downloaded package is safe or correctly signed. Use the official support website of the computer or hardware manufacturer to confirm compatibility. Avoid unfamiliar driver-download websites that offer packages solely because they contain a matching identifier. Do not publish complete device instance paths unnecessarily because they may contain device-specific information. ## Step 3: Restart Windows and Recheck the Error A normal restart is a reasonable first troubleshooting step, especially if Code 52 appeared immediately after a software or driver installation. 1. Save your work and close running applications. 2. Open Start > Power > Restart. 3. Allow Windows to restart completely. 4. Open Device Manager again. 5. Locate the affected device. 6. Open Properties > General. 7. Check whether Code 52 is still displayed. 8. If the error disappeared, test the affected device's functionality. Restarting allows Windows to initialize devices and evaluate drivers again, but it does not convert an unsigned driver into a properly signed driver. If the driver remains incompatible with Windows signing requirements, a restart alone will generally not resolve Code 52. Do not repeatedly restart without investigating a persistent signature verification failure. ## Step 4: Check Windows Update for Signed Drivers Windows Update is a recommended source for compatible driver packages. 1. On Windows 11, open Settings > Windows Update. 2. Select Check for updates. 3. Allow available updates to download and install. 4. Restart Windows if requested. 5. Return to Settings > Windows Update > Advanced options. 6. Select Optional updates if that option is available. 7. Expand Driver updates. 8. Review any driver packages offered for the affected hardware. 9. Install an appropriate package after confirming that it applies to your device. 10. Restart Windows when requested. 11. Open Device Manager > affected device > Properties > General. 12. Check whether Code 52 has disappeared. The availability of optional driver updates varies by device, Windows build, and system configuration. The absence of an optional update does not prove that no compatible signed driver exists. On Windows 10, the corresponding location is generally Settings > Update & Security > Windows Update. For organization-managed computers, driver updates may be controlled through administrator policies. If the affected device is the computer's only network adapter, obtain a verified replacement driver before making changes that could interrupt connectivity. ## Step 5: Install a Properly Signed Manufacturer Driver Microsoft recommends obtaining a properly signed driver from the hardware manufacturer when Code 52 occurs. 1. Identify the exact computer or hardware model. 2. For laptops and prebuilt computers, begin with the computer manufacturer's official support website. 3. For separately purchased components, use the component manufacturer's official support website. 4. Locate the driver download section for the exact device model. 5. Confirm compatibility with your Windows version and system architecture. 6. Review the driver's release notes and installation instructions. 7. Download the appropriate package from the official source. 8. If the manufacturer provides a documented signature or checksum verification procedure, follow it. 9. Install the driver using the manufacturer's supported installer or instructions. 10. Restart Windows when requested. 11. Open Device Manager and check whether the device now starts correctly. A driver designed for an older Windows version may not satisfy current Windows 11 signing requirements. Do not assume that a driver is suitable merely because it installed successfully on another computer. A manufacturer may provide different packages for different hardware revisions or Windows versions. Avoid using unofficial modified drivers or packages advertised as signature-fixed versions. If the manufacturer does not provide a compatible signed driver, contact its support team rather than disabling Windows security protections. ## Step 6: Check the Driver's Digital Signature You can inspect signing information for an individual driver-related file, but remember that driver package signing may use a catalog file. 1. Open Device Manager. 2. Right-click the affected device and select Properties. 3. Open the Driver tab. 4. Select Driver Details if the button is available. 5. Record the displayed driver file paths. 6. Open File Explorer and navigate to the directory containing the relevant file. 7. Right-click the file and select Properties. 8. Open the Digital Signatures tab if one is present. 9. Review the signer information. 10. Select an available signature and choose Details to inspect its reported status. 11. If the Digital Signatures tab is absent, do not conclude that the complete driver package is unsigned. Some valid driver packages are signed through a catalog file, and individual SYS files may not contain embedded Authenticode signatures. For a read-only PowerShell inspection of an individual file, run Get-AuthenticodeSignature -FilePath 'C:\Path\To\Driver.sys', replacing the example path with the exact verified file location. The PowerShell result applies to the specified file and does not automatically establish the trust status of the entire driver package. A NotSigned result for an individual SYS file can occur when the driver package relies on catalog signing. Advanced driver signature validation may require Microsoft's SignTool and the appropriate Windows SDK or WDK components. SignTool is not guaranteed to be installed on an ordinary Windows 11 computer. For an actual Code 52 failure, Device Manager, SetupAPI logs, and Code Integrity events are more informative than judging a single file's Properties dialog in isolation. Microsoft explains driver signature troubleshooting at https://learn.microsoft.com/en-us/windows-hardware/drivers/install/troubleshooting-driver-signing-installation. ## Step 7: Roll Back a Recent Driver Update If Code 52 appeared immediately after updating a driver, a previously working version may be worth restoring. 1. Open Device Manager. 2. Right-click the affected device. 3. Select Properties. 4. Open the Driver tab. 5. Select Roll Back Driver if the button is available. 6. Choose the reason requested by Windows. 7. Confirm the rollback. 8. Restart Windows if requested. 9. Reopen Device Manager > Properties > General. 10. Verify whether Code 52 has disappeared. The Roll Back Driver option is available only when Windows retains an eligible previous driver version. An earlier driver is not automatically acceptable under current Windows signing requirements. If the previous driver is also unsigned or otherwise fails signature verification, rolling back may not resolve the error. Do not attempt to restore an old driver by manually copying files into protected Windows driver directories. If the rollback works, record the working driver version and investigate the compatibility of future updates. ## Step 8: Reinstall the Device Driver Safely If the affected device still reports Code 52 after installing a verified compatible driver, reinstalling the device may help correct installation-related problems. Before proceeding, obtain the appropriate signed replacement driver and confirm that you can recover the device if Windows does not reinstall it automatically. 1. Save your work. 2. Open Device Manager. 3. Locate the device reporting Code 52. 4. Right-click it and select Uninstall device. 5. Review the confirmation dialog. 6. Do not select an option to delete or remove the driver package unless its removal is specifically justified and a verified replacement is available. 7. Confirm the uninstall. 8. Restart Windows. 9. Allow Windows to detect the device again. 10. Install the verified signed driver when necessary. 11. Restart if the installer requests it. 12. Return to Device Manager > Properties > General and inspect the resulting status. Windows may automatically reinstall a staged driver package during device detection. If the same rejected driver remains the preferred package, Code 52 may return after reinstallation. Uninstalling a device instance is not identical to removing its driver package from the Driver Store. Do not use forced driver package removal to bypass signing failures. Avoid removing boot-critical storage controllers or essential network drivers without a tested recovery procedure. If the manufacturer's official instructions specify a different installation order, follow those instructions. ## Advanced Diagnosis with PnPUtil PnPUtil is a Windows command-line utility for inspecting Plug and Play devices and driver packages. The executable is normally located at %windir%\System32\pnputil.exe. Device enumeration support is available starting with Windows 10 version 1903. Check the installed Windows build with winver. 1. Open Command Prompt as administrator. 2. Run pnputil /? to inspect the supported options. 3. Run pnputil /enum-devices /problem to list devices reporting problems. 4. Run pnputil /enum-devices /problem 52 to identify devices reporting Code 52. 5. If you know the affected device's exact instance path, run pnputil /enum-devices /instanceid "DEVICE_INSTANCE_PATH", replacing DEVICE_INSTANCE_PATH with the value copied from Device Manager. 6. On supported Windows versions, run pnputil /enum-devices /instanceid "DEVICE_INSTANCE_PATH" /drivers to inspect matching and installed drivers. 7. The /drivers option for device enumeration is supported starting with Windows 10 version 2004. 8. Run pnputil /enum-drivers to list staged third-party driver packages. 9. Compare the displayed driver information with Device Manager > affected device > Properties > Driver. 10. Record the driver provider, version, original INF filename, and published INF name when available. 11. On Windows 11 version 22H2 or later, pnputil /enum-drivers /files can list the files associated with staged third-party driver packages. 12. Do not infer driver signature validity solely from the fact that a package appears in the Driver Store. These enumeration commands are read-only and do not change device configuration. PnPUtil /enum-drivers lists third-party driver packages rather than every built-in Microsoft driver. Avoid pnputil /delete-driver with /force or other modification commands unless a qualified administrator has identified the exact package and the consequences. PnPUtil cannot make an unsigned driver properly signed. Official Microsoft reference: https://learn.microsoft.com/en-us/windows-hardware/drivers/devtest/pnputil-command-syntax. - pnputil /?: Displays supported PnPUtil commands. - pnputil /enum-devices /problem 52: Lists devices reporting Code 52. - pnputil /enum-devices /instanceid "DEVICE_INSTANCE_PATH": Inspects a specific device. - pnputil /enum-devices /instanceid "DEVICE_INSTANCE_PATH" /drivers: Displays driver information on supported Windows versions. - pnputil /enum-drivers: Lists staged third-party driver packages. - pnputil /enum-drivers /files: Lists files belonging to third-party driver packages on Windows 11 version 22H2 and later. - winver: Shows the installed Windows version and OS build. - These commands can assist diagnosis without changing system security settings. ## Check SetupAPI Logs for Signature Failures Windows records device installation information in the SetupAPI device installation log. The default log file is %windir%\INF\setupapi.dev.log. This log can contain driver signing information, installation errors, and details about driver package verification. 1. Open Command Prompt. 2. Run echo %windir% to identify the Windows installation directory. 3. Run dir "%windir%\INF\setupapi.dev.log" to verify that the log exists. 4. Run notepad "%windir%\INF\setupapi.dev.log" to open the log for inspection. 5. Search for the affected device's hardware ID or device instance identifier. 6. Examine entries recorded around the time of the failed driver installation. 7. Look for signing-related entries and installation failures. 8. Microsoft documents a Code 52 diagnostic entry containing CM_PROB_UNSIGNED_DRIVER. 9. The hexadecimal problem value 0x34 corresponds to decimal Code 52. 10. Other log entries may describe certificate trust problems, package verification failures, or additional driver installation issues. 11. Record relevant error codes and their timestamps. 12. Compare the results with Device Manager and any Code Integrity events. The SetupAPI log can contain historical information from many device installations. An old signing warning does not automatically explain the current Code 52 error. Do not rename, delete, or modify the production SetupAPI log merely to simplify troubleshooting. Microsoft documents SetupAPI signing diagnostics at https://learn.microsoft.com/en-us/windows-hardware/drivers/install/troubleshooting-driver-signing-installation. ## Check Windows Code Integrity Events Windows Code Integrity checks whether code meets applicable integrity and signing requirements. When driver loading is rejected, Code Integrity event logs may contain useful diagnostic information. 1. Press Win + R. 2. Enter eventvwr.msc and press Enter. 3. Expand Applications and Services Logs. 4. Expand Microsoft > Windows > CodeIntegrity. 5. Open Operational if the log is available. 6. Review events recorded around the time the affected driver failed to load. 7. Inspect the event description for a driver filename, signature failure, or policy-related explanation. 8. Compare the file path and timestamp with the affected device and SetupAPI installation records. 9. Microsoft documents Event ID 3004 as one event that can indicate a kernel driver attempted to load with an invalid signature. 10. Other Code Integrity event identifiers can describe different policy or signature failures. 11. An event must be interpreted according to its complete description and the active Windows configuration. 12. Do not assume every Code Integrity warning belongs to the device showing Code 52. 13. If no relevant event is present, the absence of an event does not prove that the driver signature is valid. 14. Do not disable Code Integrity logging or modify its configuration to conceal the error. The exact events recorded depend on Windows version, enabled policies, and the circumstances of the driver-loading attempt. Microsoft documents Code Integrity events at https://learn.microsoft.com/en-us/windows-hardware/drivers/install/code-integrity-event-log-messages. ## Can Memory Integrity or Secure Boot Affect Drivers? Windows 11 supports security features that help protect the operating system from untrusted or incompatible low-level code. Memory Integrity, also called Hypervisor-protected Code Integrity or HVCI, can impose additional compatibility and security requirements on kernel-mode drivers. Secure Boot helps protect the system's startup process by checking relevant boot components according to platform security policies. These features are related to system integrity but are not identical to Windows driver package signature verification. A driver incompatible with Memory Integrity does not necessarily produce Code 52. Windows may report a different error or display a separate security notification. To inspect Memory Integrity, open Windows Security > Device security > Core isolation details, when the option is supported and available. Review the Memory integrity status without changing it. To check Secure Boot status, press Win + R, enter msinfo32, and press Enter. In System Information, inspect Secure Boot State and BIOS Mode under System Summary. The available values depend on the computer's firmware and Windows configuration. Do not disable Memory Integrity, Secure Boot, or other security protections simply because a driver fails to load. If a driver is incompatible with the current security configuration, seek a corrected or supported driver from the manufacturer. For organization-managed computers, security settings may be enforced through administrative policies. The correct repair is to address driver compatibility and signing, not to weaken security requirements. - Memory Integrity provides additional kernel-mode protection when supported and enabled. - Secure Boot helps protect the trusted startup process. - Driver signing requirements can apply independently of these features. - Windows Security > Device security > Core isolation details: Inspect Memory Integrity where available. - msinfo32 > System Summary: Inspect Secure Boot State and BIOS Mode. - Do not disable security protections to force an untrusted driver to load. - Seek an updated signed driver compatible with the computer's security configuration. ## Should You Disable Driver Signature Enforcement? No. Disabling driver signature enforcement is not a recommended repair for ordinary Windows users experiencing Code 52. Driver signature enforcement helps prevent kernel-mode drivers that do not meet applicable signing requirements from loading. Bypassing this protection can expose the system to unstable, modified, or malicious low-level software. Some online instructions suggest disabling signing checks, enabling test-signing mode, changing boot configuration settings, or permanently weakening Windows security features. These approaches do not repair the driver's signature or establish that the driver is trustworthy. Test-signing and specialized driver-loading configurations exist for controlled driver development and testing environments. They are not substitutes for obtaining properly signed production drivers. If a manufacturer provides only an unsigned driver for an old device, ask whether a supported Windows 11 driver is available. If no compatible signed driver exists, the hardware may not be supported on the current Windows installation. Do not disable antivirus protection, Secure Boot, Memory Integrity, or Code Integrity merely to force the driver to load. Do not modify boot configuration settings based on unverified instructions. For business computers, bypassing driver signing requirements can also violate organizational security policies. Microsoft recommends obtaining a properly signed driver instead of bypassing kernel-mode driver signing requirements. - Unsafe: Disabling driver signature enforcement as a permanent workaround. - Unsafe: Enabling test-signing mode on a production computer to load an untrusted driver. - Unsafe: Disabling Secure Boot solely to bypass a driver compatibility problem. - Unsafe: Disabling Memory Integrity without a justified, documented security decision. - Unsafe: Modifying boot configuration to avoid driver verification. - Unsafe: Installing unofficial patched drivers. - Safe: Obtaining a properly signed driver from the manufacturer. - Safe: Using Windows Update to find a supported replacement. - Safe: Contacting the hardware manufacturer about Windows 11 compatibility. ## Code 52 vs. Other Device Manager Errors Different Device Manager codes describe different types of driver and device failures. Code 52 corresponds to CM_PROB_UNSIGNED_DRIVER and indicates a driver signature verification problem. Code 10 corresponds to CM_PROB_FAILED_START and indicates that a device failed during startup. Code 28 corresponds to CM_PROB_FAILED_INSTALL and indicates a driver installation problem where a working driver was not selected. Code 31 corresponds to CM_PROB_FAILED_ADD and indicates a failure when adding the device to its Windows device stack. Code 43 corresponds to CM_PROB_FAILED_POST_START and indicates that a device reported a problem after its startup stage. Code 39 corresponds to CM_PROB_DRIVER_FAILED_LOAD and indicates that Windows could not load the device driver. Code 48 corresponds to CM_PROB_DRIVER_BLOCKED and indicates that a driver was blocked from loading. Although some symptoms overlap, these codes are not interchangeable. A driver failure should be investigated using the exact code displayed in Device Manager > Properties > General. Microsoft maintains the technical problem code reference at https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/device-manager-problem-codes. - Code 52: Driver signature verification failure. - Code 10: Device failed to start. - Code 28: Driver installation failed or no suitable driver was selected. - Code 31: Device could not be added successfully to its device stack. - Code 43: Device reported a problem after startup. - Code 39: Windows failed to load the device driver. - Code 48: Windows blocked a driver from loading. - Always verify the exact code before following a troubleshooting procedure. ## Safe vs. Unsafe Code 52 Troubleshooting Code 52 should be investigated using supported Windows diagnostic tools and trusted driver packages. A successful repair must restore device functionality without unnecessarily weakening Windows security. The objective is to install a driver that meets the applicable signing and compatibility requirements. - Safe: Confirm Code 52 in Device Manager > Properties > General. - Safe: Identify the device using its hardware IDs. - Safe: Record the Windows version and installed driver version. - Safe: Check Windows Update for compatible drivers. - Safe: Obtain signed drivers from the official manufacturer. - Safe: Inspect relevant SetupAPI and Code Integrity logs. - Safe: Use read-only PnPUtil commands to inspect device and driver information. - Conditionally safe: Roll back to a previously working driver that satisfies current signing requirements. - Conditionally safe: Reinstall the device using a verified signed replacement driver. - Unsafe: Installing unsigned or modified drivers from untrusted sources. - Unsafe: Disabling signature enforcement to bypass Code 52. - Unsafe: Disabling Windows security features solely to load a driver. - Unsafe: Adding unverified certificates to trusted system stores. - Unsafe: Deleting files from the Windows Driver Store manually. - Unsafe: Forcing removal of critical driver packages. - Unsafe: Running registry-cleaner scripts that promise to repair driver signatures. - Not recommended: Assuming the error proves a virus infection. - Not recommended: Assuming any driver with a visible digital signature must be compatible. ## What If No Signed Driver Exists? Some older hardware devices no longer receive driver updates from their manufacturers. A driver created for an older Windows release may not satisfy modern Windows signing or security requirements. If Windows Update does not offer a compatible package, check the manufacturer's official support documentation. Confirm the exact hardware revision and supported operating systems before concluding that no driver exists. Contact the manufacturer and ask whether a properly signed Windows 11 driver is available. If the device is still supported, the manufacturer may provide an updated installer or revised driver package. If the manufacturer confirms that the hardware is unsupported, consider replacing the device with a supported alternative. Do not use unofficial modified drivers or signing-bypass utilities as a routine solution. For critical hardware, prioritize a supported replacement rather than relying on insecure workarounds. On company-managed computers, consult the administrator before replacing hardware or modifying drivers. If Code 52 appeared after an update, document the Windows build, driver version, and device model when contacting support. Reinstalling Windows does not guarantee that an unsupported unsigned driver will become compatible. When the required signed driver is unavailable, leaving the incompatible driver blocked is safer than weakening operating system protections. ## Key Takeaways and Related Guides Device Manager Code 52 indicates that Windows cannot verify the digital signature of a driver required by a hardware device. The internal Windows problem identifier is CM_PROB_UNSIGNED_DRIVER. The driver may be unsigned, incorrectly signed, damaged, or incompatible with the signing requirements enforced by the current Windows configuration. Begin by checking Device Manager, recording the device hardware ID, and identifying the installed driver version. Use Windows Update or the manufacturer's official support website to obtain a compatible signed replacement. If the error appeared after a driver update, investigate whether a previous signed driver can be restored. For advanced diagnostics, inspect %windir%\INF\setupapi.dev.log and Event Viewer > Applications and Services Logs > Microsoft > Windows > CodeIntegrity > Operational. Do not disable driver signature enforcement, Secure Boot, or Memory Integrity merely to bypass the error. If no supported signed driver exists, contact the manufacturer or consider a compatible hardware replacement. Microsoft's official Code 52 reference: https://learn.microsoft.com/en-us/windows-hardware/drivers/install/cm-prob-unsigned-driver. Microsoft's driver signing documentation: https://learn.microsoft.com/en-us/windows-hardware/drivers/install/driver-signing. Microsoft's driver signing troubleshooting reference: https://learn.microsoft.com/en-us/windows-hardware/drivers/install/troubleshooting-driver-signing-installation. Microsoft's PnPUtil command reference: https://learn.microsoft.com/en-us/windows-hardware/drivers/devtest/pnputil-command-syntax. - Code 52 is a driver signature verification failure. - A signature error does not automatically prove that malware is present. - Verify the affected hardware and exact Windows version. - Prefer Windows Update and official manufacturer drivers. - Check package signing information rather than judging a single SYS file. - Use SetupAPI and Code Integrity logs when additional diagnosis is necessary. - Never disable Windows security protections just to force an untrusted driver to load. - Do not manually delete protected driver files. - Use a compatible signed driver or supported hardware replacement when necessary. Related: - [Learn how to identify your hardware and locate compatible drivers](https://raincleaner.eu/guides/find-driver-by-hardware-id-windows) - [Follow the recommended process for updating Windows drivers](https://raincleaner.eu/guides/how-to-update-drivers-windows-11) - [See how to restore a previously working driver version](https://raincleaner.eu/guides/rollback-driver-update-windows-11) - [Understand another common driver installation error](https://raincleaner.eu/guides/device-manager-code-28-driver-not-installed) Author: [T. Vasilev](https://raincleaner.eu/about) · [About the author](https://raincleaner.eu/about) ## Official documentation - [Microsoft: storage cleanup (Windows 10 / 11)](https://support.microsoft.com/en-us/windows/experience/storage-filemanagement/free-up-drive-space-in-windows) References checked: 2026-10-25. Options and menu names can differ by system version. Read the linked documentation before making changes. Want a second opinion before deleting anything?Rain Cleaner shows what it found before cleanup, and you decide what goes. Free version without ads; Pro has a free 7-day trial, no card. Windows 10 / 11, 64-bit.[Get Rain Cleaner →](https://raincleaner.eu/)  ·  [All guides →](https://raincleaner.eu/guides) ## Quick questions What does Device Manager Code 52 mean? Code 52 means Windows cannot verify the digital signature of a driver required by a hardware device. The driver may be unsigned, incorrectly signed, damaged, or unable to satisfy the current Windows driver signing requirements. How do I fix Code 52 in Windows 11? Open Device Manager, identify the affected device, and check Windows Update for a compatible driver. If necessary, download and install a properly signed replacement from the hardware manufacturer's official support website. Should I disable driver signature enforcement to fix Code 52? No. Disabling signature enforcement weakens an important Windows security protection and does not repair the driver's signature. The recommended solution is to install a compatible, properly signed driver. Does Code 52 mean my computer has malware? Not necessarily. Code 52 can result from unsigned, incorrectly signed, corrupted, or incompatible driver files without indicating malware. However, drivers obtained from unknown sources should be treated cautiously, and unexpected suspicious activity should be investigated separately. Can I use an old unsigned driver on Windows 11? An unsigned kernel-mode driver generally cannot satisfy the signing requirements enforced by a standard 64-bit Windows 11 installation. Ask the hardware manufacturer for a supported signed driver or consider a compatible replacement device instead of bypassing Windows security controls. ## Read next - [Find a driver by Hardware ID — Read the ID, understand it and search the maker's official page.](https://raincleaner.eu/guides/find-driver-by-hardware-id-windows) - [Drivers after a clean install of Windows 11 — A sensible order for network, chipset, storage, graphics and more.](https://raincleaner.eu/guides/drivers-after-clean-install-windows-11) - [Install INF drivers with PnPUtil — Add one driver or a whole folder from the command line.](https://raincleaner.eu/guides/install-inf-drivers-pnputil-windows-11) - [Why Is DriverStore Taking So Much Space? — Understand the Windows Driver Store, find large driver packages, identify unused drivers, and recover disk space without damaging hardware support.](https://raincleaner.eu/guides/driverstore-filerepository-too-large-windows-11) - [How to Fix Device Manager Code 10 — Understand why Windows reports This Device Cannot Start, identify the affected hardware, and troubleshoot driver or device problems without risky registry changes.](https://raincleaner.eu/guides/device-manager-code-10-device-cannot-start) - [How to Fix Device Manager Code 31 — Identify why Windows cannot load a device driver, check hardware IDs, update or reinstall drivers, and troubleshoot Code 31 without risky system modifications.](https://raincleaner.eu/guides/device-manager-code-31-windows-cannot-load-drivers) - [Free up disk space on Windows 11 safely](https://raincleaner.eu/guides/free-up-disk-space-windows-11-safely) - [Windows 11 PC health check](https://raincleaner.eu/guides/windows-11-pc-health-check-before-using-a-cleaner) - [Windows 11 slow after an update](https://raincleaner.eu/guides/windows-11-slow-after-update-what-to-check) - [Rain Cleaner vs CCleaner vs BleachBit](https://raincleaner.eu/guides/rain-cleaner-vs-ccleaner-vs-bleachbit) - [Delete temporary files on Windows 11 safely](https://raincleaner.eu/guides/delete-temporary-files-windows-11-safely) - [Windows Update Cleanup: is it safe?](https://raincleaner.eu/guides/windows-update-cleanup-safe-to-delete-windows-11) - [WinSxS folder too large?](https://raincleaner.eu/guides/winsxs-folder-too-large-what-to-delete-windows-11) - [Windows.old: is it safe to delete?](https://raincleaner.eu/guides/windows-old-safe-to-delete) - [Delivery Optimization files: safe to delete?](https://raincleaner.eu/guides/delivery-optimization-files-safe-to-delete) - [Free up Android storage safely](https://raincleaner.eu/guides/free-up-storage-android-without-deleting-important-files) - [Find duplicate photos on Android](https://raincleaner.eu/guides/find-and-delete-duplicate-photos-android) - [Windows 11 cleaner without ads](https://raincleaner.eu/windows-11-cleaner) - [Windows protected your PC: verify and run Rain Cleaner](https://raincleaner.eu/windows-protected-your-pc-rain-cleaner) - [Security reporting](https://raincleaner.eu/security) - [Roadmap](https://raincleaner.eu/roadmap) - [Linux server disk full](https://raincleaner.eu/guides/linux-server-disk-full-find-what-is-using-space) - [journald logs too big](https://raincleaner.eu/guides/journald-logs-too-big-limit-journal-size) - [Find large files on Windows 11](https://raincleaner.eu/guides/find-large-files-taking-space-windows-11) - [CCleaner alternatives for Windows 11](https://raincleaner.eu/guides/ccleaner-alternatives-windows-11) - [Windows cleanup guide](https://raincleaner.eu/guides/windows-cleanup) - [Windows 11 disk cleanup checklist](https://raincleaner.eu/guides/windows-11-disk-cleanup-checklist) - [Before you clean Windows](https://raincleaner.eu/guides/before-cleaning-windows) - [hiberfil.sys and pagefile.sys](https://raincleaner.eu/guides/hiberfil-sys-pagefile-sys-can-you-delete-them) - [Clean Windows with Rain Cleaner, step by step](https://raincleaner.eu/guides/how-to-clean-windows-with-rain-cleaner) - [Windows Update Download Cache](https://raincleaner.eu/guides/softwaredistribution-download-safe-to-delete) - [Why Is System Volume Information So Large?](https://raincleaner.eu/guides/system-volume-information-too-large-windows-11) - [Windows Installer Cache: What Is Safe?](https://raincleaner.eu/guides/windows-installer-folder-safe-to-delete) - [DirectX Shader Cache: Safe Cleanup Guide](https://raincleaner.eu/guides/directx-shader-cache-safe-to-delete-windows-11) - [Windows Error Reporting Files: Safe Cleanup](https://raincleaner.eu/guides/windows-error-reporting-files-safe-to-delete) - [MEMORY.DMP: Safe Removal and Crash Dump Cleanup](https://raincleaner.eu/guides/memory-dmp-safe-to-delete-windows-11)