Microsoft shipped Windows 11 Build 29613 to Insiders this week, packing a substantial overhaul of the operating system’s audio settings. The update introduces per‑device activity meters, a streamlined default‑device selector, input/output filtering, and the ability to hide disconnected hardware—all within the Settings app. For anyone who has wrestled with Windows’ labyrinthine Sound control panel or guessed which microphone is active during a call, these changes feel overdue.

Three years after Windows 11 launched, the audio experience remains a curious mix of legacy Control Panel applets and modern Settings pages. Power users still dive into the classic Sound dialog to set default communication devices or disable unused outputs, while casual users often get lost in a sea of HDMI entries and dormant virtual cables. Build 29613.1000, currently rolling out to the Dev and Canary channels, aims to collapse those worlds into a single pane that is both approachable and precise.

A unified Default Devices hub

The most practical addition is a dedicated section for managing default audio devices. Previously, changing the default speaker or microphone required clicking through multiple menus or right‑clicking an entry in the legacy Sound panel. The new Settings page surfaces a clear “Default devices” card where users can assign a preferred output (speakers, headset, USB DAC) and input (internal mic, external mic, line‑in) with a single tap. The selection applies globally, though individual apps retain the ability to override it via Windows’ per‑app volume mixer, which remains unchanged.

The card also respects the concept of “default communication device,” a distinction that had been hidden in the old dialog for years. Video‑conferencing apps normally latch onto the communication default, so users can now set their gaming headset as the main output while keeping a webcam microphone as the default for calls—without ever opening the Control Panel. The settings sync instantly, and any application that was using a now‑unselected device gracefully migrates to the new default, a behavior that eliminates the audio‑dead‑air moment that often follows a headset swap.

Real‑time activity meters

Alongside the default‑device controls, every audio endpoint now displays a live activity meter. These miniature bars respond to actual sound levels: they spike when music plays, flicker with voice, and sit flat when the device is idle. The meters serve two purposes. First, they provide instant visual confirmation of which device is actively rendering or capturing audio. Second, they help troubleshoot routing issues—if a user expects sound from a Bluetooth speaker but the meter for the internal speakers is dancing, the culprit is obvious without digging into system trays or advanced diagnostics.

The meters update at roughly 10 Hz, a rate that is fast enough to convey rhythm but not so frantic that it becomes distracting. In testing, the meter reacts within roughly 100 ms of a signal change, making it suitable for live audio confidence monitoring during content creation. For accessibility, the meter also exposes a textual “level” label when hovered over, though a proper screen‑reader integration has yet to be documented.

Input and output filtering

Build 29613 introduces a filter bar at the top of both the output and input device lists. By default, the list shows every endpoint Windows detects, which can balloon when virtual audio devices (Voicemeeter, Nvidia Broadcast, OBS virtual camera, etc.) are installed. Tapping the filter button reveals a dropdown with categories such as “Speakers,” “Headphones,” “Microphones,” “Line‑in,” and “All.” Selecting a category instantly narrows the view.

The filter logic is intelligent enough to group typical Bluetooth headsets under “Headphones” even when they expose both a stereo output profile and a hands‑free profile, a characteristic that in the past could double the apparent device count. Microsoft has not disclosed the exact algorithm, but early hands‑on reports suggest the filter leans on the audio endpoint’s device class descriptor. If a device descriptor is ambiguous, it falls back to the friendly name, so “Jabra Evolve2 85” appears under both Speakers and Headphones when appropriate.

Show or hide disabled devices

A persistent annoyance in Windows audio has been the clutter of disabled or disconnected endpoints. Virtual audio cables, unused monitor speakers, and temporarily disconnected USB DACs often clog the selection lists, forcing users to scroll through debris to find active hardware. Build 29613 ships a toggle—“Show disabled devices”—that is off by default. With the toggle off, only devices that are currently plugged in, powered on, and not manually disabled by the user appear. With the toggle on, everything reappears, including greyed‑out entries for hardware that was used in the past.

This approach mirrors the “Show hidden devices” option in Device Manager but is much more discoverable. It also pairs elegantly with the filtering system: a user can filter for “Headphones” and still decide whether to see the disabled pair that sits in a drawer. The toggle is sticky across reboots, so once a user cleans up their view, it stays that way.

Why these changes matter now

Windows’ audio stack has been reliable for years, but its user interface froze in time. The Win32 Sound control panel dates back to Windows Vista, and while it is functional, it breaks the design language of Windows 11 and intimidates non‑technical users. Microsoft began migrating parts of audio settings to the modern Settings app in 2021, but progress stalled after a basic output-selector and volume-per-app mixer arrived in version 22H2. Build 29613 represents the most significant audio‑UX refresh since that milestone, and it suggests the company is finally retiring the legacy dialog piece by piece.

The timing aligns with broader industry trends. Remote and hybrid work have made audio management a daily ritual for hundreds of millions of people. Users constantly switch between a headset for meetings, desktop speakers for music, and a webcam mic for quick chats. The previous workflow—right‑click the speaker icon, select “Sounds,” navigate the Playback tab, find the device, click “Set Default,” close the window—felt archaic next to the fluidity of macOS or ChromeOS audio menus. The new Settings page reduces that ritual to two clicks and offers visual feedback at every step.

Insider channels and rollout

Microsoft released Build 29613.1000 to the Dev and Canary channels on March 4, 2024, according to the official Insider blog. The build is part of the active development branch (nicknamed “Gallium” internally), meaning its features are not yet tied to a specific public release version. As with all Canary builds, the code could graduate to the Beta channel after several weeks of refinement or could be scrapped if it generates critical bugs.

Insiders who wish to try the new audio settings can trigger the feature via the usual random rollout mechanism: after installing the build, a restart may enable the flag, though some users may need to run the ViVeTool command vivetool /enable /id:39652022 to force it. Microsoft frequently uses staggered rollouts even inside Dev and Canary, so patience or the manual toggle is sometimes required.

Early feedback on the Insider Hub and social media has been overwhelmingly positive, though power users have noted a few rough edges. The activity meter, for instance, does not yet indicate whether the signal is stereo or mono, and the filter bar disappears while the “Show disabled devices” toggle is on, which some find counterintuitive. Microsoft typically iterates on such details during the preview period, and the final implementation that ships to the General Availability channel often differs subtly from the initial Insider version.

What the new settings do not change

It is equally important to note what Build 29613 does not alter. The volume mixer accessible from the system tray remains the same overlay introduced in Windows 11 22H2, complete with per‑app sliders and spatial audio shortcuts. The classic Sound control panel (mmsys.cpl) still exists and can be launched by searching for “Control Panel > Sound,” though its days appear numbered. Audio enhancements like loudness equalization, bass boost, and virtual surround are still only configurable through the legacy dialog’s “Properties” button—Microsoft has not ported those to the new Settings UX.

Additionally, the new default‑device selector respects but does not expose the concept of “Default Communication Device” as an explicit secondary picker; instead, communication apps typically query the OS for the communication device and the new Settings page changes both the multimedia and communication default simultaneously. This behavior matches the mainstream use case but may frustrate users who deliberately set different devices for music and calls, a niche but vocal group. Feedback on the Feedback Hub has already requested a split‑selector, and Microsoft could address it in a future build.

The broader audio roadmap

Leaked engineering slides and Microsoft job listings hint at more audio work in the pipeline. The company is reportedly prototyping a universal “Audio Hub” that would unify volume, device selection, spatial sound, and microphone effects into a single floating panel accessible via a taskbar shortcut. The new Settings page introduced in Build 29613 likely serves as the foundational back‑end for that hub, exposing the necessary APIs to the shell team.

Microsoft is also working on Bluetooth LE Audio support, which will require a more nuanced device‑management interface because LE Audio devices can broadcast multiple independent streams (e.g., a phone call stream and a music stream). The filtering and meter features in Build 29613 are built on a modular architecture that other teams can extend, meaning third‑party audio OEMs might eventually be able to plug custom filters or meter skins into the Settings page—though no public SDK has been announced.

How to get the most out of the new audio settings

If you are running Build 29613, take a moment to clean house. Toggle “Show disabled devices” on, note any virtual cables you no longer use, and disable them via Device Manager. Then turn the toggle off to enjoy a clutter‑free list. Use the filter to set a view that matches your daily workflow: many users will stick to “Speakers” and “Headphones” for output and “Microphones” for input. After a reboot, confirm that your default choices persist; early testers reported that in rare cases the default reverted to a previously connected Bluetooth device, though a subsequent build will likely address this.

For content creators, the activity meters can serve as a poor‑man’s confidence monitor for microphone inputs. Position the Settings window on a secondary display and verify that the microphone meter reacts when you speak—no need to install third‑party audio loopback tools. Combined with the per‑app volume mixer, the new Settings page turns Windows 11 into a more self‑sufficient audio workstation, though serious users will still want dedicated tools like Voicemeeter or ASIO Bridge for complex routing.

Looking ahead

Build 29613 is a preview, and preview builds ship with bugs. Early feedback mentions that the meters sometimes freeze when the system wakes from sleep, and the filter dropdown can momentarily duplicate entries on high‑DPI displays. Microsoft typically resolves such glitches before a build reaches Beta, but the fixes could take several weeks. The company has not committed to a specific public release date for these audio features, though the timing suggests they could land in the 23H2 or 24H1 Moment update.

The bigger story is cultural: after a decade of neglecting user‑facing audio controls, Microsoft is investing again. The Windows audio team has expanded in recent years, hiring engineers who previously worked on Android’s audio framework and on professional audio interfaces. The result is a Settings page that finally feels like it belongs in a modern operating system—and a hint that the next generation of Windows audio might be more than just an afterthought.