d3dx10.dll Is Missing: Causes, Fixes and Safe Sources on Windows

If Windows says d3dx10.dll is missing, install the official DirectX End-User Runtimes (June 2010), preferably by running the game’s bundled DXSETUP.exe first. If the game still cannot start, confirm the exact filename, repair the game files, check whether it needs the x86 side-by-side runtime, and investigate antivirus quarantine before trying broader Windows repairs.

What this file actually does

d3dx10.dll is Microsoft Direct3D 10 Extensions, usually called D3DX10. It is a user-mode utility library from the legacy DirectX SDK that older games and graphics applications may load during startup.

As an Amazon Associate I earn from qualifying purchases.

The file is part of Microsoft DirectX for Windows and has the internal description “Microsoft Direct3D.” Microsoft documents d3dx10.dll as the retail D3DX10 component and d3dx10d.dll as its debug counterpart. The retail file is intended for normal applications and games; the debug file is associated with development and testing. Microsoft’s Direct3D documentation identifies the D3DX10 libraries and their redistributable status.

This distinction matters because d3dx10.dll is not:

• A graphics-card driver
• The core Direct3D runtime built into Windows
• A Visual C++ runtime
• A .NET Framework file
• A general-purpose Windows system file
• A file that should normally be registered with regsvr32

Windows 10 and Windows 11 include modern DirectX components, but optional legacy D3DX libraries are installed separately. A computer can report DirectX 11 or DirectX 12 while still lacking the D3DX10 files required by an older game. Microsoft describes D3DX9, D3DX10, and D3DX11 as optional legacy components that are not supplied through ordinary Windows Update or service packs. Microsoft’s DirectX installation guidance explains this side-by-side design.

The file is available in both 32-bit and 64-bit forms. Cataloged metadata for this filename identifies builds listed as version 9.16.843.0, with the 32-bit file shown at approximately 0.42 MB and the 64-bit file at approximately 0.45 MB. Those details are not a substitute for installing the correct Microsoft runtime package. The exact file requested by the application and its architecture matter more than a displayed file size.

Diagnose the exact error before repairing anything

The most important first step is to copy the filename exactly as Windows displays it.

You may see wording such as:

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

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

There was a problem starting d3dx10.dll.
The specified module could not be found.

You may instead see a versioned filename:

Missing DLL: d3dx10_42.dll

or:

Invalid License: Reason Code = Missing DLL: [d3dx10_35.dll]

d3dx10.dll, d3dx10_33.dll, d3dx10_37.dll, d3dx10_42.dll, and d3dx10_43.dll are different filenames. They belong to the same legacy D3DX10 family, but they are not interchangeable.

A game built against d3dx10_37.dll is asking for that particular side-by-side version. Renaming d3dx10_43.dll will not reliably satisfy it, and copying the unsuffixed d3dx10.dll into the game folder will not repair a request for d3dx10_42.dll.

Exact wording also varies between Windows versions, launchers, and application loaders. Treat the displayed filename as the authoritative clue.

Causes and the appropriate fix

What you observe	Most likely cause	Correct first action
The error appears immediately after installing an older game	Legacy DirectX component was never installed	Run the game’s bundled DXSETUP.exe
Several D3DX, XAudio, or XInput files are missing	Legacy DirectX runtime is incomplete	Install the June 2010 DirectX redistributable
Only one game fails	Damaged or incomplete game installation	Verify, repair, or reinstall that game
The filename has a suffix such as _42 or _43	The application needs a specific side-by-side version	Install the full legacy runtime and preserve the exact filename
The game worked until an update or executable change	Antivirus may have quarantined a local DLL	Check Windows Security Protection history
The error says “not designed to run,” shows 0xc000007b, or changes after copying a file	Architecture mismatch or corrupted dependency	Remove the copied file, repair the official installation, and check x86/x64 requirements
DirectX setup reports an internal system error	Installer, permissions, or Windows component problem	Use the offline package, inspect logs, then repair Windows if appropriate
Games also show rendering or driver initialization failures	Possible graphics-driver problem	Check DxDiag and repair the display driver

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

Many older games include the correct DirectX prerequisite installer in their own installation files. This is often the best first repair because the game publisher may have packaged the dependencies expected by that particular release.

Steam games

1. Open Steam.
2. Select Library.
3. Right-click the affected game.
4. Choose Properties.
5. Select Installed Files.
6. Click Browse.
7. Look for a folder named DirectX, DXRedist, _CommonRedist, Redist, or a similar prerequisite folder.
8. Open the DirectX folder.
9. Run DXSETUP.exe.
10. If Windows asks for permission, select Yes.
11. Accept the license terms and allow setup to complete.
12. Restart Steam and launch the game again.

If the game is installed under a protected location, right-click DXSETUP.exe, choose Properties, open the Compatibility tab, select Run this program as an administrator, and click Apply. You can also right-click the file and choose Run as administrator when available.

Epic Games games

1. Open the Epic Games Launcher.
2. Select Library.
3. Find the affected game.
4. Click the three-dot menu beside the game.
5. Choose Manage.
6. Select Open Install Location.
7. Search the installation folder for DXSETUP.exe.
8. Run it with administrative permission.
9. Restart the launcher and test the game.

Standalone games and applications

Open the folder where the application is installed and search for:

• DXSETUP.exe
• DirectX
• Redist
• Redistributables
• _CommonRedist
• Prerequisites

Run the DirectX setup program if you find one. Do not run an executable merely because its name contains “DLL” or “setup”; confirm that it is inside the original application’s trusted installation directory.

How to tell whether this worked

The repair succeeded if the application starts without the missing-file message. It is also a good sign if the error changes from a missing D3DX file to a different, clearly named prerequisite. That means Windows has moved past the original missing library and is now reporting the next dependency.

If the bundled installer is absent or fails, continue with the official Microsoft package below.

Fix 2: Install the official DirectX End-User Runtimes

The standard end-user repair package is Microsoft’s DirectX End-User Runtimes (June 2010). It installs legacy side-by-side components, including D3DX, XAudio, XInput, XACT, and related libraries. It does not downgrade DirectX 11 or DirectX 12 and does not replace the core DirectX version reported by Windows.

Microsoft provides two packages.

• The DirectX End-User Runtimes (June 2010) offline package uses the filename directx_Jun2010_redist.exe. Microsoft’s download page currently lists version 9.29.1974.1 and a download of approximately 95.6 MB.
• The DirectX End-User Runtime Web Installer uses the filename dxwebsetup.exe. Microsoft’s page currently lists version 9.29.1974.1.

The offline package is the better choice when the computer is offline, the web installer fails, or more than one legacy DirectX file is missing.

Install the offline package

1. Download directx_Jun2010_redist.exe from Microsoft’s Download Center.
2. Save it to a location such as Downloads.
3. Right-click the downloaded file.
4. Select Run as administrator.
5. Accept the license agreement.
6. When asked for an extraction folder, choose a short temporary path such as C:\DirectXTemp.
7. Open the extraction folder.
8. Locate DXSETUP.exe.
9. Right-click DXSETUP.exe.
10. Select Run as administrator.
11. Accept the terms and allow the installer to finish.
12. Restart Windows.
13. Launch the affected program again.

The first executable extracts the package. It does not, by itself, install every runtime file. You must open the extracted folder and run DXSETUP.exe.

If the installer says that the required components are already installed, restart Windows and test the application anyway. If the problem remains, repair or verify the application files because a game-local copy may be damaged.

Install the web installer

1. Download dxwebsetup.exe from Microsoft’s official page.
2. Right-click the file.
3. Choose Run as administrator.
4. Accept the license terms.
5. Allow the installer to download the required components.
6. Restart the computer when setup finishes.
7. Launch the game or application again.

The web installer needs access to Microsoft’s download servers. Use the offline package if the computer has restricted internet access or if the web installer repeatedly fails.

What success looks like

A successful installation normally ends without a missing-DLL error and does not require you to copy a file manually. The DirectX package may install several legacy files even when the original message mentioned only one.

Do not judge success by running dxdiag and looking for a change from DirectX 11 to DirectX 12. That number describes the core DirectX runtime and does not list every optional D3DX library.

Fix 3: Verify or repair the game installation

If the runtime is installed but only one game still reports a missing file, the game installation is the next likely problem. A failed update, incomplete download, damaged local file, or deleted prerequisite can leave the executable without the files it expects.

Verify a Steam game

1. Open Steam.
2. Go to Library.
3. Right-click the game.
4. Select Properties.
5. Open Installed Files.
6. Click Verify integrity of game files.
7. Wait for Steam to compare and replace damaged files.
8. Run the game’s bundled DXSETUP.exe again if the prerequisite folder is present.
9. Restart Steam and test the game.

Verify an Epic Games game

1. Open the Epic Games Launcher.
2. Select Library.
3. Click the three-dot menu beside the game.
4. Choose Manage.
5. Click Verify.
6. Wait for the verification to complete.
7. Open the installation folder and run its DirectX prerequisite installer if present.
8. Launch the game again.

Repair an EA app game

1. Open the EA app.
2. Select Library.
3. Find the game.
4. Click its three-dot menu.
5. Choose Repair.
6. Wait for the process to complete.
7. Run the included prerequisite installer if the game provides one.
8. Test the game.

Repair a standalone application

Look in Settings, Apps, Installed apps, or the program’s own Start menu folder for a Repair option. If no repair option exists, reinstall the program from its original trusted installer.

Do not uninstall first unless the installer does not offer repair or the installation is clearly damaged. If you do reinstall, back up saved games and configuration files when the application stores them outside its installation directory.

Fix 4: Check whether the filename is versioned

A missing d3dx10.dll message and a missing d3dx10_43.dll message require slightly different diagnosis.

Microsoft designed legacy DirectX DLLs with versioned filenames so applications could continue using the exact library version against which they were built. Installing a newer-looking filename does not necessarily satisfy an older application.

Check the message carefully:

• d3dx10.dll means the unsuffixed retail D3DX10 library was requested.
• d3dx10_33.dll through d3dx10_43.dll identify separate side-by-side files.
• d3dx10d.dll is the debug counterpart and is not normally required by a retail game.

The safest response to any of these errors is to run the official full DirectX End-User Runtimes package. Do not rename one file to imitate another.

Avoid these attempted fixes:

d3dx10_43.dll → d3dx10.dll
d3dx10.dll → d3dx10_42.dll

Renaming can create a misleading loader error, leave dependencies unresolved, or cause an architecture mismatch. It also obscures which component the application actually needs.

Fix 5: Check x86 and x64 architecture

A 64-bit version of Windows can run both 64-bit and 32-bit applications. Many older games are 32-bit even when they run on a 64-bit edition of Windows.

This means a 32-bit game needs the x86 version of the DirectX runtime. A native 64-bit application needs the x64 version. Installing only a 64-bit DLL does not satisfy a 32-bit process.

On 64-bit Windows, the conventional system directories are:

• C:\Windows\System32 for 64-bit system components
• C:\Windows\SysWOW64 for 32-bit system components

The names are counterintuitive because SysWOW64 contains the 32-bit system files used by the Windows-on-Windows 64-bit subsystem. Microsoft documents this directory redirection behavior.

The safest architecture repair is to install the complete official DirectX redistributable and let DXSETUP.exe deploy the appropriate files. Do not manually place a 32-bit DLL in System32, and do not copy a DLL from another computer.

If the error changes to one of these messages after a manual copy, undo that copy and repair the official installation:

• “The application was unable to start correctly”
• 0xc000007b
• “The specified module could not be found”
• “The program or feature cannot start because of an incompatible version”
• “The file is not designed to run on Windows”

The same symptoms can also indicate a missing dependency rather than a wrong d3dx10.dll. That is why repairing the runtime and application is safer than replacing individual files.

Fix 6: Check Windows Security quarantine

Antivirus protection can remove a game-local DLL after an update, executable modification, or false detection. This is especially relevant when the game worked previously and stopped after Windows Security or another security product reported a detection.

To inspect Microsoft Defender history:

1. Open the Start menu.
2. Type Windows Security.
3. Open Windows Security.
4. Select Virus & threat protection.
5. Click Protection history.
6. Review recent detections.
7. Open an entry that references the affected game or d3dx10.dll.
8. Check the original file path and detection details.

Only restore or allow the file if all of the following are true:

• The application came from a trusted official source.
• The quarantined path belongs to the expected game installation.
• The detection is demonstrably a false positive.
• You have scanned the application and installer appropriately.

Microsoft warns that restoring a quarantined file can cause Defender to detect it again unless it is explicitly allowed, and allowing an unsafe file can expose the computer. Microsoft’s Protection History guidance explains the available actions.

In most cases, repairing or reinstalling the game is safer than restoring a questionable file. If the DLL came from an unofficial installer, do not restore it. Remove the untrusted installer and obtain the game from its legitimate source.

Do not broadly disable antivirus protection just to install a DLL. If a trusted game repeatedly triggers a detection, submit the file or detection through the security product’s normal false-positive process after confirming the game’s source.

Fix 7: Repair the game instead of downloading an isolated DLL

Random DLL download websites are risky because the file may contain malware, belong to the wrong architecture, be a different side-by-side version, or be modified. Even a clean-looking file may not fix the root cause if the game needs additional DirectX components or a matching dependency.

Do not:

• Download d3dx10.dll from a DLL archive
• Copy it from another computer
• Rename a suffixed D3DX file
• Place an unknown file in System32
• Replace a game-local file with an unrelated system copy
• Delete groups of DirectX DLLs to force a reinstall

Use the game’s bundled DXSETUP.exe, Microsoft’s official DirectX End-User Runtime packages, and the game launcher’s verification or repair function instead.

Developers can package approved D3DX binaries application-locally as part of a supported deployment process. That developer scenario is different from downloading an isolated DLL and placing it into a Windows directory. Microsoft also provides a developer-oriented Microsoft.DXSDK.D3DX package, but it is not the normal end-user repair method. The Microsoft-owned package is documented on NuGet.

Fix 8: Repair Windows components with DISM and SFC

Use DISM and System File Checker when Windows itself is unstable, Windows Update is failing, several protected system files appear damaged, or the DirectX installer reports broader component corruption.

These tools are not guaranteed to recreate d3dx10.dll. The file is an optional legacy DirectX component, not a core protected Windows runtime file. Install the official DirectX package first.

Run DISM

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

DISM.exe /Online /Cleanup-image /Restorehealth

1. Press Enter.
2. Wait for the operation to finish.
3. Leave the window open even if progress appears to pause.

A successful result reports that the restore operation completed successfully. If DISM reports that it cannot find source files, make sure Windows Update works and that the computer has network access, then retry. Do not interrupt the process repeatedly.

Run SFC afterward

After DISM finishes, run:

sfc /scannow

Press Enter and wait until verification reaches 100 percent.

Possible results include:

• Windows Resource Protection did not find any integrity violations: protected Windows files appear intact.
• 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: review the result, restart, and consider repeating the repair or using a Windows recovery path.

Microsoft recommends running DISM before SFC. Microsoft’s System File Checker instructions provide the supported command sequence.

Repeating SFC without checking what it reported is unlikely to solve a missing optional D3DX file. If Windows is otherwise healthy and only one game reports d3dx10.dll, return to the DirectX installer and game repair steps.

When manually checking Windows integrity becomes repetitive and you are unsure which component is actually stale, Outbyte PC Repair can scan for problems and show what it identifies; its full-version repair performs the automated fixes, but it is optional and reinstalling the affected game remains the definitive repair when that program owns the damaged file.

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

Fix 9: Update Windows, but understand its limits

Keeping Windows current is sensible for compatibility and security, but Windows Update is not the normal source for legacy D3DX10 files.

To check for updates:

1. Press Windows key + I.
2. Select Windows Update.
3. Click Check for updates.
4. Install available updates.
5. Restart when prompted.
6. Test the application again.

Windows Update can repair operating-system components and improve compatibility, but it does not replace the legacy DirectX side-by-side package described here. If the only problem is d3dx10.dll, install the official DirectX End-User Runtime rather than waiting for a feature update to add it.

Fix 10: Update or reinstall the graphics driver only when symptoms point to it

A missing D3DX10 file is usually not a graphics-driver problem. The GPU driver should be investigated when:

• Direct3D applications fail beyond the DLL message.
• The game launches but crashes during graphics initialization.
• DxDiag reports display-driver errors.
• Rendering is corrupted or unavailable.
• The problem began immediately after a graphics-driver update.
• Several unrelated games fail with graphics initialization errors.

Inspect DxDiag

1. Press Windows key + R.
2. Type:

dxdiag

1. Press Enter.
2. Allow the diagnostic tool to collect information.
3. Review the System, Display, and Sound tabs.
4. Click Save All Information.
5. Save the report to the desktop or another convenient folder.

The report can show the Windows version, DirectX information, display adapter, driver model, and driver problem indicators. Microsoft’s DirectX diagnostic guidance explains how to use DxDiag.

Update through Device Manager

1. Right-click the Start button.
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. Install a driver if Windows finds one.
8. Restart the computer.

For a more complete repair, obtain the current driver from the graphics adapter manufacturer or computer manufacturer. Use the correct driver for the exact adapter and Windows architecture.

Reinstall a recently changed driver

If the problem began immediately after a driver update:

1. Open Device Manager.
2. Expand Display adapters.
3. Right-click the adapter.
4. Choose Properties.
5. Open the Driver tab.
6. Select Roll Back Driver if the option is available.
7. Restart Windows.
8. Test the game.

If no rollback is available, use the manufacturer’s official installer and choose its clean-install option when provided. Do not remove random DirectX files as part of a graphics-driver repair.

When identifying the correct driver manually would mean hunting through multiple hardware versions and repeating installs without knowing what changed, Outbyte Driver Updater can scan and identify outdated drivers; the full version performs the driver installation, but it is optional and a missing D3DX10 file still requires the official DirectX or game repair.

Fix 11: Treat Visual C++, .NET, and Windows Features as separate dependencies

Installing Visual C++ or .NET will not normally create d3dx10.dll. They may still be required by the game or by its launcher, so install them only when another error identifies the missing component or the application’s official prerequisites list them.

For Visual C++ errors, use Microsoft’s Latest Supported Visual C++ Redistributable Downloads. Choose x86 for a 32-bit application and x64 for a native 64-bit application when the application requires those packages.

For a .NET error, use the Windows feature or the application’s official prerequisite installer rather than assuming it is related to D3DX10.

Check optional Windows features

Some older games require DirectPlay, which is a separate legacy compatibility feature. Enabling it does not directly install d3dx10.dll, but it can resolve a later startup error if the game explicitly reports that DirectPlay is missing.

1. Press Windows key + R.
2. Type:

optionalfeatures

1. Press Enter.
2. Expand Legacy Components.
3. Select DirectPlay if the game requires it.
4. Click OK.
5. Allow Windows to apply the change.
6. Restart if requested.
7. Test the game again.

Do not enable unrelated features simply because a DLL error occurred. Use the exact error message and the game’s documented prerequisites to decide whether a Windows feature is relevant.

Fix 12: Do not use regsvr32 for d3dx10.dll

regsvr32 is intended for DLLs that expose COM registration entry points such as DllRegisterServer. D3DX10 is a runtime utility library, not normally a COM component that users register manually.

Running this command is not a repair:

regsvr32 d3dx10.dll

It will not install the DirectX runtime, download missing dependencies, select the correct architecture, or repair a damaged game. It may produce an error stating that the DllRegisterServer entry point was not found.

Use the DirectX installer instead. Microsoft’s regsvr32 troubleshooting documentation explains when registration applies and why a DLL without the required entry point cannot be registered.

Fix 13: Inspect DirectX installer logs

If DXSETUP.exe fails with a message such as:

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

Use the following sequence:

1. Close the DirectX installer.
2. Extract the offline package to a short local path such as C:\DirectXTemp.
3. Right-click the extracted DXSETUP.exe.
4. Choose Run as administrator.
5. If it fails again, open File Explorer.
6. Navigate to C:\Windows.
7. Look for:

C:\Windows\DXError.log
C:\Windows\DirectX.log

1. Open the logs with Notepad.
2. Record the error near the end of each file.
3. Keep the logs with the exact application name, Windows version, and missing filename.

Do not broadly disable security protection to force setup through. If an installer is blocked, identify the specific blocked file or permission issue first. A short extraction path can also avoid failures caused by very long folder names or unusual permissions.

Fix 14: Use System Restore only when the timing is clear

System Restore is appropriate when the problem began immediately after a driver installation, application update, Windows change, or other identifiable system event. It is not a normal first-line solution for a missing legacy DirectX file.

To open System Restore:

1. Press Windows key + R.
2. Type:

rstrui.exe

1. Press Enter.
2. Select Next.
3. Choose a restore point created before the problem began.
4. Select Scan for affected programs if available.
5. Review the applications and drivers that may change.
6. Select Next.
7. Confirm the restore point.
8. Allow Windows to restart and complete the operation.

System Restore does not normally remove personal documents, but it can remove recently installed applications, drivers, and updates. Microsoft’s System Restore guidance explains the process and limitations.

If the problem began after installing the game itself, repairing or reinstalling that game is usually more targeted than restoring the entire system.

Final diagnostic checklist

Before asking for further help, collect these details:

• The exact error text
• The exact filename, including any suffix such as _42 or _43
• The name of the game or application
• Whether it is 32-bit or 64-bit, if known
• Windows 10 or Windows 11 version
• Whether the game came from Steam, Epic, EA, or a standalone installer
• Whether the bundled DXSETUP.exe was run
• Whether the June 2010 DirectX package completed successfully
• Whether launcher verification or repair found damaged files
• Whether Windows Security quarantined a game file
• The contents or relevant ending of C:\Windows\DXError.log
• The contents or relevant ending of C:\Windows\DirectX.log
• The saved dxdiag report if graphics errors are also present
• Whether the error changed after any manual file copy

The most likely successful sequence is:

1. Preserve the exact filename from the error.
2. Run the game’s bundled DXSETUP.exe.
3. Install Microsoft’s DirectX End-User Runtimes (June 2010).
4. Verify or repair the game files.
5. Check Windows Security Protection history.
6. Confirm the x86 versus x64 requirement.
7. Use DISM and SFC only when broader Windows corruption is indicated.
8. Investigate graphics drivers only when DxDiag or rendering symptoms point to them.

This approach installs the runtime through the supported source and keeps the application’s side-by-side DirectX dependencies intact.

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.