# Device Manager Code 31: Windows Cannot Load Drivers > Fix Device Manager Code 31 in Windows 11. Learn why Windows cannot load required drivers and how to update, reinstall, or troubleshoot them safely. URL: https://raincleaner.eu/guides/device-manager-code-31-windows-cannot-load-drivers Short answer: Device Manager Code 31 means Windows failed to load the drivers required for a device, and the recommended first repair is to update its driver using Windows Update, Device Manager, or the manufacturer's official package. ## What Does Device Manager Code 31 Mean? Device Manager Code 31 is a Windows device initialization error. Its internal Windows problem identifier is CM_PROB_FAILED_ADD. The complete error message is: This device is not working properly because Windows cannot load the drivers required for this device. (Code 31) Microsoft explains that Code 31 can occur when the function driver for a device returns an error from its AddDevice routine. For drivers using Windows Driver Frameworks, the failure may occur during the corresponding device-add callback. This means Windows has encountered a problem adding the device to the operating system's device stack. The error does not automatically mean that the hardware itself is damaged. Possible contributing factors include an incompatible driver, a damaged driver installation, a failed driver update, or a device-specific software configuration problem. Code 31 identifies the failure category but does not reveal the exact cause. The correct repair depends on the affected hardware, driver package, and Windows configuration. Microsoft documents the technical meaning of Code 31 at https://learn.microsoft.com/en-us/windows-hardware/drivers/install/cm-prob-failed-add. ## Which Devices Can Show Code 31? Code 31 can appear for different hardware categories because it describes a failure during device initialization rather than an error specific to one manufacturer. An affected device may appear in Device Manager with a yellow warning symbol. The symptoms depend on the device. A network adapter may stop providing connectivity, an audio device may become unavailable, or a peripheral may fail to initialize. A device can still be detected by Windows even when its driver cannot be loaded successfully. The exact device name, hardware identifier, and driver version should be recorded before making changes. - Network adapters: Wi-Fi or Ethernet connectivity may stop working. - Bluetooth adapters: Bluetooth functionality may become unavailable. - Audio devices: Speakers, microphones, or other audio functions may fail. - USB devices: Connected peripherals may fail to initialize correctly. - Graphics adapters: Display features or graphics acceleration may be affected. - Printers and scanners: Windows may detect the device without being able to use it. - Virtual devices: Drivers associated with software-defined devices may fail to initialize. - Storage controllers: A driver problem may affect storage availability and requires additional caution. ## Step 1: Confirm Code 31 and Your Windows Version Before changing drivers, verify that the affected device actually reports Code 31. 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, type devmgmt.msc, and press Enter. 5. Look for a device with 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 it displays Code 31. 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 events associated with the device. The Device status field is the primary location for identifying the exact Device Manager problem code. Windows 10 and Windows 11 both support Device Manager, although some interface details can differ between Windows versions. Do not follow Code 31 repair instructions if the device actually reports a different problem code. ## Step 2: Restart Windows and Recheck the Device Restarting Windows is a simple first step that allows the operating system to initialize hardware and drivers again. 1. Save your work and close running applications. 2. Open Start > Power > Restart. 3. Wait for Windows to restart completely. 4. Open Device Manager using devmgmt.msc. 5. Locate the previously affected device. 6. Open Properties > General. 7. Check whether Code 31 is still displayed. 8. If the error has disappeared, test the device's actual functionality. 9. If Code 31 remains, continue with driver identification. Using Restart is preferable to assuming that shutting down and turning the computer back on always performs an equivalent restart. Windows Fast Startup can affect shutdown behavior on supported configurations. A successful restart does not prove the underlying problem was permanently resolved. If the error returns, investigate the driver and device configuration. Avoid repeated restarts when the computer shows signs of storage failure, overheating, or other serious hardware problems. ## Step 3: Identify the Device Using Hardware IDs Hardware identifiers help determine which driver package belongs to the affected device. This is especially useful when Device Manager displays a generic device name. 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 from the same dropdown and record the value when more precise device identification is required. 7. Identify the computer manufacturer, device manufacturer, and exact hardware model. 8. Compare the identifiers with the manufacturer's official technical or driver documentation. PCI hardware IDs commonly contain VEN and DEV identifiers representing vendor and device information. USB hardware IDs commonly contain VID and PID identifiers. For example, a PCI device identifier may begin with PCI\VEN_ and include a DEV_ field. These identifiers help match hardware to compatible drivers, but they do not establish whether a downloaded driver package is trustworthy. Use official manufacturer resources rather than unfamiliar driver download websites. A hardware ID may contain information specific to the device. Avoid publishing complete device instance paths unnecessarily. ## Step 4: Check Windows Update for Compatible Drivers Microsoft recommends Windows Update as a primary source for compatible driver updates. 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 an update requires it. 5. Open Settings > Windows Update > Advanced options. 6. Select Optional updates if the option is available. 7. Expand Driver updates. 8. Review the available driver packages. 9. Install a relevant update only after confirming that it applies to the affected device. 10. Restart Windows if requested. 11. Open Device Manager > affected device > Properties > General. 12. Check whether Code 31 has disappeared. On Windows 10, the corresponding update interface is generally Settings > Update & Security > Windows Update. The availability and location of optional driver updates depend on the Windows version, update configuration, and administrative policies. If no optional driver update is offered, it does not prove that the installed driver is compatible or that no newer manufacturer driver exists. If the affected device is the computer's only network adapter, obtain a verified replacement driver through another trusted device before attempting changes that could interrupt connectivity. ## Step 5: Update the Driver Through Device Manager If Windows Update does not resolve Code 31, try updating the affected device through Device Manager. 1. Press Win + X and select Device Manager. 2. Expand the category containing the affected device. 3. Right-click the device. 4. Select Update driver. 5. Choose Search automatically for drivers. 6. Follow the instructions displayed by Windows. 7. If Windows finds a suitable driver, allow the installation to complete. 8. Restart Windows when requested. 9. Return to Device Manager > Properties > General and check the device status. If Windows reports that the best driver is already installed, that message does not guarantee that the current driver is functioning correctly. Device Manager may not discover every compatible manufacturer-specific driver package. If you have already downloaded a verified driver from the hardware manufacturer, select Update driver > Browse my computer for drivers. Choose the directory containing the extracted compatible driver files and follow the installation instructions. Do not install an arbitrary INF file simply because its filename resembles the affected device. Never disable driver signature enforcement or Windows security protections to force an unverified driver to load. Microsoft's official instructions are available at https://support.microsoft.com/en-us/windows/hardware/drivers/update-drivers-through-device-manager-in-windows. ## Step 6: Install the Official Manufacturer Driver A manufacturer-specific driver may be necessary when Windows does not provide a working package. 1. Identify the exact computer or hardware model using Device Manager and the manufacturer's documentation. 2. For laptops and prebuilt desktops, begin with the computer manufacturer's official support website. 3. For separately purchased components, check the component manufacturer's official support website. 4. Confirm that the package supports the exact device model. 5. Verify compatibility with your Windows version and system architecture. 6. Review any manufacturer instructions or known issues. 7. Download the appropriate driver package from the official source. 8. Save the installer or extracted driver files before beginning installation. 9. Follow the manufacturer's installation instructions. 10. Restart Windows when requested. 11. Open Device Manager and check the resulting device status. The newest driver is not automatically the most appropriate package for every computer. Some laptop manufacturers provide customized graphics, audio, chipset, or networking drivers for particular models. Do not replace a manufacturer-customized driver with a generic package without confirming compatibility. For storage controllers and other boot-critical devices, avoid driver replacement without a verified recovery procedure. If the manufacturer recommends a firmware update, follow its official documentation and assess the additional risks before proceeding. If Code 31 persists after installing the correct package, record the exact driver version and continue with targeted troubleshooting. ## Step 7: Roll Back a Driver After a Recent Update If Code 31 first appeared immediately after a driver update, rolling back to a previously working version may help. 1. Open Device Manager. 2. Right-click the affected device and select Properties. 3. Open the Driver tab. 4. Select Roll Back Driver if the button is available. 5. Choose the reason requested by Windows. 6. Confirm the rollback. 7. Restart Windows if prompted. 8. Return to Properties > General and check whether Code 31 is resolved. The Roll Back Driver option requires administrator permissions and an eligible previously installed driver version. The button may be unavailable when Windows has no suitable previous driver package or rollback is unsupported for the device. Do not attempt to force a rollback by manually deleting files from the Windows Driver Store. If the rollback restores normal operation, record the working driver version before making another update. A successful rollback suggests a compatibility or installation problem involving the newer driver, but does not establish that the newer driver is defective on all systems. ## Step 8: Reinstall the Device Driver Carefully When updating or rolling back the driver does not resolve Code 31, reinstalling the affected device may help Windows reconstruct its driver configuration. Before proceeding, make sure you can reinstall a compatible driver if Windows cannot restore one automatically. 1. Identify the exact affected device in Device Manager. 2. Obtain an official compatible driver package in advance when necessary. 3. Save your work and close applications using the device. 4. Right-click the affected device. 5. Select Uninstall device. 6. Review the confirmation dialog carefully. 7. Do not select an option to delete or remove the driver package unless you specifically intend to remove it and have verified that a suitable replacement is available. 8. Confirm Uninstall. 9. Restart Windows. 10. Allow Windows to detect the device and attempt driver installation. 11. If the driver is not restored automatically, install the verified manufacturer package. 12. Open Device Manager > Properties > General and verify the resulting status. Some devices can also be redetected through Device Manager > Action > Scan for hardware changes. The exact uninstall dialog varies by Windows version and device configuration. Uninstalling a device instance is not identical to deleting its driver package from the Driver Store. Do not casually uninstall boot-critical storage controllers, the only available network adapter, or essential system devices without an appropriate recovery method. Windows may reinstall the same problematic driver if it remains the preferred available package. If Code 31 returns, investigate the package and manufacturer guidance rather than repeatedly uninstalling it. Some devices require additional vendor software or installation procedures. Follow the manufacturer's documentation where applicable. ## Advanced Diagnosis with PnPUtil Windows includes PnPUtil, a command-line utility for inspecting Plug and Play devices and driver packages. The executable is normally located at %windir%\System32\pnputil.exe. PnPUtil device enumeration is supported from Windows 10 version 1903 onward. Verify the installed Windows version with winver. 1. Open Command Prompt as administrator. 2. Run pnputil /? to display the options supported by the installed Windows version. 3. Run pnputil /enum-devices /problem to list devices reporting problem codes. 4. Run pnputil /enum-devices /problem 31 to list devices currently reporting Code 31. 5. If the exact device instance path is known, 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 available starting with Windows 10 version 2004. 8. To list staged third-party driver packages, run pnputil /enum-drivers. 9. Compare the reported driver information with Device Manager > affected device > Properties > Driver. 10. Record the relevant driver provider, version, published INF name, and device instance identifier. These enumeration commands are read-only and do not remove drivers or change device configuration. PnPUtil /enum-drivers lists third-party driver packages rather than every built-in Windows driver. If the command reports no devices with Code 31, return to Device Manager and confirm whether the error is still present. Avoid using pnputil /delete-driver, /force, /disable-device, or other modification commands without identifying the exact device and understanding the consequences. Microsoft documents PnPUtil syntax and Windows version requirements at https://learn.microsoft.com/en-us/windows-hardware/drivers/devtest/pnputil-command-syntax. - pnputil /?: Displays supported PnPUtil commands. - pnputil /enum-devices /problem 31: Finds devices reporting Code 31. - pnputil /enum-devices /instanceid "DEVICE_INSTANCE_PATH": Inspects a specific device instance. - pnputil /enum-devices /instanceid "DEVICE_INSTANCE_PATH" /drivers: Displays matching and installed drivers on supported Windows versions. - pnputil /enum-drivers: Lists staged third-party driver packages. - winver: Displays the Windows version and OS build. - devmgmt.msc: Opens Device Manager. - Driver enumeration is safer than deleting or replacing packages without diagnosis. ## Check Windows Device Installation Logs Windows records information about device installation and driver setup in the SetupAPI device installation log. The default log location is %windir%\INF\setupapi.dev.log. 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 inspect the existing log without editing it. 5. Search for the affected device's hardware ID or device instance identifier. 6. Examine relevant installation entries and timestamps. 7. Look for recorded installation errors, driver selection problems, or package verification failures. 8. Compare those findings with Device Manager > affected device > Properties > Events. The SetupAPI log primarily records device installation operations. Code 31 may arise from a driver initialization failure that is not fully explained by this log. A missing installation error does not establish that the device driver is healthy. You can also press Win + R, enter eventvwr.msc, and inspect Windows Logs > System for relevant device or driver events. Some driver failures may be logged by additional diagnostic providers. Event availability varies by device, driver, and Windows configuration. Do not assume every warning or error in Event Viewer is related to Code 31. Microsoft documents the SetupAPI log at https://learn.microsoft.com/en-us/windows-hardware/drivers/install/setupapi-device-installation-log-entries. ## Code 31 on Wi-Fi, Ethernet, or Bluetooth Adapters Code 31 on a network or Bluetooth adapter can make connectivity unavailable even when Windows still detects the hardware. For a network adapter, open Device Manager > Network adapters and inspect the affected device's Properties > General tab. For Bluetooth devices, open Device Manager > Bluetooth when that category is available. Record the exact adapter model, hardware ID, and installed driver version. If the problem began after a driver update, check whether Roll Back Driver is available. If the adapter cannot provide internet access, use another trusted device to obtain the correct driver from the computer or adapter manufacturer's official support website. Transfer the verified driver package using a removable drive when necessary. Install the compatible driver according to the manufacturer's instructions and restart when requested. For an external USB Bluetooth or network adapter, check the physical USB connection and try another suitable port. Do not uninstall the only working network adapter or delete its driver package without obtaining a verified replacement first. Avoid generic registry modifications, network-stack resets, or unrelated firewall changes unless a specific diagnosis justifies them. A network adapter reporting Code 31 is primarily a device or driver initialization problem. Changing DNS settings or resetting browser preferences does not directly repair a driver that Windows cannot load. - Identify the adapter under Device Manager > Network adapters or Bluetooth. - Confirm Code 31 in Properties > General. - Record the hardware ID and installed driver version. - Check for a compatible driver through Windows Update when connectivity is available. - Use an official offline driver package when network access is unavailable. - Consider rollback if the error began after an update. - Check physical connections for removable adapters. - Preserve a recovery path before uninstalling network drivers. ## Safe vs. Unsafe Code 31 Troubleshooting The safest troubleshooting sequence starts with identifying the affected device and using supported driver-management tools. Avoid instructions that attempt to repair all Device Manager errors through unrelated registry changes or automatic deletion of driver files. - Safe: Confirming Code 31 under Device Manager > Properties > General. - Safe: Recording hardware IDs, driver versions, and Windows build information. - Safe: Restarting Windows and rechecking device status. - Safe: Inspecting available driver updates through Windows Update. - Generally safe: Installing a compatible driver obtained from the official manufacturer. - Conditionally safe: Rolling back to a previous working driver version. - Conditionally safe: Reinstalling a device when a recovery path and compatible driver are available. - Safe: Using read-only PnPUtil commands to inspect device and driver information. - Safe: Reviewing SetupAPI and Event Viewer logs without modifying them. - Unsafe: Installing drivers from untrusted download websites. - Unsafe: Disabling driver signature enforcement to force incompatible or unverified drivers. - Unsafe: Manually deleting files from the Windows Driver Store. - Unsafe: Running registry-cleaner scripts that promise to fix Code 31 automatically. - Unsafe: Removing critical storage or network drivers without recovery preparation. - Unsafe: Forcing removal of driver packages that Windows reports as being in use. - Not recommended: Assuming Code 31 always indicates permanent hardware failure. - Not recommended: Repeatedly reinstalling the same driver without investigating the cause. ## Code 31 vs. Code 10, Code 28, and Code 43 Device Manager uses different problem codes to describe failures at different stages of device installation and initialization. Code 31 corresponds to CM_PROB_FAILED_ADD. It indicates that the device could not be added successfully to the device stack, including cases where the function driver's AddDevice routine returned an error. Code 10 corresponds to CM_PROB_FAILED_START. It indicates a failure during the device-start process. Code 28 corresponds to CM_PROB_FAILED_INSTALL. It indicates that device driver installation did not complete successfully and a working driver was not selected. Code 43 corresponds to CM_PROB_FAILED_POST_START. It indicates a device problem reported after the start stage. These codes may appear on similar hardware, but their technical meanings differ. Always inspect Device Manager > affected device > Properties > General to verify the exact code before selecting a repair procedure. Microsoft's technical reference is available at https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/device-manager-problem-codes. - Code 31: Windows could not add the device successfully to its device stack. - Code 10: The device failed to start. - Code 28: Device driver installation failed or no working driver was selected. - Code 43: A problem was reported after the device-start stage. - The same device can encounter different error codes under different conditions. - The exact problem code is more useful than the warning symbol alone. ## What If Code 31 Still Appears? If Code 31 persists after installing a verified compatible driver, investigate whether the problem involves additional driver components, firmware, hardware, or Windows configuration. Record the computer model, affected device name, hardware ID, Windows build, installed driver version, and exact error message. Check the hardware manufacturer's support documentation for known driver compatibility problems. Review Settings > Windows Update > Update history if the problem began after an update. If the computer manufacturer provides an official diagnostic utility for the affected hardware, follow its documented instructions. For external peripherals, test another suitable port or cable where applicable. Testing a removable device on another compatible computer may help distinguish device-specific problems from issues on the original Windows installation. If multiple unrelated devices fail after the same system change, investigate that change before independently reinstalling every driver. Do not edit device class registry filters, driver service entries, or protected Windows files without a documented diagnosis specific to the affected hardware. For company-managed computers, consult the administrator before changing driver packages, firmware, or security settings. For critical storage devices, preserve important data and seek qualified assistance when necessary. A persistent Code 31 error does not guarantee a software-only solution. Some failures require manufacturer support or hardware service. Reinstalling Windows should not be the first response to a single Device Manager Code 31 error. ## Key Takeaways and Related Guides Device Manager Code 31 means Windows cannot load the drivers required for a hardware device because the device initialization process has failed. The internal problem identifier is CM_PROB_FAILED_ADD, which is distinct from the Code 10 device-start failure. Begin by recording the error message, Windows build, hardware ID, and driver version. Try a normal Windows restart, then check Windows Update and Device Manager for compatible driver updates. If the error began after an update, consider rolling back to a previously working driver. Use an official manufacturer driver when Windows does not provide an appropriate package. Reinstall the device only when you have a suitable replacement driver and an appropriate recovery method. Use PnPUtil and Windows logs for additional diagnosis without making unnecessary system changes. Avoid unverified drivers, forced driver deletion, registry-cleaner shortcuts, and disabling Windows security protections. Microsoft's official Code 31 technical documentation: https://learn.microsoft.com/en-us/windows-hardware/drivers/install/cm-prob-failed-add. Microsoft's Device Manager error guidance: https://support.microsoft.com/en-us/windows/hardware/drivers/error-codes-in-device-manager-in-windows. Microsoft's driver update and reinstall instructions: https://support.microsoft.com/en-us/windows/hardware/drivers/update-drivers-through-device-manager-in-windows. Microsoft's PnPUtil command reference: https://learn.microsoft.com/en-us/windows-hardware/drivers/devtest/pnputil-command-syntax. - Code 31 identifies a driver-loading and device-initialization failure. - It does not automatically mean the hardware is permanently damaged. - Check Device Manager > Properties > General for the exact error. - Record hardware IDs and installed driver details before modifying anything. - Prefer Windows Update and official manufacturer drivers. - Roll back recent driver updates when appropriate. - Use driver reinstallation only with a recovery method available. - Avoid dangerous registry edits and forced driver removal. - Investigate device-specific hardware or software issues when the error persists. Related: - [Understand what happens when Windows cannot find a suitable driver](https://raincleaner.eu/guides/device-manager-code-28-driver-not-installed) - [Identify your hardware and find a compatible driver](https://raincleaner.eu/guides/find-driver-by-hardware-id-windows) - [Follow a safer process for updating Windows drivers](https://raincleaner.eu/guides/how-to-update-drivers-windows-11) - [Learn how to restore an earlier working driver version](https://raincleaner.eu/guides/rollback-driver-update-windows-11) 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 31 mean? Code 31 means Windows cannot load the drivers required for a device to work properly. Its internal problem identifier is CM_PROB_FAILED_ADD, which indicates a failure while adding the device to the Windows device stack. How do I fix Code 31 in Windows 11? Restart Windows and confirm the error in Device Manager > affected device > Properties > General. Then check Windows Update, update the driver using Device Manager, or install a verified compatible package from the hardware manufacturer. Is Code 31 caused by a missing driver? Not necessarily. Code 31 indicates a device initialization failure involving required drivers, while Code 28 more specifically indicates that driver installation failed or no working driver was selected. An incompatible or malfunctioning installed driver can also be involved in Code 31. Can I uninstall and reinstall a device showing Code 31? Yes, reinstalling the affected device through Device Manager may help when driver updating and rollback have not resolved the issue. Make sure a compatible driver and a recovery method are available, particularly for network adapters and critical system devices. Does Code 31 mean my hardware is broken? No, Code 31 does not automatically prove hardware failure. The problem may involve driver compatibility, installation, or device configuration, although hardware issues remain possible if appropriate software troubleshooting does not resolve the error. ## 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 52 — Understand Windows driver signature errors, identify affected devices, inspect signing information, and restore hardware functionality without disabling Windows security protections.](https://raincleaner.eu/guides/device-manager-code-52-driver-signature-error) - [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)