d3d11.dll Missing: Find the Right Fix for Windows or Games

d3d11.dll is the Microsoft Direct3D 11 runtime, a genuine Windows component used by games and graphics applications. If d3d11.dll is missing, corrupt, incompatible, or cannot be loaded, the correct repair depends first on the full path shown in the error.

A missing file under C:\Windows\System32 or C:\Windows\SysWOW64 usually calls for Windows repair. A file with the same name inside a game folder may belong to a graphics mod, overlay, injector, or the game itself. In that case, verifying the game files is usually more appropriate.

As an Amazon Associate I earn from qualifying purchases.

Do not download an isolated d3d11.dll from a random DLL website. The file may contain malware, have the wrong architecture, belong to a different Windows build, or leave the actual problem untouched.

Check the path in the error first

Before changing Windows files, copy the complete path from the message. The location tells you which repair path to follow.

Path or clue	What it usually means	Start with
C:\Windows\System32\d3d11.dll	The Windows 64-bit system copy on 64-bit Windows	Windows Update, DISM, and SFC
C:\Windows\SysWOW64\d3d11.dll	The Windows 32-bit system copy on 64-bit Windows	Windows Update, DISM, and SFC
The game’s installation folder	A private game DLL, wrapper, mod, or overlay may be loading	Remove the mod or verify game files
An entry-point error	The loaded DLL may be old, incompatible, or the wrong architecture	Check private DLLs, mods, and drivers
d3d11.dll named as a crash module	The graphics pipeline or driver may have failed there	Check drivers, overlays, and dxdiag

The names are counterintuitive on 64-bit Windows:

• System32 contains 64-bit system files.
• SysWOW64 contains 32-bit system files.
• A 32-bit application normally uses the 32-bit copy.
• A 64-bit application normally uses the 64-bit copy.

This layout is part of Windows’ WOW64 file-system behavior, not an installation mistake. See Microsoft’s explanation of the Windows File System Redirector.

Windows also searches an application’s directory before the system directories in the normal DLL search order. Therefore, a game-folder d3d11.dll can override the Windows copy even when the Windows copy is perfectly healthy. Microsoft documents this behavior in its guide to dynamic-link library search order.

Recognize the exact error

You may see one of several different error families.

A missing-file message may say:

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

Another common form is:

The code execution cannot proceed because d3d11.dll was not found.

A damaged Windows copy may produce a Bad Image message:

[program].exe - Bad Image

C:\Windows\System32\d3d11.dll is either not designed to run on Windows
or it contains an error.
Try installing the program again using the original installation media
or contact your system administrator or the software vendor for support.
Error status 0xc000012f

An older mod or wrapper can instead trigger an entry-point error:

The procedure entry point CreateDXGIFactory2 could not be located
in the dynamic link library C:\Windows\System32\d3d11.dll.

That message does not necessarily mean the Windows runtime is missing. It can indicate that an old graphics wrapper, injector, or incompatible private DLL is being loaded.

The wording “d3d11.dll could not be loaded” may come from a game, launcher, crash log, or third-party loader rather than from a standard Windows dialog. Treat the path and the surrounding message as more useful evidence than the wording alone.

Fix 1: Install Windows updates, then repair system files

Time needed: 15 to 45 minutes, depending on pending updates and disk speed.

Use this fix when the error points to System32 or SysWOW64, affects more than one program, or reports Bad Image, 0xc000012f, or a damaged Windows component.

Install pending updates

On Windows 11:

1. Open Start.
2. Select Settings.
3. Select Windows Update.
4. Select Check for updates.
5. Install all available updates.
6. Restart the computer, even if Windows does not insist on an immediate restart.

On Windows 10:

1. Open Start.
2. Select Settings.
3. Select Update & Security.
4. Select Windows Update.
5. Select Check for updates.
6. Install the available updates.
7. Restart Windows.

Microsoft provides the current procedure in its guide to installing Windows updates.

Run DISM from 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.
6. Run this command:

DISM.exe /Online /Cleanup-Image /RestoreHealth

1. Wait until the command finishes. Do not close the window while it is working.

DISM checks and repairs the Windows component store. This matters because SFC may need a healthy component store as its repair source.

Run System File Checker

In the same administrator Command Prompt, run:

sfc /scannow

Wait for the scan to reach 100 percent. Restart Windows after it completes, then test the affected application again.

A successful repair may report that protected files were repaired. If SFC reports that it found corruption but could not repair everything, keep the result available for troubleshooting and continue with the Windows recovery options below. Microsoft’s documented order is DISM first and SFC second in its guide to using System File Checker.

If you want help identifying which Windows repair tasks need attention instead of repeatedly reading DISM and SFC output, Outbyte PC Repair provides a free scan that shows what it found; repairs are performed by the full version, and it is not required for the built-in Microsoft repair process.

Check whether the system copies exist

After restarting, you can inspect the expected files with these commands:

dir "%windir%\System32\d3d11.dll"
dir "%windir%\SysWOW64\d3d11.dll"

On 32-bit Windows, the SysWOW64 path may not exist. That is expected.

PowerShell can show the file’s location, size, and version information:

Get-Item "$env:windir\System32\d3d11.dll",
         "$env:windir\SysWOW64\d3d11.dll" |
  Select-Object FullName, Length, VersionInfo

There is no universal d3d11.dll version or file size. These values vary with Windows edition, architecture, build, and servicing level. A version number that differs from a value seen online does not automatically mean the file is wrong.

You can also inspect the system copy’s signature:

Get-AuthenticodeSignature "$env:windir\System32\d3d11.dll"

A valid signature provides evidence about the file’s authenticity, but it does not by itself prove that the file matches the Windows build installed on your computer.

Fix 2: Remove a game-local wrapper and verify the game

Time needed: 10 to 30 minutes, plus download time if files must be replaced.

Use this fix when the path points into a game folder, the problem started after installing ReShade, SweetFX, ENB, an overlay, or a graphics mod, or only one game refuses to launch.

Check the game directory

Open the game’s installation folder and look for files such as:

• d3d11.dll
• dxgi.dll
• ReShade files
• SweetFX files
• ENB files
• Overlay or injector files

Do not assume that every game-folder d3d11.dll is a Windows system copy. A private DLL may be deliberately supplied by a mod or graphics tool.

If the problem began after installing a mod, follow that mod’s official uninstall instructions. If no uninstaller exists, rename the suspected file rather than deleting it. For example:

d3d11.dll

can be renamed to:

d3d11.dll.disabled

Renaming preserves a way to restore the file if it turns out to be unrelated.

Do not replace a game-local wrapper with a copy from System32. The wrapper may have a different purpose, and replacing it can create an entry-point error or stop the game from loading.

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 Steam to finish.
8. Restart Steam and launch the game again.

Verify an Epic Games Launcher game

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

Other launchers generally provide a similarly named Verify, Repair, or Scan command. Use the launcher’s own repair process instead of copying DLL files from another computer.

If the game launches after verification, the missing or damaged file belonged to the game installation. If the game still fails and the same private DLL remains in the folder, disable mods and overlays before testing again.

Fix 3: Check the graphics driver

Time needed: 15 to 40 minutes.

Use this fix when several Direct3D games fail, the application crashes while creating a graphics device, the issue began after a driver update or rollback, or dxdiag reports a display-driver problem.

The graphics driver is not the same file as d3d11.dll. Direct3D uses the vendor’s user-mode display driver while creating and operating the graphics device. A crash that names d3d11.dll as the faulting module does not prove that the Microsoft DLL is damaged.

Inspect DirectX and display information

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

dxdiag

1. Press Enter.
2. Allow the diagnostic tool to collect information.
3. Review the System tab.
4. Review the Display tab or tabs.
5. Select Save All Information if you need to provide the report to the game publisher or support technician.

Also press Windows key + R, type winver, and press Enter to record the installed Windows version.

Microsoft explains how to check DirectX information with DxDiag.

Use Device Manager

1. Right-click Start.
2. Select Device Manager.
3. Expand Display adapters.
4. Right-click the graphics adapter.
5. Select Properties.
6. Open the Driver tab.

If the problem began after an update, select Roll Back Driver if the button is available. Restart and test the application.

To request a driver update through Windows:

1. Right-click the graphics adapter.
2. Select Update driver.
3. Select Search automatically for drivers.
4. Restart Windows if a driver is installed.

For the newest compatible driver, use Windows Update or the official support site for the graphics chip manufacturer. The main vendors are NVIDIA, AMD, and Intel. On a laptop, check the computer manufacturer first because its driver may be customized for that model.

Avoid driver packages from download aggregators. Match the driver to the graphics adapter and Windows architecture.

If you want to avoid manually comparing driver versions across the adapter, Windows build, and hardware manufacturer, Outbyte Driver Updater offers a free scan that identifies outdated drivers; driver installation is performed by the full version, and it is not required if Device Manager or the hardware manufacturer’s installer resolves the issue.

Disable graphics additions while testing

Temporarily disable:

• ReShade or SweetFX
• ENB-style modifications
• Game overlays
• Recording overlays
• GPU monitoring overlays
• Overclocking utilities
• Third-party frame-rate limiters

Test the game with its original graphics configuration. If it works, re-enable additions one at a time to identify the conflicting component.

Fix 4: Install legacy DirectX files only when the error names them

Time needed: 10 to 20 minutes.

Windows 10 and Windows 11 include the modern DirectX runtime for their Windows release. Direct3D 11 is part of Windows, not a normal standalone download. The DirectX End-User Runtime packages do not replace the built-in d3d11.dll.

The legacy package is relevant when the error names optional older files such as:

d3dx9_43.dll
d3dx11_43.dll
D3DCompiler_43.dll
xinput1_3.dll
XAudio2_7.dll
xactengine3_7.dll

For those files, use Microsoft’s DirectX End-User Runtime Web Installer or the offline DirectX End-User Runtimes June 2010 package.

These packages install optional legacy components from older DirectX SDK releases. They do not repair or reinstall the Windows Direct3D 11 runtime.

Do not install the June 2010 package as the default response to a missing d3d11.dll. If the error names only d3d11.dll, return to the path-based Windows, game, or driver fixes above.

Do not use Windows Features as a d3d11.dll repair

Windows Features does not reinstall the built-in Direct3D 11 runtime.

If an older application separately identifies a missing optional Windows feature, open the feature panel as follows:

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

optionalfeatures

1. Press Enter.
2. Enable only the feature specifically named by the application.
3. Select OK.
4. Restart if Windows requests it.

Do not enable or disable unrelated features while troubleshooting d3d11.dll.

Visual C++ and .NET are separate components

Visual C++ is relevant when the error names files such as:

VCRUNTIME140.dll
MSVCP140.dll

It is not a general repair for d3d11.dll. The Visual C++ package architecture must match the application, and older runtime families may remain installed side by side.

.NET repair or installation is relevant when the application reports a .NET runtime problem. It does not reinstall the native Direct3D 11 runtime.

Do not register d3d11.dll

Do not run:

regsvr32 d3d11.dll

regsvr32 is intended for certain COM or OLE DLLs that provide a registration entry point named DllRegisterServer. The Direct3D runtime is loaded as an API component, not registered as a COM server.

The likely result is an error similar to:

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

Running the command repeatedly will not repair the file. Use DISM and SFC for a Windows copy, or the game launcher’s verification process for a game copy.

Fix 5: Check antivirus quarantine safely

Time needed: 5 to 30 minutes.

Use this fix when the file disappeared after a security scan, a game launcher reports a missing file, or the problem began immediately after antivirus activity.

1. Open Start.
2. Type Windows Security.
3. Open the application.
4. Select Virus & threat protection.
5. Select Protection history.
6. Review recent detections and actions.

Do not restore a file merely because its name is d3d11.dll. Confirm whether it came from:

• The Windows system directory.
• The game’s official installation.
• A graphics mod or injector.
• An unknown or unexpected source.

If the missing file is a Windows copy, repair it with Windows Update, DISM, and SFC. If it is a game file, verify the game through its launcher. If malware is plausible, run a full scan or use Microsoft Defender Offline.

Do not immediately exclude the file from antivirus scanning. A restored file from an untrusted source can expose the computer to the same threat that caused the quarantine.

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

Fix 6: Use System Restore when the timing is clear

Time needed: 20 to 60 minutes.

System Restore is useful when d3d11.dll errors began immediately after a driver installation, Windows update, graphics mod, or other system change.

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

rstrui.exe

1. Press Enter.
2. Select an appropriate restore point.
3. Select Scan for affected programs.
4. Review the applications and drivers that will be affected.
5. Continue only if the restore point matches the time when the problem was not present.
6. Restart Windows and test the application.

System Restore does not replace personal files, but it can roll back drivers, applications, and system changes. Microsoft describes the process in its guide to System Restore.

If the problem began immediately after a Windows update and System Restore is unavailable, Windows Recovery may offer Troubleshoot > Advanced options > Uninstall Updates. Use that route only when the timing strongly connects the error to the update.

Fix 7: Repair Windows 11 in place if component corruption continues

Time needed: 30 minutes to several hours, depending on download and installation time.

On supported Windows 11 installations, Microsoft may provide a repair option that reinstalls the current Windows version while preserving apps, files, and settings.

1. Open Start.
2. Select Settings.
3. Select System.
4. Select Recovery.
5. Look for Fix problems using Windows Update.
6. Select Reinstall now.
7. Follow the on-screen instructions.
8. Restart and test the application.

This option is intended to repair Windows system files and components when ordinary servicing has not resolved the issue. Microsoft documents it in Fix issues by reinstalling the current version of Windows.

If the option is not available, continue with the recovery options appropriate for your Windows installation rather than copying d3d11.dll from another computer.

Fix 8: Reinstall the affected application when its own files are damaged

Time needed: 15 minutes to several hours.

If only one application fails, Windows repair succeeds, the graphics driver is healthy, and game-file verification does not resolve the issue, reinstall that application from its official launcher or installer.

Before reinstalling:

1. Back up saved games or application data if the program stores them locally.
2. Disable mods and overlays.
3. Uninstall the application through Windows or its launcher.
4. Restart Windows.
5. Install the application again from its official source.
6. Test it before adding mods or overlays back.

If the application explicitly supplies a private d3d11.dll, its installer is the correct source for that file. Do not substitute the Windows copy.

Why d3d11.dll errors happen

The same filename can point to several different failures. These are the main causes in practical troubleshooting order, not a published percentage ranking.

Corrupt or missing Windows system copy

This is likely when the path is under System32 or SysWOW64, several unrelated applications fail, or the message says Bad Image, not designed to run on Windows, or 0xc000012f.

The repair is Windows Update followed by DISM and SFC. If Windows still reports component corruption, use System Restore or the Windows 11 repair reinstall when available.

Game-local DLL or graphics wrapper

This is likely when only one game fails, the path points to the game directory, or the issue began after installing a mod, overlay, or injector.

The repair is to undo the modification, rename the private DLL, and verify the game files. Do not replace the private DLL with a system copy.

Graphics-driver failure

This is likely when applications crash during graphics initialization, several Direct3D games fail, or the issue started after a driver update or rollback.

The repair is to roll back or reinstall the correct driver, restart Windows, and test with overlays and overclocking disabled.

Failed update or servicing corruption

This is likely when the error began immediately after Windows Update, SFC cannot repair files, or several Windows components are affected.

The repair is DISM followed by SFC, followed by Windows recovery options if the corruption continues.

Antivirus quarantine

This is likely when the file disappeared after a scan or the launcher reports that a game file is missing.

The repair depends on the file’s origin. Use Windows servicing for a Windows file and launcher verification for a game file. Confirm provenance before restoring anything.

Wrong architecture or incompatible private DLL

This is likely when a 32-bit application receives a 64-bit DLL, a file was copied manually, or the error mentions an entry point.

On 64-bit Windows, do not assume that System32 means 32-bit. Remove or rename the manually copied private file and restore it through Windows servicing or the application’s official installer.

Unsupported or obsolete Windows version

Direct3D 11 was included with Windows 7 and later. Windows Vista required the applicable Direct3D 11 platform update. If an obsolete operating system lacks the required platform support, use the applicable Microsoft servicing update or upgrade Windows. Do not copy a modern d3d11.dll from another release.

Final decision tree

Use this short sequence after reading the path:

1. Does the error name System32 or SysWOW64?
2. Install Windows updates.
3. Run DISM.
4. Run SFC.

5. Restart and test again.

6. Does the error name a game or application folder?

7. Disable mods and overlays.
8. Rename the private d3d11.dll if appropriate.

9. Verify the game files through its launcher.

10. Does the error name another file such as d3dx11_43.dll, D3DCompiler_43.dll, or xinput1_3.dll?

    ×

    Quick wins for a faster PC:

    Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →
    Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

11. Use Microsoft’s legacy DirectX End-User Runtime package.

12. Does the application crash rather than report a missing file?

13. Run dxdiag.
14. Check the graphics driver.

15. Disable overlays, injectors, and overclocking.

16. Did the issue begin after antivirus activity?

17. Review Protection History.
18. Do not restore the file without confirming its origin.

19. Run a full scan or Defender Offline when appropriate.

20. Did the issue begin after an update or driver change?

    ×

    Recommended Free Tools

    Windows Errors? Fix Them Before They Spread

    Fix My PC Now →Free scan · no reinstall

    Outdated Drivers Are Slowing You Down

    Scan My Drivers Free →Free scan · exact hardware match

    PC Slower Than It Used to Be?

    Run a Free PC Scan →Free scan · Windows 10 & 11
    Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
21. Consider driver rollback, System Restore, or the relevant Windows recovery option.

When every repair appears to fail

Record the following details before seeking support:

• The complete path shown in the error.
• The exact error wording and status code.
• Whether one application or several applications fail.
• Whether the application is 32-bit or 64-bit.
• Your Windows version from winver.
• The System and Display results from dxdiag.
• Whether the problem began after an update, driver change, mod installation, antivirus event, or disk migration.
• Whether the application folder contains d3d11.dll, dxgi.dll, ReShade, SweetFX, ENB, or overlay files.
• The final result reported by DISM and SFC.
• Whether game-file verification replaced any files.

This evidence separates a Windows servicing problem from an application-local DLL, driver, or security problem.

Frequently asked questions

Can I download d3d11.dll separately?

No. Do not use random DLL download sites websites. The safe repair for a Windows copy is Windows Update, DISM, and SFC. The safe repair for a game copy is the game’s official installer or launcher verification.

Is d3d11.dll part of DirectX?

Yes. It is the Direct3D 11 runtime supplied as part of Windows. Applications use Direct3D functions such as D3D11CreateDevice to create a graphics device and communicate with the display driver. Microsoft identifies D3D11.dll as the required DLL for that API in its documentation for D3D11CreateDevice.

Will the June 2010 DirectX package replace d3d11.dll?

No. The June 2010 package installs optional legacy files such as D3DX, older compiler components, XInput, and XAudio files. It does not replace the built-in Windows Direct3D runtime.

Should I install Visual C++ Redistributable?

Only if the error names a Visual C++ runtime file such as VCRUNTIME140.dll or MSVCP140.dll. Visual C++ does not generally repair d3d11.dll.

Is d3d11.dll a graphics driver?

No. It is the Direct3D 11 runtime. The graphics driver is supplied by the GPU or computer manufacturer and works with Direct3D during graphics-device creation and rendering.

Should I run regsvr32 d3d11.dll?

No. d3d11.dll is not repaired by COM registration. Use DISM and SFC for the Windows copy or launcher verification for a game copy.

Why does the error mention System32 when the game is 32-bit?

On 64-bit Windows, System32 contains 64-bit system files, while SysWOW64 contains 32-bit system files. Windows uses the appropriate architecture through its file-system redirection behavior.

Why does a crash report list d3d11.dll as the faulting module?

The application may have encountered a rendering or driver failure while executing through the Direct3D runtime. A crash report naming d3d11.dll does not prove that the file itself is corrupt.

Do file size and version prove that my copy is correct?

No. File versions and sizes vary by Windows build, architecture, edition, and servicing level. Use Windows servicing and signature information rather than comparing the file with an arbitrary online listing.

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.