d3d9.dll Not Found: Repair Windows, Games, and DirectX Safely

d3d9.dll is Microsoft’s Direct3D 9 runtime component, and a literal missing or corrupt system copy should usually be repaired through Windows. If only one game reports that d3d9.dll cannot load, the cause may instead be a damaged game file, a local graphics wrapper, an antivirus quarantine, or a graphics-driver problem.

Do not start by downloading d3d9.dll from a DLL website or by running regsvr32. First identify which copy is failing and whether the problem affects one application or Windows programs generally.

As an Amazon Associate I earn from qualifying purchases.

File detail	What it means
File name	d3d9.dll
Internal description	Microsoft Direct3D
Publisher	Microsoft Corporation
Part of	Microsoft Windows Operating System
Function	Direct3D 9 runtime used by games and graphics applications
64-bit Windows locations	%WINDIR%\System32\d3d9.dll for 64-bit apps, %WINDIR%\SysWOW64\d3d9.dll for 32-bit apps
32-bit Windows location	%WINDIR%\System32\d3d9.dll
Version and size	Vary by Windows release, architecture, language, and servicing level

Historical Windows 10 metadata includes 64-bit builds such as 10.0.19041.488 at approximately 1.78 MB and 32-bit builds around 1.54 MB. Other historical entries include 10.0.18362.387, 10.0.18362.329, and 10.0.18362.1. These are not repair targets. The correct version is the one supplied and serviced by your installed Windows build.

Understand the name before repairing anything

d3d9.dll is the DLL behind the Direct3D 9 API. Direct3D provides interfaces used to create rendering devices, textures, surfaces, shaders, and other graphics resources. Microsoft’s Direct3DCreate9 documentation identifies D3d9.dll as the required DLL for that API.

This makes d3d9.dll different from files such as:

• d3dx9_24.dll
• d3dx9_25.dll
• d3dx9_43.dll
• xinput1_3.dll
• xaudio2_7.dll
• d3dcompiler_43.dll

Those are optional legacy DirectX side-by-side libraries. They are commonly installed by the DirectX End-User Runtime packages, while the core Direct3D runtime is part of Windows.

Windows may report DirectX 12 in dxdiag while still supporting older Direct3D interfaces. The DirectX version displayed there is not a complete inventory of every legacy DirectX helper DLL installed on the computer. Microsoft explains this distinction in its DirectX FAQ.

Use the exact file name in the error:

• d3d9.dll: repair Windows, the affected program, its local files, or the graphics driver.
• d3dx9_*.dll: install Microsoft’s legacy DirectX runtime.
• xinput1_3.dll, x3daudio1_7.dll, xaudio2_7.dll, or d3dcompiler_*.dll: the June 2010 DirectX package may be appropriate.
• MSVCP140.dll or VCRUNTIME140.dll: install or repair the appropriate Microsoft Visual C++ Redistributable instead.

Identify the exact error and its scope

Common messages include:

Failed to load library 'd3d9.dll'

The program can't start because d3d9.dll is missing from your computer.
Try reinstalling the program to fix this problem.

The code execution cannot proceed because d3d9.dll was not found.
Reinstalling the program may fix this.

C:\Windows\System32\d3d9.dll is either not designed to run on Windows
or it contains an error.

The application or DLL ...\d3d9.dll is not a valid Windows image.

The wording differs between Windows versions, applications, and loaders. Microsoft-hosted troubleshooting discussions document missing-library messages involving games and other applications, but the message alone does not identify the root cause.

Before changing anything, answer these questions:

1. Does every game or graphics application fail, or only one?
2. Does the error show a full path?
3. Is the named path System32, SysWOW64, the game folder, or another directory?
4. Did the issue begin after a Windows update, graphics-driver update, mod installation, antivirus scan, or power failure?
5. Does the message name d3d9.dll, or does it name a different DirectX or Visual C++ file?

This gives you the initial decision:

• Multiple applications fail and the Windows path is named: repair Windows.
• One game fails while Windows copies appear present: repair the game and inspect its local files.
• A local d3d9.dll exists beside the game executable: investigate a wrapper, mod, overlay, or damaged local installation.
• The error names d3dx9_43.dll or another helper DLL: install the legacy DirectX runtime.
• The file loads but the game reports Direct3D initialization failure: investigate the graphics driver, adapter, or device creation.

Check the Windows copies without replacing them

On 64-bit Windows, open File Explorer and enter each path in the address bar:

%WINDIR%\System32

Then check:

%WINDIR%\SysWOW64

Look for d3d9.dll in both locations.

System32 contains 64-bit system files on 64-bit Windows. SysWOW64 contains 32-bit system files, despite the name. A 32-bit game normally needs the copy in SysWOW64, while a 64-bit game needs the copy in System32.

On 32-bit Windows, the applicable system location is:

%WINDIR%\System32

To inspect a file:

1. Right-click d3d9.dll.
2. Select Properties.
3. Open the Details tab.
4. Check File description, Product name, Copyright, and File version.
5. Open the Digital Signatures tab if it is available.
6. Select the Microsoft signature and choose Details.

A legitimate file should identify Microsoft-related product information and have a valid signature. Do not treat a missing or unfamiliar version number as proof by itself. Windows servicing changes file versions and sizes, so an old version list from another computer is not a replacement source.

Also check the application directory. A d3d9.dll beside a game executable may be an intentional third-party wrapper from ReShade, ENB, DXVK, an overlay, or another graphics modification. Windows normally searches the application directory before the system directories, so a local copy can take precedence over Microsoft’s system copy. Microsoft documents this behavior in its DLL search order reference.

Do not delete a local file immediately. Move it to a temporary folder outside the game directory so it can be restored if necessary.

Fix 1: Install pending Windows updates

Windows updates service core operating-system components, including DirectX components. The standalone legacy DirectX installer does not replace the Windows Direct3D runtime.

To check for updates:

1. Open Start.
2. Select Settings.
3. Choose Windows Update.
4. Select Check for updates.
5. Choose Download & install if updates are offered.
6. Restart the computer, even if Windows does not immediately require a restart.
7. Test the affected program again.

Microsoft’s current instructions are available in its Windows Update guidance.

If the error began immediately after an update, the update may have exposed a driver, compatibility, or application-local problem. Continue with the repair steps below rather than repeatedly installing the legacy DirectX package.

Fix 2: Repair Windows with DISM and SFC

Use this path when:

• Several games or graphics applications fail.
• The message names %WINDIR%\System32\d3d9.dll or %WINDIR%\SysWOW64\d3d9.dll.
• The file is missing, unsigned, or visibly damaged.
• The problem began after a failed update, disk problem, system cleanup, or power interruption.
• Windows reports that the file is not a valid image or is not designed to run on Windows.

Microsoft recommends running DISM before SFC. DISM repairs the Windows component source that SFC uses to replace protected files.

Open an elevated terminal

1. Open Start.
2. Type Terminal.
3. Right-click Windows Terminal.
4. Select Run as administrator.
5. Approve the User Account Control prompt.

You can also use Command Prompt (Admin) if that is available on your Windows installation.

Run DISM

Enter this command exactly:

DISM.exe /Online /Cleanup-Image /RestoreHealth

Press Enter and wait for it to finish. The scan may appear to pause at a percentage for several minutes.

A successful result normally says that the restore operation completed successfully and that the operation completed successfully. Restarting immediately is not required yet. Run SFC next.

Run SFC

Enter:

sfc /scannow

Press Enter and wait until verification reaches 100 percent.

SFC may report one of several outcomes:

• Windows Resource Protection did not find any integrity violations: protected system files were not detected as damaged.
• Windows Resource Protection found corrupt files and successfully repaired them: restart Windows and test the application.
• Windows Resource Protection found corrupt files but was unable to fix some of them: restart, run DISM again, and repeat SFC. If the issue remains, continue to the escalation section.
• Windows Resource Protection could not start the repair service: restart Windows and run the command again from an elevated terminal.

Restart after SFC completes:

shutdown /r /t 0

You can also restart through the Start menu.

Microsoft’s complete procedure is in its System File Checker and DISM instructions.

If DISM says that source files cannot be found, do not download an individual DLL. Use a matching Windows installation source instead:

DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:C:\RepairSource\Windows /LimitAccess

C:\RepairSource\Windows is only a placeholder. Replace it with a valid repair source matching the installed Windows edition and build. Microsoft’s SFC and DISM instructions explain the source requirements.

When this repair works, the original Windows copy is restored through Windows servicing. Do not copy a file from another computer into System32 or SysWOW64.

Repeatedly comparing versions, guessing which component is damaged, and rerunning SFC and DISM without knowing what changed can be time-consuming. Outbyte PC Repair offers a scan that shows what it found; repair is performed by the full version, and the Microsoft DISM/SFC path remains the direct Windows repair method.

Fix 3: Repair the affected game or application

Use this path when only one game or application fails and the Windows copies appear legitimate.

A game installation may contain a damaged local DLL, an incomplete update, an altered configuration file, or a dependency removed by antivirus software. Use the launcher’s repair function before reinstalling the entire game.

Steam games

1. Open Steam.
2. Select Library.
3. Right-click the affected game.
4. Select Properties.
5. Open Installed Files.
6. Select Verify integrity of game files.
7. Wait for the process to finish.
8. Restart Steam and launch the game again.

The verification process may replace missing or damaged files. It may not remove every third-party mod or wrapper, so inspect the game folder afterward if the error continues.

Epic Games Launcher games

1. Open the Epic Games Launcher.
2. Select Library.
3. Find the game.
4. Select the three-dot menu beside it.
5. Choose Manage.
6. Select Verify.
7. Wait for verification to complete.
8. Launch the game again.

EA app games

1. Open the EA app.
2. Find the game in your library.
3. Select its three-dot menu.
4. Choose Repair.
5. Wait for the repair to finish.
6. Test the game again.

Other launchers and ordinary applications

Look for a menu named Verify, Repair, Scan and repair, or Validate files. Use the program’s official installer or launcher rather than replacing a DLL manually.

For a Windows application that supports Microsoft’s built-in repair controls:

1. Open Start.
2. Select Settings.
3. Choose Apps.
4. Select Installed apps.
5. Find the application.
6. Select its three-dot menu.
7. Choose Advanced options.
8. Select Repair.
9. Test the application.
10. If it still fails, use Reset if you are comfortable losing the application’s local settings.

If repair and verification do not help, uninstall the application, restart Windows, and reinstall it from its official installer. Back up saved games and configuration files first when the program stores them outside cloud synchronization.

Fix 4: Remove a local graphics wrapper, mod, or overlay

A local d3d9.dll is not automatically malware or a damaged Microsoft file. Graphics modifications often use that name deliberately to intercept Direct3D calls.

Examples include:

• ReShade
• ENB
• DXVK
• Older compatibility wrappers
• Frame-rate overlays
• Capture software
• GPU monitoring overlays
• Game-specific injectors

Use this path when the game folder contains d3d9.dll, especially if the problem began after installing or updating a mod.

1. Close the game and its launcher.
2. Open the game’s installation folder.
3. Locate d3d9.dll beside the game executable.
4. Look for related files with names such as dxgi.dll, dinput8.dll, configuration files, shader folders, or mod documentation.
5. Create a folder outside the game directory, such as Desktop\Game DLL Backup.
6. Move the local wrapper and its clearly related configuration files into that backup folder.
7. Do not move or delete the copies in %WINDIR%\System32 or %WINDIR%\SysWOW64.
8. Verify the game files through its launcher.
9. Launch the game without the wrapper.

If the game now starts, the wrapper or mod is the cause. Reinstall it only by following instructions for that exact game and executable. A 32-bit game needs a 32-bit wrapper, and a 64-bit game needs a 64-bit wrapper.

DXVK’s Windows guidance specifically warns users not to replace Windows DLLs in System32 or SysWOW64. A wrapper belongs beside the application that uses it, not in the Windows system directories.

If moving the local file changes nothing, restore it if the mod requires it and continue with the driver and diagnostic steps.

Fix 5: Check antivirus quarantine

Security software can remove an application-local d3d9.dll, particularly when the file belongs to an older game modification or injector. A missing local copy after a security scan does not prove that the file was safe.

To inspect Windows Security:

1. Open Start.
2. Type Windows Security.
3. Open the application.
4. Select Virus & threat protection.
5. Choose Protection history.
6. Review recent detections.
7. Expand any entry associated with the affected game or application.

Do not restore an unknown DLL merely because it has the familiar name d3d9.dll. First check:

• The full path of the quarantined file.
• Whether it was part of the original application installation.
• Whether the application vendor confirms the file.
• Whether the file has a valid digital signature.
• Whether the file appeared after installing a mod or unofficial patch.

If the file came from the official application installation and the security product identifies it as a false positive, use the security product’s documented restore or allow process, then verify the game files. If the Windows system copy is affected, use Windows Update and DISM/SFC instead of restoring a quarantined copy from an unknown source.

If malware is plausible, run a full scan. For a deeper check, use Microsoft Defender Offline:

1. Open Windows Security.
2. Select Virus & threat protection.
3. Choose Scan options.
4. Select Microsoft Defender Offline scan.
5. Select Scan now.
6. Save open work before Windows restarts.

Microsoft describes the process in its Defender Offline scanning guidance.

Fix 6: Install the legacy DirectX runtime only when the error names it

Install the legacy package when the error names a file such as:

d3dx9_43.dll

or:

xinput1_3.dll

Do not use it as the first repair for a literal d3d9.dll system-file error.

Microsoft provides two official choices:

• The DirectX End-User Runtime Web Installer, which uses dxwebsetup.exe.
• The DirectX End-User Runtimes June 2010 package, which uses directx_Jun2010_redist.exe.

The June 2010 package installs optional legacy components side by side, including D3DX libraries, XInput, XAudio, and XACT. It does not replace or upgrade the core Windows Direct3D runtime.

For the offline package:

1. Download directx_Jun2010_redist.exe from Microsoft.
2. Run the installer.
3. Choose an empty extraction folder when prompted.
4. Open that folder after extraction finishes.
5. Run DXSETUP.exe as an administrator.
6. Accept the license terms.
7. Allow the installation to complete.
8. Restart Windows.
9. Launch the game again.

If the installer reports an internal error, confirm that the original error actually names a legacy component. If it does, retry the offline package and inspect its installer logs. If Windows servicing also appears damaged, run DISM and SFC.

Installing this package will not repair a corrupt %WINDIR%\System32\d3d9.dll.

Fix 7: Check the graphics driver and Direct3D device

A program can show d3d9.dll as the faulting module even when the DLL itself loaded successfully. The actual failure may occur while Direct3D creates a device or communicates with the graphics adapter.

Typical clues include:

• “Failed to initialize Direct3D.”
• A black screen followed by a crash.
• A crash report naming d3d9.dll after a driver update.
• Failure only on one graphics adapter.
• Failure in a laptop power-saving mode.
• Failure through Remote Desktop or a virtual machine.
• Several games failing after a graphics-driver change.

Collect DirectX diagnostics

1. Press Win+R.
2. Type:

dxdiag

1. Press Enter.
2. Wait for the diagnostic tool to finish checking.
3. Select Save All Information.
4. Save the report somewhere easy to find.
5. Review the Display sections.

Look for the active adapter, driver information, feature levels, and any notes or errors. Microsoft explains how to use dxdiag in its DirectX diagnostic instructions.

Update or reinstall through Device Manager

1. Right-click Start.
2. Select Device Manager.
3. Expand Display adapters.
4. Right-click the graphics adapter.
5. Select Update driver.
6. Choose Search automatically for drivers.
7. Restart Windows if a driver is installed.
8. Test the game.

If the driver appears damaged:

1. Open Device Manager again.
2. Expand Display adapters.
3. Right-click the affected GPU.
4. Select Uninstall device.
5. Confirm the removal.
6. Restart Windows.
7. Install the current driver from the computer or graphics-card manufacturer.

Use the laptop manufacturer’s driver when the system uses switchable graphics, because the generic GPU package may not include the required power-management integration.

If the problem began directly after a driver update:

1. Open Device Manager.
2. Expand Display adapters.
3. Right-click the GPU.
4. Select Properties.
5. Open the Driver tab.
6. Select Roll Back Driver if the button is available.
7. Restart Windows.
8. Test the application again.

Microsoft’s Device Manager driver guidance covers updating, uninstalling, and rolling back drivers.

Manually finding the correct driver can mean comparing hardware models, notebook revisions, operating-system builds, and driver packages. Outbyte Driver Updater can scan and identify outdated drivers; its free scan shows what it found, while driver installation is performed by the full version, and the manufacturer’s driver remains the preferred source for compatibility-sensitive systems.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Fix 8: Use Windows Features only for features the game actually needs

Windows Features does not reinstall d3d9.dll. Do not enable random features as a substitute for repairing Windows.

Some older games separately require DirectPlay. If the game documentation specifically identifies DirectPlay:

1. Open Start.
2. Type Windows Features.
3. Select Turn Windows features on or off.
4. Expand Legacy Components.
5. Select DirectPlay.
6. Select OK.
7. Restart Windows if prompted.
8. Launch the game again.

DirectPlay is separate from the Direct3D 9 runtime. Enabling it will not replace a missing or corrupt d3d9.dll.

Fix 9: Restore the system after a recent change

If the error began immediately after installing a driver, application, update, or system utility, System Restore may reverse the change.

1. Press Win+R.
2. Enter:

rstrui.exe

1. Press Enter.
2. Select Next.
3. Choose a restore point dated before the problem began.
4. Select Scan for affected programs.
5. Review the programs and drivers that will be affected.
6. Select Close, then Next.
7. Confirm the restore.
8. Allow Windows to restart.

System Restore normally rolls back system files, registry settings, drivers, and installed programs without removing personal files. It does not replace a game’s local mod with the correct version, so verify the game afterward.

Microsoft’s System Restore documentation explains the process and limitations.

Why regsvr32 d3d9.dll is not a fix

Do not run:

regsvr32 d3d9.dll

regsvr32 is intended for DLLs that expose a DllRegisterServer function, usually COM or ActiveX components. Direct3D’s runtime DLL is loaded as a graphics API library and is not repaired by adding a registry entry.

The command will generally produce an error stating that DllRegisterServer was not found. That message does not mean Direct3D needs a different registration command. It means the command does not apply to this type of DLL. Microsoft documents the registration requirement through its DllRegisterServer reference.

What not to do

Do not download a random d3d9.dll

Individual DLL download sites may provide:

• The wrong Windows version.
• The wrong 32-bit or 64-bit architecture.
• A modified or malicious file.
• A file with incompatible dependencies.
• A copy that does not match Windows servicing.

Even a genuine copy from another Windows installation may not match your edition, build, architecture, signature, or component store.

Use Windows Update, DISM, SFC, the application’s official installer, or Microsoft’s official DirectX packages instead.

Do not copy a downloaded file into System32

Copying a DLL into System32 can create a version conflict, break system file verification, or cause applications to load an incompatible binary. On 64-bit Windows, copying the wrong architecture into either System32 or SysWOW64 can create additional loader errors.

Do not replace the Windows copy with a mod wrapper

A ReShade, ENB, or DXVK d3d9.dll belongs in the application directory when its documentation requires one. It is not a replacement for the Windows system component.

Do not assume a crash report proves the DLL is corrupt

Event Viewer or a crash report may name d3d9.dll because the failure surfaced while Direct3D was creating a device. The graphics driver, adapter mode, overlay, shader, or application code may be responsible.

Do not confuse Visual C++ with DirectX

Visual C++ Redistributables and DirectX legacy components are separate technologies. Installing Visual C++ will not repair d3d9.dll, and installing DirectX will not repair MSVCP140.dll.

If the error names Visual C++ files, use Microsoft’s supported Visual C++ Redistributable downloads. A 32-bit application may require the x86 package even on 64-bit Windows.

If the error says “not designed to run on Windows”

Messages containing “not designed to run on Windows,” “not a valid Windows image,” or error code 0xc000012f indicate a bad-image or compatibility problem rather than a simple missing file.

Check these items in order:

1. Record the complete path in the error.
2. Determine whether the file is in the game folder, System32, or SysWOW64.
3. Inspect the file’s publisher and digital signature.
4. Remove recently installed mods and overlays from the application folder.
5. Confirm that the application architecture matches the DLL.
6. Run DISM followed by SFC.
7. Check whether the error began after a graphics-driver or Windows update.
8. Verify or reinstall the affected application.

Do not rename the DLL or substitute one from another Windows release.

If every normal repair fails

Collect the information below before making further changes:

• The complete error text.
• The full path displayed by the error.
• The affected application and launcher.
• Whether other games or graphics applications fail.
• Windows edition, build, and architecture.
• The saved dxdiag report.
• Event Viewer details from Windows Logs → Application.
• The faulting module and exception code.
• Whether copies exist in System32, SysWOW64, and the application folder.
• Whether the issue remains with mods and overlays disabled.
• The date of any recent Windows, driver, antivirus, or application change.

If Windows remains damaged after DISM and SFC, Windows 11 may provide a repair reinstall:

1. Open Start.
2. Select Settings.
3. Choose System.
4. Select Recovery.
5. Find Fix problems using Windows Update.
6. Select Reinstall now if the option is available.
7. Follow the prompts.

Microsoft says this process reinstalls the current Windows version while preserving applications, files, and settings. Availability depends on the Windows installation and update state. See Microsoft’s Windows repair reinstall instructions.

A matching in-place repair using Windows installation media is a further possibility. Back up important files first and use installation media that matches the installed Windows edition and architecture. Microsoft provides installation-media repair guidance.

Frequently asked questions

Is d3d9.dll the same as d3dx9_43.dll?

No. d3d9.dll is the core Direct3D 9 runtime component supplied with Windows. d3dx9_43.dll is an optional legacy helper library installed by the DirectX End-User Runtime package.

Does DirectX 12 replace Direct3D 9?

No. Windows can report DirectX 12 while still providing older Direct3D runtime interfaces. The DirectX version shown by dxdiag does not list every optional legacy library installed.

Should I install the June 2010 DirectX package for d3d9.dll?

Usually not. Install it when the error names a legacy file such as d3dx9_43.dll, xinput1_3.dll, or xaudio2_7.dll. For a literal d3d9.dll system-file error, repair Windows and investigate the affected application.

Where is d3d9.dll on 64-bit Windows?

The 64-bit copy is normally in:

%WINDIR%\System32\d3d9.dll

The 32-bit copy is normally in:

%WINDIR%\SysWOW64\d3d9.dll

The directory names are counterintuitive because System32 contains 64-bit system files on 64-bit Windows.

Why does the file exist if the program says it is missing?

The program may need the opposite architecture, may be loading a local wrapper first, or may actually be failing because a dependency of d3d9.dll is missing. The file may also exist but be corrupt, unsigned, or incompatible.

Can I copy d3d9.dll from another computer?

No. Windows versions, architectures, servicing levels, signatures, and dependencies may differ. Use DISM, SFC, Windows Update, or the official application installer.

Should I register d3d9.dll with regsvr32?

No. Direct3D’s runtime DLL is not a COM or ActiveX component that should be manually registered.

Why does Event Viewer name d3d9.dll when the driver is the problem?

The failure may occur during Direct3D device creation or driver communication. The DLL can be the location where the failure surfaced without being damaged itself.

What is the correct fix if only one game fails?

Verify or repair the game files, inspect the game folder for a local d3d9.dll, temporarily remove mods and overlays, and reinstall the game if necessary. If other games work and the Windows copies are legitimate, a Windows-wide DirectX reinstall is unlikely to be the right first step.

What is the correct fix if every game fails?

Install pending Windows updates, run DISM followed by SFC, inspect dxdiag, and update or roll back the graphics driver. If Windows continues to report system-file corruption, use System Restore or a Windows repair reinstall.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.