d3d9.dll is missing or crashes a game: what the file is and how to fix it
d3d9.dll is the Direct3D 9 Runtime, the part of Windows that draws the graphics of older games built on DirectX 9. Windows ships it, so there is nothing to install. When a game crashes in it or says it is missing, the cause is usually a graphics mod's copy in the game folder, the graphics driver, a compatibility setting, or a damaged Windows file.
Prefer to fix it yourself? The manual steps follow.
How to fix d3d9.dll errors
First read the file name in the message letter by letter. If it says d3dx9_43.dll or another d3dx9_ file, you have a different problem: that library is not part of Windows and comes with the DirectX End-User Runtime. If it really says d3d9.dll, look in the folder of the game that fails, next to its .exe file. A d3d9.dll there is not Windows' copy: it belongs to a graphics enhancer, a shader injector or a translation layer, and the game loads it instead of the genuine file in System32. Rename it to d3d9.dll.bak and start the game. If the game now starts, update or remove that mod. If there is no copy in the game folder, install the newest graphics driver, close overlays, turn off compatibility mode for the game, and read the crash event. When several games fail, repair Windows: install the pending updates, then run sfc /scannow and DISM from an administrator Command Prompt.
The DirectX End-User Runtime is not the fix for d3d9.dll itself. That package installs the old D3DX9 helper libraries, such as d3dx9_43.dll, which many DirectX 9 games need and Windows does not include. d3d9.dll is already part of Windows 10 and Windows 11, is not in that package, and is repaired and updated only by Windows itself.

Step by step
- Check which file the message names. d3d9.dll and d3dx9_43.dll look alike but are different files. A message about a d3dx9_ file, d3dcompiler_43.dll or xinput1_3.dll is solved by installing the DirectX End-User Runtime from Microsoft. Only a message that names d3d9.dll exactly belongs to this page.
- Look in the game folder. Right-click the game's shortcut and choose Open file location, or in a game launcher use the option to browse local files. If you see d3d9.dll next to the .exe, often together with an .ini file, a folder of shaders or presets, or other DLLs such as d3d8.dll, d3d11.dll or dxgi.dll, a graphics mod or tool put it there. Games almost never ship their own copy of this Windows file.
- Rename that copy and test. Rename it to d3d9.dll.bak rather than deleting it, so you can put it back. Start the game. If it runs, the mod's copy was the cause. Two tools that both want to be d3d9.dll cannot both sit in one folder, and a game update or a new driver often breaks these tools until their authors release a new version. Update the mod, keep only one such tool, or leave it disabled.
- Verifying the game files will not remove it. The verify or repair option of a game launcher checks the files the game shipped and puts back what is damaged. It usually leaves extra files alone, so a mod's d3d9.dll stays in place after a verify. Remove or rename it yourself.
- Install the newest graphics driver. Download the driver for your card from the website of its maker, or from the maker of your laptop, and install it. If the crashes started right after a driver update, install the previous version instead. d3d9.dll passes every draw call of a DirectX 9 game to the graphics driver, so a driver fault is the most common reason the file appears in a crash report. On a laptop with two graphics chips, also check in Settings, System, Display, Graphics that the game uses the one you expect.
- Turn off compatibility mode and overlays. Right-click the game's .exe, choose Properties, Compatibility, and clear Run this program in compatibility mode for, then test again. Old games are often set to a Windows XP or Windows 7 mode by an earlier fix, and that mode can make Direct3D 9 crash on a modern PC. Also turn off in-game overlays, FPS counters, recording tools and RGB or fan utilities one at a time, because they hook into the same drawing step.
- Read the crash event. Press Windows+R, type eventvwr.msc and press Enter. Open Windows Logs, Application, and look for an Error from the source Application Error at the time of the crash. Faulting application name tells you which program crashed; Faulting module path tells you which d3d9.dll was involved. A game folder path means a mod's copy; C:\Windows\System32 or SysWOW64 means Windows' copy, which points to the driver, an overlay, a compatibility setting or the game itself.
- Install Windows updates and restart. Open Settings, Windows Update, install everything that is offered and restart, even if Windows does not ask. Updates replace system files, d3d9.dll included, with the current build for your Windows release.
- Run System File Checker. Type cmd in the Start menu, right-click Command Prompt and choose Run as administrator. Run sfc /scannow and wait until it reaches 100%. It compares protected Windows files with the stored originals and repairs a damaged or replaced d3d9.dll in System32 or SysWOW64. Restart afterwards.
- If System File Checker cannot repair everything, run DISM. In the same administrator window run DISM /Online /Cleanup-Image /RestoreHealth. It repairs the store that System File Checker copies its originals from, using Windows Update. When it finishes, run sfc /scannow once more, then restart.
- Still failing: repair Windows in place. On Windows 11, Settings, System, Recovery offers Fix problems using Windows Update, which reinstalls the current version of Windows and keeps your files, apps and settings. On Windows 10 the same result comes from running Microsoft's installation media and choosing to keep personal files and apps.
Download the genuine d3d9.dll for your Windows version
Each file below is Microsoft's own d3d9.dll for one Windows release, fetched from Microsoft's own server and checked against Winbindex, the index of the files in Windows images and updates. Pick your Windows version (Settings, System, About shows it) and the build: 64-bit for System32, 32-bit for SysWOW64. Most DirectX 9 games are 32-bit and use the copy in SysWOW64. The repair steps above are still the better fix, because Windows protects these folders and keeps its copy updated. Use a file here to compare it with a copy you have, or when System File Checker and DISM cannot repair the file.
Older Windows releases
A free uGetFix account is needed to download. Sign in, or create one in a minute, and you come straight back here.
What not to do
Do not install the DirectX End-User Runtime for d3d9.dll.
It is the right fix for d3dx9_ files, and it does not help here. It adds legacy DirectX helper libraries that Windows lacks, and it does not contain or replace d3d9.dll. If the message names d3d9.dll, the error stays exactly as it was.
Do not download d3d9.dll from a DLL collection site.
You cannot tell which Windows release, build or architecture the file comes from, or whether it was changed. d3d9.dll works together with the rest of the graphics stack of your Windows build, so a copy from another release can break every DirectX 9 game at once. Use the genuine files above, and the checker below for a file you already have.
Do not copy a file into System32 or SysWOW64 by hand.
These copies are protected Windows files owned by the system. A hand-placed file of the wrong build or architecture can stop every older game and some desktop programs from drawing anything, and the next update or System File Checker run may replace it anyway. Repair with sfc /scannow instead.
Do not put a downloaded Windows copy into the game folder.
A game folder copy of d3d9.dll only makes sense for a graphics mod. A Windows copy there adds nothing, because Windows already loads the one in System32, and it stays behind, out of date, when Windows updates its own.
Do not keep a flagged copy by turning off protection.
If Microsoft Defender quarantines a d3d9.dll from a game folder, find out where that mod came from before you restore it. Graphics injectors are sometimes flagged because of how they work, but the same name can be used by cheats and by malicious mod packages. The security page linked below explains how to tell them apart.
Check the copy on your PC
Choose the d3d9.dll you are unsure about, for example the one in a game folder. Its checksum is calculated in your browser and compared with 264 Microsoft builds of the file from Windows releases and updates.
The file stays on your computer. Nothing is uploaded: the checksum is computed locally.
1 genuine programs have been documented loading a planted copy of d3d9.dll. Found a d3d9.dll you did not expect, in a game folder you did not mod, in Downloads, Temp or AppData? The name is used by graphics mods, and it can be used by cheats and malware. That is a security question, not a missing-file one. Is the d3d9.dll you found genuine? On 2-Spyware
The error messages and what each one means
The wording tells you which problem you have. These are the texts Windows and games show, as written, with the file name filled in. Game messages differ from title to title, so look for the closest match.

The code execution cannot proceed because d3d9.dll was not found. Reinstalling the program may fix this problem.
The wording of Windows 10 and Windows 11. Windows did not find a usable copy for that program. Because Windows ships the file, this points to a damaged or missing system file: install updates, then run sfc /scannow and DISM. If the name in the message is d3dx9_ followed by a number, install the DirectX End-User Runtime instead.
d3d9.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.
A d3d9.dll was found but could not be loaded. Almost always this is a copy in the game folder: a graphics mod of the wrong build, a damaged download, or a file blocked by security software. Rename the game folder copy and test again.
The application was unable to start correctly (0xc000007b). Click OK to close the application.
This one does not name a file, but after installing a graphics mod it often means a 64-bit d3d9.dll in the folder of a 32-bit game, or the other way round. Most DirectX 9 games are 32-bit. Use the build of the mod that matches the game.
The procedure entry point Direct3DCreate9Ex could not be located in the dynamic link library d3d9.dll.
The program asked for Direct3D 9Ex, the extended Direct3D 9 that Windows Vista and later provide. On Windows XP the function does not exist and the program cannot run. On Windows 10 or 11 the same message points to an old or incomplete mod copy in the program's folder: rename it.
Faulting module name: d3d9.dll
A line from the Application log in Event Viewer after a crash. Look at the Faulting module path line of the same event. A game folder path means the crash happened inside a mod's copy: update or remove that mod. A System32 or SysWOW64 path means the driver, an overlay or a compatibility setting: update the graphics driver, close overlays and turn off compatibility mode.
Failed to create the Direct3D device
A game's own message, worded differently in each title. The game asked d3d9.dll for a graphics device and the driver refused. Typical causes are a missing graphics driver (Device Manager shows Microsoft Basic Display Adapter), a resolution or refresh rate the game cannot use, or starting the game over Remote Desktop. The file itself is rarely at fault.
File facts
d3d9.dll is the Direct3D 9 Runtime. Games and programs built on DirectX 9 load it to create a graphics device, send their textures, shaders and draw calls to the graphics driver, and present each finished frame. Since Windows Vista the same file also provides Direct3D 9Ex, the extended version that works with the Windows desktop compositor. New games use Direct3D 11 or 12 through other files, but Windows 10 and Windows 11 keep and update d3d9.dll so that the large library of older games, and some desktop programs and video players, keep working. What Windows reports for the genuine file:
- Description in the file
- Direct3D 9 Runtime
- Where the genuine d3d9.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, System32 holds the 64-bit file and SysWOW64 the 32-bit one; the folder names are historical. When a game starts, Windows looks for d3d9.dll in the game's own folder first, which is exactly what graphics enhancers, shader injectors and translation layers rely on: DXVK, for example, ships its own d3d9.dll that turns Direct3D 9 calls into Vulkan. A file with this name next to the game's .exe is loaded instead of the Windows copy. The genuine file describes itself as Direct3D 9 Runtime (Properties, Details, File description) and is between 1 and 2.2 MB: in the Windows 11 24H2 and 25H2 builds the 64-bit file is 1,799,712 bytes and the 32-bit one 1,550,992 bytes, in Windows 10 22H2 the 64-bit file is 1,915,168 bytes and the 32-bit one 1,634,280 bytes. A mod's copy usually shows another description, another size, and no Microsoft signature.

d3d9.dll versions by Windows release
Every Windows release has its own build of d3d9.dll, updated together with Windows. Winbindex lists 229 distinct Microsoft builds; the table shows the newest one indexed for each release and the update that delivered it.
| Windows release | File version | Delivered by | Size, 64-bit |
|---|---|---|---|
| Windows 11 26H1 | 10.0.28000.2525 | KB5101649, July 14, 2026 | 1,741,120 bytes |
| Windows 11 25H2 | 10.0.26100.9549 | KB5127648, October 13, 2026 | 1,799,712 bytes |
| Windows 11 24H2 | 10.0.26100.9549 | KB5127648, October 13, 2026 | 1,799,712 bytes |
| Windows 11 23H2 | 10.0.22621.5415 | KB5126653, October 13, 2026 | 1,736,944 bytes |
| Windows 11 22H2 | 10.0.22621.5415 | KB5126653, October 13, 2026 | 1,736,944 bytes |
| Windows 11 21H2 | 10.0.22000.2600 | KB5044280, October 8, 2024 | 1,728,608 bytes |
| Windows 10 22H2 | 10.0.19041.7802 | KB5126657, October 13, 2026 | 1,915,168 bytes |
| Windows 10 21H2 | 10.0.19041.7802 | KB5126657, October 13, 2026 | 1,915,168 bytes |
| Windows 10 21H1 | 10.0.19041.7802 | KB5126657, October 13, 2026 | 1,915,168 bytes |
| Windows 10 20H2 | 10.0.19041.7802 | KB5126657, October 13, 2026 | 1,915,168 bytes |
| Windows 10 2004 | 10.0.19041.7802 | KB5126657, October 13, 2026 | 1,915,168 bytes |
| Windows 10 1909 | 10.0.18362.1500 | KB5013945, May 10, 2022 | 1,845,416 bytes |
Older copies of d3d9.dll found on PCs
Public DLL catalogues have collected 35 copies of d3d9.dll uploaded from PCs, from version 4.9.0.901 to 10.0.19041.488. Many come from Windows XP, Vista, 7 and 8 and from early Windows 10 releases. The table lists each with its checksums, so you can tell which one you have.
None of these replaces the file your Windows ships: the newest build indexed for Windows is 10.0.28000.2525, and each release keeps its own. A d3d9.dll from Windows XP or Windows 7 in a game folder is a common leftover of old fix guides. If the check on this page finds your file in this list, confirm the Microsoft signature, remove the copy from the game folder, and let Windows use its own.
| Version | Build | Size | MD5 | SHA-1 |
|---|---|---|---|---|
10.0.19041.488 | 64-bit | 1.8 MB | 7f7ca5c4731b95a497f0a02de50835b9 | 936a456d64b28d925bd6702472795fdd7c3e5de8 |
10.0.19041.423 | 32-bit | 1.5 MB | e598bc6ed8efed7b03fa29d91d972b63 | b7255ea40ebb46460ac2c4b8bfd85f3b13721614 |
10.0.19041.1 | 64-bit | 1.8 MB | 0e754a1819b9959fd7d9d9f9785164b9 | 741f1a06946ecbd5359fb40630100216dfc1da57 |
10.0.19041.1 | 32-bit | 1.5 MB | 59df6e246437c34f3ea880fe674a6809 | 55b2a9ff78d681aaf34f9fb261e1e7f4326bf608 |
10.0.18362.387 | 64-bit | 1.8 MB | 00a77dc70009944164236c684ef2f5a2 | 500a78419f1b5c108a7fb0100541788bad7cf872 |
10.0.18362.387 | 32-bit | 1.5 MB | 50bd9902c00fb258ed1b0a9d9d4aad93 | 788d1131555a2f40e6e367b56a8afc35dbe0a43e |
10.0.18362.329 | 64-bit | 1.8 MB | 8c4d0dfdf89b257ab720f083feed465a | 67b24dd725c91dd26f24ef0f52b2d8f20308f82c |
10.0.18362.1 | 64-bit | 1.8 MB | 548f9dc89aa91c611d824c849c2cad3f | bd892765ea2f8f830d2ef7f386971447f9362509 |
10.0.17763.1 | 64-bit | 1.6 MB | d5bac74becfac501a55a17e3db87df98 | c7d07d634f3b45fc6ba3bb020ada1e1a305cef5c |
10.0.16299.98 | 64-bit | 1.6 MB | de99750cf68f639683435ad1375b0f39 | e4d916d5746e2cad15127378cbf49357b9f1dd5c |
10.0.15063.0 | 64-bit | 1.5 MB | 1bbe7d3f447a60f4a443bcd270acfc24 | 3f042363595b3c1aab3ed7a011ab1316955b1c70 |
10.0.15063.0 | 32-bit | 1.4 MB | 89c616a2351571c80a1c8e59f06993c0 | 667918f55d934d3cc7de6983d797fefb93b1f5d0 |
10.0.14393.0 | 64-bit | 1.5 MB | 2d002258749111b2edbdf8b7f32d8c48 | eb844fa879b4e38841307aae7d258b7ffbecd471 |
10.0.14393.0 | 32-bit | 1.4 MB | d10ce25f7304cd6f69e1ef859d52e43e | 1f9d45d797eaa063a24859ec2a5a97383b3ef932 |
10.0.10586.494 | 64-bit | 2.0 MB | 556e7c9734b9d2581022c56a23c96b78 | d77a2bcf77e15482adef8d50a5b302efcad30b5f |
10.0.10586.494 | 32-bit | 1.8 MB | 4102898869c3f72fbd50e7a7d003f530 | 0eebf3b27a72f82f2ad02fcb1710787e3bbdc5b7 |
10.0.10586.0 | 64-bit | 2.0 MB | 6842bee591a23720e628e475fd918ab1 | 853bf165f7ff93f2e537092456ca47ad2f36621b |
10.0.10586.0 | 32-bit | 1.8 MB | 9d8bc943f18912a09c5724f35691b765 | 58d95f0907140a4b9fdac1b6c0c901be6f7d5b94 |
10.0.10240.16412 | 64-bit | 2.0 MB | 91e005e44100e257761a8fd49bc62e51 | b0fc2d10817c0e6b0ce224961b20da1f3648c9f7 |
10.0.10240.16412 | 32-bit | 1.8 MB | e731e28520e527e9eac2049b3147d536 | 0cd7e7383b1c0bfd90f9c5e6f291c001d1ea9bc6 |
6.3.9600.17415 | 64-bit | 2.1 MB | 972b9c13c75465b0d5a527584bb5819f | a9e9cd45d93819a29196fb94c5e7236a445afeec |
6.3.9600.17415 | 32-bit | 1.8 MB | 0936955770489965eb9041d00636369d | 4663fab19d9f2229fde4edcbe6f80869b6d9b77c |
6.3.9600.17095 | 64-bit | 2.0 MB | c1e44a99f7cf8c3a08cd5addf451636c | 770f3aeb1f2befc26006018c128b2b608aeb78dd |
6.3.9600.17095 | 32-bit | 1.7 MB | 949e0e42daad0418513b44c31a697ca5 | 132e9cbdb6cc617ce239216ec741079dab116c72 |
6.3.9600.16404 | 32-bit | 1.7 MB | d85f310b0871af13961d1c9a9695d756 | 520769173d8cc37e4c6800497db4117974b9ecfb |
6.2.9200.16384 | 64-bit | 2.0 MB | 94c17410f8a3e6bd1b1af59539d2437e | 294df899e9ca485ecf9c646ce15d79ca991725c8 |
6.2.9200.16384 | 32-bit | 1.7 MB | 118ba3061b4040bdc17432b775f3a292 | 47d2843bfa6fee105abfcc4625bee8fbbfa0755c |
6.1.7601.17514 | 32-bit | 1.7 MB | 6ef5f3f18413c367195f06e503ab86a6 | 74e5861dd61d6ddec17dc802664e26196d628bc9 |
6.1.7600.16385 | 32-bit | 1.7 MB | 7459301d21c2e21468823f73042d9f87 | c69e4b71fd39a2ebcd1ad56f05cc902be82a9984 |
6.0.6001.18000 | 64-bit | 1.8 MB | 515417b02df24e1768b2e93f74b010ea | e0008b0d382c5d5ffaf7b0783f4a8c0d62cf04c0 |
6.0.6001.18000 | 32-bit | 1.7 MB | fab8f08ec64a54917c07bdb6dc811c95 | 507b378f655808fc03aae18f21172e33a4dc1a00 |
5.3.2600.5512 | 32-bit | 1.6 MB | 3aab4a2f773eeb6dc732d6ccfb559c4a | cc1a12f476c453d97758feb62d118b44c0d87eb9 |
5.3.2600.2180 | 32-bit | 1.6 MB | 013a032aa914b35ff98c7c209d8fe556 | 07bdb89a6da0017996aa1e803f78c5597ff28d19 |
5.3.2600.2180 | 32-bit | 1.6 MB | 7b25a35ceb71b1790a785b29bd5c529c | 917add57feef2b35c82fadae3375dd865de6a710 |
4.9.0.901 | 32-bit | 1.5 MB | cfef78d10f8d0531d494334e29f6f3a2 | a2e8184efe677305f9a1e300085053079337850e |
Copies uploaded by users to a public DLL catalogue, read on 14 October 2026. We list their checksums so you can identify a file; we do not offer them for download and we did not verify each one against Microsoft's signature.
Questions people ask
Is d3d9.dll a virus?
The copies in System32 and SysWOW64 are genuine Windows files and are harmless. A d3d9.dll in a game folder is not Windows' copy: most often it is a graphics mod, but other tools can use the same name because games load it automatically. Check the file with the tool on this page and read the security page linked above.
Is d3d9.dll the same as d3dx9_43.dll?
No. d3d9.dll is the Direct3D 9 Runtime and is part of Windows. d3dx9_43.dll and the other d3dx9_ files are helper libraries from the old DirectX SDK that games bring along or that the DirectX End-User Runtime installs. A missing d3dx9_ file is fixed with that runtime; a d3d9.dll problem is fixed with the steps on this page.
Do I need to install DirectX 9 to get d3d9.dll?
No. Windows 10 and Windows 11 already include Direct3D 9, and d3d9.dll cannot be installed separately. The DirectX End-User Runtime adds the old helper libraries and does not touch this file. If Windows' own copy is damaged, System File Checker, DISM and Windows Update repair it.
Why does an old game crash at start when it ran fine before?
If you use a graphics mod, the usual reason is its d3d9.dll in the game folder: a game update or a new driver breaks it until its author releases an update. Rename d3d9.dll in the game folder to test. Without mods, a new graphics driver, a new overlay or a compatibility mode setting on the game's .exe are the next things to check.
Can I delete d3d9.dll?
Not the copies in System32 or SysWOW64: every DirectX 9 game needs them, and Windows treats them as protected system files. A d3d9.dll in a game folder can be removed or renamed safely as far as Windows is concerned; only the mod that relies on it stops working.
Will System File Checker remove a mod's d3d9.dll?
No. System File Checker repairs protected Windows files in the Windows folders. It does not look inside game folders, so a mod's d3d9.dll there stays until you remove it.
Should I use the 32-bit or the 64-bit d3d9.dll?
For Windows itself you need both, and Windows already has both: the 64-bit file in System32 and the 32-bit file in SysWOW64. For a graphics mod, use the build that matches the game. Most DirectX 9 games are 32-bit, so they need the 32-bit build of the mod; a mismatch causes error 0xc000007b.
Related guides
d3d9.dll is missing or crashes a game: what the file is and how to fix it
Sources
- Winbindex, the Windows binaries index (m417z)
- Microsoft Learn: Use the System File Checker tool to repair missing or corrupted system files
- HijackLibs: d3d9.dll
File data read on October 17, 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.
…