The short answer
If sound stopped after a specific driver update, reverse that one change before replacing unrelated components. Confirm the output has not simply switched, record the affected device and version, then check whether Device Manager offers rollback. If not, use an exact supported package from the manufacturer.
When recovery is appropriate
These Windows 11 steps apply when you have a plausible before-and-after link between a driver change and a new playback or capture failure. They do not establish that every post-update sound problem was caused by an audio driver. Windows updates can also change defaults, privacy permissions or application behavior.
Before touching a controller, check the selected output and input again. A graphics update may affect sound through HDMI; a Bluetooth adapter update may affect a wireless headset. The internal sound chip's package is not a universal repair for every audio destination.
Preserve a known-good route
Record the PC or external device's exact model, Windows version, controller name, driver provider and version, update timing and symptom. Download a compatible previously working package from an official support page if available. Keep a second way to hear or communicate, such as a tested wired or USB device, when sound is important for work.
Save files and ensure you can restart and sign in. If manufacturer instructions specify paired audio components or a particular install order, follow those instructions rather than removing components individually. Administrator access may be needed to change drivers.
Trace which component actually changed
Imagine sound from an HDMI television stopped after installing a graphics package. The laptop's analog speakers still play. Before rolling back the laptop sound codec, check that the television supports the expected audio output, select its endpoint and inspect the graphics/display-audio component that changed. A monitor or television muted at its own controls would not be fixed by reverting that component either.
Now imagine the opposite: laptop speakers and the 3.5 mm jack stopped together after an internal audio package update, but a USB headset remains usable. That pattern makes the internal controller's version and the laptop maker's supported audio components a more defensible recovery target. The USB device remains a valuable communication fallback while making the change.
Recovery is not a command to return every version to an earlier date. Work from an identified device and a reproducible before-and-after test. Otherwise a successful restart may be mistaken for a successful rollback while the actual cause was simply a switched output.
Try the narrowest reversal first
In Device Manager find the identified device, open Properties > Driver and check Roll Back Driver. This button is unavailable if Windows has no previous driver for that device. Do not assume the absence of rollback means the update succeeded or failed.
- Recheck Sound settings and select the intended output or input; test at low volume.
- Identify the changed controller and note its provider and version before editing it.
- If Roll Back Driver is available, follow the prompts for that one device and restart when requested.
- Test playback, recording, jacks and the original app; if still broken, inspect the result before considering reinstall.
Caution: Do not uninstall every device under Audio inputs and outputs or Sound, video and game controllers as a blanket first step.
When rollback is unavailable
Use the precise model's official support package or documented Windows Update path. Follow the vendor's reinstall instructions, including any prerequisites. If the installer reports incompatible hardware, stop; forcing a package or disabling signature protection is not a recovery method.
Where manufacturer or Microsoft instructions specifically call for uninstalling an affected device, identify it carefully and ensure a recovery package is accessible first. A reboot may restore a basic Windows driver but may not restore the maker's extensions. Change only the device involved and retain a record of the result.
Check what recovered and what did not
After restart, test a local sound, a brief recording, headphones or monitor audio if those were affected, and the app where the symptom began. If one endpoint returns but another fails, investigate that separate path rather than declaring the whole audio system fixed.
If the device repeatedly disappears, fails a maker diagnostic, or remains silent across multiple known-good outputs despite a supported installation, contact the computer or device manufacturer. Further package swaps may conceal a port, speaker or controller fault.
Choose between rollback, reinstall and support
Rollback is appropriate only when an older version is available for the implicated device. An official reinstall may be more suitable when a package is damaged, a vendor requires coordinated components, or rollback is unavailable. If Windows offers only basic audio after reinstall, consult the exact-model support instructions rather than forcing a similar model's extensions.
A repeated disappearance across restarts, an obviously loose connector or a device that fails a manufacturer's hardware test is a reason to seek official support. Explain what you tried, which endpoints still work and which package versions changed. This record lets support assess compatibility or service without asking you to repeat blind uninstall cycles.