d3dcompiler_38.dll Not Found: Causes and Safe Fixes for Windows 10/11

If Windows reports that d3dcompiler_38.dll is missing, install the official legacy DirectX runtime rather than downloading an individual DLL. d3dcompiler_38.dll is a versioned Microsoft Direct3D HLSL shader-compiler component, and the correct package is usually the DirectX End-User Runtime.

Identification detail	What it means
File name	d3dcompiler_38.dll
Category	DirectX
Component type	Versioned Direct3D HLSL compiler runtime
_38 generation	DirectX SDK June 2008 compiler generation
Normal source	The legacy DirectX runtime or the program that installed it
Modern DirectX status	Separate from the core DirectX runtime included with Windows
Architecture	The application must receive the matching x86 or x64 component
Public identification clues	Some inventories report version 9.23.949.2378, with different approximate sizes for x86 and x64 files. These are clues only, not Microsoft integrity standards.

The safest fix for d3dcompiler_38.dll

Start with Microsoft’s DirectX End-User Runtime Web Installer. Download dxwebsetup.exe, close the affected application, run the installer, and allow it to complete.

As an Amazon Associate I earn from qualifying purchases.

If the web installer fails, use Microsoft’s DirectX End-User Runtimes (June 2010). This package contains the June 2010 and earlier side-by-side DirectX components, including the legacy compiler family required by older software.

The offline package does not install immediately when you launch it. It first extracts its files. After extraction:

1. Choose a temporary folder when the package asks where to extract its contents.
2. Open that folder in File Explorer.
3. Run DXSETUP.exe.
4. Accept the license terms and complete setup.
5. Launch the affected game or application again.

Restart Windows if the installer requests it. If the application still reports the same error, continue with the application-specific checks below.

What d3dcompiler_38.dll actually is

D3DCompiler_38.dll is a Direct3D compiler library used to compile or support High-Level Shader Language code. In practical terms, older games and 3D applications can use it while preparing graphics shaders for the Direct3D renderer.

The number in the file name matters. _38 identifies a particular legacy compiler generation associated with the DirectX SDK June 2008 release. It is not a generic name that can be replaced with any other DirectX compiler DLL.

These files are separate components:

• d3dcompiler_38.dll
• d3dcompiler_43.dll
• d3dcompiler_47.dll
• d3d11.dll
• graphics-card driver files
• Microsoft Visual C++ runtime files

An application built against _38 can request that exact file even if _43 or _47 is already installed. Renaming another compiler DLL does not make it equivalent and can create an invalid or incompatible installation.

Microsoft designed older DirectX components to coexist side by side. The core DirectX runtime included with modern Windows does not guarantee that every optional library from older DirectX SDK releases is present. Microsoft’s DirectX installation guidance explains why applications can still need the legacy End-User Runtime.

Does Windows 10 or Windows 11 include this DLL?

Windows 10 and Windows 11 include modern DirectX components, but that does not mean they include every optional legacy DirectX SDK library.

This distinction explains many of these errors:

• The operating system can support DirectX 12.
• dxdiag can report a modern DirectX version.
• A game can still fail because its older installer needs d3dcompiler_38.dll.
• Installing the legacy End-User Runtime does not replace the modern DirectX core built into Windows.
• The legacy package adds optional side-by-side libraries needed by older applications.

After installation, the file may be placed in a Windows system directory such as System32 or SysWOW64, depending on architecture and Windows file-system redirection. A game or tool can also keep its own copy beside its executable.

A copy in System32 does not prove that the file originally shipped as an inbox Windows 10 or Windows 11 component. It may have been added by a game installer, a graphics application, or the DirectX End-User Runtime.

The dxdiag version number is therefore not a complete inventory of optional DirectX libraries. If the error specifically names d3dcompiler_38.dll, install the legacy runtime instead of relying on the DirectX version shown by diagnostics.

Error messages you may see

The wording depends on the Windows version, the application, and whether the file itself or one of its dependencies is causing the failure. Common messages include:

This application has failed to start because D3DCompiler_38.dll was not found.

The program can't start because d3dcompiler_38.dll is missing from your computer.

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

Error loading d3dcompiler_38.dll.
The specified module could not be found.

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

You may also see:

0xc000007b

“The specified module could not be found” does not always mean that the named DLL is absent. Windows may have found d3dcompiler_38.dll but failed to load one of its dependencies. A “not designed to run on Windows” message can indicate corruption, an architecture mismatch, or a damaged dependency.

Fix 1: Install the official DirectX Web Installer

This is the best first step when an older game or 3D application fails soon after installation, especially on a newly installed or recently reset computer.

Microsoft lists the web installer as dxwebsetup.exe. The package page identifies it as the DirectX End-User Runtime Web Installer.

Steps

1. Open Microsoft’s DirectX End-User Runtime Web Installer.
2. Download dxwebsetup.exe.
3. Open the downloaded file from your browser’s download list or the Downloads folder.
4. If Windows displays a security prompt, confirm that the publisher is Microsoft.
5. Accept the license terms.
6. Decline any optional offer that is unrelated to DirectX if one appears.
7. Let setup detect and install the required legacy components.
8. Click through to finish the installation.
9. Start the game or application again.

The web installer downloads the components needed by the computer, so it requires an active internet connection. The Microsoft page lists package version 9.29.1974.1.

How to tell whether it worked

The clearest test is to launch the application that produced the error. If it reaches its menu or main interface without the missing-DLL message, the runtime installation solved the problem.

Do not use the DirectX version shown by dxdiag as the only test. A modern DirectX version can still be present even when an optional legacy compiler file is missing.

If the web installer fails

Use the offline package described in the next section. It is also useful when the affected computer has restricted internet access or when the web installer completes without resolving the exact file.

Fix 2: Run the June 2010 offline package and DXSETUP.exe

The offline package is Microsoft’s DirectX End-User Runtimes (June 2010). Microsoft describes it as containing the complete set of June 2010 and earlier side-by-side components.

The download is named directx_Jun2010_redist.exe. The package page lists version 9.29.1974.1.

Steps

1. Open Microsoft’s June 2010 DirectX package page.
2. Download directx_Jun2010_redist.exe.
3. Open the downloaded file.
4. When asked for an extraction location, create or select a temporary folder, such as a folder on the Desktop named DirectX-Jun2010.
5. Wait for extraction to finish.
6. Open the extraction folder.
7. Find DXSETUP.exe.
8. Right-click DXSETUP.exe and select Run as administrator.
9. Accept the license terms.
10. Allow the setup program to install the legacy components.
11. Restart Windows if prompted.
12. Start the affected application.

The first executable extracts the package. DXSETUP.exe performs the actual DirectX installation. Running only the self-extracting package without completing DXSETUP.exe is a common reason the problem remains.

How to tell whether it worked

Launch the original program. If it starts, reaches its normal loading screen, or gets past the point where the missing file was reported, the installation succeeded.

If the error remains, do not immediately download a second copy of the DLL from an unrelated website. Move to the application-specific repair steps. The problem may be a damaged app-local copy, a wrong architecture, or a missing dependency.

Fix 3: Run the program’s own DirectX installer

Many older games include their required DirectX files in the installation folder. The installer is often stored in a path resembling:

Redist\DirectX\DXSETUP.exe

The exact folder name varies by product.

Steps

1. Close the game or application.
2. Open its installation folder.
3. Look for folders named Redist, DirectX, Support, Prerequisites, or Installers.
4. Search inside those folders for DXSETUP.exe.
5. Right-click it and select Run as administrator.
6. Complete the setup.
7. Launch the game again.

If the application was installed through Steam, Epic, GOG, or another launcher, the prerequisite files may be inside the launcher’s game library rather than in the Downloads folder.

When this is the right fix

Use the bundled installer when only one game or tool fails and other Direct3D applications work normally. It can restore the exact runtime generation expected by that product.

An application can intentionally load a DLL from its own directory. Windows searches the application directory as part of the DLL loading process, so a damaged local file can cause an error even when a usable system copy exists.

Microsoft documents this behavior in its DLL search order documentation.

Fix 4: Verify or repair the game files

If the error affects only one installed game, the local installation may be incomplete or corrupted. This can happen after a failed update, a partial restore from backup, interrupted file movement, or antivirus quarantine.

Use the launcher’s built-in verification function before manually replacing files.

Epic Games Launcher

1. Open Epic Games Launcher.
2. Select Library.
3. Find the affected game.
4. Click the three dots beside the game.
5. Select Manage.
6. Select Verify.
7. Wait for the check to finish.
8. Launch the game again.

Verification checks for damaged or changed files and replaces them without affecting saved data.

Other launchers

Steam, GOG, and other launchers use similar commands, although the labels differ. Look for:

• Verify integrity of game files
• Verify
• Repair
• Validate
• Scan and repair

If verification reports damaged files, allow the launcher to replace them. If the game still fails afterward, run its bundled DXSETUP.exe as well.

How to tell whether it worked

A successful repair normally lets the game start without the original loader error. If the launcher replaces d3dcompiler_38.dll and the same file is quarantined again immediately, inspect Windows Security before trying another repair.

Fix 5: Check Windows Security quarantine

Antivirus software can quarantine a file from a game folder or installer. A cleanup utility can also remove older runtime files that appear unused.

Do not automatically restore a quarantined DLL. First determine where it came from.

Steps

1. Open Start.
2. Type Windows Security.
3. Open Windows Security.
4. Select Virus & threat protection.
5. Select Protection history.
6. Review recent detections.
7. Open any detection related to the affected game, application, or DirectX file.
8. Check the original file path and detection details.

Microsoft explains the Protection History process in its Windows Security Protection History documentation.

What to do with the result

If the file came from Microsoft’s DirectX installer or the legitimate application installer, reinstalling that package is preferable to restoring an isolated file. A clean reinstall gives you a known source and can restore related dependencies.

If the file came from a random DLL download site, an unknown archive, or an unexpected location, do not restore it. Remove the untrusted file and run a Windows Security scan.

How to tell whether this was the cause

After reinstalling the official runtime or repairing the game, check Protection History again. If the same legitimate file is quarantined repeatedly, confirm the file’s origin and allow only a verified application through the relevant security controls. Do not create a broad antivirus exclusion just to make an unknown DLL load.

Fix 6: Check whether the application needs x86 or x64

A 32-bit application needs the x86 version of the library. A 64-bit application needs the x64 version.

On 64-bit Windows, the directory names are historically confusing:

• System32 contains 64-bit system binaries.
• SysWOW64 contains 32-bit system binaries.

Microsoft describes this behavior in its File System Redirector documentation.

Why this matters

A 32-bit game can fail if it receives only a 64-bit compiler DLL. A 64-bit application can fail if an incorrect 32-bit file has been copied beside its executable. The error may appear as a missing DLL, an invalid image, or 0xc000007b.

The official DirectX installer handles the required component architecture. That is safer than deciding which file belongs in which system folder yourself.

Steps to identify the application architecture

There is no single universal click path for every program, but these checks are useful:

1. Check the game’s documentation or installation folder.
2. Look for separate executable names or folders containing x86, x64, or Win64.
3. Check the launcher’s system requirements.
4. If the application provides its own diagnostic or log window, review whether it identifies itself as 32-bit or 64-bit.
5. Install the official DirectX package rather than copying files into system folders.

Do not put both architectures into both system directories. Do not overwrite a working file simply because its name looks similar.

Fix 7: Install Windows updates

Windows Update is not the primary source for this particular legacy DirectX DLL, but updates can repair broader Windows components, security services, or device support that affect application startup.

Steps

1. Open Start.
2. Select Settings.
3. Select Windows Update.
4. Select Check for updates.
5. Install the available updates.
6. Restart Windows if prompted.
7. Test the affected application again.

Microsoft’s Windows Update instructions cover this process.

If Windows Update reports that the system is current and the same file is still missing, return to the official DirectX installer. Do not assume that a current Windows build contains every optional legacy DirectX component.

Fix 8: Repair Windows components with DISM and SFC

Use DISM and SFC when multiple unrelated Windows features or applications are damaged, not as the first replacement method for an optional DirectX side-by-side file.

Microsoft documents DISM as a tool for repairing the Windows component store and SFC as a tool for checking protected Windows system files.

Run DISM first

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 complete.
3. Keep the Command Prompt window open.

DISM can take time and may appear to pause. Do not close it merely because progress is slow.

Run SFC second

After DISM finishes, enter:

sfc /scannow

Press Enter and wait until verification reaches 100 percent.

What success looks like

DISM should report that the restore operation completed successfully or that no component-store corruption was detected. SFC should report whether it found and repaired integrity violations.

Restart Windows after both commands finish and test the application.

These commands may repair Windows-protected files, but they are not guaranteed to restore d3dcompiler_38.dll because this DLL is an optional legacy DirectX component rather than a normal protected inbox Windows file.

If repeating DISM and SFC without knowing what changed is wasting time, Outbyte PC Repair can use a free scan to show broader Windows problems; repair is handled by the full version, and it is not required for the official DirectX repair.

For the official procedures, see Microsoft’s DISM repair guidance and System File Checker documentation.

Fix 9: Check Windows Features only for separate legacy requirements

Windows Features is not where d3dcompiler_38.dll is normally installed. Do not expect enabling a random Windows feature to supply this file.

If the game separately reports that it needs DirectPlay, you can check the legacy feature:

1. Open Start.
2. Type Windows Features.
3. Select Turn Windows features on or off.
4. Expand Legacy Components.
5. Select DirectPlay if the game specifically requires it.
6. Select OK.
7. Restart Windows if prompted.
8. Test the game again.

DirectPlay and the Direct3D compiler runtime are different components. Enabling DirectPlay will not replace a missing d3dcompiler_38.dll. Continue to use the Microsoft DirectX installer for the DLL error itself.

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

A graphics driver is not normally the source package for d3dcompiler_38.dll. Driver repair is appropriate when every Direct3D application fails, the display driver recently changed, Device Manager reports an error, or the screen shows broader graphics problems.

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. Review the Device status message.

If Windows reports a device problem, use the driver repair procedure.

Reinstall through Device Manager

1. Right-click Start.
2. Select Device Manager.
3. Expand Display adapters.
4. Right-click the affected adapter.
5. Select Uninstall device.
6. Confirm the uninstall.
7. Restart Windows.

Microsoft documents this Device Manager driver procedure. Windows will attempt to reinstall the driver after the restart.

Do not remove the DirectX compiler DLL while troubleshooting the driver. The driver and d3dcompiler_38.dll serve different roles.

Manually hunting through many driver versions can be tedious when it is unclear which component is stale. Outbyte Driver Updater can use a free scan to show which drivers need attention; installation is handled by the full version, and a driver tool is not required when the only problem is this legacy DirectX file.

How to tell whether the driver was involved

If all Direct3D applications begin working after the driver repair, the driver was likely part of the broader problem. If only one game still reports d3dcompiler_38.dll, return to that game’s bundled runtime and file verification instead.

Fix 11: Use System Restore when the timing is clear

System Restore is useful when the error appeared immediately after a cleanup program, driver change, software installation, or Windows change and a suitable restore point exists.

System Restore rolls back system files, settings, drivers, and installed programs while preserving personal files.

Steps

1. Open Start.
2. Type Control Panel.
3. Open Control Panel.
4. Select Recovery.
5. Select Open System Restore.
6. Choose a restore point created before the error began.
7. Review the affected programs and drivers.
8. Start the restore process.
9. Let Windows restart and complete the operation.

You can also open the System Restore interface by pressing Windows key + R, entering:

rstrui.exe

and selecting OK.

Do not choose a restore point at random. Use this method when the timing clearly matches a system change and the DirectX installer, game repair, and security checks have not solved the problem.

Fix 12: Check for malware when files keep disappearing

Malware is not the normal explanation for one missing DirectX compiler DLL, but investigate it when files are repeatedly removed, several unrelated executables are damaged, or Windows Security reports unexpected detections.

Basic scan

1. Open Start.
2. Type Windows Security.
3. Open Windows Security.
4. Select Virus & threat protection.
5. Select Quick scan.
6. Allow the scan to finish.
7. Review any detections.
8. Restart Windows if requested.

If a suspicious standalone DLL was downloaded from an untrusted source, remove it rather than trying to make it work. Reinstall the official runtime from Microsoft and scan the system.

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

Why regsvr32 does not fix this file

Do not run regsvr32 d3dcompiler_38.dll as a general installation command.

Microsoft documents regsvr32 as a utility for DLLs that expose registration entry points such as DllRegisterServer. It is intended for registerable components, including certain COM libraries.

The Direct3D compiler is a runtime library loaded by the application. It is not normally a COM component that needs to be registered in the Windows registry. Running the command can produce:

The module was loaded but the entry-point DllRegisterServer was not found.

That result does not mean the DirectX runtime is repaired. It means the DLL does not provide the registration entry point that regsvr32 expects.

See Microsoft’s regsvr32 documentation and D3DCompile API documentation for the distinction between a registerable DLL and a compiler runtime library.

What not to do

Do not download the DLL from a random DLL website

Standalone DLL download sites can provide:

• the wrong compiler generation;
• the wrong x86 or x64 architecture;
• a damaged or modified file;
• an incomplete set of dependencies;
• a file that fixes the message temporarily but leaves the application broken;
• malware disguised as a system component.

The safer sources are Microsoft’s DirectX Web Installer, Microsoft’s June 2010 offline package, and the original game or application installer.

Do not rename another compiler DLL

These are not interchangeable:

d3dcompiler_38.dll
d3dcompiler_43.dll
d3dcompiler_47.dll

Changing the name of _43 or _47 to _38 does not change the binary’s interfaces or dependencies. It can turn a clear missing-file error into an invalid-image error.

Do not copy files randomly into system folders

Do not copy a downloaded DLL into System32 or SysWOW64 just because a website recommends it. Do not put an x86 file into the 64-bit system directory or a 64-bit file into the 32-bit redirected directory.

The preferred repair is the official runtime installer. Manual extraction should be reserved for a narrow, controlled case involving a known-good file from the official redistributable or the original application installer.

Do not delete other DirectX files

Deleting d3dcompiler_43.dll, d3dcompiler_47.dll, or unrelated DirectX files will not force Windows to install _38. It can create new errors for applications that depend on those versions.

Do not assume Visual C++ is the same thing

Microsoft Visual C++ Redistributables are a separate runtime family. Install a Microsoft Visual C++ Redistributable only when the application also reports missing MSVC files or a separate Visual C++ runtime problem.

Manual copying as a controlled fallback

Manual copying is not the normal repair method, but it can be appropriate when an application is designed to use an app-local copy and the original official installer is available.

Use these rules:

1. Obtain the file from Microsoft’s official DirectX redistributable or the application’s original installer.
2. Extract the matching architecture.
3. Preserve the original filename.
4. Place it beside the affected executable only when that application uses an app-local runtime.
5. Do not copy an unknown file into a Windows system directory.
6. Do not overwrite _43 or _47.
7. Do not delete existing DirectX files.
8. Re-run the application’s repair or verification process if possible.

If the file was restored from the official package and the application still fails, the error may concern a dependency rather than d3dcompiler_38.dll itself. The application’s bundled installer or a complete reinstall is usually more reliable than continuing to copy individual files.

A practical diagnosis path

Use the scope of the failure to choose the next step.

Only one game or application fails

Start with:

1. Verify or repair the application files.
2. Run its bundled Redist\DirectX\DXSETUP.exe.
3. Install Microsoft’s June 2010 offline package.
4. Check antivirus Protection History.
5. Confirm that the application is not using a damaged local DLL.
6. Reinstall the application if its files remain incomplete.

This pattern usually points to a missing prerequisite, a damaged local installation, or an application-specific architecture problem.

Several older games or 3D tools fail

Start with:

1. Run the Microsoft DirectX Web Installer.
2. If necessary, run the June 2010 offline package and DXSETUP.exe.
3. Install Windows updates.
4. Run DISM, then SFC.
5. Review antivirus quarantine.
6. Check the display driver if every Direct3D application is affected.

Every Direct3D application fails

Look beyond this one DLL:

1. Check Device Manager for display-adapter errors.
2. Reinstall the graphics driver if appropriate.
3. Run Windows Update.
4. Run DISM and SFC.
5. Scan with Windows Security.
6. Consider System Restore if the problem began after a clear system change.

A driver problem can cause broad graphics failures, but it is not normally the package that supplies d3dcompiler_38.dll.

Frequently asked questions

Is d3dcompiler_38.dll a virus?

The file name belongs to a genuine Microsoft Direct3D compiler component. That does not mean every file with that name is trustworthy. Verify its source and prefer reinstalling it from Microsoft’s DirectX package or the legitimate application installer.

Can DirectX 12 install this file?

DirectX 12 support in Windows does not guarantee that optional legacy DirectX SDK libraries are installed. Use the DirectX End-User Runtime for older applications that specifically request _38.

Can I use d3dcompiler_43.dll instead?

No. The numbered compiler libraries are separate versions. A program linked against _38 may continue looking specifically for _38.

Should I put the file in System32?

Do not begin by copying the file manually. Install the official DirectX runtime so Windows receives the appropriate architecture. A game may also need an application-local copy, which is why repairing or reinstalling that game is important.

Is d3dcompiler_38.dll the same as a graphics driver?

No. It is a Direct3D shader-compiler runtime component. A graphics driver can cause other Direct3D failures, but it is not normally the source package for this DLL.

Will regsvr32 fix the error?

No. regsvr32 is for DLLs that support registration entry points. This Direct3D runtime library is loaded by the application and does not normally need registry registration.

Why does the error say “specified module could not be found” when the file exists?

Windows may be unable to load a dependency of the named DLL. The message can also result from the wrong architecture, a damaged local file, or an invalid dependency chain.

Does 0xc000007b mean the DLL is missing?

Not necessarily. 0xc000007b commonly points to an invalid image or architecture/dependency mismatch. Check x86 versus x64, remove manually copied runtime files, and repair the application with its official installer.

Should I run SFC first?

For this specific error, install or repair the legacy DirectX component first. Run DISM followed by SFC when several Windows components are damaged or the broader system appears unstable. SFC is not guaranteed to restore an optional legacy DirectX DLL.

What is the definitive fix if one game still fails?

Verify the game files, run its bundled DirectX setup, and reinstall the game from its original legitimate installer if necessary. When the file belongs to one specific application, repairing that application is more reliable than repeatedly copying a standalone DLL.

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.