Match the symptom before changing settings
| What you observe | Where to focus |
|---|---|
| Driver date or provider changed with the failure | Compare rollback or reinstall the known-good OEM package |
| Several related devices failed together | Repair their chipset, USB, PCI or wireless parent |
| The device works after restart but fails after sleep | Investigate firmware, power state and platform drivers |
| The hardware fails on another PC too | Treat it as hardware rather than an update problem |
Diagnose device failed after update before replacing drivers
Check whether the device is now missing, disabled, or showing a new Device Manager code. A changed device state after update helps distinguish driver regression from hardware failure.
Verify the device and its cable/port still work before blaming the update. If possible, test the device on another computer or use a known-good replacement on this PC.
Use the symptom evidence to select the correct layer. “Driver date or provider changed with the failure” points toward compare rollback or reinstall the known-good oem package, while “Several related devices failed together” suggests repair their chipset, usb, pci or wireless parent. Also note what changed immediately before the failure: a Windows update, driver package, new dock, BIOS update, sleep or hibernation cycle, physical impact, liquid exposure or installation of device-management software.
If the device broke immediately after a driver update, test the previous supported driver from the exact manufacturer. Keep the known-good package before removing the new one.
Restart Windows, disconnect unrelated devices, and retest before uninstalling the update. A one-time post-update enumeration glitch can clear after a full restart.
The remaining symptoms also narrow the search: “The device works after restart but fails after sleep” means you should investigate firmware, power state and platform drivers, while “The hardware fails on another PC too” means you should treat it as hardware rather than an update problem. After each repair, verify the original function rather than accepting a successful installer message. A package can finish correctly while Windows still loads another driver or the hardware remains unavailable.
Confirm what the update actually changed
Open Settings > Windows Update > Update history and note the installation time and type. In Device Manager, record the device's current provider, version, date and error code. A Windows quality update, optional driver update and manufacturer utility update require different rollback paths.
Restart once and test the device in a second app, port or computer. Updates often coincide with an ordinary cable, battery or hardware failure. Preserving this evidence prevents removal of a security update when only one replaceable driver needs attention.
1Try the narrowest repair first
- Use Roll Back Driver if the device driver changed.
- Install the exact current OEM package if rollback is unavailable.
- Repair the failed parent controller before its child devices.
2Compare Windows recovery options
- Use System Restore when a suitable restore point exists.
- Remove a recent update only when evidence links it to the fault.
- Pause repeated driver delivery temporarily while confirming the fix.
Reinstall without losing the recovery path
Download the correct package and create a restore point before uninstalling. Remove only the affected device, restart and allow Windows to redetect it. Install the saved OEM package when Windows restores a generic driver without the required features.
For network, keyboard or storage controllers, make sure you have an alternate input, network path or recovery media. Removing a critical driver without preparation can make the repair harder than the original failure.
Escalate from driver rollback to system recovery
If several Windows components fail and system files may be damaged, run DISM and then SFC from an elevated terminal. Use an in-place repair installation only after targeted driver and component repairs fail; it is not the first step for one faulty USB accessory.
Report reproducible update conflicts to the PC or device manufacturer with the Windows build, update number, hardware ID and driver versions. That evidence supports a corrected package and is far more useful than disabling updates permanently.
Verify the repair before making more changes
Restart Windows—not only the affected app—and confirm that the device works after restart, sleep and the normal workload that previously triggered the failure. Check Device Manager again: the device should remain present without a warning icon, and Device status should say it is working properly.
After rollback, reinstall, or corrective update, test the same device function, restart Windows, and confirm the fix survives sleep/wake or reconnect.
Technical order checked against Microsoft's current driver update, rollback and reinstall guidance. Device-specific menus and driver availability vary by manufacturer.
Frequently asked questions
Should I uninstall the Windows update immediately?
Not first. Confirm the changed driver and device status, then use the narrowest rollback that matches the evidence.
What if Roll Back Driver is greyed out?
Install the previous supported OEM package manually or use System Restore when an appropriate restore point exists.
Why does the device fail only after sleep?
The driver, firmware or platform power state may not resume correctly. Update the exact OEM platform stack and compare.