Choose by the evidence and timing
Update when an official supported package addresses a specific need; roll back when a new failure closely follows an update and Windows has an earlier version available; reinstall only when official troubleshooting or a known damaged installation justifies that extra disruption. Device Manager offers controls, not a diagnosis.
This applies to Windows 11 and supported Windows 10 devices. Record the installed version and current status, identify the exact model, and protect access to the PC before changing network, display, storage, or input devices. Administrator permission may be required.
Make a single reversible decision
For example, if a USB adapter stopped connecting immediately after yesterday's change, a rollback may be more informative than installing a third candidate. If it never worked on this Windows release, a supported model-specific package and a connection check are better first steps.
- Read Properties → General status and Properties → Driver provider and version; record when the symptom began.
- For a documented compatible fix, use Windows Update or the manufacturer's supported installer; Device Manager can browse to a maker-provided driver folder.
- For a new post-update issue, use Properties → Driver → Roll Back Driver only if it is available, then restart when prompted and retest.
- If official guidance specifically recommends reinstallation, secure the compatible package and fallback first, follow that device's instructions, and verify each function afterward.
When a button is unavailable or no action helps
A grey rollback button can mean no previous version is stored. An update search saying the best driver is installed covers its own search sources, not every vendor release. Reinstalling does not repair a broken cable, failed component, or unsupported hardware.
Do not remove the only working storage or input controller to make a menu option appear. If the device becomes inaccessible, use official Windows or manufacturer recovery guidance. The parent guide and warning-icons sibling help return to the evidence before choosing another intervention.
Example: distinguish a regression from a long-standing fault
If an audio device worked yesterday and stopped immediately after a specific driver installation, the previous version is a useful comparison. Check output selection first, then consider a rollback if Windows offers it. If the same audio device has never been detected since a hardware replacement, rolling back an unrelated package has little diagnostic value; confirm the device model, connections, and supported software instead.
If you decide a documented reinstall is necessary, keep a compatible installer and a record of which device you intend to change. Reinstallation is not a bulk clean-up operation. Test the speaker or microphone path after the change and compare the result with the baseline. A normal Device Manager status with silence may indicate the wrong output endpoint rather than a corrupt driver, so avoid repeating the reinstall without new evidence.