No Sound in Windows 11: Output Device, Volume Mixer, Services, Drivers, Enhancements, and Hardware Troubleshooting

Treat “no sound” as a routing problem until the evidence points somewhere else. Open Settings > System > Sound and look under Output. Select the speakers, wired headphones, USB interface, dock, monitor, TV, or other playback device that should actually receive audio, then make sure the master volume is not muted. Microsoft’s current no-sound guidance starts with this output selection because Windows can keep several playback endpoints available at the same time.

Use a known Windows system sound or a local media file while you test. If one output works but another is silent, the Windows audio stack is at least partly functional and the problem is likely limited to that endpoint, cable, display path, driver, or device. If every output is silent, continue through the system-wide checks below instead of repeatedly changing one pair of headphones or speakers.

Windows 11 can mute an individual application or route it to a different output from the system default. Go to Settings > System > Sound > Volume mixer and check the affected application’s volume and output device. Microsoft specifically documents per-app volume and output-device selection as causes of app audio failing while system sounds still work.

This branch matters after connecting HDMI or DisplayPort monitors, USB audio devices, docks, capture hardware, or several headsets. An application may still be targeting an endpoint that is disconnected or no longer intended. Correct the app route, then restart the application if it does not immediately follow the new device choice. If every application is silent, move on to endpoint detection and the Windows audio path.

If the intended speakers or headphones do not appear at all under Sound > Output, treat that as a device-detection problem rather than a volume problem. Microsoft notes that missing audio outputs can be caused by a driver that is missing, outdated, disabled, corrupted, or not loading correctly. Restart Windows once, then check Device Manager for the audio device and any warning state before making broader changes.

Also inspect the physical path. For 3.5 mm analog audio, verify the correct jack and any headset splitter required by the PC or device. For USB audio, try a direct known-good USB port rather than an unverified hub. For HDMI or DisplayPort audio, remember that sound is sent through the GPU/display connection and the monitor or TV must expose a playback endpoint and route it to built-in speakers or its own audio output. A detected monitor does not guarantee that the monitor itself has speakers.

If multiple outputs fail at once, audio disappears after sleep or an update, or the devices remain visible but playback is broadly broken, restart the supported Windows audio services before changing drivers. Microsoft documents restarting Windows Audio and Windows Audio Endpoint Builder as a recovery step for audio failures.

Open Services by running services.msc, restart Windows Audio, then restart Windows Audio Endpoint Builder and test again. Do not disable these services, change unrelated service startup modes, or apply generic “debloat” service lists as an audio fix. A service restart is a bounded diagnostic step; if one endpoint alone remains broken afterward, return to that endpoint’s driver, cable, connection, or hardware path.

Audio enhancements and an unsuitable default format can cause playback or quality problems on some devices. Microsoft’s current support guidance recommends turning audio enhancements off and testing a different default format when normal routing is already correct but sound remains absent, distorted, crackling, or otherwise abnormal.

Change one setting at a time under the affected output device in Settings > System > Sound, then retest the same known audio source. Do not copy an arbitrary sample-rate or bit-depth value from another PC as a universal fix. Supported formats depend on the device and driver. If disabling enhancements immediately restores playback, leave the device in the working state and update the OEM audio package before assuming Windows itself is defective.

Move to the driver branch when Device Manager shows an error, the output disappeared after an update, the failure began immediately after a driver change, or supported routing and service checks did not restore playback. Microsoft recommends checking Windows Update and Device Manager for audio-driver updates and documents uninstalling the audio device and restarting Windows so the driver can be reinstalled when the installation may be corrupted.

Prefer Windows Update or the supported PC, motherboard, GPU, dock, USB-interface, or audio-device manufacturer package. Avoid third-party driver-updater sites and random driver archives. If the problem began immediately after a known driver update and a rollback option is available, use the existing Core Tech Tips Windows 11 driver-rollback guide rather than mixing rollback instructions into this page.

Microsoft currently directs Windows 11 users to the automated audio troubleshooter in the Get Help app for no-sound problems. It is reasonable after the basic output, mixer, detection, service, enhancement, and driver checks because it can inspect common Windows audio configuration without requiring registry edits or a system reset.

Do not treat a full Windows reset, random registry modification, BIOS flashing, or disabling unrelated services as a first-line sound fix. Those actions have a much wider blast radius than the symptom justifies. If the troubleshooter identifies a specific device or driver problem, follow that evidence; if it finds nothing, use hardware isolation rather than escalating blindly.

Test the same speakers or wired headphones on another known-good device when possible, and test a second known-good output device on the affected PC. Swap only one cable, port, dock, or adapter at a time. For digital display audio, test another HDMI or DisplayPort input or a direct GPU-to-display connection if a dock, KVM, receiver, or adapter is in the path. This distinguishes a Windows configuration problem from a failed transducer, cable, connector, display, USB device, or intermediate link.

If several known-good outputs fail only on this Windows 11 PC, the common Windows, driver, controller, or motherboard path deserves more attention. If one speaker set or headset is silent on multiple hosts, the playback hardware is more likely at fault. For Bluetooth-specific cases, use the dedicated Bluetooth-headphones-no-sound guide because pairing state, profiles, multipoint behavior, and Bluetooth-adapter drivers add failure modes that are intentionally outside this general playback page. Microphone/input failures likewise belong in the separate Windows 11 microphone troubleshooting guide.