A device stopped working after a Windows update
A missing, replaced or incompatible driver is one of the most common outcomes of a Windows update - the update can silently swap the manufacturer's driver for a generic or newer-but-incompatible one. Rollback is the fastest recovery.
Broke right after the September 2026 update? Check the live tracker of known update bugs first - USB audio and AMD Radeon are confirmed cases right now →Why this happens
- Windows Update replaced the vendor driver with its own catalog version.
- The update is incompatible with the installed driver version.
- Windows re-detected the device from scratch and its settings were lost.
Quick checks first
1Find the affected device
Win+X → Device Manager. Look for warning icons or the device missing from its section. Compare against what stopped working (sound → Sound controllers, Wi-Fi → Network adapters).
2Check Update history
Settings → Windows Update → Update history. Driver updates are listed separately - if a driver for your device was installed on the failure date, that's the prime suspect.
3Do a full shutdown once
Shift + Shut down (bypasses Fast Startup), wait ten seconds, power on. Some devices stay stuck in a half-initialized state after an update until a true cold boot.
If the device is still broken, the update most likely replaced or damaged its driver - the next step is to identify the device and restore a working driver version.
Fixing it manually
Roll back the driver
- Device Manager → the affected device → Properties → Driver tab → Roll Back Driver.
- Reboot and test. Rollback returns the previous driver that worked before the update.
Reinstall the manufacturer's version manually
- If rollback is unavailable: Properties → Details → Hardware Ids, copy the first value.
- Find the driver in our database - pick the version dated before the problematic update, matching your Windows version.
- Create a restore point and install it.
Stop Windows from re-breaking it
- Windows may reinstall the same problematic driver. If the issue recurs, note the driver version Windows keeps installing - sticking to a newer vendor version usually stops the cycle.
Know the exact device model?
Search the driver database by device name or Hardware ID and pick the version dated before the problematic update, matching your Windows version.
The affected device is identified in Device Manager by its section and warning icon; its Hardware ID (Properties → Details) pins down the exact hardware for a manual driver search.
Try for example: Realtek Audio · read the Hardware ID guide
Frequently asked questions
▸Is the driver always the cause when something breaks after an update?
No - updates can also change settings, services or power management. But the driver is the most common and the easiest cause to verify: if Roll Back Driver fixes it, it was the driver.
▸Can I check what the update broke without digging through Device Manager?
Device Manager is still the direct way, but two shortcuts narrow it down fast: Settings → Windows Update → Update history shows exactly which drivers the update replaced and when, and in Device Manager the affected device usually carries a yellow warning icon. Cross-reference the two and you have the culprit in a minute.