d3dx9_30.dll Is Missing: Fixes for Windows 11 and 10

d3dx9_30.dll is missing, so the affected game or application cannot start. d3dx9_30.dll was not found, could not be loaded, or is reported as not designed to run on Windows.

The exact errors you may see

Windows and older games use slightly different wording for the same underlying problem. Common messages include:

As an Amazon Associate I earn from qualifying purchases.

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

×Performance · Free Tool

PC Slower Than It Used to Be?

A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.

Run a Free PC Scan →Free scan · Windows 10 & 11

Stop driver crashes →Clean & speed up →

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

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

#1 Best Overall

Sale

Microsoft Windows 11 (USB)

• Less chaos, more calm. The refreshed design of Windows 11 enables you to do what you want effortlessly.
• Biometric logins. Encrypted authentication. And, of course, advanced antivirus defenses. Everything you need, plus more, to protect you against the latest cyberthreats.
• Make the most of your screen space with snap layouts, desktops, and seamless redocking.
• Widgets makes staying up-to-date with the content you love and the news you care about, simple.
• Stay in touch with friends and family with Microsoft Teams, which can be seamlessly integrated into your taskbar. (1)

$128.99

Buy on Amazon

This application failed to start because d3dx9_30.dll was not found.

The dynamic link library d3dx9_30.dll could not be found in the specified path.

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

×

Do these 3 things before closing this tab:

1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errors

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

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

The file d3dx9_30.dll could not be loaded or is corrupt.

These messages do not automatically mean that Windows itself is damaged. In most cases, an older game or graphics application needs an optional legacy DirectX component that is not installed, was removed, or does not match the program’s architecture.

The 60-second answer

First, check the affected game’s installation folder for a folder named Redist, DirectX, CommonRedist, or something containing dxsetup.

Run the included DXSETUP.exe, preferably by right-clicking it and selecting Run as administrator. This is usually the best fix because the game may have been packaged with the exact legacy DirectX components it expects.

If the game does not include its own installer, use Microsoft’s official DirectX End-User Runtime Web Installer. If the web installer fails or you need an offline package, download Microsoft’s DirectX End-User Runtimes (June 2010), extract it, and run DXSETUP.exe.

Do not download an isolated d3dx9_30.dll file from a random DLL website. Those files may contain malware, be the wrong architecture, be damaged, or fail to install the other legacy components the program needs.

After installation, restart Windows and launch the game again. If the same error remains, continue through the checks below.

What is d3dx9_30.dll?

d3dx9_30.dll is an optional legacy D3DX9 utility library used by older Direct3D applications. It is associated with the April 2006 D3DX9 component documented by Microsoft, not with a product called “DirectX 30.”

The number 30 is part of the D3DX release identifier. It is not the version of DirectX installed on your computer.

This distinction matters because Windows includes the core DirectX runtime, while individual D3DX libraries were distributed as additional, side-by-side components. Microsoft documents D3DX as an optional DirectX SDK library rather than a core Windows component. Microsoft’s D3DX documentation

The file is normally supplied by the program’s installer, a game’s bundled DirectX redistributable, or Microsoft’s legacy DirectX End-User Runtime. It is not normally something you should obtain as a standalone file and copy into a Windows folder.

A commonly recorded 32-bit copy has file version 9.12.589.0. That version should not be treated as a guarantee that every historical installation has identical metadata.

Why DirectX 12 does not guarantee this file is installed

Windows 10 and Windows 11 can report a modern DirectX version, including DirectX 12, while an older game still reports that d3dx9_30.dll is missing.

The DirectX version shown by dxdiag describes the core runtime and installed platform support. It does not prove that every optional D3DX9 library is present.

D3DX libraries are installed side by side. A newer D3DX file does not automatically replace an older one with a different filename. For example, d3dx9_43.dll and d3dx9_30.dll are separate components. A program linked specifically to d3dx9_30.dll still requests that exact filename.

Installing the latest Windows updates also does not reliably install every optional legacy D3DX component. Use Windows Update for Windows servicing and normal driver updates, but use the legacy DirectX End-User Runtime for this missing component. Microsoft’s DirectX installation documentation

Modern Windows is not incompatible with older DirectX applications. The application may simply need its legacy support files installed separately.

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

This is the first fix when only one game or application fails.

Game installers commonly place prerequisite files in one of these locations:

• The game’s installation folder
• A Redist folder
• A DirectX folder
• A CommonRedist folder
• A folder containing dxsetup
• The original DVD or installer media

Find and run the bundled installer

1. Open the game launcher.
2. Open the game’s installation location. In Steam or another launcher, use the option that opens or browses the installed files.
3. Look for folders named Redist, DirectX, CommonRedist, or DirectX June 2010.
4. Search inside those folders for DXSETUP.exe.
5. Right-click DXSETUP.exe.
6. Select Run as administrator.
7. Accept the license terms.
8. Allow the setup program to complete.
9. Restart Windows.
10. Start the game again.

If the game came on physical media, inspect the disc for a folder with a name such as directx_apr2007_redist. Some older games specifically instruct users to run the included dxsetup.exe from their original media.

How to tell whether it worked

The game should launch without the missing-DLL message. The installer may finish without reporting that a particular DLL was copied. That is normal. DirectX Setup installs a group of components and may leave existing newer files untouched.

If DXSETUP.exe says that the component is already installed but the game still fails, check the game directory for a damaged or incompatible application-local copy. Also inspect antivirus quarantine history and continue with the architecture checks below.

Fix 2: Install Microsoft’s official DirectX runtime

If the game has no usable DXSETUP.exe, install the missing legacy components directly from Microsoft.

Use the web installer

1. Open Microsoft’s DirectX End-User Runtime Web Installer.
2. Download dxwebsetup.exe.
3. Open the downloaded file.
4. Accept the license agreement.
5. Decline any optional software that is not needed for the DirectX installation.
6. Let the installer download and install the required legacy components.
7. Restart Windows.
8. Start the affected game or application.

The web installer is convenient when the computer has a working internet connection. It downloads the components required by the system instead of giving you a large package to extract manually.

Use the offline June 2010 package

Use the offline package when the web installer fails, the computer has restricted internet access, or you want a local installer that can be reused.

1. Download Microsoft’s DirectX End-User Runtimes (June 2010).
2. Save directx_Jun2010_redist.exe to a local folder.
3. Run the downloaded executable.
4. When it asks where to extract the files, choose a simple local folder such as C:\DXRedist.
5. Open C:\DXRedist.
6. Find DXSETUP.exe.
7. Right-click it and select Run as administrator.
8. Complete the installation.
9. Restart Windows.
10. Launch the game again.

The downloaded self-extracting file is not the final installation step. It only unpacks the redistributable files. You must open the extracted folder and run DXSETUP.exe.

The June 2010 package includes the June 2010 and earlier side-by-side legacy components, including D3DX libraries. It does not downgrade Windows’ core DirectX runtime.

If the installer appears to do nothing

Check these points:

• Run DXSETUP.exe from the extracted folder, not only the original self-extracting file.
• Extract the package to a local folder rather than a cloud-synchronized folder.
• Use a short folder path such as C:\DXRedist.
• Right-click DXSETUP.exe and select Run as administrator.
• Temporarily check whether antivirus software blocked or quarantined the installer.
• Restart Windows and run the installer again.
• If the game includes its own redistributable, try that package before repeatedly reinstalling the general Microsoft package.

Fix 3: Check whether the game needs x86 or x64

Architecture mismatches are a common reason a DLL appears to be installed but cannot be loaded.

Most older Windows games are 32-bit applications. A 32-bit game on 64-bit Windows requires the x86 DirectX component. A native 64-bit application requires the x64 component.

A 32-bit DLL cannot be loaded into a 64-bit process, and a 64-bit DLL cannot be loaded into a 32-bit process.

Check whether Windows is 32-bit or 64-bit

1. Right-click Start.
2. Select Settings.
3. Select System.
4. Select About.
5. Check System type.

This tells you the architecture of Windows, but it does not always tell you the architecture of the game. A 64-bit Windows installation can run many 32-bit games.

Check the application

Look for information from the game publisher or launcher about whether the executable is 32-bit or 64-bit. If the game is an older title, assume it may be 32-bit unless its documentation says otherwise.

Do not copy an x64 DLL into a 32-bit game folder just because Windows itself is 64-bit. The game needs the architecture of its own process.

On 64-bit Windows, System32 is used for native 64-bit system files, while SysWOW64 contains 32-bit system files. The names are confusing, which is another reason to use DirectX Setup instead of manually placing files. Microsoft’s file-system redirector documentation

Microsoft’s DirectX installation guidance specifically distinguishes the x86 component needed by 32-bit applications from the x64 component needed by native 64-bit applications. Microsoft’s DirectX setup guidance

Fix 4: Repair or verify the game files

If the error started after an update, migration, mod installation, interrupted download, or partial reinstall, the game itself may be damaged.

Repair the game before performing broad Windows repairs.

General launcher repair

Open the launcher that starts the program and look for an option named:

• Verify
• Verify integrity
• Repair
• Scan and repair
• Check files
• Validate installation

Run the check and allow the launcher to replace missing or damaged files. Restart the launcher afterward and test the game.

Steam

1. Open Steam.
2. Select 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. Start the game again.

If verification replaces the game’s local DirectX files but the error remains, run the bundled DXSETUP.exe manually. Some games store prerequisite installers separately from their primary game files.

Reinstall the affected program

If verification does not help:

1. Back up save files if they are not stored in the cloud.
2. Uninstall the game or application through its launcher or Windows.
3. Restart Windows.
4. Install it again from the original installer or official store.
5. Watch for a DirectX prerequisite step during installation.
6. If the installer offers to install DirectX, allow it.
7. Launch the program before adding mods or custom files.

Reinstalling the affected program remains the definitive fix when its own installer is responsible for an application-local copy of d3dx9_30.dll.

Fix 5: Check antivirus quarantine

Security software can remove or quarantine a DLL after a game update, a repair operation, or a change in detection rules.

Only restore a file when it came from the official Microsoft package or the game’s trusted original installer and you have verified that source.

Check Microsoft Defender

1. Open Windows Security from the Start menu.
2. Select Virus & threat protection.
3. Select Protection history.
4. Open any item associated with the affected game or DirectX installer.
5. Review the file path and detection details.
6. If the file came from an official trusted installer, use the available restore or allow option.
7. Run the official DirectX installer again if necessary.
8. Start the game.

Do not restore a standalone DLL obtained from an unofficial website. Remove it, run a full security scan, and reinstall the required component from Microsoft or the program’s original installer.

Microsoft notes that restored files may be detected again unless they are explicitly allowed, and that you should not allow a file when its safety is uncertain. Microsoft Protection History guidance

If antivirus repeatedly removes a file from the game folder, do not simply keep restoring it. Determine which installer created the file and verify that the installation media is genuine.

Fix 6: Repair Windows components with DISM and SFC

SFC and DISM are useful when the problem affects multiple applications or Windows components, or when logs point to broader system corruption.

They are not the primary repair tools for a missing optional D3DX library. If one older game is missing d3dx9_30.dll, install the legacy DirectX component first.

Run DISM

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

DISM /Online /Cleanup-Image /RestoreHealth

1. Press Enter.
2. Wait for the command to finish.
3. Restart Windows.

DISM may take some time and can appear to pause. Do not close the window while it is working.

Run System File Checker

After DISM completes:

1. Open Command Prompt as administrator again.
2. Enter:

sfc /scannow

1. Press Enter.
2. Wait until verification reaches 100 percent.
3. Restart Windows.
4. Run the official DirectX installer again if the game still reports the missing file.

Possible SFC results include:

• Windows Resource Protection did not find any integrity violations: SFC found no protected Windows-file problem.
• Windows Resource Protection found corrupt files and successfully repaired them: restart and test again.
• Windows Resource Protection found corrupt files but was unable to fix some of them: review the broader Windows repair situation and run the official DirectX installer separately.

Because d3dx9_30.dll is an optional legacy DirectX component, SFC may report a clean system even when the game still needs the file. Microsoft’s instructions recommend running DISM before SFC for Windows component repair. Microsoft’s System File Checker instructions

Outbyte PC Repair can reduce the manual work of hunting through Windows component problems and repeating SFC or DISM without knowing what changed; its free scan shows detected issues, while repair is handled by the full version. It is optional, and reinstalling the affected game remains the definitive fix when that program owns the missing dependency.

Fix 7: Update or reinstall graphics drivers only when justified

A graphics-driver reinstall is not the normal fix for a missing d3dx9_30.dll. The error identifies a missing or unloadable DirectX utility library, not automatically a display-driver failure.

Check drivers when:

• Several games have graphics-related failures.
• dxdiag reports display problems.
• DirectX Setup logs mention display or driver initialization.
• The game starts but crashes during rendering.
• The issue began immediately after a driver change.

Check DirectX diagnostics

1. Open the Start menu.
2. Type dxdiag.
3. Open DirectX Diagnostic Tool.
4. Review the System tab.
5. Review the Display tab.
6. Select Save All Information if you need to provide diagnostics to support.

Do not interpret the DirectX version shown there as proof that d3dx9_30.dll is installed. It reports core DirectX information, not every optional legacy D3DX component. Microsoft’s DxDiag guidance

Update 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. Select Search automatically for drivers.
7. Restart Windows.
8. Test the game.

Reinstall the display adapter

Use this when the driver is visibly malfunctioning or Windows reports a device problem.

1. Right-click Start.
2. Select Device Manager.
3. Expand Display adapters.
4. Right-click the graphics adapter.
5. Select Uninstall device.
6. Confirm the action.
7. Restart Windows.
8. Install the current driver through Windows Update or the graphics hardware manufacturer’s official site.

Outbyte Driver Updater can help identify which installed drivers are stale instead of making you hunt through multiple hardware packages; its free scan shows the detected driver issues, while installation is handled by the full version. It is optional and should not replace DirectX Setup when the only problem is a missing d3dx9_30.dll.

Fix 8: Check Windows Features, but do not expect them to install this DLL

There is no general Windows Features checkbox that reliably installs d3dx9_30.dll.

You can still check the optional Windows components when another application specifically requires one of them:

1. Press Win + R.
2. Enter:

optionalfeatures

1. Press Enter.
2. Review the available Windows features.
3. Enable only a feature required by the program’s documentation.
4. Select OK.
5. Restart if Windows requests it.

Do not enable random features as a substitute for the DirectX End-User Runtime. Do not uninstall core DirectX components. The legacy DirectX package adds side-by-side support files and does not replace or downgrade Windows’ core DirectX runtime.

Fix 9: Use System Restore after a recent system change

System Restore is reasonable when the error began immediately after:

• A driver installation
• A cleanup utility
• A Windows change
• A security event
• A program installation
• A failed update

Start System Restore

1. Press Win + R.
2. Enter:

rstrui.exe

1. Press Enter.
2. Select a restore point created before the problem began.
3. Select Scan for affected programs.
4. Review what will be changed.
5. Continue only if the restore point matches the timing of the failure.
6. Restart Windows when prompted.

System Restore normally rolls back system files, registry settings, and installed programs without removing personal files. It does not replace a missing game dependency in every situation, so run the official DirectX installer after the restore if the error remains. Microsoft’s System Restore guidance

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 use random DLL download sites

A standalone DLL from an unknown source can be:

• Malicious
• The wrong architecture
• A different release
• Incomplete
• Corrupt
• Missing required dependencies

It may also make Windows load an application-local file that conflicts with the version expected by the game.

Use the game’s original installer or Microsoft’s official DirectX End-User Runtime instead.

Do not rename d3dx9_43.dll

Renaming d3dx9_43.dll to d3dx9_30.dll does not convert it into the requested component. The files are separate side-by-side libraries and may expose different functions.

Do not copy it blindly into System32 or SysWOW64

System folders have architecture-specific behavior and are not a general storage location for game files. Copying the wrong DLL there can create conflicts and make troubleshooting harder.

If the software vendor explicitly supports application-local deployment, a correctly sourced DLL may belong beside the exact executable that loads it. In that narrow case, use a file from the official redistributable or original installer and match the application’s architecture. Windows searches an unpackaged application’s executable directory as part of its DLL search order. Microsoft’s DLL search-order documentation

Application-local copies can also introduce version conflicts and DLL-preloading security risks. Microsoft’s DLL security documentation

Do not use regsvr32 for this file

regsvr32 is used for self-registering COM or OLE DLLs that provide registration entry points such as DllRegisterServer.

d3dx9_30.dll is a DirectX runtime library, not a COM component that you normally register. Running this command is not a repair method:

regsvr32 d3dx9_30.dll

It may produce an error about a missing entry point or self-registration failure, and it will not install the missing DirectX component. Use DirectX Setup instead. Microsoft’s Regsvr32 documentation

Do not install Visual C++ or .NET at random

Visual C++ and .NET are separate runtimes. They do not directly provide d3dx9_30.dll.

Repair those runtimes only if the application reports a separate Visual C++ or .NET error, or if the DirectX installer log identifies a related prerequisite problem.

When the file exists but Windows still cannot load it

A visible file name does not prove that the correct binary is being used.

Possible explanations include:

• The file is the wrong architecture.
• The file is truncated or corrupt.
• A dependency of the file is missing.
• The game is loading a different copy from its own folder.
• Antivirus software removed another required file.
• The application expects a different D3DX release.
• The file is blocked or inaccessible.
• The installer placed the component in the wrong location.

If the error says “The specified module could not be found,” the missing module may be a dependency rather than the named DLL itself.

Start with the game’s bundled DXSETUP.exe, then verify the game files, check antivirus history, and reinstall the program if necessary. Avoid replacing files one at a time from unrelated computers.

When DirectX Setup reports an internal system error

A common DirectX Setup message is:

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

×

The Tool Desk

Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Check these files:

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

Retry with a fresh offline package

1. Download a fresh copy of Microsoft’s June 2010 offline package.
2. Extract it to a new local folder such as C:\DXRedist.
3. Do not extract it into OneDrive or another synchronized folder.
4. Right-click the extracted DXSETUP.exe.
5. Select Run as administrator.
6. Allow the installation to complete.
7. Restart Windows.
8. Test the game.

Look for messages indicating architecture problems, invalid executables, permission failures, or another prerequisite that could not be installed.

If the game provides its own redistributable, use that package first. It may contain an older component set selected specifically for that game.

If the installer says the component is already installed but the game still fails, inspect:

• The game’s own folder
• The launcher configuration
• Antivirus Protection history
• The application architecture
• Any local copy of d3dx9_30.dll
• The relevant lines in DXError.log and DirectX.log

SFC and DISM versus DirectX Setup

Use the following rule:

• One game fails with a missing d3dx9_30.dll: run the game’s DirectX setup and verify the game.
• Several unrelated games fail with legacy DirectX errors: install the official legacy runtime and check antivirus history.
• Multiple Windows applications have corruption symptoms: run DISM followed by SFC.
• Display drivers are failing in several programs: inspect dxdiag and repair the graphics driver.
• The issue began immediately after a system change: consider System Restore.

This prevents a common mistake: using Windows repair commands to solve a missing optional game runtime.

FAQ

Is d3dx9_30.dll a Windows system file?

It is a DirectX component, but it is not a core Windows DirectX component that every modern Windows installation must contain. It is normally installed separately by the legacy DirectX redistributable or by the program that requires it.

Is d3dx9_30.dll a game file?

It may be installed in the game directory by the game’s own installer, but it is a shared legacy DirectX component rather than a file unique to one game. The safest source is the game’s original installer or Microsoft’s official DirectX End-User Runtime.

Why does my Windows 11 or Windows 10 computer need DirectX 9 files?

Modern Windows can provide the core DirectX runtime while omitting optional legacy D3DX libraries. Older software can require a specific side-by-side file such as d3dx9_30.dll.

Will installing DirectX 12 fix the error?

No. Installing or already having DirectX 12 does not guarantee that the requested D3DX9 component is installed. Install the legacy End-User Runtime separately.

Will d3dx9_43.dll work instead?

No. d3dx9_43.dll and d3dx9_30.dll are different side-by-side components. Install the exact component requested by the application.

Should I copy the file into System32?

No, not as a general fix. Use DirectX Setup. If the software vendor explicitly supports an application-local copy, use the correct file from an official installer and place it beside the exact executable that requires it.

Should I copy the file into SysWOW64?

Do not use folder copying as a substitute for DirectX Setup. On 64-bit Windows, SysWOW64 is associated with 32-bit system files despite its confusing name. The program’s architecture determines which component it needs.

Should I run regsvr32?

No. DirectX runtime libraries are not normally self-registering COM DLLs. regsvr32 will not install or repair this component.

Will SFC repair d3dx9_30.dll?

Usually not when the problem is simply that the optional legacy component was never installed. SFC repairs protected Windows components. Use the official DirectX installer for a missing D3DX library.

Could antivirus have deleted the file?

Yes. Check Windows Security’s Protection history and the history of any other antivirus program. Restore a quarantined file only when it came from the official Microsoft package or the trusted original game installer.

Do I need to update my graphics driver?

Not usually for this error. Update or reinstall the driver when dxdiag reports display problems, several games fail graphically, or DirectX logs point to a driver issue.

Is the file always version 9.12.589.0?

No version should be assumed to be universal. 9.12.589.0 is a commonly recorded version for a 32-bit copy, but the installation source and application architecture matter more than a number copied from an unrelated file.

Can Windows Update install it?

Windows Update does not reliably provide every optional legacy D3DX component. Use Microsoft’s DirectX End-User Runtime or the game’s bundled installer.

Should I enable a Windows Feature?

There is no general Windows Features setting that reliably installs d3dx9_30.dll. Use the official DirectX package instead.

Can I uninstall DirectX and reinstall it?

Do not try to uninstall Windows’ core DirectX runtime. Install the legacy End-User Runtime side by side. The package adds optional components rather than replacing the core runtime.

If the error still persists

Collect this information before contacting the game or application publisher:

• The complete error message
• The name of the executable that fails
• The game or application version
• Whether Windows is 32-bit or 64-bit
• Whether the failure affects one program or several
• Whether the installation folder contains Redist, DirectX, or DXSETUP.exe
• Whether game-file verification found or replaced anything
• Whether antivirus quarantined a file
• The relevant contents of C:\Windows\DXError.log
• The relevant contents of C:\Windows\DirectX.log
• The saved output from dxdiag

At that stage, the application may require a private patched build, a specific application-local dependency, or a vendor-supported compatibility fix. The publisher can identify that requirement more accurately than a generic DLL replacement.

For most users, however, the correct order is straightforward: run the game’s own DXSETUP.exe, install Microsoft’s legacy DirectX End-User Runtime if necessary, verify or reinstall the affected program, check architecture and antivirus history, and use SFC, DISM, or driver repair only when the wider symptoms justify them.

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.