d3dx9_29.dll: Legacy DirectX Repair Steps for Windows 11

If d3dx9_29.dll is missing, the safest repair is to install the official Microsoft DirectX End-User Runtime, preferably through the affected game’s bundled DXSETUP.exe or Microsoft’s June 2010 redistributable. d3dx9_29.dll is a legacy D3DX9 library, so having DirectX 11 or DirectX 12 installed does not prove that this optional component is available.

Do not download the DLL from a random DLL website or copy an unknown file into System32. The correct installer handles the required architecture and related DirectX files together.

As an Amazon Associate I earn from qualifying purchases.

File detail	Reported information
File name	d3dx9_29.dll
Category	DirectX
Reported architecture	32-bit
Reported version	9.11.519.0
Reported size	2.22 MB
Installed by	The program that installed it
Internal description	Not listed

What d3dx9_29.dll is

d3dx9_29.dll belongs to the D3DX9 utility libraries used by older Direct3D 9 games and applications. Microsoft describes D3DX as a deprecated, optional part of the legacy DirectX SDK rather than a core Windows graphics component. Multiple D3DX releases can exist side by side because older applications may require different numbered files.

The 29 in the filename identifies a particular D3DX9 release. It does not mean that the computer needs “DirectX version 29.”

Windows includes core DirectX technologies such as Direct3D, DirectInput, and DirectSound. Optional D3DX libraries are installed separately by DirectSetup or by a game’s redistributable installer. Microsoft also states that Windows Update does not provide these optional DirectX components. See Microsoft’s D3DX documentation and DirectX installation guidance.

This explains why a newly installed Windows 10 or Windows 11 computer can report a missing d3dx9_29.dll file even though dxdiag shows DirectX 11 or DirectX 12.

Errors caused by this file

The exact wording depends on Windows, the game launcher, and whether the loader finds a missing file, an invalid file, or a dependency with the wrong architecture.

Common messages include:

• This application has failed to start because d3dx9_29.dll was not found. Re-installing the application may fix this problem.
• C:\Windows\system32\d3dx9_29.dll is either not designed for Windows or it contains an error.
• missing d3dx9_29.dll error 0x7e
• missing dll d3dx9_29.dll error: 0x000000c1
• The code execution cannot proceed because d3dx9_29.dll was not found.
• The program can't start because d3dx9_29.dll is missing from your computer.

A message mentioning d3dx9_29.dll does not always mean the file itself is absent. The file may be present but invalid, the wrong 32-bit or 64-bit version, blocked by antivirus software, or unable to load one of its dependencies.

Fix 1: Run the game’s bundled DirectX installer

This is the best first repair because the game publisher may have supplied the exact DirectX components the application expects.

Find the installer

1. Close the game and its launcher.
2. Open File Explorer.
3. Browse to the game’s installation folder.
4. Look for a folder named Redist, DirectX, Support, __Installer, or _CommonRedist.
5. Check these common locations:

text
_CommonRedist\DirectX\Jun2010\Redist\
__Installer\directx\redist\
Support\DirectX\
Redist\

1. Look for DXSETUP.exe.

The exact folder depends on the game and launcher. If the game was installed through Steam, Epic Games Launcher, EA App, GOG, or another platform, use that platform’s option to open or browse the local installation files.

Run DXSETUP.exe

1. Right-click DXSETUP.exe.
2. Select Run as administrator.
3. Approve the User Account Control prompt.
4. Accept the license terms.
5. Allow setup to complete.
6. Restart Windows.
7. Launch the game again.

The repair worked if the game starts without the missing-DLL message. A successful installation may not display a large confirmation beyond the installer completing normally.

If DXSETUP.exe reports that setup could not download files, the bundled installer is incomplete, or the folder does not contain a usable installer, continue with the official Microsoft offline package below.

Fix 2: Install Microsoft DirectX End-User Runtimes

Microsoft’s DirectX End-User Runtimes (June 2010) package contains the legacy side-by-side DirectX components used by older games, including D3DX libraries.

The download is named:

directx_Jun2010_redist.exe

Microsoft lists version 9.29.1974.1 and a download size of approximately 95.6 MB for this package.

Extract the offline package

1. Open Microsoft’s June 2010 DirectX download page.
2. Select Download.
3. Save directx_Jun2010_redist.exe.
4. When the download finishes, open the file.
5. Choose an empty extraction folder.

You can create a folder such as:

C:\DXRedist

The outer file is a self-extracting package. It is not the final DirectX installation step.

Run the extracted installer

1. Open the folder where the package was extracted.
2. Find DXSETUP.exe.
3. Right-click DXSETUP.exe.
4. Select Run as administrator.
5. Accept the license terms.
6. Let DirectSetup finish.
7. Restart Windows.
8. Try the affected game or application again.

Running only directx_Jun2010_redist.exe without extracting and launching DXSETUP.exe may leave the legacy components uninstalled. The important step is the extracted DXSETUP.exe.

Installing this package does not downgrade DirectX 12, remove DirectX 11, or replace the modern DirectX runtime. It adds optional legacy libraries beside the existing Windows components.

For a developer-controlled silent installation, Microsoft documents:

DXSETUP.exe /silent

Ordinary users should normally use the graphical installer so that setup errors are visible.

Use the web installer when appropriate

Microsoft also provides the smaller DirectX End-User Runtime Web Installer, named:

dxwebsetup.exe

Microsoft lists version 9.29.1974.1 and a download size of approximately 288.4 KB. It downloads the required components during setup.

Use it when the computer has reliable internet access:

1. Open the Microsoft download page.
2. Download dxwebsetup.exe.
3. Right-click the file and select Run as administrator.
4. Accept the license terms.
5. Allow setup to download and install the required files.
6. Restart Windows.
7. Test the application.

Use the offline June 2010 package instead if the web installer fails, the computer has limited connectivity, or the installer cannot retrieve its components.

Fix 3: Verify or repair the game files

If the DirectX installer succeeds but the game still reports the same error, the game’s own files may be incomplete or damaged.

Steam

1. Open Steam.
2. Open Library.
3. Right-click the affected game.
4. Select Properties.
5. Select Installed Files.
6. Select Verify integrity of game files.
7. Wait for the process to finish.
8. Run the game’s bundled DXSETUP.exe again if it is available.
9. Restart the game.

Steam verification can restore files removed or damaged by an update or antivirus quarantine.

Epic Games Launcher

1. Open Epic Games Launcher.
2. Open Library.
3. Select the three-dot menu beside the game.
4. Select Manage.
5. Select Verify.
6. Wait for verification to finish.
7. Run the game again.

Epic’s verification process replaces damaged or changed game files without normally affecting saved data.

EA App

1. Open EA App.
2. Open Library.
3. Select the three-dot menu for the game.
4. Select Repair.
5. Wait for the repair to complete.
6. Start the game again.

Other launchers use similar commands named Verify, Repair, Scan, or Check files.

If verification repeatedly replaces the same file, the installation may be damaged, the disk may have a problem, or security software may be removing the file. In that situation, uninstall and reinstall the game from legitimate installation media, then run its bundled DirectX installer before launching it.

Fix 4: Check whether antivirus software quarantined the file

Antivirus software can remove a game-local DLL or an installer file. Microsoft warns that restoring a detected item can put the computer at risk, so do not restore a file merely because a game needs it.

Review Windows Security

1. Open Start.
2. Type Windows Security.
3. Open the application.
4. Select Virus & threat protection.
5. Select Protection history.
6. Review recent events related to the game, its installer, or d3dx9_29.dll.

If the file came from an unofficial DLL archive, do not restore it. Remove the untrusted copy and reinstall the game or Microsoft DirectX runtime from an official source.

If the file came from the game’s legitimate installer and the detection is clearly a false positive, verify the game installation first. Then follow your organization’s security policy or antivirus vendor’s documented restoration process. Do not disable antivirus protection broadly.

Protection History keeps events for a limited period, so an old quarantine event may no longer be visible.

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

Many older games are 32-bit even when Windows is 64-bit. A 32-bit game needs the x86 DirectX runtime. Installing or copying only a 64-bit DLL does not satisfy a 32-bit application.

On 64-bit Windows, the usual system locations are:

%WINDIR%\System32
%WINDIR%\SysWOW64

Despite the names, System32 normally contains 64-bit system files on 64-bit Windows, while SysWOW64 contains 32-bit system files. Microsoft explains this behavior in its File System Redirector documentation.

A 32-bit process cannot load a 64-bit DLL, and a 64-bit process cannot load a 32-bit DLL. Microsoft documents this restriction in its guidance on running 32-bit applications.

Search for existing copies

Open Command Prompt and run:

where /r "%WINDIR%\System32" d3dx9_29.dll
where /r "%WINDIR%\SysWOW64" d3dx9_29.dll

The commands may find no files, one file, or several copies.

Finding a copy does not prove that it is valid. It may be damaged, the wrong architecture, blocked by security software, or unrelated to the game’s installation.

The safest architecture repair is to run the official DirectX installer again. Do not mix individual DLLs between System32, SysWOW64, and the game folder.

Fix 6: Check for a damaged application-local copy

Games sometimes place required DLLs beside their executable. Windows normally searches the application directory before the system directories for ordinary desktop applications. Microsoft describes this behavior in its DLL search-order documentation.

This means a damaged local copy can override a working system copy.

To check:

1. Open the game’s installation folder.
2. Find the folder containing the game’s main .exe file.
3. Look for d3dx9_29.dll.
4. Do not download a replacement from the internet.
5. Use the launcher’s file verification or repair function.
6. If no repair function exists, reinstall the official game files.
7. Run the bundled DXSETUP.exe afterward.

Avoid deleting a DLL from the game folder unless the game publisher’s repair instructions specifically tell you to do so. Removing a file manually can create another error and may interfere with file verification.

Fix 7: Check DirectX with dxdiag

dxdiag is useful for recording the computer’s DirectX and graphics-driver environment. It does not prove that every optional D3DX9 library is installed.

1. Press Win+R.
2. Enter:

text
dxdiag

1. Press Enter.
2. Wait for the diagnostic tool to finish loading.
3. Review the System and Display tabs.
4. Select Save All Information if technical support needs the report.

If dxdiag shows DirectX 11 or DirectX 12, that only confirms the modern core DirectX environment. It does not replace the June 2010 side-by-side runtime.

Fix 8: Enable Legacy Components only for related compatibility errors

Some older games also need the Windows DirectPlay compatibility feature. DirectPlay is separate from d3dx9_29.dll, so enabling it will not install the missing DLL. It is useful only when the game reports a DirectPlay or network compatibility error as well.

To check the feature:

1. Press Win+R.
2. Enter:

text
optionalfeatures

1. Press Enter.
2. Expand Legacy Components.
3. Select DirectPlay if the game specifically requires it.
4. Select OK.
5. Restart Windows if prompted.
6. Try the game again.

Do not enable unrelated Windows features as a general DLL repair. For a d3dx9_29.dll error, DirectSetup remains the relevant installation path.

Fix 9: Repair broader Windows component corruption

DISM and SFC are not the primary installers for optional D3DX9 files. Use them when Windows itself is malfunctioning, DirectSetup fails because of broader system corruption, or several unrelated Windows components are damaged.

Microsoft recommends running DISM before SFC.

Run DISM

1. Open Start.
2. Type Command Prompt.
3. Right-click Command Prompt.
4. Select Run as administrator.
5. Run:

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

1. Wait for the command to complete.
2. Restart Windows if requested.

Run System File Checker

Open an elevated Command Prompt again and run:

sfc /scannow

Wait until the scan reaches 100 percent. Then restart Windows and run DXSETUP.exe again.

Possible SFC results include:

• Windows found no integrity violations.
• Windows found corrupt files and repaired them.
• Windows found corrupt files but could not repair some of them.

If DISM or SFC reports errors, follow Microsoft’s repair guidance before repeating DirectSetup. Do not assume that SFC will restore d3dx9_29.dll; D3DX9 is an optional runtime component, not normally a protected core Windows file.

Repeating DISM and SFC while guessing which component changed can be tedious; Outbyte PC Repair offers a free scan that shows what is wrong, while repair is handled by the full version. It is optional, and when this file belongs to a specific game or app, reinstalling that program remains the definitive fix.

Fix 10: Update or reinstall graphics drivers when the timing fits

A graphics-driver update will not normally install d3dx9_29.dll. It is relevant when the error began immediately after a driver change, the game also crashes with graphics errors, or Device Manager reports a display-device problem.

Check Device Manager

1. Right-click Start.
2. Select Device Manager.
3. Expand Display adapters.
4. Right-click the graphics adapter.
5. Select Properties.
6. Open the Driver tab.
7. Review the driver provider, date, and version.
8. Select Update Driver.
9. Choose Search automatically for drivers.
10. Restart Windows if a driver is installed.

If the problem began after a recent driver update:

1. Open the same Driver tab.
2. Select Roll Back Driver if the button is available.
3. Follow the prompts.
4. Restart Windows.

If Device Manager cannot find a suitable driver, use Windows Update or the graphics adapter manufacturer’s official support channel. Do not expect this step alone to fix a missing D3DX9 component.

Manually checking dozens of driver versions is slow; Outbyte Driver Updater offers a free scan that shows what is stale, while driver installation is handled by the full version. For a file owned by a specific game or app, reinstalling that program remains the definitive fix.

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

Fix 11: Use System Restore only for a matching change

System Restore can help when the error started immediately after a driver installation, game cleanup, Windows change, or other known system modification. It is not a substitute for installing the DirectX redistributable.

To open System Restore:

1. Press Win+R.
2. Enter:

text
rstrui.exe

1. Press Enter.
2. Select Next.
3. Choose a restore point created before the problem began.
4. Review the affected programs.
5. Select Finish.
6. Allow Windows to restart.

You can also open it through:

Control Panel > Recovery > Open System Restore

System Restore normally rolls back system files, settings, and installed programs without affecting personal documents. Use it only when the restore point matches the time and cause of the failure.

What not to do

Do not download the DLL from a random website

Standalone DLL download sites can provide malware, tampered files, the wrong D3DX release, or the wrong architecture. Even a clean-looking file may not match the game or its dependencies.

A manual copy also leaves the original problem unresolved. The game may still have incomplete files, a broken installer, or a quarantined component.

Use the game’s bundled DXSETUP.exe, Microsoft’s June 2010 DirectX redistributable, or Microsoft’s DirectX web installer.

Do not copy a 64-bit DLL into a 32-bit game

A 32-bit game requires the x86 runtime even on 64-bit Windows. Copying files between System32, SysWOW64, and the game folder can create architecture conflicts and make troubleshooting more difficult.

Do not use regsvr32 for this file

regsvr32 is intended for DLLs that expose registration entry points such as DllRegisterServer. D3DX9 is a runtime library loaded by the application, not a COM or ActiveX component that users register.

Running regsvr32 against d3dx9_29.dll will not install the DirectX runtime and may produce another confusing error. Microsoft documents the purpose of regsvr32 and DllRegisterServer separately.

Do not install Visual C++ or .NET as a substitute

Visual C++ redistributables provide Microsoft C and C++ runtime libraries. They do not provide d3dx9_29.dll.

Install Visual C++ only if the application separately reports files such as MSVCP*.dll or VCRUNTIME*.dll. Likewise, .NET does not supply D3DX9. Several missing-runtime messages can represent separate prerequisites.

Do not treat Windows Update as the DirectX repair

Windows Update and graphics-driver packages do not replace the optional legacy D3DX redistributable. Update Windows for general security and compatibility, but install the DirectX component through DirectSetup.

Final repair order

Use this order so that the most likely cause is handled first:

1. Check the game folder for DXSETUP.exe.
2. Run the bundled installer as administrator.
3. If it is missing or fails, install Microsoft’s June 2010 offline DirectX package.
4. Run the extracted DXSETUP.exe.
5. Restart Windows.
6. Verify the game files through its launcher.
7. Check Windows Security Protection History.
8. Confirm that the affected game is 32-bit or 64-bit and reinstall the correct official runtime.
9. Use dxdiag and the where commands for diagnostics.
10. Run DISM followed by SFC only when broader Windows corruption is suspected.
11. Check Device Manager if the problem began with a graphics-driver change.
12. Reinstall the game or application if its local files remain damaged.

Frequently asked questions

Is d3dx9_29.dll a Windows system file?

It is a Microsoft DirectX library, but it is not a core Windows DLL. It belongs to the optional legacy D3DX9 runtime and may be installed by DirectSetup or by an application’s redistributable.

Will installing DirectX 12 fix the error?

Not necessarily. DirectX 12 and other modern DirectX components do not automatically install every optional D3DX9 side-by-side library. Install the legacy DirectX runtime separately.

Does dxdiag show whether this DLL is installed?

No. dxdiag reports the core DirectX environment and driver information. It does not confirm that every optional D3DX9 DLL is present.

Should I place the file in System32?

No. Do not use manual copying as the normal repair. The correct architecture may be 32-bit, and some games use an application-local copy. Run DirectSetup instead.

Does every DirectX 9 game need d3dx9_29.dll?

No. Different games require different D3DX9 releases and other DirectX components. Install the runtime requested by the game’s own installer rather than assuming every DirectX 9 application needs this exact file.

Why does the error say “not designed for Windows”?

That wording usually indicates an invalid image, damaged DLL, architecture mismatch, or an incompatible dependency. Reinstall the official runtime and verify the game files. Do not replace the file with random x86 and x64 downloads.

Can Visual C++ fix it?

No. Visual C++ supplies different runtime libraries. Install it only when the application separately reports a Visual C++ runtime file.

Can SFC restore d3dx9_29.dll?

Not normally. SFC repairs protected Windows system files. It is not the primary installer for optional D3DX9 components. Use DirectSetup first.

What if the file is present but the game still will not start?

The copy may be corrupt, the wrong architecture, blocked by antivirus, or unable to load another dependency. Verify the game files, inspect Protection History, reinstall the official DirectX runtime, and avoid mixing files manually.

What if the installer still fails?

Record the DirectSetup error, run DISM and SFC if Windows corruption is suspected, check available disk space and permissions, and retry from the game’s own installer or Microsoft’s offline package. If only one game is affected, repair or reinstall that game.

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.