dxgi.dll Errors on Windows 11 and 10: Safe Repair Guide

dxgi.dll is the Microsoft DirectX Graphics Infrastructure component built into Windows. If dxgi.dll is missing, not found, or could not be loaded, the safe fix depends on whether the failing copy belongs to Windows or sits beside one game or application.

Do not download a replacement from a random DLL website. A downloaded file can contain malware, target the wrong architecture, come from an incompatible Windows build, or leave the real problem untouched. Use Windows repair tools, Windows Update, the affected program’s installer, or an official Microsoft runtime instead.

As an Amazon Associate I earn from qualifying purchases.

First, identify which situation you have

Before changing anything, note the complete error message and determine its scope.

The three important possibilities are:

• Only one game or application fails, especially after installing ReShade, DXVK, an overlay, injector, or mod.
• Several graphics applications fail, or Windows itself reports a dxgi.dll error.
• The message mentions an entry point such as CreateDXGIFactory2, particularly on an old Windows installation.

The repair is different for each case.

Look for an application-local copy

1. Close the affected program and its launcher.
2. Right-click the program’s shortcut and choose Open file location. If that opens a shortcut folder, right-click the shortcut again, choose Properties, and inspect the Target path.
3. Open the folder containing the program’s executable.
4. Look for a file named dxgi.dll.

A dxgi.dll beside the executable may be legitimate middleware from ReShade, DXVK, another graphics wrapper, or a game mod. Windows commonly searches the application directory before the system directory, so this local file can override the genuine Windows component. Microsoft documents this behavior in its DLL search order documentation.

If no local copy exists and multiple programs fail, continue with the Windows repair steps below.

Understand the Windows directories

On 64-bit Windows:

• %SystemRoot%\System32 normally contains the native 64-bit system files.
• %SystemRoot%\SysWOW64 normally contains 32-bit system files used by 32-bit applications.

The names are confusing, but do not swap files between these folders. A 32-bit game needs the 32-bit runtime, while a 64-bit application needs the 64-bit runtime. Microsoft explains this behavior in its file-system redirector documentation.

There is no single universal dxgi.dll size or version. The file varies according to the Windows release, servicing branch, updates, and architecture. A version number found on another computer is not a safe reason to replace your copy.

Fix 1: Update Windows and restart

Time needed: 10–30 minutes, depending on pending updates.

Modern DXGI is serviced through Windows. There is not a separate modern DirectX replacement package that should be downloaded to overwrite dxgi.dll.

Windows 11

1. Open Start.
2. Select Settings.
3. Choose Windows Update.
4. Select Check for updates.
5. Install all available updates.
6. Restart the computer, even if Windows does not immediately require it.
7. Test the affected game or application again.

Windows 10

1. Open Start.
2. Select Settings.
3. Choose Update & Security.
4. Select Windows Update.
5. Choose Check for updates.
6. Install available updates and restart.
7. Test the program again.

Microsoft’s instructions for this process are available in its Windows Update guidance.

If Windows Update fails, reports that files are missing, or cannot complete the installation, continue with the repair commands rather than copying dxgi.dll manually.

Fix 2: Repair Windows with DISM and SFC

Time needed: 15–45 minutes, plus restart time.

Use this fix when:

• Several games or graphics applications fail.
• Windows reports the error during startup.
• The message identifies a path such as C:\Windows\System32\dxgi.dll.
• The file is missing from a Windows system directory.
• The message says the file is a “Bad Image” or contains an error.

DISM repairs the Windows component store. SFC then checks protected Windows files and replaces damaged copies from that repaired store.

Run DISM first

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

DISM.exe /Online /Cleanup-Image /RestoreHealth

1. Press Enter.
2. Wait for the operation to finish. It may appear to pause at a percentage for several minutes.
3. Do not close the window while the scan is running.

A successful result usually says that the restore operation completed successfully. If DISM reports that it cannot find source files, see the repair-source section below.

Run SFC after DISM

In the same elevated Command Prompt, enter:

sfc /scannow

Press Enter and wait until verification reaches 100 percent.

Possible results include:

• Windows Resource Protection did not find any integrity violations: SFC found no protected-file corruption.
• Windows Resource Protection found corrupt files and successfully repaired them: restart Windows and test the program.
• Windows Resource Protection found corrupt files but was unable to fix some of them: run DISM again if necessary, then run SFC again.
• Windows Resource Protection could not start the repair service: restart Windows and repeat the command from an elevated window.

Restart after the commands finish. Then test more than one graphics application if possible. If only the original game still fails, the problem is more likely application-specific.

If repeating DISM and SFC leaves you unsure what changed, Outbyte PC Repair can reduce the manual detective work: its free scan shows what it identifies as wrong, while repair is performed by the full version. It is optional, and when the file belongs to a specific game or app, repairing or reinstalling that program remains the definitive fix.

Microsoft documents the repair process in Repair a Windows Image and the SFC commands in its System File Checker documentation.

Run a targeted SFC scan

If the general scan reports a problem or you want to check a specific protected file, use the full path.

For the native system path:

sfc /scanfile=%windir%\System32\dxgi.dll

On 64-bit Windows, also check the 32-bit path if it exists:

sfc /scanfile=%windir%\SysWOW64\dxgi.dll

Run the second command only when %windir%\SysWOW64 exists. The /scanfile option checks and repairs the specified file rather than scanning every protected file.

If DISM cannot find repair files

A failed DISM repair does not mean that downloading dxgi.dll is the answer. It can mean that the component store is damaged or that Windows cannot obtain the required repair files from Windows Update.

Microsoft supports using a matching Windows installation source. The source must correspond to the installed Windows version and edition.

The command format is:

DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:C:\test\mount\windows /LimitAccess

Replace the example source path with the actual path to a matching Windows installation source. Do not use unrelated installation media. A mismatched source can fail or provide the wrong component set.

After DISM completes, run:

sfc /scannow

If SFC still cannot repair the file, review:

%windir%\Logs\CBS\CBS.log

The log can identify which protected files could not be repaired. Persistent repair failures may point to storage problems, severe component-store corruption, permissions issues, or an unsupported Windows installation.

Fix 3: Repair the affected game or application

Time needed: 10–60 minutes, depending on the program and download speed.

Use this fix when only one program fails, especially if the problem began after:

• Installing or updating ReShade.
• Installing DXVK or another graphics wrapper.
• Adding an overlay or injector.
• Installing a graphics mod.
• Updating the game.
• An interrupted reinstall or disk error.
• An antivirus detection involving the game directory.

Temporarily isolate a local dxgi.dll

If you found dxgi.dll beside the program’s executable:

1. Make sure the program and launcher are closed.
2. Right-click the local dxgi.dll.
3. Choose Rename.
4. Rename it to something such as:

dxgi.dll.backup

1. Start the program.

Renaming is reversible and safer than deleting the file. If the program starts, the local wrapper or mod was probably the cause. Restore the original mod configuration only through its documented removal or installation process.

If the program no longer starts after renaming the file, restore the original name and use the launcher’s repair function. The local file may be required middleware, but it may still be the wrong version for the current game build.

Do not bypass anti-cheat controls. Some anti-cheat systems reject injected or modified DLLs. Remove the modification and restore the vendor’s original files instead.

Verify the game files

Use the launcher’s built-in repair process.

Steam

1. Open Steam.
2. Select Library.
3. Right-click the game.
4. Choose Properties.
5. Select Installed Files.
6. Choose Verify integrity of game files.
7. Wait for the process to finish.
8. Restart Steam and test the game.

Epic Games Launcher

1. Open the Epic Games Launcher.
2. Select Library.
3. Find the game.
4. Select the three-dot menu beside it.
5. Choose Manage.
6. Select Verify.
7. Wait for verification to finish.
8. Start the game again.

EA app

1. Open the EA app.
2. Select Library.
3. Find the game.
4. Open its three-dot menu.
5. Choose Repair.
6. Wait for the repair to complete.
7. Test the game.

If verification restores the program, the installation or its local files were damaged. If the error returns after a mod is reinstalled, the mod or wrapper is incompatible with the current game version.

For a non-launcher application, use its official installer’s Repair, Modify, or reinstall option. Back up saved games and configuration files first when the program stores them inside its installation directory.

Fix 4: Install the correct legacy DirectX components

Time needed: 10–20 minutes.

This fix applies when the error names a legacy file such as:

• d3dx9_*.dll
• d3dx10_*.dll
• d3dx11_*.dll
• xinput1_3.dll
• xaudio2_7.dll
• xactengine*.dll

Windows 10 and Windows 11 include modern DirectX, but older games may require optional side-by-side libraries. The official DirectX End-User Runtime Web Installer installs these legacy components.

To use it:

1. Open Microsoft’s download page.
2. Download dxwebsetup.exe.
3. Run the downloaded installer.
4. Accept the license terms.
5. Allow the installer to complete.
6. Restart Windows.
7. Test the game.

Microsoft also provides the offline DirectX End-User Runtimes June 2010 package for systems that need the redistributable files without downloading each component during setup.

These packages do not replace or repair the core Windows dxgi.dll. Microsoft states that the legacy installer does not modify the DirectX runtime already installed in Windows. Therefore, installing June 2010 DirectX is not the definitive repair for a missing or corrupt Windows dxgi.dll.

Fix 5: Check the error for an API compatibility problem

Time needed: 5–30 minutes for identification; longer if Windows must be upgraded.

An entry-point error is different from a missing-file error. For example:

The procedure entry point CreateDXGIFactory2 could not be located in the dynamic link library dxgi.dll.

CreateDXGIFactory2 belongs to DXGI 1.3 and requires Windows 8.1 or later, according to Microsoft’s CreateDXGIFactory2 documentation.

If the computer runs Windows 10 or Windows 11 and displays this message, first repair Windows with DISM and SFC, install updates, and check for an app-local dxgi.dll. A local older or modified DLL can expose the wrong API.

If the computer runs Windows 7 or another older release, the program may require an API that the operating system does not provide. Windows 7 SP1 received updated graphics components through Microsoft’s Platform Update, documented in the KB2670838 documentation, but compatibility still depends on the application.

Do not copy a Windows 10 or Windows 11 dxgi.dll into Windows 7. A newer DLL does not safely add the operating-system support required by the application and can destabilize Windows.

Fix 6: Check Windows Security and Protection History

Time needed: 5–20 minutes.

An antivirus action can remove a local game DLL, a graphics wrapper, or a malicious replacement. Do not assume that every quarantined dxgi.dll is authentic.

1. Open Start.
2. Search for Windows Security.
3. Open it.
4. Select Virus & threat protection.
5. Choose Protection history.
6. Review detections involving dxgi.dll.
7. Expand the event to see its path and detection details.

Microsoft says Protection History retains events for only two weeks. Review the path carefully:

• A file in C:\Windows\System32 or C:\Windows\SysWOW64 should normally be repaired through Windows servicing, SFC/DISM, or Windows Update.
• A file in a game folder may be legitimate middleware, a modified game file, or an unsafe replacement.
• A file from an unofficial download should not be restored merely because the program wants it.

Use Restore only when the file’s authenticity and source are known. Do not disable Windows Security to make an unknown DLL load. If you suspect malware, run a full scan. For a serious concern, use Scan options and select Microsoft Defender Offline scan.

Microsoft’s explanation of this feature is available in Protection History in Windows Security.

Fix 7: Update or reinstall the graphics driver

Time needed: 15–45 minutes.

A graphics driver normally does not supply the Windows dxgi.dll, so reinstalling a driver is not the primary repair for a genuinely missing system file. Driver work is appropriate when DXGI loads but the symptoms include:

• Device removed or device hung errors.
• Driver resets.
• Black screens.
• Crashes during rendering.
• Application failures after a GPU driver update.
• Problems across several 3D applications without a missing-file message.

Check Windows Update driver options

1. Open Settings.
2. On Windows 11, select Windows Update. On Windows 10, select Update & Security, then Windows Update.
3. Open Advanced options.
4. Select Optional updates if it is available.
5. Expand Driver updates.
6. Install an applicable graphics driver.
7. Restart Windows.

Check the adapter in Device Manager

1. Press Windows key + X.
2. Select Device Manager.
3. Expand Display adapters.
4. Right-click the graphics adapter.
5. Choose Update driver.
6. Select Search automatically for drivers.
7. Restart if Windows installs an update.

If the problem began immediately after a driver update:

1. Open Device Manager.
2. Expand Display adapters.
3. Right-click the graphics adapter.
4. Choose Properties.
5. Open the Driver tab.
6. Select Roll Back Driver if the button is available.
7. Restart and test the application.

For a full reinstall, download the driver package from the GPU or computer manufacturer’s official support page. Use the installer’s clean-install option when it provides one. Avoid driver packages from unofficial download sites.

Manually identifying which of several driver components is stale can take time, particularly after a Windows or GPU update. Outbyte Driver Updater provides a free scan that shows which drivers it identifies as needing attention, while driver installation is performed by the full version. It is optional, and a game-specific dxgi.dll problem still requires repairing or reinstalling that game.

Fix 8: Use Windows Features only for separate legacy requirements

Time needed: 5–15 minutes.

Windows Features does not normally install or repair dxgi.dll. Do not enable random features in the hope of replacing it.

If an older game separately reports a DirectPlay requirement, you can enable that legacy feature:

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

optionalfeatures

1. Press Enter.
2. Expand Legacy Components.
3. Select DirectPlay.
4. Select OK.
5. Restart Windows if requested.
6. Test the game.

If an application specifically reports that it needs .NET Framework 3.5, enable that feature only for that separate requirement. A .NET error and a dxgi.dll error are not the same problem.

Do not use regsvr32 for dxgi.dll

regsvr32 registers DLLs that provide registration entry points such as DllRegisterServer. It is used for certain COM and ActiveX components, not as a general repair command.

dxgi.dll is a graphics runtime/API DLL, not a normal user-registered COM component. Running:

regsvr32 dxgi.dll

is not an appropriate repair. It may produce an error stating that DllRegisterServer was not found, because that registration entry point is not what DXGI provides.

Do not run regsvr32 against files in System32 or SysWOW64 as a substitute for DISM or SFC. Microsoft documents the command’s intended purpose in its regsvr32 documentation.

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

What the exact error wording tells you

“The program cannot start because dxgi.dll is missing”

This usually means that the loader could not find a usable DLL in the locations searched for that application. Check the application folder first, then repair the program or Windows depending on whether one or several programs fail.

“This application has failed to start because dxgi.dll was not found”

The wording is similar, but the complete message and affected program matter. A missing app-local wrapper and a missing Windows component can produce similar text.

“The specified module could not be found”

This does not always mean that dxgi.dll itself is absent. The DLL may exist but depend on another missing or incompatible component. Check the application’s installation, architecture, and any mod or wrapper files.

“The application was unable to start correctly” or “Bad Image”

A Bad Image error indicates that the binary may be corrupt, incompatible, or invalid. Check the path named in the message. A path in the Windows directory points toward Windows repair; a path in the game directory points toward application repair or a local mod.

“The procedure entry point could not be located”

This is usually an API compatibility or wrong-DLL problem. Check for an app-local copy and confirm the Windows version. Do not replace a system DLL manually.

“Could not be loaded”

This is not one standardized Windows dialog. A game engine, loader, Wine or Proton environment, or application-specific log may generate it. Record the complete message, error code, executable path, and DLL path before choosing a repair.

Common causes and their matching fixes

Evidence	Likely area	Appropriate response
One game fails and has a local dxgi.dll	Wrapper, mod, overlay, or damaged game files	Disable the modification, rename the local file temporarily, then verify or repair the game
Several graphics applications fail	Windows component corruption or servicing problem	Install Windows updates, run DISM, then run SFC
DWM or Windows startup reports the error	Protected Windows component	Use Windows Update, DISM, and SFC; escalate to System Restore or repair installation if needed
Entry point such as CreateDXGIFactory2 is missing	Unsupported Windows API or wrong local DLL	Check the Windows version and app-local files; upgrade or apply supported updates
Problem began after an interrupted game update	Damaged application installation	Use the launcher’s Verify, Repair, or reinstall function
Protection History names the file	Quarantine or security cleanup	Inspect the path and detection; repair from the official source rather than restoring an unknown DLL
Only a 32-bit application fails	Architecture mismatch	Restore the application’s correct 32-bit files; do not copy from System32 to SysWOW64
DXGI loads but the driver crashes	Graphics driver or hardware issue	Update or reinstall the official GPU driver and investigate temperature, power, and hardware symptoms
Only one Windows account fails	Profile, permissions, or per-user injection	Test another account and remove per-user overlays or injected components

The filename alone does not prove which cause applies. The scope of the failure and the path shown in the error are more useful than the name by itself.

When normal repair does not work

Use System Restore after a recent change

Time needed: 15–45 minutes.

System Restore is appropriate when the problem began immediately after a driver, Windows update, application installation, or system configuration change.

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

rstrui.exe

1. Press Enter.
2. Select an appropriate restore point from before the problem began.
3. Review the affected programs.
4. Start the restore process.
5. Allow Windows to restart.

System Restore normally preserves personal files but reverts system files, registry settings, and installed programs. Microsoft provides additional information about System Restore.

Test another Windows user profile

If the system copy is intact and only one account fails:

1. Sign in with another existing account, or create a temporary test account.
2. Run the same application.
3. Compare the result.

If the program works under another profile, inspect per-user overlays, permissions, startup utilities, and user-specific configuration. This is a diagnostic step, not proof that the Windows dxgi.dll itself is damaged.

Check Event Viewer and DirectX diagnostics

For persistent failures, collect:

• The exact full error text and error code.
• The executable and DLL paths shown in the message.
• The Windows version and build from winver.
• Whether the application is 32-bit or 64-bit.
• The result of DISM and SFC.
• Whether the problem affects every graphics application or only one.
• A dxdiag report.

To open DirectX Diagnostic Tool:

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

dxdiag

1. Press Enter.
2. Allow the tool to gather information.
3. Select Save All Information.
4. Save the report for the application or technician handling the problem.

Perform an in-place Windows repair

If Windows repair commands, updates, application repairs, driver work, and local-DLL removal do not resolve a system-wide problem, an in-place repair installation may be appropriate.

Use matching Windows installation media, back up important files first, and follow Microsoft’s supported installation process. An in-place repair can replace damaged Windows components while preserving applications and personal files when the correct options are selected.

A clean installation should be reserved for cases where repair installation, storage checks, and hardware diagnosis do not resolve the corruption.

Frequently asked questions

Is dxgi.dll a real Windows file?

Yes. dxgi.dll is the DirectX Graphics Infrastructure API DLL supplied as part of Microsoft Windows. DXGI handles low-level graphics tasks such as adapter enumeration, swap-chain creation, presentation, and communication between Direct3D and graphics hardware. Microsoft introduced it with Windows Vista. See Microsoft’s DXGI overview.

Is dxgi.dll part of DirectX 9, DirectX 11, or DirectX 12?

DXGI is shared graphics infrastructure used by Direct3D applications across different DirectX generations. It is not the same type of optional legacy library as d3dx9_*.dll or xinput1_3.dll.

Modern DXGI is part of Windows. Older games may additionally need the legacy DirectX End-User Runtime, but that package does not replace the Windows core dxgi.dll.

Should I reinstall Visual C++?

Not for a dxgi.dll error alone. Visual C++ Redistributables provide C and C++ runtime libraries such as msvcp140.dll and vcruntime140.dll. Install or repair the correct architecture only when the application reports a Visual C++ runtime requirement or a separate Visual C++ error. Microsoft maintains the Visual C++ Redistributable documentation.

Should I install .NET?

Only when the program reports a .NET runtime requirement or a separate .NET error. .NET is a managed application runtime and does not supply the Windows DXGI component. Official downloads are available from Microsoft .NET.

Will the DirectX June 2010 package repair dxgi.dll?

Usually no. It installs optional legacy side-by-side components used by older games. A missing or corrupt Windows dxgi.dll should normally be repaired through Windows Update, DISM, SFC, Windows recovery, or the affected program’s official installer.

Can I copy dxgi.dll from another computer?

No. The file depends on the Windows build, servicing state, architecture, and supported APIs. Copying a file from another computer can create a version mismatch or destabilize Windows.

Can I copy the file from System32 to SysWOW64?

No. On 64-bit Windows, System32 normally holds native 64-bit system files and SysWOW64 normally holds 32-bit system files. They are not interchangeable.

Is every dxgi.dll in a game folder malware?

No. ReShade, DXVK, and other graphics wrappers can legitimately use app-local DLLs. However, an unexpected file can also be unsafe or incompatible. Verify its origin, inspect Windows Security Protection History, and use the application’s official repair or documented mod-removal process.

Will reinstalling the GPU driver fix a missing system DLL?

Not usually. A driver reinstall can address rendering crashes, device-removed errors, black screens, and driver resets. It does not replace the normal Windows repair process for a missing or damaged system dxgi.dll.

Should I run regsvr32 dxgi.dll?

No. dxgi.dll is not normally repaired by registration. Use DISM and SFC for a Windows copy, or verify and repair the application for a local copy.

What if the program says CreateDXGIFactory2 is missing?

Check for an app-local dxgi.dll first. If the computer runs an old Windows release, the application may require an API that the operating system does not support. Upgrade Windows or install a documented supported platform update. Do not copy a newer Windows DLL into an older installation.

What is the safest repair order?

For one affected game, check for a local dxgi.dll, disable recent mods or wrappers, and verify the game files. For multiple applications or a Windows startup error, install updates, run DISM, run SFC, and restart. If the error names a legacy DirectX file rather than dxgi.dll, use Microsoft’s official legacy runtime 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.