Troubleshooting peripheral recognition issues after Windows 11 updates

In this article, we've gathered and organized information scattered across Microsoft notes, community threads, and technical articles to provide you with a comprehensive guide. You'll find typical symptoms, confirmed causes, specific patches, and practical procedures to restore your computer to normal without wasting time trying things out blindly.

Common symptoms after updating Windows 11

The issues vary depending on the patch and hardware , but the most common ones include disappearing devices, driver startup errors, and intermittent crashes . These are the most frequent patterns:

• USB: Scanners that support the eSCL protocol stop connecting via USB after 24H2, which prevented even the update from being offered on many devices until patch KB5048667.
• Bluetooth and audio- Headphones not pairing or outputting sound after a crash; in some cases, audio devices appear but have no output. Problems have been reported on computers with Dirac Audio and the cridspapo.dll component.
• biometrics: fingerprint readers or facial recognition Windows Hello they disappear from Device administrator, especially after several cumulative updates in certain portable.
• Camera: apps that do not respond or close when using the built-in camera with object or face detection functions activated in 24H2.
• Mouse: Loss of pointer within Chromium-based applications (browsers like Chrome or Edge).
• Keyboard at login: keyboard that works on BIOS but does not respond on the password screen of Windows until the port is changed or a patch is rolled back.
• File Browser: The explorer.exe process continues in the background but the window does not open or hangs after the update KB5051987.
• NDI streaming: When using NDI to output audio and video with tools such as OBS or NDI Tools, stuttering, desyncing, and latency occur after installing the August 2025 update KB5063878.
• Desktop Personalization: Live wallpaper apps leave invisible icons, fail to preview, or fail to launch in 24H2 until you update or uninstall them to complete the installation.
• UAC: Standard users receive unexpected warnings when repairing MSIs, launching apps such as certain Autodesk apps, or running msiexec fu, due to a security patch released in August 2025 (CVE 2025 50173).

Common causes confirmed by Microsoft and manufacturers

The triggers aren't always the same. Sometimes they're driver incompatibilities , other times security changes or cumulative errors that are later corrected. This is the most relevant information that has been documented:

• eSCL USB Scanners: 24H2 incompatibility with eSCL devices, including standalone and multifunction scanners. Microsoft released the block by releasing KB5048667 and recommends not forcing the update using the installation tools until the fix is ​​complete. After installing this update, it may take up to 48 hours for 24H2 to be available.
• Audio Dirac/cridspapo.dllOn certain devices, audio output on built-in and Bluetooth speakers is lost after 24 hours, and apps fail to detect devices. A compatibility hold has been applied until the manufacturer releases a fixed driver.
• Intel Smart Sound Technology (SST)- On 11th Gen Intel processors with IntcAudioBus.sys driver version 10.29.0.5152 or 10.30.0.5152, 24H2 may cause blue screens. You must update to 10.29.00.5714 or 10.30.00.5714 (or later) before upgrading to 24H2.
• sprotect.sys driver: Conflict between 24H2 and SenseShield's sprotect.sys, which can be introduced with security software. The update is prevented until a fix is ​​available.
• UAC hardening on MSI repairs: The August 2025 security update (KB5063878) triggers administrator credential prompts for MSI repair operations on standard users, mitigable with KIR group policy in managed environments.
• NDI and RUDP transportAfter KB5063878, RUDP mode is experiencing crashes and stuttering. NDI recommends manually changing the receive mode to TCP or UDP.
• Installing with WUSA from shared foldersInstalling a .msu from a network path with multiple .msu files may fail with ERROR_BAD_PATHNAME as of KB5058499. The workaround is to copy the package locally and run it from there. A KIR rollback mitigates this for most users.
• CertEnroll Events: After KB5062660 and later, event 57 is logged indicating that the Microsoft Pluton cryptographic provider failed to load. It is harmless and is gradually resolved with KB5064081.
• Wallpaper apps: cause desktop anomalies after 24H2. Windows may prompt you to uninstall before completing the installation or upgrade to a compatible version.
• Camera and Hello: In 24H2, using face/object detection on the built-in camera may cause apps to crash or prevent the use of Windows Hello on some models. A hold has been applied until fixed.

Real cases and compatibility retentions

Beyond this specific failure, Microsoft uses protective holds to prevent updates from reaching problematic computers. These holds are applied based on hardware or detected drivers and block the 24H2 offer in Windows Update.

• Holds for Dirac Audio cridspapo.dll, for Intel SST affected, for sprotect.sys and for wallpaper apps. On the page Windows Update You will see a notice that no action is required and a link for more information.
• For the USB issue with eSCL scanners, the block was lifted upon posting KB5048667After installing it, it may take about 24 hours for the 2H48 offer to appear.
• It is recommended to avoid using the Setup Wizard. Windows 11 and the Media Creation Tool for do not force an update which is being held for security.

Step-by-step resolution guide

We offer a practical roadmap that covers everything from the basics to specific documented cases. You don't need to do it all at once : try it out in stages until you restore normal operation.

1. Windows Troubleshooters and Targeted Reboots

If you're using NDI and experiencing dropouts after updating, change the receive mode in your NDI tools to TCP or UDP instead of RUDP. This is the recommended workaround until a fix is ​​released for Windows.

2. Device Manager: Uninstall and Reinstall

When a device stops responding after a patch, sometimes simply reinstalling its driver is enough. Open Device Manager, locate the device (audio, microphone, Bluetooth, camera, or biometrics), and click Uninstall device. Restart your computer, disconnect and reconnect the device if it's external, and let Windows reinstall the driver.

For audio and microphone issues, both Microsoft support and community threads recommend this sequence. If that doesn't work , install the driver from your computer manufacturer's website and use dxdiag to diagnose audio problems.

3. Update critical drivers before 24H2

On systems with 11th generation Intel processors, check the Intel Smart Sound Technology driver in System Devices. If you see versions 10.29.0.5152 or 10.30.0.5152, update to 10.29.00.5714 or 10.30.00.5714 (or later) via Windows Update or from the OEM before upgrading to 24H2.

If your computer has Dirac Audio with the cridspapo.dll component or security software that installs sprotect.sys, wait for your manufacturer to release new drivers. Retention protects your computer in the meantime.

4. Install or uninstall key cumulatives

For the eSCL USB scanner issue, install KB5048667 and wait up to 48 hours for Windows to offer 24H2. Avoid forcing the installation with manual tools.

If File Explorer doesn't open or freezes after installing KB5051987, go to Settings, Windows Update, Update History, Uninstall updates, find the cumulative update, and remove it. Restart your computer to validate . If a patch installation gets stuck at 98 or 99 percent and then reverts, note the error code (for example, 0x800f0993, 0x800F081F, 0x80070032, 0xC004F211) and try again later or with a clean install.

In Bluetooth and cameras affected by KB5050009 , several users report that uninstalling that patch restored functionality while awaiting the fix.

5. Reset Windows Update components

If your update cache becomes bloated with a file larger than 8,6 GB that you can't delete, use a tool like Windows Update Reset to restore components. Download it, run it as administrator, and choose to restore Windows Update components . In some extreme cases, the only way to clear the cache was a clean installation.

6. System restore point

Windows creates restore points automatically, and you can also create them manually. Search Start for "create restore point," go to System Protection, click System Restore, and select a restore point from before the problematic update. This is a safe way to revert to a previous state that won't erase your data.

7. New user profile and Windows Hello

If biometrics stopped working or the Biometric Devices disappeared from the Device Manager, remove fingerprint and face authentication from Accounts > Sign-in Options, and reconfigure. If the problem persists , create a new local user, give it administrator privileges, and try setting up Windows Hello on that profile to rule out profile corruption.

8. Keyboard not working when logging in

When the keyboard responds in BIOS but not on the password screen, try connecting it to a rear USB 2.0 port, boot into Safe Mode from the recovery environment, and uninstall the latest cumulative update. Enable the on-screen keyboard to enter the password and refer to how to troubleshoot non-functional or misconfigured keys in Windows ; once in Safe Mode, reinstall the USB drivers and disable USB selective suspend in the power options.

Also check in the BIOS that Legacy USB/PS2 support is enabled and that there are no security options blocking peripherals at boot time . Avoid making drastic changes if you don't know what each setting does.

9. Installations from WSUS and WUSA

If you are an administrator and the August 2025 KB5063878 update failed due to WSUS error 0x80240069, Microsoft has fixed the service. Please resynchronize and approve the deployment. If you applied a KIR , it is no longer required in this case.

For manual installations with WUSA from a shared folder with multiple .msu files, copy the package locally before running it to avoid ERROR_BAD_PATHNAME. Rolling back known issues mitigates this issue for most unmanaged users.

10. Family Safety and browsers

If children unexpectedly close unsupported browsers and parental consent doesn't trigger, activity reporting is temporarily enabled. Microsoft included a fix in the July 2025 preview update KB5062660 and is gradually rolling it out.

11. Background and camera apps

If 24H2 is crashing due to background apps, update to a compatible version or uninstall them when prompted by Windows. You can complete the update and reinstall them afterward. For cameras that freeze apps with face detection, wait for a fix or temporarily disable those features.

Additional information and scope

Although we're mainly discussing modern input/output devices here, recognition problems also affect older peripherals like CD, DVD, and Blu-ray optical drives . Manufacturers provide specific diagnostic guides for Windows, and you should consult them if your drive stops appearing.

The issue extends to a wide variety of devices: Alienware, Inspiron, OptiPlex, Vostro, XPS, G series, and Latitude, as well as desktop and mobile workstations from various OEMs. Compatibility blocks are applied by model, driver, or device family, not just by brand.

Please note that some documentation in official communities may appear automatically translated, with some unusual expressions. The technical content , however, is valid and usually includes clear steps for testing.