d3dcompiler_47.dll Missing: Windows, DirectX, and Game Repairs

“The program can’t start because D3DCOMPILER_47.dll is missing from your computer.” If Windows reports that d3dcompiler_47.dll was not found or could not be loaded, use the repair path that matches your Windows version, application, and error location.

Do not download this DLL from a random DLL website or copy an unknown file into System32. The file may be the wrong architecture, an incompatible version, corrupted, or bundled with malware. The safest sources are Windows Update, Microsoft servicing packages, and the official installer for the affected application.

As an Amazon Associate I earn from qualifying purchases.

Which fix applies to you

Use this list before changing anything:

• Windows 10 or Windows 11, and several programs are affected: install pending Windows updates, then run DISM and SFC.
• One game or application is affected: repair or verify that application first. It may use its own copy of the DLL.
• Windows 7 SP1, Windows Server 2008 R2 SP1, or Windows Server 2012: install Microsoft update KB4019990.
• Windows Server 2008 SP2: install KB4019478 instead.
• The file is present but Windows says it is invalid or “not designed to run on Windows”: check the file location, architecture, version, signature, and antivirus history.
• The problem began after a graphics update and involves crashes or rendering failures: inspect or reinstall the graphics driver.
• The message appears after antivirus removed a file: investigate Protection History before restoring anything.
• The error names another DLL too: repair that dependency separately. Visual C++ files and DirectX legacy files are not interchangeable with d3dcompiler_47.dll.

What d3dcompiler_47.dll does

d3dcompiler_47.dll is a Microsoft Direct3D compiler runtime library. It provides functions used to compile, inspect, and process HLSL shaders, including APIs such as D3DCompile, D3DCompileFromFile, and D3DReflect. Microsoft lists these APIs in its Windows API availability documentation.

Games and graphics applications use the compiler when preparing shader code for rendering. A missing file can therefore stop an application during startup, but the error does not automatically mean that the graphics card or its driver is defective.

The file is related to Direct3D, but several common descriptions are misleading:

• It is not a Visual C++ Redistributable file.
• It is not normally installed by a graphics-card driver.
• It is not the same as the older d3dcompiler_33.dll through d3dcompiler_43.dll files installed by some legacy DirectX packages.
• It is not a COM or ActiveX server that needs registration with regsvr32.
• It may be supplied by Windows or deployed beside a particular application.

Microsoft documents that the D3DCompiler runtime is included in Windows 10, while developers may also deploy an application-local copy. The Microsoft GDK framework package documentation distinguishes the Windows 10 SDK version from older side-by-side DirectX components.

First check the erroring file and Windows version

The same filename can exist in multiple places. Before repairing anything, identify which copy the application is expected to load.

Press Windows key + R, type:

winver

Press Enter and record the Windows edition and version.

Then check these locations in File Explorer:

%windir%\System32\d3dcompiler_47.dll
%windir%\SysWOW64\d3dcompiler_47.dll

On 64-bit Windows:

• System32 normally contains the 64-bit system DLL.
• SysWOW64 normally contains the 32-bit system DLL.
• A 32-bit program cannot load the 64-bit DLL.
• A 64-bit program cannot load the 32-bit DLL.

This naming is confusing, but SysWOW64 is the normal Windows location for 32-bit system files on a 64-bit installation. Microsoft explains this behavior in its documentation for the file-system redirector and running 32-bit applications.

Also inspect the folder containing the affected program. An application can contain its own copy:

C:\Program Files\Example App\d3dcompiler_47.dll
C:\Program Files (x86)\Example Game\d3dcompiler_47.dll

An application-local copy can have a different version from the Windows copy. Windows’ DLL search order may cause the program to load its private copy first. Multiple copies are therefore not automatically evidence of malware.

Fix 1: Repair Windows 10 or Windows 11

For a system-wide failure on Windows 10 or Windows 11, start with Windows Update and then repair the Windows component store.

Install pending Windows updates

On Windows 11:

1. Open Start > Settings.
2. Select Windows Update.
3. Select Check for updates.
4. Install all available quality, cumulative, and servicing updates.
5. Restart when Windows requests it.
6. Check for updates again after restarting.

On Windows 10:

1. Open Start > Settings.
2. Select Update & Security.
3. Select Windows Update.
4. Select Check for updates.
5. Install the available updates.
6. Restart the PC and check again.

Microsoft’s current update instructions are available in Install Windows updates.

Run DISM and SFC

Open an elevated Command Prompt:

1. Open Start.
2. Type Command Prompt.
3. Right-click Command Prompt.
4. Select Run as administrator.
5. Select Yes if User Account Control asks for permission.

Run these commands separately:

DISM.exe /Online /Cleanup-Image /RestoreHealth

Wait for it to finish. Then run:

sfc /scannow

DISM repairs the Windows component store that SFC uses as a source. SFC then checks protected Windows files and replaces damaged copies when possible. Microsoft recommends this order in its System File Checker instructions and Windows image repair documentation.

Restart after SFC completes and test the program again.

Success usually looks like one of these outcomes:

• The application starts normally.
• SFC reports that it found corrupt files and repaired them.
• The missing-file message disappears after restarting.

If DISM reports that source files could not be found, install pending updates first and run the command again. If SFC repeatedly reports corruption that it cannot repair, continue to the application-specific and security checks below rather than repeatedly replacing DLLs manually.

If you prefer help identifying which Windows components are damaged instead of repeatedly guessing through DISM and SFC results, Outbyte PC Repair can scan for reported Windows problems; its free scan shows what it found, while repair is handled by the full version.

Check Windows Features only when .NET is involved

d3dcompiler_47.dll is not repaired simply by enabling a random Windows feature. However, a program may also depend on .NET Framework.

To inspect the available .NET features:

1. Press Windows key + R.
2. Type optionalfeatures.
3. Press Enter.
4. Look for .NET Framework 3.5 (includes .NET 2.0 and 3.0) and .NET Framework 4.8 Advanced Services.
5. Enable a feature only when the application documentation or its error specifically requires it.
6. Select OK and allow Windows to obtain the required files.
7. Restart if requested.

On older Windows versions, .NET Framework 4.7 WPF depends on D3DCompiler_47.dll. Microsoft states that Windows 7 SP1, Windows Server 2008 R2 SP1, and Windows Server 2012 did not include the file by default and require the relevant update before .NET Framework 4.7 can be installed. This is described in Microsoft’s known issue for .NET Framework 4.7.

Fix 2: Install the correct update on older Windows

The Windows 7-era fix is different from the Windows 10 and Windows 11 repair path.

Windows 7 SP1, Server 2008 R2 SP1, and Server 2012

Install KB4019990, titled “Update for the d3dcompiler_47.dll component on Windows Server 2012, Windows 7, and Windows Server 2008 R2.”

Use Windows Update first:

1. Open Control Panel.
2. Select System and Security.
3. Select Windows Update.
4. Select Check for updates.
5. Install the offered update if KB4019990 appears.
6. Restart the computer.
7. Test the affected program.

If Windows Update does not offer it, use the Microsoft Update Catalog search for KB4019990. Choose the package matching the exact Windows edition and architecture. Do not install x86 and x64 packages randomly.

Microsoft documents the update, its prerequisites, and its historical file details in the KB4019990 article.

Windows Server 2008 SP2

Windows Server 2008 SP2 uses a different package: KB4019478.

Install it through Windows Update when available, or follow Microsoft’s KB4019478 article.

Windows 7 support ended in 2020, so these older systems should be treated as legacy environments. Avoid using a Windows 10 or Windows 11 DLL as a substitute.

When KB4019990 says “not applicable”

Do not keep trying unrelated packages. “Not applicable” commonly means one of the following:

• The operating system is not supported by that update.
• The required service pack or servicing prerequisite is missing.
• The package architecture does not match the installation.
• The update is already installed or has been superseded.
• The application needs a private copy rather than a Windows system copy.
• Windows servicing itself is damaged.

Check winver, open Control Panel > System and Security > System, and review installed updates under Control Panel > Programs > View installed updates.

If the file is missing only from one application folder, KB4019990 may not address the problem. Repair that application instead.

Fix 3: Repair one affected game or application

If Windows works normally and only one program reports the error, treat the application installation as the primary suspect.

Repair an installed Windows application

For an application with a repair option:

1. Open Settings.
2. Select Apps.
3. Select Installed apps on Windows 11, or Apps & features on Windows 10.
4. Select the application.
5. Open its advanced options if available.
6. Select Repair.
7. Start the application again.

If there is no repair option, uninstall and reinstall the application from its official installer or store. Save settings and game saves first if the application stores them locally.

Verify a Steam game

1. Open Steam.
2. Open Library.
3. Right-click the affected game.
4. Select Properties.
5. Open Installed Files.
6. Select Verify integrity of game files.
7. Wait for the check to finish.
8. Start the game again.

Verification can restore an application-local copy of d3dcompiler_47.dll. It cannot repair a missing Windows system component.

Verify an Epic Games installation

1. Open Epic Games Launcher.
2. Open Library.
3. Find the game.
4. Select the three-dot menu beside it.
5. Select Manage.
6. Select Verify.
7. Wait for the process to finish and start the game.

Repair a GOG Galaxy installation

1. Open GOG Galaxy.
2. Select the affected game.
3. Open Manage installation.
4. Select Verify / Repair.
5. Wait for the repair to complete.
6. Start the game again.

For another launcher, look for an option named Verify, Repair, Scan, or Verify game files. If the launcher repeatedly removes the same DLL after verification, inspect antivirus history before running the game again.

Fix 4: Check antivirus quarantine

Security software can quarantine an application-local DLL. A missing-file dialog does not prove that this happened, so confirm it.

In Windows Security:

1. Open Start.
2. Type Windows Security.
3. Open the application.
4. Select Virus & threat protection.
5. Select Protection history.
6. Look for a detection involving d3dcompiler_47.dll.
7. Check the full path, detection name, publisher, and action taken.

Do not restore a quarantined file merely because the application requests it. First:

1. Update the application from its official source.
2. Update antivirus definitions.
3. Scan the file and its parent folder.
4. Check the file’s digital signature in Properties > Digital Signatures.
5. Confirm that the path belongs to the expected application.
6. Restore or allow the file only if you have established that the detection is a false positive.

Microsoft explains the risks of allowing files and how to use Protection History.

If the file was in a temporary folder, a modified game directory, a plug-in folder, or an unfamiliar location, do not restore it. Reinstall the application from its official source and scan the system.

Fix 5: Check architecture and incompatible copies

A file can exist and still fail to load.

Common causes include:

• A 32-bit application finding a 64-bit DLL.
• A 64-bit application finding a 32-bit DLL.
• An application-local copy being older or damaged.
• A third-party installer replacing the expected file.
• A dependency of the named DLL being missing.
• A file being blocked by security software.
• The application loading a different copy because of DLL search order.

Some file versions seen on Windows builds include 32-bit and 64-bit variants with version strings such as 10.0.16299.15, 10.0.17134.12, 10.0.17763.132, and 10.0.18362.1. These are examples, not universal versions for every Windows installation. The correct file depends on the operating-system build, architecture, servicing level, and application.

To inspect a file:

1. Right-click d3dcompiler_47.dll.
2. Select Properties.
3. Open Details.
4. Review File version and Product version.
5. Open Digital Signatures if that tab is present.
6. Confirm the path and signer before taking action.

Do not overwrite a system file with a version copied from another computer. A file that appears newer may still be incompatible with the application or operating system.

Fix 6: Update or reinstall the graphics driver only for driver-related symptoms

A graphics driver is not the normal source of a simple “file not found” error. Driver work becomes relevant when the application starts but crashes during rendering, reports a faulting graphics module, displays corrupted graphics, or specifically documents a delayed-load failure involving this DLL.

Check the installed graphics adapter

1. Right-click Start.
2. Select Device Manager.
3. Expand Display adapters.
4. Note the graphics adapter name.
5. Right-click the adapter and select Properties.
6. Open the Driver tab.
7. Record the provider, date, and version.

To try Windows’ built-in update:

1. Select Update driver.
2. Select Search automatically for drivers.
3. Install a result if Windows finds one.
4. Restart and test the application.

For a clean vendor repair, download the driver only from the graphics hardware manufacturer or the computer manufacturer. Follow its installer instructions and restart afterward.

If the problem began immediately after a driver update:

1. Return to Device Manager.
2. Right-click the adapter.
3. Select Properties > Driver.
4. Select Roll Back Driver if available.
5. Restart and test again.

If you want to avoid manually identifying hardware models and searching through several driver packages, Outbyte Driver Updater can scan for reported driver mismatches; its free scan identifies findings, while driver installation is handled by the full version.

A driver reinstall will not replace a missing Windows component or repair a damaged game installation. Use it for driver symptoms, not as the default response to every DLL message.

Fix 7: Understand the DirectX installer correctly

Windows 10 and Windows 11 include modern DirectX components, but older games may still require legacy side-by-side files.

Microsoft’s DirectX End-User Runtime Web Installer is the official source for legacy components such as older D3DX, XInput, XAudio, XACT, and related files.

It is not a universal repair for d3dcompiler_47.dll. Microsoft’s GDK documentation lists legacy compiler files through D3DCompiler_43.dll separately from D3DCompiler_47.dll, which is associated with Windows 10 SDK and application-local deployment.

Use the legacy DirectX installer when:

• The error also names a file such as d3dx9_43.dll, xinput1_3.dll, or xaudio2_7.dll.
• The game’s official requirements specifically call for the legacy DirectX runtime.
• The game installer includes the official Microsoft runtime as a prerequisite.

Do not use it as a substitute for KB4019990 on old Windows or for Windows component repair on Windows 10 and Windows 11.

Why Visual C++ reinstalling may not help

Visual C++ Redistributables repair files with names such as:

MSVCP*.dll
VCRUNTIME*.dll
MSVCR*.dll

They do not provide d3dcompiler_47.dll.

Installing Visual C++ can still be appropriate if the same error log names a Visual C++ runtime file. It is not the primary fix when the only missing file is d3dcompiler_47.dll.

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

Why regsvr32 should not be used

Do not run:

regsvr32 d3dcompiler_47.dll

regsvr32 is intended for DLLs that expose registration entry points such as DllRegisterServer and DllUnregisterServer. d3dcompiler_47.dll is a compiler/runtime library, not a COM or ActiveX registration server.

The resulting message may say that the module was loaded but the entry point DllRegisterServer or DllUnregisterServer was not found. That message does not mean the file needs a different registration command. It means registration is the wrong repair method.

Why manual DLL copying is risky

Do not download d3dcompiler_47.dll from a search result, DLL archive, file-sharing page, or forum attachment.

A manually copied DLL can:

• Contain malware.
• Be the wrong 32-bit or 64-bit architecture.
• Match a different Windows build.
• Be missing a required digital signature.
• Replace a legitimate application-local file.
• Hide the real problem, such as a damaged installer or missing dependency.
• Leave the Windows component store corrupted.

The supported application-local scenario is different. A software vendor or developer may distribute a matching signed copy beside its own executable. Microsoft’s DirectX SDK documentation describes side-by-side redistribution and warns against copying SDK redistributables into the Windows system directory.

For ordinary users, let Windows Update, the official application installer, or the game launcher restore the file.

What different error messages mean

“The program can’t start because D3DCOMPILER_47.dll is missing”

The named file could not be found in the locations searched by the application. The likely causes are a missing Windows update, damaged application files, antivirus quarantine, or an incorrect application-local deployment.

“The code execution cannot proceed because d3dcompiler_47.dll was not found”

This is another missing-file loader message. Start by identifying whether the application is 32-bit or 64-bit and whether other programs are affected.

“d3dcompiler_47.dll is either not designed to run on Windows or it contains an error”

This usually indicates a damaged, incompatible, wrong-architecture, or invalid copy. Check the full path and file signature. If only one application is affected, repair that application before replacing system files.

“The module was loaded but the entry-point DllUnregisterServer was missing”

This indicates an incorrect regsvr32 attempt. The compiler DLL should not be registered.

The file exists but the application still fails

The application may be loading another copy, or one of the DLL’s dependencies may be missing. Windows can report a load failure involving a named module even when that module exists. Microsoft documents this behavior in its LoadLibraryEx documentation and explains how DLL search order affects which copy is loaded.

When System Restore or Windows repair is appropriate

Use System Restore when:

• The error began immediately after a driver, cleanup, or system change.
• A suitable restore point exists.
• The affected program previously worked.
• Windows component repair and application repair did not resolve it.

To open System Restore:

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

rstrui.exe

1. Press Enter.
2. Select a restore point dated before the problem began.
3. Review the affected programs.
4. Start the restore and allow Windows to restart.

Microsoft describes the process in System Restore.

If System Restore is unavailable and multiple Windows components fail, use Windows’ built-in recovery or repair installation options after backing up important files. A full reset should be a last resort for this specific error.

Prevention

Keep Windows, the affected application, and antivirus definitions updated. Let game launchers complete updates rather than copying replacement DLLs between installations.

When installing older games, use their official prerequisite installers if included. Legacy DirectX components may be required even though Windows already contains modern DirectX.

Avoid “DLL fixer” utilities that promise to replace every missing file. They can install mismatched files and make diagnosis harder.

If antivirus repeatedly quarantines the same application file, do not create a broad exclusion. Confirm the file’s path and signature, update the application from its official source, and contact the application publisher if the detection continues.

FAQ

Is d3dcompiler_47.dll part of Windows?

On Windows 10 and later, Windows normally supplies the component. Applications may also carry an application-local copy. Older systems, including Windows 7 SP1 and Windows Server 2012, required a specific Microsoft update before the file was available for relevant uses.

Is d3dcompiler_47.dll part of DirectX?

It is part of the Direct3D compiler/runtime family, but it should not be confused with the legacy DirectX End-User Runtime files. The legacy installer does not universally restore version 47.

Does installing DirectX fix the error?

It can fix separate legacy DirectX errors involving files such as d3dx9_43.dll or xinput1_3.dll. It is not the general fix for a missing d3dcompiler_47.dll on Windows 10, Windows 11, or the old Windows platforms that require KB4019990.

Does reinstalling Visual C++ fix it?

Not normally. Visual C++ repairs a different group of runtime files. Install it only when the application also reports a Visual C++ dependency.

Does .NET Framework 4.7 require this file?

On Windows 7 SP1, Windows Server 2008 R2 SP1, and Windows Server 2012, Microsoft documented D3DCompiler_47.dll as a prerequisite for .NET Framework 4.7 WPF. Install the applicable Windows update before installing .NET Framework 4.7 on those systems.

Should I copy the file into System32?

No. Use Windows Update or Windows component repair for a system copy. Only use an application-local copy when it comes from the application’s official installer or SDK and matches the application architecture.

Why are there copies in both System32 and SysWOW64?

A 64-bit Windows installation maintains separate 64-bit and 32-bit system locations. This is normal and allows 64-bit and 32-bit applications to load the correct architecture.

When is a graphics-driver reinstall relevant?

Use it when the application crashes during rendering, reports a graphics fault, or the issue began with a driver change. A simple missing-file message is more commonly caused by Windows servicing, application files, quarantine, or architecture mismatch.

What information should I provide when asking for help?

Include:

• Windows edition and version from winver.
• Whether Windows is 32-bit or 64-bit.
• The complete error text.
• The application or game name.
• Whether one program or several programs fail.
• The full path of every d3dcompiler_47.dll copy found.
• The file version and digital-signature status.
• Recent Windows, game, antivirus, or driver changes.
• The result of Windows Update, DISM, SFC, and launcher verification.

That information separates a missing Windows component from a damaged application copy, wrong architecture, quarantine event, dependency failure, or unrelated graphics-driver problem.

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.