d3dcompiler_34.dll Not Found: Repair the Legacy DirectX Setup

“The program can’t start because d3dcompiler_34.dll is missing from your computer.”

You may instead see “d3dcompiler_34.dll was not found,” “The code execution cannot proceed,” or “Error loading d3dcompiler_34.dll.” These errors usually mean that an older game or graphics application needs a legacy DirectX component that is not installed, was damaged, or was removed from the program’s installation.

As an Amazon Associate I earn from qualifying purchases.

The safest repair is to install Microsoft’s DirectX End-User Runtime, preferably the full June 2010 package, then repair or verify the affected game or application.

Which fix applies to you

Use the description that best matches what you are seeing.

• If one older game or program fails immediately after installation, install the DirectX End-User Runtime, then use the game launcher’s Verify or Repair command.
• If the file disappeared after antivirus detection, check Windows Security Protection History before reinstalling anything.
• If the file exists but the error says “Bad Image” or “not designed to run on Windows,” check the file path, architecture, digital signature, and error code.
• If several unrelated applications fail, install Windows updates and run DISM followed by SFC.
• If multiple DirectX games show crashes, display corruption, or graphical artifacts, investigate the graphics driver.
• If the failure began after a driver, update, cleanup utility, or software installation, System Restore may be appropriate.
• If you found a proposed fix telling you to download the DLL and copy it into System32, stop. That is not the normal repair path for this file.
• If you are considering regsvr32, do not use it for d3dcompiler_34.dll. This DLL is not repaired by registering it.

The rest of this guide takes these fixes in order, starting with the one most likely to solve the problem.

What d3dcompiler_34.dll actually is

d3dcompiler_34.dll is a Microsoft Direct3D HLSL compiler library. HLSL is the High-Level Shader Language used by Direct3D applications to compile shader code for rendering.

The _34 suffix identifies an older compiler generation. It does not mean “DirectX version 34,” and it does not describe your graphics card.

Microsoft documents the D3DCompiler*.dll family as deployable Direct3D compiler components. These files are not built into Windows in the same way as core Direct3D runtime files, so an application or DirectX setup program must install them. See Microsoft’s Direct3D deployment documentation.

This distinction explains why a computer can have DirectX 11 or DirectX 12 and still report that d3dcompiler_34.dll is missing. Modern Windows includes current DirectX technology, but older applications can depend on optional, side-by-side components from earlier DirectX SDK releases.

The file is:

• A Direct3D and HLSL compiler dependency.
• An older DirectX side-by-side component.
• Used by the program that installed or requested it.
• Not a Visual C++ Redistributable DLL.
• Not a graphics-card driver.
• Not the same type of core Windows component as d3d9.dll, d3d11.dll, or dxgi.dll.

Different legacy DirectX DLLs can coexist. Installing d3dcompiler_47.dll, .NET, or a Visual C++ Redistributable does not automatically install d3dcompiler_34.dll.

Why DirectX 12 does not solve this error

Windows 10 and Windows 11 include modern DirectX components, but they do not automatically include every historical compiler DLL used by older games.

Microsoft’s DirectX End-User Runtime adds older side-by-side technologies without replacing or changing the main DirectX runtime installed in Windows. The official DirectX End-User Runtime Web Installer is intended for connected systems.

The more useful repair for a stubborn or offline installation is the DirectX End-User Runtimes (June 2010). It is a full redistributable package containing the June 2010 and earlier legacy DirectX components.

Installing this package does not downgrade DirectX 12, remove DirectX 11, or replace your graphics driver.

Fix 1: Install the official June 2010 DirectX runtime

This is the primary fix for a missing d3dcompiler_34.dll.

Download the correct Microsoft package

1. Close the game or application showing the error.
2. Open Microsoft’s DirectX End-User Runtimes (June 2010) page.
3. Download directx_Jun2010_redist.exe.
4. Save it somewhere easy to find, such as your Downloads folder.
5. Right-click the downloaded file and select Run as administrator.
6. Accept the license terms.
7. When the installer asks where to extract its files, create a new temporary folder. For example, use a folder named DirectX_June2010 on the Desktop.
8. Open the extraction folder in File Explorer.
9. Find DXSETUP.exe.
10. Right-click DXSETUP.exe and select Run as administrator.
11. Follow the DirectX setup prompts.
12. Restart Windows after setup finishes.
13. Launch the affected game or application.

The first executable extracts the package. DXSETUP.exe is the setup program that actually installs the legacy components.

How to tell whether it worked

The repair worked if:

• The game or application starts normally.
• The missing-file dialog no longer appears.
• The program reaches its menu or main window.
• Other older DirectX components requested by the same program are also resolved.

Do not judge success by whether a new DirectX version appears in dxdiag. This package adds side-by-side components and does not change the main DirectX version displayed there.

If the web installer fails

The web installer downloads components during setup, so it can fail because of network restrictions, permissions, security software, or an incomplete download.

Use the full June 2010 package instead:

1. Download directx_Jun2010_redist.exe from Microsoft.
2. Extract it to a new folder.
3. Run DXSETUP.exe from that folder as administrator.
4. Restart Windows.
5. Try the affected application again.

Avoid deleting files from System32 or `SysWOW64 to force DirectX setup to continue. That can create a larger Windows problem and is not a general DirectX repair method.

Fix 2: Repair or reinstall the affected program

If only one game or application reports the error, its installation may be incomplete or damaged. Installing DirectX first is sensible, but the application itself may still need repair.

Repair an application in Windows 11

1. Open Start.
2. Select Settings.
3. Select Apps.
4. Select Installed apps.
5. Find the affected application.
6. Select the three-dot menu beside it.
7. Select Advanced options.
8. Select Repair if the option is available.
9. Launch the application again.

Windows repairs the program without normally removing its personal data. If Repair is unavailable or does not help, return to the same page and use Reset only if you understand that the application may lose its local settings.

For a traditional desktop game, use the game’s own installer or launcher repair function instead.

Verify a Steam game

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 scan to finish.
8. Start the game again.

Steam’s official instructions are available in its Verify Integrity of Game Files support page.

Other launchers may call the same operation Verify, Repair, Scan, or Validate. Use that option before manually replacing individual files.

When reinstalling is the right answer

Reinstall the affected program when:

• Verification reports missing or damaged files.
• The program was interrupted during installation.
• The game was moved manually between drives.
• Its bundled DirectX installer was removed.
• The error names a DLL inside the game’s own folder.
• The program still fails after the Microsoft runtime is installed.

Uninstall the program through its normal installer or Windows settings, restart Windows, then install it again from the official vendor or launcher. If the installer offers to install DirectX components, allow that step to complete.

For a file belonging to one particular game, reinstalling that game remains the definitive repair for a damaged application-local copy.

Fix 3: Check whether antivirus quarantined the file

Security software may remove a DLL from a game directory after detecting a suspicious or modified file. It may also quarantine a legitimate file if the installer or application was altered.

Do not broadly disable antivirus protection to install an unverified DLL.

Check Protection History

1. Open Start.
2. Search for Windows Security.
3. Open it.
4. Select Virus & threat protection.
5. Select Protection history.
6. Review recent detections.
7. Look for an entry naming d3dcompiler_34.dll, the affected game, or its installer.
8. Open the detection details.
9. Confirm that the original source was a trusted game installer or Microsoft runtime package.

If the file came from a trusted, unmodified installer and the detection is a false positive, use the available Restore action. Windows may detect the file again. Only allow it when you have verified the source and understand what was restored.

If the DLL came from a random download page, do not restore it. Remove it and reinstall the application or DirectX runtime from an official source.

How to tell whether quarantine caused the failure

Quarantine is a likely cause when:

• The program worked before a security alert.
• The error appeared immediately after an update or cleanup scan.
• Protection History names the game directory or DLL.
• Reinstalling the game temporarily restores the file, but it disappears again.

If the file is repeatedly quarantined, scan the full system and investigate the application installer. Repeated deletion can indicate a modified installer, an unwanted program, or a genuinely suspicious file.

Fix 4: Check the application architecture and file path

Both 32-bit and 64-bit variants of legacy DirectX compiler files exist. The application’s architecture determines which one it needs.

On 64-bit Windows:

• C:\Windows\System32 contains 64-bit system binaries.
• C:\Windows\SysWOW64 contains 32-bit system binaries.

The names are confusing, but this is normal Windows behavior. A 32-bit application needs the x86 DLL even when it is running on 64-bit Windows. A 64-bit application needs the x64 DLL.

Do not choose the DLL based only on the operating system’s bitness.

Find the path named by the error

Read the complete error dialog carefully. The path can reveal which installation is failing.

• A path beside the game executable points toward an application-local problem.
• A path under System32 points toward a 64-bit or system-wide lookup.
• A path under SysWOW64 points toward a 32-bit or system-wide lookup.
• A path under a temporary folder or an unexpected user-writable directory deserves additional scrutiny.

Windows searches the application directory before other locations. An incorrect application-local DLL can therefore override a correct system-wide copy. Microsoft describes this behavior in its documentation for dynamic-link library redirection.

Check the file properties

If the file exists:

1. Right-click d3dcompiler_34.dll.
2. Select Properties.
3. Open the Details tab.
4. Record the file version and product information.
5. Open the Digital Signatures tab if it is present.
6. Select the signer.
7. Select Details.
8. Check whether Windows reports that the digital signature is valid.

A cataloged 64-bit copy is commonly reported as version 9.19.949.46 and approximately 1.34 MB, but legacy packages can contain different builds. File version and size alone do not prove that a DLL is safe or appropriate.

A file that is the wrong architecture, truncated, unsigned, or located in an unexpected directory should be replaced through the official runtime or the program’s installer, not by copying a similarly named file from another computer.

Fix 5: Install pending Windows updates

Windows Update is not a substitute for the legacy DirectX runtime, but it can repair broader operating-system and driver problems that interfere with installation or application startup.

1. Open Start.
2. Select Settings.
3. Select Windows Update.
4. Select Check for updates.
5. Select Download & install if updates are available.
6. Restart when Windows requests it.
7. Check for updates again after the restart.
8. Run the affected application.

Microsoft’s current instructions are in Install Windows updates.

If Windows Update reports errors, resolve those errors separately before assuming that it installed the DirectX compiler DLL. The optional D3DCompiler*.dll files are not guaranteed to be restored by normal Windows Update.

Fix 6: Repair broader Windows corruption with DISM and SFC

Use DISM and SFC when several Windows components are failing, DirectX setup reports operating-system corruption, or the problem began after a damaged update or storage failure.

They are not the primary way to restore d3dcompiler_34.dll. Microsoft identifies this compiler family as an optional deployable DirectX component rather than an in-box Windows component. That means the June 2010 DirectX runtime or the affected program’s installer should remain your first repair source.

Run DISM and SFC in the correct order

1. Open Start.
2. Type Command Prompt.
3. Right-click Command Prompt.
4. Select Run as administrator.
5. Select Yes if User Account Control appears.
6. Run this command:

DISM.exe /Online /Cleanup-image /Restorehealth

1. Wait for DISM to finish. Do not close the window while it is working.
2. When DISM completes, run:

sfc /scannow

1. Wait until the verification reaches 100 percent.
2. Restart Windows.
3. Run DXSETUP.exe again if DirectX setup previously failed.
4. Launch the affected program.

Microsoft recommends running DISM before SFC. See Using System File Checker in Windows.

Interpret the result

• Windows Resource Protection did not find any integrity violations: SFC found no protected Windows corruption. Continue with DirectX setup and application repair.
• Windows Resource Protection found corrupt files and successfully repaired them: Restart and test the application.
• Windows Resource Protection found corrupt files but was unable to fix some of them: Run DISM again, check Windows Update, and review the CBS log if deeper repair is needed.
• DISM cannot find source files: Windows may need access to a matching repair source.

Microsoft documents this form when Windows Update cannot provide the required files:

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

Replace C:\RepairSource\Windows with a valid, matching Windows installation source. Do not use a random folder or an installation source from a different Windows edition.

If SFC succeeds but the original error remains, that does not prove SFC failed. It may have repaired Windows files while leaving the optional DirectX compiler dependency untouched.

Outbyte PC Repair can reduce the guesswork when you are repeatedly hunting through Windows repair steps: its free scan shows what it identifies, while repair is performed by the full version. It is optional, and reinstalling the affected game remains the definitive fix when that program owns the damaged file.

Fix 7: Do not use Windows Features as a random DirectX repair

Windows includes optional features that some older software needs, but enabling features at random will not normally install d3dcompiler_34.dll.

In particular, DirectPlay under Legacy Components is a compatibility feature for older networking behavior. It is separate from the Direct3D HLSL compiler DLL.

If a game specifically says it requires DirectPlay, you can check it as follows:

1. Open Start.
2. Search for Windows Features.
3. Select Turn Windows features on or off.
4. Expand Legacy Components.
5. Select DirectPlay only if the game’s documentation or error message requires it.
6. Select OK.
7. Restart Windows if requested.
8. Test the game.

Do not enable DirectPlay as a substitute for installing the DirectX End-User Runtime. It does not provide d3dcompiler_34.dll.

Fix 8: Update or reinstall the graphics driver only for broader symptoms

A graphics-driver reinstall is not the normal fix for a missing d3dcompiler_34.dll. The compiler DLL is a DirectX runtime dependency, not the display driver itself.

Investigate the driver when you also see:

• Crashes in several unrelated DirectX applications.
• Display corruption or flickering.
• Black screens.
• Device Manager warnings.
• Failures that began immediately after a driver update.
• A graphics card that is not detected correctly.

Reinstall through Device Manager

1. Right-click Start.
2. Select Device Manager.
3. Expand Display adapters.
4. Right-click the graphics processor.
5. Select Uninstall device.
6. Review the confirmation options carefully.
7. Select Uninstall.
8. Restart Windows.
9. Allow Windows to detect and reinstall the display driver.
10. Test the affected application.

Microsoft documents this process in Update drivers through Device Manager in Windows.

If the issue started after a recent driver update, use the device’s Properties page and check whether Roll Back Driver is available. For a normal missing-DLL error without wider graphics symptoms, return to the DirectX runtime and application repair steps instead.

Outbyte Driver Updater can save time when identifying stale drivers across a system: its free scan shows what it finds, while driver installation is performed by the full version. It is optional, and reinstalling DirectX remains the correct repair for this missing compiler DLL.

Why regsvr32 is the wrong command

Do not run:

regsvr32 d3dcompiler_34.dll

regsvr32 is intended for DLLs that provide registration entry points such as DllRegisterServer, commonly used by COM or ActiveX components. Microsoft explains the command’s intended scope in its regsvr32 documentation.

d3dcompiler_34.dll is loaded by an application as a DirectX compiler dependency. It is not repaired by registering it. Running regsvr32 can produce another error, including a missing entry point or architecture mismatch, which makes the original problem harder to understand.

The correct actions are:

• Install the official DirectX runtime.
• Repair or reinstall the affected program.
• Verify the game files.
• Check antivirus quarantine.
• Match the application architecture.
• Repair Windows only when broader corruption is present.

Why random DLL downloads are risky

Random DLL download websites are a common source of bad advice for this error.

A downloaded file may be:

• The wrong x86 or x64 architecture.
• A different legacy compiler build.
• Modified or corrupted.
• Missing its own dependencies.
• Unsigned or falsely labeled.
• Incompatible with the application.
• Carrying malware or another unwanted program.

Even a genuine copy may not fix the root cause if the application installation is incomplete or another dependency is missing.

Do not:

• Download d3dcompiler_34.dll from an arbitrary DLL repository.
• Copy it from another computer.
• Overwrite System32 blindly.
• Overwrite SysWOW64 blindly.
• Replace an application-local file with a file from an unrelated game.
• Assume 64-bit Windows requires the x64 DLL for every program.

Use Microsoft’s DirectX End-User Runtime Web Installer, the full June 2010 offline package, or the affected application’s official installer.

Manual application-local deployment can be valid for developers and software vendors deploying a verified, matching DLL beside their own executable. It is not the recommended consumer repair procedure.

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

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

A missing-file message does not always mean the named file is absent. The loader may be looking in a different directory, may need a different architecture, or may be reporting a missing dependency of the DLL.

Check these details:

1. Record the complete path shown in the error.
2. Check whether the application is 32-bit or 64-bit.
3. Check the file’s Properties and Digital Signatures tabs.
4. Repair the application if the file is beside its executable.
5. Install the official DirectX runtime if the file is absent.
6. Check Protection History.
7. Test again after restarting Windows.

If the file is in the game folder, the game’s copy takes priority over a system-wide copy. A damaged application-local copy can therefore cause failure even when another copy exists elsewhere.

“Bad Image” and “Not designed to run on Windows”

Errors such as these usually mean Windows found a file but rejected it as invalid, corrupted, incompatible, or the wrong architecture. They do not prove that the DLL is simply missing.

Record:

• The exact error code, such as 0xc000007b or 0xc000012f.
• The full path shown in the dialog.
• Whether the application is 32-bit or 64-bit.
• The DLL’s file version and size.
• The result shown under Digital Signatures.
• Whether one program or many programs are affected.

A 0xc000007b error often points toward an architecture mismatch or another invalid dependency. Reinstalling a random DLL into System32 is especially unlikely to solve that situation.

Repair the affected program, reinstall the official DirectX runtime, and investigate other dependencies named in the error. If several unrelated programs show bad-image errors, treat the issue as possible system corruption or storage failure rather than continuing to replace individual DLLs.

System Restore for a recent change

Use System Restore when the failure clearly began after a driver installation, Windows update, cleanup utility, or software installation and a suitable restore point exists.

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

rstrui.exe

1. Press Enter.
2. Select Next.
3. Choose a restore point created before the failure began.
4. Select Scan for affected programs if available.
5. Review the programs and drivers that may be changed.
6. Select Next.
7. Select Finish.
8. Allow Windows to restart and complete the restoration.

System Restore can roll back system files, registry settings, drivers, and installed programs without intentionally deleting personal files. Microsoft’s guidance is available under System Restore.

Back up important files before using any recovery option. If the problem began after installing one game, repairing or reinstalling that game is usually more targeted than restoring the entire system.

If every normal fix fails

Escalate the diagnosis when:

• The affected program is obsolete or incompatible with the current Windows release.
• The game installer contains a broken or incomplete DirectX redistributable.
• The error appears before login, suggesting a startup program rather than the game.
• Several unrelated programs fail with different DLL errors.
• The DLL is recreated and quarantined repeatedly.
• The disk reports errors or Windows has other signs of corruption.
• The program works for another Windows user profile but not the current one.
• The failure continues after a clean application reinstall and official DirectX installation.

For repeated file corruption, scan the system, check drive health, and preserve important data. If many unrelated DLLs produce bad-image errors, consider Windows recovery or an in-place repair installation instead of replacing files individually.

Prevention

Once the program works again:

• Keep the game or application installed through its official launcher.
• Do not remove bundled DirectX redist folders during cleanup.
• Allow the installer’s DirectX setup step to finish.
• Keep Windows and graphics drivers current.
• Check antivirus quarantine before restoring or allowing a file.
• Do not use generic DLL download pages as a maintenance source.
• Keep separate installers or recovery media for older games you still use.
• Avoid copying DLLs between computers unless you are a developer deploying a verified application-local dependency.
• Record the exact application, path, architecture, and error code if the message returns.

Frequently asked questions

Is d3dcompiler_34.dll a Windows system file?

It can be installed into a Windows system directory by DirectSetup, but it is not an in-box Windows component merely because Windows includes DirectX 11 or DirectX 12. Microsoft describes the D3DCompiler*.dll files as deployable application or DirectSetup components.

Is d3dcompiler_34.dll part of Visual C++?

No. It is a Direct3D HLSL compiler DLL. Visual C++ Redistributables provide Microsoft C and C++ runtime libraries and do not automatically provide this DirectX component.

Should I install DirectX 12?

Windows 10 and Windows 11 already include modern DirectX technology. The relevant repair is the legacy DirectX End-User Runtime, especially the June 2010 package, which adds side-by-side components without replacing the main DirectX version.

Do I need the x64 file because I have 64-bit Windows?

Not necessarily. A 32-bit game needs the x86 DLL even on 64-bit Windows. A 64-bit application needs the x64 version. The application’s architecture matters more than the operating system’s architecture.

Should I copy the file into System32?

No. Install the official DirectX runtime or repair the application. Manual copying can place the wrong architecture or build in the wrong directory and can interfere with the application’s own files.

Will regsvr32 fix the error?

No. regsvr32 is for DLLs that support registration entry points such as DllRegisterServer. d3dcompiler_34.dll is a DirectX dependency loaded by applications, not a COM or ActiveX component that users repair by registering it.

Will SFC restore this DLL?

SFC can repair protected Windows components, but Microsoft’s deployment documentation identifies this compiler family as an optional DirectX component. Use the official DirectX runtime or the application installer first. Use DISM and SFC when broader Windows corruption is also suspected.

Why does the file exist but the game still fail?

The application may be loading a different copy, finding the wrong architecture, or reporting a missing dependency of the DLL. Check the full path, application architecture, file signature, and application installation.

What if only one game reports the error?

Install the official DirectX runtime, then verify or repair that game. If the error names a DLL inside the game directory, reinstalling the game may be necessary.

What if several games report DirectX errors?

Install the legacy DirectX runtime first, then check Windows Update and investigate the graphics driver if you also see display corruption, crashes across multiple applications, or Device Manager warnings.

What is the safest source for d3dcompiler_34.dll?

Do not obtain it as an isolated file from a random download page. Use Microsoft’s DirectX End-User Runtime Web Installer, the full DirectX End-User Runtimes (June 2010), or the affected program’s official installer.

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.