winmm.dll not found or crashing: what the Windows Multimedia file is and how to fix it
winmm.dll is the Windows Multimedia library. It carries the old sound, MIDI, CD audio and timer functions that games, music software and many ordinary programs still call. Windows installs it, so you never need to download it to make a program work. An error that names it almost always comes from a second copy in a program folder, left there by a mod, a sound wrapper or a cracked game, or from a damaged Windows file that Windows can repair itself.
Prefer to fix it yourself? The manual steps follow.
How to fix winmm.dll errors
Open the folder of the program that shows the error and look for winmm.dll beside its .exe. Windows keeps its own copy only in System32 and SysWOW64, so any other winmm.dll is an add-on: an ASI or plugin loader, a CD music replacement for an old game, a frame or timer fix, or a file that came with a cracked release. Rename that copy to winmm.dll.bak and try again. If the error is gone, the add-on is the cause. If there is no extra copy, let Windows repair itself: Windows Update first, then sfc /scannow and DISM in a Command Prompt opened as administrator.
No runtime package contains this file. Installers such as the Visual C++ Redistributable or the DirectX End-User Runtime add other libraries and leave winmm.dll alone, so reinstalling them does not change a winmm.dll error. Only Windows installs, updates and repairs this file.

Step by step
- Find the program's folder. Right-click the shortcut and choose Open file location. In a game launcher, open the game's properties and use the option to browse the installed files. The error is about the folder where the .exe sits, not about your desktop or Downloads.
- Look for a winmm.dll there. A winmm.dll in that folder did not come from Windows. It is often surrounded by clues: a scripts or plugins folder, files ending in .asi, an .ini file with settings, a music folder full of .ogg tracks, or a text file from the group that released a crack. Windows never puts its multimedia library next to a game.
- Rename the copy, then start the program. Change the name to winmm.dll.bak. Keep it rather than deleting it, because you may want it back. If the program now starts, the add-on was the problem. Game updates break loaders and wrappers often; get the version of that add-on built for your game version, or keep it disabled.
- Install Windows updates. Go to Settings, Windows Update and install everything offered, optional quality updates included, then restart. Each cumulative update carries the current build of winmm.dll for your Windows release and replaces an older or damaged one.
- Run System File Checker. Search for cmd, right-click Command Prompt and choose Run as administrator. Type sfc /scannow and let it run to 100%. It checks the protected copies in System32 and SysWOW64 against Windows' stored originals and restores any that were changed. Restart when it finishes.
- Run DISM when System File Checker reports files it could not fix. In the same window type DISM /Online /Cleanup-Image /RestoreHealth. DISM downloads clean parts from Windows Update to rebuild the component store that System File Checker relies on. Then run sfc /scannow a second time and restart.
- Last resort: reinstall Windows over itself. Windows 11 has Fix problems using Windows Update under Settings, System, Recovery; it reinstalls the system files and keeps your apps, files and settings. On Windows 10, run Microsoft's installation media from inside Windows and choose to keep personal files and apps.
Download the genuine winmm.dll for your Windows version
Every file here is Microsoft's own winmm.dll for one Windows release, taken from Microsoft's symbol server and matched against Winbindex, the public index of files in Windows releases and updates. Check your release in Settings, System, About, then pick the 64-bit build (System32) or the 32-bit build (SysWOW64). For a working PC the steps above are the better route: Windows guards both folders and updates the file by itself. These downloads are for comparing a copy you already have, or for a repair that System File Checker and DISM could not finish.
Older Windows releases
Downloads need a free uGetFix account. Sign in, or sign up in a minute, and you return to this page.
What not to do
Do not fetch winmm.dll from a DLL download site.
Such sites rarely say which Windows build or architecture a file belongs to, and you cannot see whether anyone modified it. A file that matches no Microsoft build is exactly what an attacker would hand you. Use the genuine files above, and check a copy you already have with the tool below.
Do not paste a Windows copy into the game folder.
If you delete a mod's winmm.dll, the game simply uses the one in System32. Putting a Windows copy in its place does nothing useful, and that copy never gets updated when Windows updates its own.
Do not overwrite the file in System32 or SysWOW64 by hand.
Windows owns these copies. A file from another release or of the wrong architecture can break sound in many programs at once, and System File Checker or the next update may put the original back. Repair with sfc /scannow instead.
Do not reinstall audio drivers or runtimes to fix this file.
Sound drivers, the Visual C++ Redistributable and the DirectX End-User Runtime do not contain winmm.dll. Reinstalling them changes nothing about an error that names this file, and it costs time you could spend on the game folder check.
Do not switch off Microsoft Defender to keep a quarantined copy.
If Defender quarantines a winmm.dll from a program folder, find out which add-on or release it came from first. Loaders are often flagged for the way they work, but cracked releases use the same name for code you would not want.
Check the copy on your PC
Choose the winmm.dll you are not sure about, for example one beside a game's .exe. Your browser computes its checksum and compares it with 437 Microsoft builds of the file from Windows releases and updates.
The file stays on your computer. Nothing is uploaded: the checksum is computed locally.
9 genuine programs have been documented loading a planted copy of winmm.dll. Found a winmm.dll you cannot explain, beside a program you never modified, or in Downloads, Temp or AppData? Attackers have planted files with this name next to trusted Windows programs. That is a security question, not a repair one. Is the winmm.dll on your PC genuine? On 2-Spyware
The error messages and what each one means
Read the message before you change anything: each text points to a different place. Below are the texts Windows uses, with the file name as Windows writes it.

The code execution cannot proceed because WINMM.dll was not found. Reinstalling the program may fix this problem.
Shown by Windows 10 and Windows 11. Windows could not find a usable winmm.dll for the program. Since Windows always installs the file, this points to a damaged system copy: install updates, then run sfc /scannow and DISM.
The program can't start because WINMM.dll is missing from your computer. Try reinstalling the program to fix this problem.
The same problem worded the way Windows 7 and Windows 8 put it. The fix does not change. On those old releases, install the last updates they received before running System File Checker.
C:\Games\...\winmm.dll is either not designed to run on Windows or it contains an error. Try installing the program again using the original installation media or contact your system administrator or the software vendor for support. Error status 0xc000012f.
This window has the title Bad Image and shows the full path of the file. Look at that path: if it is a program folder, the add-on copy there is damaged, incomplete or blocked. Rename it. If the path is System32 or SysWOW64, run sfc /scannow.
The application was unable to start correctly (0xc000007b). Click OK to close the application.
No file is named, but after you add a loader or wrapper this usually means its build does not match the program: a 64-bit winmm.dll beside a 32-bit game, or the reverse. Download the build of the add-on made for that game.
The procedure entry point could not be located in the dynamic link library WINMM.dll.
The program asked for a function that the loaded winmm.dll does not offer. The genuine Windows file offers all of the Windows Multimedia functions, so this points to a wrapper or loader that passes on only some of them. Replace it with a complete, current version.
Faulting module name: WINMM.dll
A line in Event Viewer, Windows Logs, Application, after a program closed by itself. The same event shows the Faulting module path. A program folder there means the add-on copy crashed. System32 or SysWOW64 means Windows' copy was where the crash surfaced: update the program and your audio driver, then run sfc /scannow.
File facts
winmm.dll holds the Windows Multimedia API, the sound and timing interface Windows has offered since the 1990s. Programs call it to play and record wave audio (the waveOut and waveIn functions), to send and receive MIDI, to play sounds with PlaySound, to control media devices through MCI commands, which older games used to play music from CD audio tracks, to read simple joysticks, and to use the multimedia timers, such as timeGetTime and timeBeginPeriod, that many games use to pace frames. Newer audio interfaces sit beside it, but Windows keeps winmm.dll so that old and new software still runs. What Windows reports for the genuine file:
- Description in the file
- MCI API DLL
- Where the genuine winmm.dll belongs
C:\Windows\System32C:\Windows\SysWOW64- Signed by
- Microsoft Windows, with a Windows catalog signature: the file's Properties show no Digital Signatures tab, which is normal. Check it in PowerShell: Get-AuthenticodeSignature <path to the file> (Status: Valid).
On 64-bit Windows the 64-bit library is in System32 and the 32-bit library in SysWOW64. When a program starts, Windows checks the program's own folder for winmm.dll before it checks System32, and loaders and wrappers rely on exactly that: a file with this name beside the .exe is loaded first and then passes calls on to Windows' copy. The genuine file is signed by Microsoft and describes itself as MCI API DLL. In Windows 11 24H2 and 25H2 the 64-bit file is 240,912 bytes and the 32-bit file 213,144 bytes; in Windows 10 22H2 they are 148,376 and 150,352 bytes. A game folder copy usually has a different description and size and no Microsoft signature.

winmm.dll versions by Windows release
Windows updates winmm.dll together with the rest of the system, and each release has its own build. Winbindex knows 421 different Microsoft builds; the table shows the newest one indexed for each release and the update it came in. For a few Windows 10 releases the newest indexed 64-bit build is a very small file of about 10 KB; it is still a Microsoft build.
| Windows release | File version | Delivered by | Size, 64-bit |
|---|---|---|---|
| Windows 11 26H1 | 10.0.28000.2605 | KB5121000, August 11, 2026 | 224,680 bytes |
| Windows 11 25H2 | 10.0.26100.9549 | KB5127648, October 13, 2026 | 240,912 bytes |
| Windows 11 24H2 | 10.0.26100.9549 | KB5127648, October 13, 2026 | 240,912 bytes |
| Windows 11 23H2 | 10.0.22621.5415 | KB5126653, October 13, 2026 | 216,360 bytes |
| Windows 11 22H2 | 10.0.22621.5415 | KB5126653, October 13, 2026 | 216,360 bytes |
| Windows 11 21H2 | 10.0.22000.1 | original release | 211,096 bytes |
| Windows 10 22H2 | 10.0.19041.3636 | KB5126657, October 13, 2026 | 148,376 bytes |
| Windows 10 21H2 | 10.0.19041.3636 | KB5126657, October 13, 2026 | 148,376 bytes |
| Windows 10 21H1 | 10.0.19041.3636 | KB5126657, October 13, 2026 | 148,376 bytes |
| Windows 10 20H2 | 10.0.19041.3636 | KB5126657, October 13, 2026 | 148,376 bytes |
| Windows 10 2004 | 10.0.19041.3636 | KB5126657, October 13, 2026 | 148,376 bytes |
| Windows 10 1909 | 10.0.18362.1474 | KB5001337, April 13, 2021 | 10,240 bytes |
Older copies of winmm.dll found on PCs
Public DLL catalogues hold 16 copies of winmm.dll that people uploaded from their PCs, from version 4.3.0.1998 to 10.0.18362.1. Most belong to older Windows releases. The table gives the checksums of each, so you can identify the one you have.
None of them is a substitute for the build your Windows ships: the newest build indexed for Windows is 10.0.28000.2605, and every release has its own. If the check on this page finds your file here, it is most likely an older Microsoft build that someone copied by hand. Confirm the Microsoft signature, remove the copy from the program folder, and let Windows use its own.
| Version | Build | Size | MD5 | SHA-1 |
|---|---|---|---|---|
10.0.18362.1 | 64-bit | 123 KB | 965eb822d0ef8fda78ccb1f41def093d | 67e25361dce72026b1472607ec389040dbaf5e94 |
10.0.18362.1 | 32-bit | 133 KB | 7f48ce53dbaf54edf1f514680e00c55e | 679d7b025c7522bc3654c4b6a496e4c9ce6a829c |
10.0.14393.0 | 64-bit | 123 KB | f16410f5d557337b05cf4f93691ec106 | 777af463ca2bf5419b2ef974d73ff58cc1df5a13 |
10.0.14393.0 | 32-bit | 133 KB | 2cdb8e874f0950ea17a7135427b4f07d | 73b16f132eb0247ea124b6243ca4109f179e564c |
10.0.10586.0 | 64-bit | 123 KB | 8e1621aa8f1e227873f41d1aece13ef3 | d6d0c96f144e4bfa906f98e441160312522aedcd |
10.0.10586.0 | 32-bit | 133 KB | 4875a62de7dbb832e232f37858b3e0f4 | 8199acd303cdf0e1fdd77bed7e26c6209cc7488c |
6.3.9600.16384 | 32-bit | 123 KB | 8a606c90276dcac67f3d45a0a235ecd6 | 1dabd448babfab2f9e5a833d4d5330ed40319220 |
6.2.9200.16642 | 32-bit | 123 KB | 0e38a984be8c1f4a095b4a4e8ba1eb23 | 8a59674bb8d7f6a647ea15fdd07b829abc60b707 |
6.1.7601.17514 | 32-bit | 195 KB | d5aefad57c08349a4393d987df7c715d | 41905c387fa657d91da8a743abc04b6c11a38b52 |
6.1.7600.16385 | 32-bit | 195 KB | 26a634b2e0fd87f23541ad13a503ca72 | 375eade80ce972027071119762a2cfbdeba1e655 |
6.0.6001.18000 | 64-bit | 205 KB | bfd7bae538c981166add21d61710b100 | e3cce07f7e5f76e02361305e0c6313b1d77ef056 |
6.0.6001.18000 | 32-bit | 184 KB | eefe4228157ce404f4a69da90f288eca | 2c348b5659ad2118a5484716b7a52ead0a145aec |
5.1.2600.5512 | 32-bit | 174 KB | b282349de03532dd4cb68faa85e131b0 | 98b5e7de251bd6394cc77011a462eb0e98041e94 |
5.1.2600.2180 | 32-bit | 174 KB | 0923eff852a41dbe4cbc274fbc6bf49f | a359dce178d5a5a16a8cf9324e142f26221d2b46 |
5.1.2600.2180 | 32-bit | 174 KB | 90fdaa22f38d9e911f91fa3b8a1f7e5d | cb523bc4f80955dbf89bfdbdd813e8f1a1d68c29 |
4.3.0.1998 | 32-bit | b14717f245b8158041869e068fb99cca | 3558ee58f6142f4fcab479fc179308d4a510ae23 |
Copies uploaded by users to a public DLL catalogue, read on 14 October 2026. The checksums help you identify a file; we do not offer these copies for download and did not check each one against Microsoft's signature.
Questions people ask
Is winmm.dll a virus?
The copies in System32 and SysWOW64 are Microsoft's and safe; a winmm.dll anywhere else is someone else's file, so check it with the tool on this page and read the security page linked above.
Do I need to install anything to get winmm.dll?
No. Windows 10 and Windows 11 include winmm.dll, and no separate installer for it exists. A program that reports it missing either found a broken add-on copy in its folder or a damaged system copy. Remove the add-on copy, or repair Windows with updates, System File Checker and DISM.
Why is there a winmm.dll in my game folder?
Something you or a game package added put it there. Plugin loaders that inject .asi files, wrappers that play an old game's CD music from audio files, timer and frame rate fixes, and the files of cracked releases all use this name, because the game loads it before Windows' copy. Games do not need to ship Windows' own multimedia library.
A game crashes after an update and names winmm.dll. What happened?
If you use a loader or wrapper called winmm.dll, the game update most likely changed what that add-on expects to find. Rename the file in the game folder and start the game. If it runs, wait for the add-on's update made for the new game version, then put it back.
Can I delete winmm.dll?
Not from System32 or SysWOW64: Windows protects those files, and sound, timers and media playback in many programs depend on them. A copy in a program folder is safe to remove as far as Windows is concerned. The program falls back to Windows' copy and only the add-on stops working.
Will reinstalling my sound driver fix a winmm.dll error?
Rarely. The driver sits below winmm.dll and does not include or replace it. A missing or not found message is about the file itself; repair it with System File Checker. A driver update can help when Event Viewer shows a crash in Windows' own copy while the program was playing sound.
Which build do I need, 32-bit or 64-bit?
Windows needs both and already has both: 64-bit in System32, 32-bit in SysWOW64. A loader or wrapper must match the program instead of Windows: a 32-bit game needs a 32-bit winmm.dll beside it, a 64-bit game a 64-bit one. A mismatch is the usual cause of error 0xc000007b after adding one.
Related guides
How to fix winmm.dll missing or not found error in Windows?
FixHow to fix DDraw.dll missing or not found error in Windows?
FixHow to fix "DLL is either not designed to run on Windows or it contains an error"?
FixHow to fix DSOUND.dll is missing or not found error in Windows?
Sources
- Winbindex, the Windows binaries index (m417z)
- Microsoft Learn: Use the System File Checker tool to repair missing or corrupted system files
- HijackLibs: winmm.dll
File data read on October 14, 2026.
The editors who write and check uGetFix guides and reference pages. File facts are read from Microsoft's own installers and documentation, and every page shows the date its data was read.
Questions and experiences
Ask about this page: members and our editors answer. Reading is open; writing needs a free account.
…