Windows 11 is louder than most people want it to be. The default event sounds are fine for a fresh install, and they get old fast. There is also a wider problem hiding under the surface: a lot of the sounds you hear every day are not in the list you can change, because they belong to apps, drivers, or the firmware running on the laptop itself. Knowing where the line is between what you can change and what you cannot saves you from chasing settings that were never going to do what you hoped.
This walkthrough covers the part you can change, the part you cannot, and a few small traps that catch people the first time they try. Nothing here requires a third-party app, and nothing here disables hardware beeps. You should be able to finish in five minutes and revert in one.
Open the right Sound control panel, not the modern one
The first trap is that Windows 11 has two Sound settings pages. The modern one lives in the Settings app, and it covers most output devices, volume mixing, and spatial audio. It does not include the per-event sound picker that has existed since the Windows 95 days. That picker lives in the legacy Sound control panel, which you can still reach by searching for it.
The fastest path is to type in the search box at the bottom of the screen:
- Open the Windows search bar.
- Type Control Panel.
- Press Enter.
From the Control Panel, click Hardware and Sound, then Sound. The dialog that opens is the old one. That is the one you want. The Sounds tab at the top is where event sounds live. If you instead opened Settings and went to System, then Sound, you are on the modern page and there is no per-event picker here. Switch back to the Control Panel route before continuing.
This is the single most common reason people think Windows 11 removed the feature. It did not. The feature just moved out of the default settings path.
Pick an event, then pick a sound, then listen before saving
Once the Sounds tab is open, the window lists every event Windows can play a sound for. Calendar reminders. Battery alarms. Critical stops. The list scrolls. Some entries are system events, others are tied to specific Windows features like the sign-in screen or the notification area.
A short sequence that avoids the most common mistakes:
- Scroll to the event you want to change. For your first attempt, pick something obvious like Critical Battery Alarm or Calendar Reminder.
- Look at the Sound drop-down at the bottom of the dialog. There are dozens of options.
- Click one, then click the Test button to hear it.
- Only click Apply if the sound is what you wanted. Click OK to close.
The Test button is the friend of everyone who hates surprises. Pick the wrong chime, click Apply, and you will hear it for every matching event until you change it back. Pick the right chime, listen to it once or twice on different event types, and you can move on.
Note the original sound before you change anything
This is the one piece of advice the source article gets exactly right and most walkthroughs skip. Before you change a single sound, write down which sound the original event had. Windows does not show you a “restore to default” button per event, and the Sound Scheme drop-down at the top is closer to a preset than a per-event reset.
A practical way to capture the defaults:
- Pick the first three or four events you plan to change.
- Click each one and read the Sound field. The display name is enough.
- Write them down in a note, or take a screenshot of the dialog before clicking Apply.
If you change your mind later, the note is the difference between a five-minute fix and a half-hour scavenger hunt through the Windows theme files. There is no undo button on this dialog.
There is also a global mute option in the same dialog, called Sound Scheme. If you want everything silent for a stretch of focused work, you can switch the Sound Scheme to No Sounds. That is the right tool when you want quiet for an hour, not when you want to tune specific events. Switch it back to Windows Default when you are done.
Know what you cannot change in this dialog
The dialog is only for sounds that Windows itself owns. Several categories of sound are off-limits here, and trying to change them through the legacy panel is a waste of time. The categories are:
- Sounds produced by third-party apps. Discord, Slack, your email client, and most chat tools ship their own notification sounds. Those live inside each app’s settings.
- Sounds produced by games. The audio engine in most games owns its own sound bank. The Windows event list does not touch it.
- Hardware beeps and chimes. If your laptop beeps when you press the power button or when you plug in the charger, that is firmware, not Windows. There is no setting in the Sound control panel that silences those.
You can also not change the sign-in or lock screen sounds from this dialog in recent Windows 11 builds. Those live in Settings under Personalization, then Lock screen. That is a different walkthrough.
If you find yourself wishing the dialog had an entry for something that seems obvious, that is usually the cue that the sound comes from one of the categories above. Knowing that ahead of time saves you from opening every menu Windows has.
Trade-offs
The benefit of using the legacy Sound dialog is that it is built in, supported on every edition of Windows 11, and does not require you to install anything. The downside is that the modern Settings app hides it, so most people never find it. The other downside is granularity: the Sounds list treats every event as one slot. There is no per-event volume, no scheduled quiet hours per event, and no separate volume for system sounds versus media.
If you want a finer knob, the modern volume mixer (right-click the speaker icon, then Open Volume Mixer) can mute specific apps. That is a different problem from changing event sounds. The two tools overlap less than they look.
You also trade visibility for control. Changing one event at a time means a misclick is recoverable with the note you took earlier. A blanket scheme change means everything sounds different at once, and you may not notice what is wrong until the next time you are not paying attention.
Quick checklist before you close the dialog
A short list to run through once you have made your changes:
- Every event you wanted to change has a new sound picked from the drop-down.
- You clicked Test for each one and you actually heard the sound play.
- You wrote down the original sound for each event you changed.
- The Sound Scheme is still on Windows Default, unless you wanted global silence.
- Nothing in the list is showing No Sounds unintentionally.
If you can answer yes to all five, click Apply, then OK. If you cannot answer yes to all five, click Cancel, take the note, and try again. Cancel closes the dialog without saving anything. That is the safer default when you are not sure.
The whole job takes about five minutes when you are not hunting for the right dialog, and about fifteen minutes when you are. Knowing which dialog to open is most of the work.