Windows command guide
Restart Windows Audio Services with PowerShell
Not every sound problem means the speaker is broken or the driver must be reinstalled immediately. In many cases, the audio stack simply gets stuck after sleep, an update, a headset switch, or a crash in a media or communication app. Restarting the main audio services is one of the cleaner first steps before deeper driver work.
This guide is written around the specific symptom-command match for restart audio services, not as a generic dump of terminal lines. That makes the page more useful for real troubleshooting and reduces the chance of running the wrong repair step.
powershell -Command "Restart-Service Audiosrv,AudioEndpointBuilder -Force"
Best place to run it
Elevated PowerShell is the right execution context for this page. Because this repair touches protected Windows state, a normal unelevated shell can return misleading access errors or partial results.
Fast repair workflow
- Start from the exact symptom on this page: The speaker icon shows problems even though the device is connected
- Run the service or app repair line exactly as shown: powershell -Command "Restart-Service Audiosrv,AudioEndpointBuilder -Force".
- This workflow is tuned for this repair, so avoid mixing it with unrelated repair commands too early.
- Re-open the affected app, service, or feature and check whether the same component still fails.
- If the issue persists, check service state, dependencies, package integrity, or event logs before doing a broader repair.
Copyable wrapper script
Use this wrapper when you want the page command inside a clearer script block with start and finish prompts.
$ErrorActionPreference = "Continue"
Write-Host "Run this PowerShell block in an elevated window before trusting the result."
Write-Host "Starting targeted Windows repair step..."
powershell -Command "Restart-Service Audiosrv,AudioEndpointBuilder -Force"
Write-Host "`nReview the output above before moving to the next fix."
Verification commands after the repair
These follow-up commands help you check whether the repair actually changed the Windows state that matters, instead of assuming success from a single line.
Get-Service Audiosrv,AudioEndpointBuilder
What problem this command is trying to solve
This command targets temporary Windows audio failures where the operating system still knows sound hardware exists, but playback, switching, or detection is no longer behaving correctly.
- The speaker icon shows problems even though the device is connected.
- No sound comes out after sleep, wake, or a driver update.
- Audio devices vanish or fail to switch correctly between speakers, headset, and monitor output.
How the command works
The PowerShell command restarts the Windows Audio service and the Audio Endpoint Builder service. That refreshes the software layer responsible for device endpoints, playback routing, and audio session handling.
When it makes sense to run it
Use it when sound disappeared suddenly and you want to refresh the audio subsystem without rebooting the whole machine. It is especially useful during troubleshooting when you want a quick reset of services first.
Before you run this command
- Open an elevated Command Prompt or PowerShell window before running powershell -Command "Restart-Service Audiosrv,AudioEndpointBuilder -Force".
- Confirm that the symptom really matches this guide, especially if you are seeing signs such as: the speaker icon shows problems even though the device is connected.
- Identify the exact Windows component that is failing before you use powershell -Command "Restart-Service Audiosrv,AudioEndpointBuilder -Force", so you do not reset unrelated parts of the system.
What result to expect
After running powershell -Command "Restart-Service Audiosrv,AudioEndpointBuilder -Force", compare the result against the symptom that brought you here. The most useful checkpoint is whether the speaker icon shows problems even though the device is connected becomes less frequent, changes form, or produces a clearer error message. A command page is stronger when it helps you verify a real change instead of just assuming the line must have worked.
How to verify that it worked
The best verification step after powershell -Command "Restart-Service Audiosrv,AudioEndpointBuilder -Force" is to repeat the action that previously triggered the problem. If no sound comes out after sleep, wake, or a driver update still appears in exactly the same way, the command probably was not the whole answer and you should move to the next targeted check instead of assuming the page is finished.
Why administrator rights matter here
This command changes a Windows service, package, or built-in app component. Run it in an elevated shell so Windows can apply the repair instead of only returning an access or privilege error.
Before you run it
Restarting these services can briefly interrupt active meetings, recordings, games, or media playback. It will not fix every driver problem, hardware fault, or physical cable issue by itself.
When this is probably the wrong fix
This is not the right first fix for every generic crash. Use it when the failing part is a Windows service, built-in app package, indexing component, print queue, audio stack, or similar subsystem.
What to do if it does not help
If powershell -Command "Restart-Service Audiosrv,AudioEndpointBuilder -Force" does not improve the speaker icon shows problems even though the device is connected, move to the next repair step that matches the same symptom family instead of piling on random commands. The best follow-up depends on whether the failure is mainly about a Windows service, package, or built-in app component.
Frequently asked questions
Should I use powershell -Command "Restart-Service Audiosrv,AudioEndpointBuilder -Force" for this exact Windows symptom?
Use it when the behavior on your PC lines up with the repair target on this page: This command targets temporary Windows audio failures where the operating system still knows sound hardware exists, but playback, switching, or detection is no longer behaving correctly.
What should I check right after powershell -Command "Restart-Service Audiosrv,AudioEndpointBuilder -Force"?
Check whether the original trigger still reproduces the same failure. For this page, a useful checkpoint is whether the speaker icon shows problems even though the device is connected becomes less frequent, changes form, or points you toward a more specific next step.
When should I not rely on powershell -Command "Restart-Service Audiosrv,AudioEndpointBuilder -Force" alone?
This is not the right first fix for every generic crash. Use it when the failing part is a Windows service, built-in app package, indexing component, print queue, audio stack, or similar subsystem.