Sound stopped working after an update
When sound stops after an update, the update may have changed the default output, reset an application route, disabled an enhancement, or replaced a device component. It may also have exposed a pre-existing connection problem. Record what changed and whether the audio endpoint is still visible before trying another update. The absence of sound alone does not prove that the newest driver is defective.
Protect active work before recovery: calls, broadcasts, recordings, and audio editing sessions can be interrupted by a restart, device removal, or profile change. Check the update history and the computer maker's support information. Use rollback when the supported evidence points to the changed driver, and avoid a blanket system reset that discards unrelated settings.
In this guide
- Key Takeaways
- Record the change and current state
- Use supported recovery
- Validate routing after recovery
- Common Questions
No sound and audio output troubleshooting Topics
Key Takeaways
- 1
Check whether the update changed the selected output or application route.
- 2
Compare device status and driver details before and after the change.
- 3
Protect calls and recordings before restarting or rolling back audio software.
- 4
Use a supported rollback or model-specific package, not an indiscriminate reset.
Record the change and current state
Note whether the change was a Windows update, a driver installation, a computer-maker utility, or a firmware operation. Open sound settings and identify the active output and input, then check per-application routing. In Device Manager, record the audio device name, driver provider, and status. If the endpoint is present and a system sound works, focus on routing or application settings before rolling anything back.
- Write down the update name, time, affected endpoint, and exact symptom.
- Check system output, input, application routing, and mute state.
- Save custom audio settings and close live calls or recordings before recovery.
Use supported recovery
If the device disappeared or reports an error immediately after a driver change, use Device Manager's supported rollback when available. If the system update has its own documented removal or recovery option, read its consequences before proceeding. When rollback is unavailable, obtain the exact-model package from the computer maker. Do not force an older package, disable security controls, or remove every audio entry simply to make the list look clean.
- Choose the recovery action that matches the identified change.
- Keep the computer connected to power and do not interrupt an active recovery.
- Restart only when the supported procedure requests it.
Validate routing after recovery
Test the intended speakers, headset, microphone, and any required display output separately. Reopen the application that originally failed and select its endpoint again; an update can leave the app attached to a removed device. Check enhancements only after basic playback works. If sound is restored but a specialized control is missing, treat the control component as a separate compatibility question and retain the successful driver details.
Common Questions
Should I immediately uninstall the update?
Not before checking output selection, application routing, and device status. If the endpoint works, uninstalling an update may add risk. Use rollback only when the change and symptom are connected and supported recovery is available.
Why did my default speaker change after an update?
Updates, display connections, docks, and newly detected devices can change the default endpoint. Select the intended output and correct application routing before changing the audio package.