Beeps are very simple and should probably just be recreated similarly via one of wine's multimedia libs.

Windows sounds are probably not redistributable which are regardless also not included with wine for legal purposes hence winetricks.

Search repo for WAV files for tests/examples:

./dlls/dmime/tests/resource.rc:21:/* ffmpeg -f lavfi -i "sine=frequency=600" -t 0.1 -ar 44100 -f wav -acodec pcm_u8 test.wav */

Code generated sounds are probably better for simplicity vs using more elaborate sound tools such as LMMS.

Suggested impl seems reasonable otherwise.

On Tue, Jul 21, 2026 at 5:02 PM Barath Rk via Wine-Devel <wine-devel@list.winehq.org> wrote:

This is in reference to https://bugs.winehq.org/show_bug.cgi?id=50109

Looking at Windows 10, the console 'beep' sound is represented in the
registry under the respective key as a path i.e.
C:\Windows\media\sound.wav. So the implementation should be as simple
as getting the value from this key and calling PlaySound on the
retrieved path.

Is this the expected way to implement the beep?

Also, would it be alright to simply get the .wav files from a Windows
10 install and store them in a windows\media folder when the wine
prefix is created or will there be (legal)issues lifting the .wav
files from Win10?

Regards
Barath Kannan