The short answer
Windows can roll back a driver only if a previous version remains available for the selected device. A greyed-out Roll Back Driver button is not a failure of the repair process; choose a compatible manufacturer package or another documented recovery path instead.
Target the changed hardware
On Windows 11, first confirm that Sound settings did not switch to a different endpoint. Determine whether the update concerned the PC sound controller, a USB interface, Bluetooth adapter or graphics/display audio. Rollback on the wrong device will not address the observed path. Record the current version and the update timing.
What the rollback control does not establish
The button applies to the selected device entry, not to all computer sound. A laptop may have an internal codec plus a graphics audio function for a display and a separate Bluetooth adapter. Rolling back the codec will not necessarily affect a silent HDMI television or disconnected wireless headset. Confirm the path with a second playback test before choosing the device.
If the button is enabled, that means Windows has a previous driver version for the selected device. It does not mean that the previous version is guaranteed to solve a cable fault or an app route. Note the current version so that you can compare it after restarting. If sound worsens, use the manufacturer's supported instructions to revisit the change.
An unavailable button does not indicate a corrupt installation. It often simply means no prior package is retained. Search the exact PC or accessory model's official support listing for a compatible version. Avoid unofficial archives claiming to unlock rollback; compatibility and provenance are more important than a version number alone.
Inspect the Driver tab
Open Device Manager, expand the relevant device category, and inspect Properties > Driver for the device actually changed. Roll Back Driver may ask why you are reverting and may require administrator permission. Save your work and make sure a restart is possible.
- Record current output/input choice and the controller's provider and version.
- Open Properties > Driver for that controller and check whether Roll Back Driver is available.
- If available, follow the prompts and restart as requested; do not roll back unrelated devices.
- Retest low-volume playback, microphone capture if relevant and the original symptom.
Caution: If you rely on audio for accessibility or urgent communication, prepare a tested alternative before a driver change.
If rollback does not restore sound
If the button is unavailable, Windows may have no older version saved; check the exact model's official support page. If rollback completes but the endpoint remains silent, inspect routing and physical connections before further changes. Note the new driver version after restart.
If the controller is repeatedly missing or official installation rejects the hardware, contact the device maker for diagnosis. Do not bypass signature validation or force a package for a different model.