The 11 Unplayable .raw Files in Windows Are Xbox UI Sounds—Here's How to Access Them

{
"title": "The 11 Unplayable .raw Files in Windows Are Xbox UI Sounds—Here's How to Access Them",
"content": "Neowin reported on July 29, 2026, that the cache of .raw audio files Windows users have spotted for years in C:\Windows\Media isn’t a forgotten debug artifact or corrupt junk. Those 11 stubbornly unplayable clips are a deliberate part of Microsoft’s WinUI control-sound system, and they were designed first for Xbox—which is why double-clicking them on a PC produces nothing but silence.

The Discovery: 11 Files, Zero Players

When you open the C:\Windows\Media folder—a familiar pit-stop for anyone who has customized Windows sounds—you’ll typically see a list of familiar .wav files for system events: “Windows Hardware Insert.wav,” “Windows Logon Sound.wav,” and a few dozen others. But on any modern Windows 10 or Windows 11 installation, the same directory also holds 11 files with a .raw extension. Their names are suspiciously descriptive: Focus048000Hz.raw, Focus148000Hz.raw, all the way through Focus448000Hz.raw, plus GoBack48000Hz.raw, Hide48000Hz.raw, Invoke48000Hz.raw, MoveNext48000Hz.raw, MovePrevious48000Hz.raw, and Show48000Hz.raw.

Attempt to play any of them with Windows Media Player, Groove Music, or even a robust third-party tool like Audacity without specific settings, and you’ll either get an outright refusal or a burst of digital static. That’s not a bug. It’s the result of the container-free .raw format. As Neowin’s investigation detailed, these .raw files contain pure audio samples without the header information that tells software how many channels exist, what sample rate to expect, or even the bit depth. Without that metadata, audio engines can’t interpret the data correctly, and they’ll either guess wrong or give up.

By manually applying parameters, Neowin confirmed that every file holds 48 kHz, 16-bit signed PCM, mono audio—values that align perfectly with the “48000Hz” in each filename. The sounds themselves are almost comically brief: each is a UI cue lasting only a few dozen milliseconds, a tiny click or blip that’s more akin to an Apple Mac’s “tink” than a Windows notification fanfare. The five Focus variants are not duplicates; they’re subtly differentiated, likely to provide slightly different feedback for repeated focus events.

The table below maps the filenames to the WinUI ElementSoundKind constants they represent: