Driver problem after Windows Update: update, roll back or reinstall the right device
Use timing and Device Manager status to choose between a newer driver, rollback and device-specific reinstall.
- Identify the exact device that stopped working.
- Open its Device Manager Properties and record the Device status message/code.
- Check Windows Update, including relevant optional driver updates.
- Use rollback only when the failure clearly followed a recent driver update.
What this problem usually means
Driver repair should be tied to a specific device and a clear timeline. Microsoft notes that rollback can be appropriate when a problem began after Windows Update, while current drivers can also arrive through Windows Update and Device Manager.
Work from the narrowest fix to the broader one.
Check for the current driver first
Low riskWhy this belongs here: A corrected driver may already be available through Windows Update or the device manufacturer.
- Open Settings > Windows Update and check for updates.
- Review Advanced options > Optional updates for relevant driver updates.
- If the PC manufacturer provides a model-specific driver, verify it matches the device and Windows version before installation.
Roll back when the new driver is the clear trigger
Medium riskWhy this belongs here: Rollback targets the recent driver change without resetting unrelated components.
- Open Device Manager and the affected device Properties.
- Open the Driver tab and choose Roll Back Driver if available.
- Restart Windows and retest the device.
Reinstall only the affected device driver when needed
Medium riskWhy this belongs here: A device-specific reinstall is narrower than broad driver-cleaner or system-reset approaches.
- Use the manufacturer’s instructions or Device Manager for the affected device only.
- Restart or scan for hardware changes as appropriate.
- Confirm the device no longer reports an error in Device Manager.
When this guide stops being the right path
If the device is physically absent, disabled in firmware, or reports a hardware-oriented code after a clean driver path, move to hardware/vendor diagnostics.
If the problem is still not fixed
Use the Device Manager error code as the next branch when one is present. Codes 10, 28, 31 and 43 have different meanings and should not be treated as interchangeable.
Sources reviewed for this page
Primary technical guidance is preferred. A source supports the scope stated here; it does not imply that every possible cause is covered.