d3dx9_40.dll Missing: Rebuild the Legacy DirectX Runtime

If d3dx9_40.dll is missing, not found, or could not be loaded, install the official Microsoft DirectX End-User Runtime rather than downloading the individual DLL. d3dx9_40.dll is a legacy Direct3D 9 Extensions component, so a computer with DirectX 11 or DirectX 12 can still lack it.

The safest repair order is:

1. Run the game’s own DXSETUP.exe, if it includes one.
2. Install the official DirectX End-User Runtimes (June 2010).
3. Verify or repair the affected game.
4. Check whether the application and runtime architecture match.
5. Investigate antivirus quarantine, installer failures, Windows corruption, or driver problems only if the normal runtime installation does not work.

Do not download d3dx9_40.dll from a random DLL website, copy d3dx9_43.dll over it, or run regsvr32 against it. Those actions can add the wrong architecture, the wrong D3DX version, a damaged file, or an app-local copy that overrides the correct installation.

As an Amazon Associate I earn from qualifying purchases.

What d3dx9_40.dll actually is

d3dx9_40.dll is a Microsoft Direct3D 9 Extensions runtime DLL. It belongs to the optional, versioned D3DX portion of DirectX rather than the modern DirectX core built into Windows.

The filename matters. The _40 identifies a particular D3DX9 interface version used by software built against that release. d3dx9_40.dll, d3dx9_41.dll, d3dx9_42.dll, and d3dx9_43.dll are separate runtime files. An application that imports _40 does not become compatible merely because _43 is present.

Microsoft explains that D3DX components are version-specific and can be installed side by side. The D3DX documentation and DirectX installation documentation distinguish these optional components from the DirectX core runtime.

This is why the file may be described in different ways:

• It is a Microsoft DirectX file.
• It may be installed by a game or graphics application.
• It may be stored beside the game executable as a private application copy.
• It may also be installed into the Windows system directories by the DirectX redistributable.
• It is not a Visual C++ runtime file.
• It is not a .NET Framework file.
• It is not normally supplied by a graphics-driver package.

The program that reports the error is often only the program that needs the file. The missing component may never have been installed, may have been removed by an incomplete game installation, or may have been replaced by a bad private copy.

Why DirectX 11 or DirectX 12 does not guarantee this file

The DirectX version shown by Windows describes the operating system’s main DirectX support. It does not mean that every optional, older DirectX SDK component is installed.

Older games commonly depend on side-by-side files from the legacy DirectX End-User Runtime, including D3DX, XAudio 2.7, XInput 1.3, XACT, and related components. Installing a newer DirectX core does not automatically recreate every older optional DLL.

The June 2010 redistributable adds those legacy components without downgrading or replacing the computer’s main DirectX version. In other words, installing it is normally compatible with a system that already uses DirectX 11 or DirectX 12.

Fix 1: Run the game’s bundled DXSETUP.exe

Time needed: 5–15 minutes

A game’s own DirectX installer is usually the most targeted repair because it was packaged with the game and may contain the exact optional components expected by that release.

Find the bundled installer

Look inside the game’s installation folder for one of these locations or names:

• DirectX
• Jun2010
• _CommonRedist\DirectX
• Redist
• Redistributable
• DXSETUP.exe

On Steam, open the game’s library entry, choose Manage, then Browse local files. Search the opened folder for DXSETUP.exe.

Some Steam games store the installer in a shared location resembling:

Steam\steamapps\common\Steamworks Shared\_CommonRedist\DirectX\Jun2010\DXSETUP.exe

The exact folder can differ between games.

Run the installer

1. Right-click DXSETUP.exe.
2. Select Run as administrator.
3. Accept the license terms.
4. Let the installer complete.
5. Restart Windows.
6. Launch the affected game again.

Do not run DXSETUP.exe from inside an archive. If the game provides a compressed redistributable, extract it first and then run the installer from the extracted folder.

If the installer reports that the components are already installed, restart Windows and test the game. If the error remains, continue with the full Microsoft redistributable and game-file verification below.

Fix 2: Install the official June 2010 DirectX redistributable

Time needed: 10–20 minutes

The most reliable general repair is Microsoft’s DirectX End-User Runtimes (June 2010). This is the full redistributable package, not a download of one isolated DLL.

Install the offline package

1. Download directx_Jun2010_redist.exe from Microsoft.
2. Create a temporary folder such as:

text
C:\DXRedist

1. Run the downloaded executable.
2. When it asks where to extract the files, select C:\DXRedist.
3. Open the extracted folder.
4. Right-click DXSETUP.exe.
5. Select Run as administrator.
6. Complete the DirectX setup wizard.
7. Restart Windows.
8. Try the game or application again.

The extraction folder is only a staging location. Do not extract the package directly into C:\Windows\System32 or C:\Windows\SysWOW64, and do not manually copy its cabinet files into either directory.

DXSETUP.exe examines the installed optional DirectX components and installs what is needed. That is safer than checking for one filename and copying a replacement by hand.

Use the web installer when appropriate

Microsoft also provides the DirectX End-User Runtime Web Installer, downloaded as dxwebsetup.exe.

Use it when:

• The computer has reliable internet access.
• You want the smaller installer.
• You do not need a local copy for another computer.
• The web installer itself has not already failed.

To use it:

1. Download dxwebsetup.exe from Microsoft.
2. Right-click it and select Run as administrator.
3. Follow the wizard.
4. Decline any unrelated optional software offered by the installer, if shown.
5. Complete setup.
6. Restart Windows.
7. Launch the affected application.

Prefer the full June 2010 redistributable when the web installer fails, the computer has unreliable internet access, or you want all setup files available locally.

The package version shown on Microsoft’s download pages identifies the redistributable package. It should not be confused with the internal version of an individual D3DX DLL.

Fix 3: Verify or repair the game files

Time needed: 5–30 minutes, depending on the game size

If the error affects only one game, the game installation may be incomplete or a game-local DirectX file may have been damaged. A private DLL beside the game executable can take precedence over the copy installed in Windows.

Steam

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

If the game has a bundled DirectX installer, run that after verification.

Epic Games Launcher

1. Open the Epic Games Launcher.
2. Select Library.
3. Find the affected game.
4. Select the three dots beside the game.
5. Choose Manage.
6. Select Verify.
7. Wait for the process to complete.
8. Start the game again.

GOG or another launcher

Open the game’s management menu and use its installed-file verification, repair, or validate command. The wording can differ between launcher versions. If no repair command exists, use the launcher’s reinstall option or the publisher’s repair instructions.

A verification process can restore a game-local copy, but it does not replace the official system-wide DirectX repair when the legacy runtime was never installed. If verification reports no problems and the DLL error remains, run DXSETUP.exe from the game folder or install Microsoft’s June 2010 package.

Fix 4: Check the 32-bit and 64-bit architecture

Time needed: 5–10 minutes

A file can exist on the disk and still be unusable because it has the wrong architecture.

On 64-bit Windows:

• %windir%\System32 contains 64-bit system files.
• %windir%\SysWOW64 contains 32-bit system files.
• A 32-bit game generally needs the x86 DirectX runtime.
• A native 64-bit game generally needs the x64 DirectX runtime.

The directory names are counterintuitive. System32 is the 64-bit directory on 64-bit Windows, while SysWOW64 contains 32-bit files for the Windows 32-bit compatibility layer. Microsoft documents this behavior in its file-system redirector documentation.

On 32-bit Windows, the 32-bit runtime belongs in %windir%\System32, and SysWOW64 normally does not exist.

What to do

Install the complete official DirectX redistributable rather than trying to decide which individual file to copy. The installer handles the architecture-specific components.

If the file exists beside the game executable, that private copy may be:

• The wrong architecture.
• Corrupted.
• From a different D3DX release.
• Incomplete because its dependencies are missing.
• A replacement copied from an untrusted source.

Do not immediately delete files from System32 or SysWOW64. If you find a suspicious app-local copy beside the game, make a backup or rename it temporarily, then verify the game files and run the official DirectX setup.

For a more precise architecture check, inspect the game executable with a trusted application-analysis tool or consult the game publisher’s technical documentation. A 32-bit game commonly runs through Windows’ 32-bit compatibility layer even on a 64-bit installation.

Fix 5: Handle “not designed to run on Windows” or “contains an error”

Time needed: 10–30 minutes

An error such as this points to more than simple absence:

d3dx9_40.dll is either not designed to run on Windows or it contains an error.

Common explanations include:

• A corrupted DLL.
• A wrong-architecture DLL.
• An incompatible private copy beside the game.
• A damaged installation package.
• A dependent component that cannot load.
• Security software blocking the program.

Use this order:

1. Close the game and its launcher.
2. If a manually copied d3dx9_40.dll exists beside the game executable, rename it rather than deleting it immediately. For example:

text
d3dx9_40.dll.old

1. Verify the game files through Steam, Epic, GOG, or the relevant launcher.
2. Run the game’s bundled DXSETUP.exe.
3. If necessary, install the official June 2010 DirectX redistributable.
4. Restart Windows.
5. Test the game again.

If the error continues, check whether the application is 32-bit or 64-bit and whether the installed runtime matches it. Also check the game’s launcher, mod loader, compatibility layer, or overlay. A launcher can load a different executable or DLL search path than the game itself.

Fix 6: Check Windows Security quarantine

Time needed: 5–15 minutes

If the file disappeared after an antivirus event, inspect Windows Security before reinstalling repeatedly.

1. Open Start.
2. Search for Windows Security.
3. Open Virus & threat protection.
4. Select Protection history.
5. Expand the relevant detection.
6. Review the file path and detection details.
7. Restore the file only if you can verify that it came from the official Microsoft DirectX package or the trusted game installation.
8. Reinstall the official runtime if necessary.
9. Run a full security scan.

Microsoft’s Protection History guidance warns that restoring or allowing a detected file can expose the computer if the detection is genuine.

The filename alone does not prove that a particular copy is safe. A file in a game directory created by the official installer is a different situation from a DLL found in a random download folder, temporary directory, or unofficial mod package.

If Defender detects the file again, do not keep allowing it without understanding the detection. Remove the untrusted copy, scan the computer, and reinstall the runtime from Microsoft.

Fix 7: Repair Windows components with DISM and SFC

Time needed: 15–45 minutes

DISM and SFC are appropriate when Windows servicing is damaged, protected system files are corrupt, or the DirectX installer itself cannot work correctly. They are not normally the source of d3dx9_40.dll, because this DLL is an optional legacy DirectX component rather than a standard protected Windows system file.

Run DISM before SFC, as Microsoft recommends in its System File Checker guidance.

1. Open Start.
2. Search for Command Prompt.
3. Right-click Command Prompt.
4. Select Run as administrator.
5. Approve the User Account Control prompt.
6. Run:

cmd
DISM.exe /Online /Cleanup-Image /RestoreHealth

1. Wait for it to finish.
2. Then run:

cmd
sfc /scannow

1. Wait until the scan reaches 100 percent.
2. Restart Windows.
3. Run the official DirectX installer again.

Possible SFC results include:

• No integrity violations: Windows protected files were not found to be damaged.
• Corrupt files were found and repaired: restart and test again.
• Corrupt files were found but could not all be repaired: inspect the result, restart, and consider additional Windows repair steps.

Do not expect SFC to download or recreate every optional D3DX file. If the scan succeeds but the game still reports d3dx9_40.dll missing, install the DirectX redistributable.

Repeating SFC and DISM without knowing what changed can make troubleshooting slow and unclear. Outbyte PC Repair can scan for the Windows issues it identifies and show what needs attention, while repairs are performed by the full version; it is optional, and reinstalling a game remains the definitive fix when that game owns the damaged installation.

Fix 8: Install Windows updates, but do not rely on them for this DLL

Time needed: 10–30 minutes

Windows Update can repair operating-system components and installer prerequisites, but it does not normally supply every optional D3DX side-by-side component.

1. Open Start.
2. Select Settings.
3. Open Windows Update.
4. Select Check for updates.
5. Install available updates.
6. Restart Windows.
7. Run the official DirectX installer again.

Use Windows Update as supporting maintenance, not as a replacement for the DirectX End-User Runtime.

Fix 9: Do not use Windows Features as a substitute for DirectX setup

Time needed: 2–5 minutes to check

Windows Features is not where the normal d3dx9_40.dll repair is installed.

To inspect it:

1. Open Start.
2. Search for Turn Windows features on or off.
3. Open the result.
4. Review the available features.

Do not randomly enable or disable features to resolve this DLL error. Some older games may separately require a Windows feature such as DirectPlay, but enabling that feature does not install d3dx9_40.dll. Use the game’s documented requirements for any separate legacy feature.

The correct source for this DLL is the game’s bundled DirectX setup or Microsoft’s DirectX End-User Runtime.

Fix 10: Update or reinstall the graphics driver only for related graphics failures

Time needed: 10–30 minutes

A graphics-driver reinstall is not the primary fix for a missing d3dx9_40.dll. It becomes relevant when the error changes to a Direct3D initialization failure, device-creation failure, black screen, rendering corruption, or driver crash after the runtime has been installed successfully.

Check the driver in Device Manager

1. Press Win + X.
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.

For the most appropriate driver, use the support channel for the computer manufacturer or graphics-card manufacturer. A laptop may require a customized driver from its computer manufacturer.

Reinstall the driver

If the driver is clearly damaged:

1. Open Device Manager.
2. Expand Display adapters.
3. Right-click the graphics adapter.
4. Select Uninstall device.
5. Confirm the removal.
6. Restart Windows.
7. Install the current driver supplied for the computer or graphics adapter.
8. Restart again.
9. Test the game.

Do not uninstall the display adapter as the first response to a filename-specific D3DX error. Install the legacy runtime first.

Finding the correct driver manually can involve checking hardware identifiers, Windows versions, laptop variants, and clean-install options. Outbyte Driver Updater can scan for the driver issues it identifies and show which updates are available, while installation is handled by the full version; it is optional, and it will not replace the DirectX runtime when that is the actual cause.

Fix 11: Use System Restore when the timing points to a system change

Time needed: 20–45 minutes

System Restore is worth considering when the game worked previously and the error began immediately after a specific update, cleanup operation, driver installation, security event, or other system change.

1. Press Win + R.
2. Enter:

text
rstrui.exe

1. Press Enter.
2. Select an appropriate restore point from before the problem began.
3. Choose Scan for affected programs, if available.
4. Review the affected applications and drivers.
5. Start the restore.
6. Let Windows restart and complete the process.
7. Test the game.

System Restore rolls back system files, settings, and installed programs but normally does not remove personal files. Microsoft describes the process in its System Restore guidance.

A restore does not replace the need to install the official DirectX runtime if the component was never installed. Use it when there is a clear before-and-after event, not as the first response to every missing-DLL message.

Fix 12: Resolve a DirectX installer internal error

Time needed: 15–45 minutes

The installer may report:

An internal system error occurred. Please refer to DXError.log and DirectX.log in your Windows folder to determine the problem.

The message is generic. Do not apply a universal registry hack based on it.

Use this repair sequence:

1. Download a fresh copy of Microsoft’s June 2010 redistributable.
2. Save it to a local folder.
3. Create a new extraction folder such as:

text
C:\DXRedist

1. Extract the package there.
2. Right-click DXSETUP.exe.
3. Select Run as administrator.
4. Temporarily close unnecessary launchers and background utilities.
5. Confirm that security software is not blocking the installer.
6. Make sure the system drive has free space.
7. Run DISM and SFC if Windows components may be damaged.
8. Restart Windows.
9. Run DXSETUP.exe again.

If setup still fails, inspect:

%windir%\DXError.log
%windir%\DirectX.log

These logs may point to a damaged cabinet file, insufficient permissions, locked files, security software interference, storage problems, or an incompatibility in the legacy setup environment.

The DirectX setup documentation recommends allowing DXSETUP.exe to determine which optional components need installation. File-existence checks and manual copying cannot provide the same installation context.

Common causes, ranked by troubleshooting priority

The following order is a practical priority list, not a measured percentage distribution.

Likely cause	What it means	Correct response
Legacy DirectX was never installed	The game expects an optional D3DX9 component that Windows does not guarantee	Run the game’s DXSETUP.exe or install Microsoft’s June 2010 redistributable
Wrong architecture	A 32-bit game cannot use only a 64-bit runtime, and a 64-bit application cannot use only the x86 file	Install the complete official runtime and avoid manual copying
Incomplete game installation	A failed installation, update, mod, or disk problem removed a game-local file	Verify or repair the game files
Corrupt private copy	A DLL beside the executable overrides a working system copy	Rename the suspicious app-local copy, verify files, and run official setup
Failed DirectX installation	The installer did not complete or could not write its components	Use a fresh full redistributable, elevation, and the DirectX logs
Antivirus quarantine	Security software removed or blocked a copy	Review Protection History, restore only a trusted file, scan, and reinstall officially
Windows component corruption	Servicing or protected system files are damaged	Run DISM, then SFC, and retry DirectX setup
Outdated Windows	Updates or servicing prerequisites are missing	Run Windows Update, restart, and install DirectX
Graphics-driver failure	The runtime is installed but Direct3D initialization fails	Update or reinstall the graphics driver
Malware or storage failure	Files are being modified or disappearing for a broader reason	Run security scans, check storage health, and investigate other changed files
A recent system change	The problem started after an update, cleanup, or installation	Consider System Restore if a suitable restore point exists

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

What not to do

Do not download the isolated DLL

Random DLL download sites can provide:

• The wrong D3DX version.
• The wrong 32-bit or 64-bit architecture.
• A corrupt or modified file.
• A file with missing dependencies.
• An app-local copy that overrides the correct runtime.
• Malware disguised as a familiar filename.

The safe sources are the affected game’s own redistributable and Microsoft’s DirectX End-User Runtime Web Installer or June 2010 redistributable.

Do not replace _40 with _43

d3dx9_43.dll is not a drop-in replacement for d3dx9_40.dll. The numbered files represent separate versioned interfaces. Copying one over another can leave the original import unresolved or introduce a new loader error.

Do not run regsvr32

regsvr32 is intended for self-registering COM and ActiveX components. A Direct3D runtime DLL is installed by the DirectX redistributable and is not repaired by manually registering it.

A command such as this is therefore not a solution:

regsvr32 d3dx9_40.dll

It may produce an error stating that the module was loaded but the entry point was not found, or that the module is not self-registerable. That does not mean another regsvr32 variation will repair the runtime.

Do not install Visual C++ or .NET for this filename

Visual C++ errors usually name files such as MSVCP*.dll or VCRUNTIME*.dll. .NET errors identify .NET assemblies or framework components. Neither package normally installs d3dx9_40.dll.

Install Visual C++ only when the error specifically identifies a Visual C++ runtime file. Install or repair .NET only when the affected program requires it for a separate reason.

Do not delete system DLLs first

Deleting files from System32 or SysWOW64 can create additional failures and make diagnosis harder. Use the official installer, verify the game, and rename suspicious app-local files only when you have a clear reason.

Error-specific diagnosis

“The program cannot start because d3dx9_40.dll is missing”

Install the game’s bundled DirectX runtime or Microsoft’s June 2010 redistributable. Restart Windows and test again.

If the error remains, verify the game files and check whether the game is 32-bit or 64-bit. A file existing in one system directory does not prove that the application can load it.

“The code execution cannot proceed because d3dx9_40.dll was not found”

This generally indicates that the loader could not find a usable copy in the application directory or normal system search locations.

Check for:

• A missing legacy runtime.
• A wrong-architecture installation.
• A damaged game-local copy.
• A launcher or mod loader using a different executable.
• A dependent DLL that is also missing.

Run the official setup rather than placing a downloaded DLL beside the executable.

“The file exists, but the program still says it is missing”

Possible explanations include:

• The game is 32-bit and only the x64 file is present.
• The game is 64-bit and only the x86 file is present.
• The file is corrupt.
• A dependent DLL is missing.
• Security software is blocking access.
• The game is loading a different copy from its own directory.
• A mod loader or compatibility layer changed the DLL search path.

Microsoft documents the normal DLL search order. The application directory is searched early, which is why a bad private copy can override a correct installed runtime.

The problem affects only one game

Repair that game first. Verify its files, run its bundled DirectX installer, disable or remove recently added mods for testing, and inspect the game directory for an unexpected private DLL.

If other Direct3D 9 games work normally, a game-specific installation problem is more likely than a system-wide graphics-driver failure.

The problem began after an update, cleanup, or mod

Treat the timing as evidence. Reverse the most recent relevant change:

• Verify game files after an update.
• Remove or disable the newly installed mod.
• Check antivirus Protection History after a quarantine event.
• Use System Restore if a suitable restore point exists.
• Reinstall the official DirectX runtime if the optional component was removed.

Frequently asked questions

Is d3dx9_40.dll a Windows file or a game file?

It is a Microsoft DirectX runtime file. A game may install it, use an app-local copy, or depend on the copy installed by Microsoft’s DirectX redistributable. Calling it a generic Windows DLL is misleading because Windows does not guarantee that every optional D3DX component is present.

Will DirectX 12 install this file?

Not necessarily. DirectX 12 support does not guarantee the presence of older, optional D3DX9 files. Install the legacy DirectX End-User Runtime when an older program requests this filename.

Should I install both the web installer and the June 2010 package?

Usually one is enough. Start with the game’s own DXSETUP.exe. If that is unavailable, use the web installer with reliable internet access or the full June 2010 package when you want a local, complete redistributable.

Does the June 2010 package downgrade DirectX?

No. It adds legacy side-by-side components. It does not replace the computer’s main DirectX version.

Where should I put the file?

Do not manually choose a folder. Let DXSETUP.exe install the correct architecture. On 64-bit Windows, Windows uses System32 for 64-bit system files and SysWOW64 for 32-bit system files, but those names are not instructions to copy a downloaded DLL manually.

Why does copying d3dx9_43.dll not work?

The _40 and _43 files represent different versioned interfaces. Software importing _40 specifically looks for that interface and does not treat _43 as an equivalent replacement.

Will Visual C++ Redistributable fix it?

No. Visual C++ provides a different family of runtime libraries. Use it only when the error names a Visual C++ DLL.

Will reinstalling my graphics driver fix it?

Not normally. A driver reinstall is relevant to Direct3D initialization failures, rendering problems, or driver crashes after the missing runtime has been repaired.

Should I use System File Checker first?

Not usually. Install the official DirectX runtime first. Use DISM and SFC when Windows servicing or protected system files appear damaged, especially if the DirectX installer itself fails.

What information should I provide if none of this works?

Record:

• The exact error text.
• The name and version of the game or application.
• Whether it affects one program or several.
• Whether the program is 32-bit or 64-bit.
• Whether the game has a bundled DXSETUP.exe.
• Which official DirectX package you ran.
• Whether game-file verification found anything.
• The contents or relevant error lines from %windir%\DXError.log and %windir%\DirectX.log.
• Any recent update, mod installation, cleanup operation, antivirus quarantine, or driver change.
• Whether the file exists beside the game executable, in System32, or in SysWOW64.

That information separates a missing optional runtime from a wrong-architecture DLL, corrupted game installation, blocked installer, or broader Windows problem.

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.