xinput1_2.dll Missing: Restore the Legacy DirectX Runtime

If xinput1_2.dll is missing, Windows cannot start a game or application that expects this legacy DirectX controller library. xinput1_2.dll belongs to the Microsoft Common Controller API and is normally restored by installing the correct DirectX side-by-side runtime, not by downloading an isolated DLL.

Start with this diagnostic checklist

Before changing Windows, record four details:

• Which game or application shows the error.
• Whether the failure happens during launch, after loading, or when connecting a controller.
• Whether one program fails or several unrelated programs fail.
• Whether the affected program is likely 32-bit or 64-bit.

Also copy the exact message. Common examples include:

As an Amazon Associate I earn from qualifying purchases.

• “The program can’t start because xinput1_2.dll is missing from your computer.”
• “The code execution cannot proceed because xinput1_2.dll was not found.”
• “Error loading xinput1_2.dll. The specified module could not be found.”
• “xinput1_2.dll is either not designed to run on Windows or it contains an error.”

The wording matters. A missing-file error usually points to an absent legacy runtime. A “bad image” or “not designed to run on Windows” message points more strongly to a damaged, incorrect, or incompatible copy.

If only one old game fails, begin with that game’s files and bundled prerequisites. If every affected game fails, install the legacy DirectX runtime first, then investigate Windows components.

What xinput1_2.dll is

xinput1_2.dll is a legacy DirectX/XInput runtime library used by older games and controller-enabled applications. XInput provides an interface for applications that communicate with game controllers and related input devices.

It is not:

• A Visual C++ runtime file.
• A .NET runtime file.
• An NVIDIA, AMD, Intel, Xbox, or motherboard driver.
• A modern replacement for DirectX 12.
• A file that should normally be downloaded separately from an unknown source.

Microsoft’s XInput documentation distinguishes Windows components from older DirectX redistributable components. Modern Windows versions include current DirectX components, but older applications can still require optional side-by-side libraries from the legacy DirectX runtime. See Microsoft’s XInput version documentation.

That is why a computer can report DirectX 12 while an older game still reports that xinput1_2.dll is missing. The installed DirectX version and the legacy libraries required by a particular game are related, but they are not the same installation set.

Fix 1: Install the official DirectX June 2010 runtime

This is the most likely fix for a clean Windows installation, an older game migrated from another computer, or a game whose prerequisite installer was canceled or blocked.

Use Microsoft’s offline package when possible:

DirectX End-User Runtimes (June 2010)

The package does not replace DirectX 12 and does not downgrade Windows. It installs optional legacy components alongside the current Windows components. Independent package inventories identify the older XInput files in the DirectX runtime packages.

Install the offline package

1. Open the Microsoft DirectX End-User Runtimes download page.
2. Download directx_Jun2010_redist.exe.
3. Save it to a known location such as Downloads.
4. Right-click the downloaded file.
5. Select Run as administrator.
6. Accept the license terms.
7. When asked where to extract the files, create a temporary folder such as:

text
C:\DXRedist

1. Open the extraction folder.
2. Find DXSETUP.exe.
3. Right-click DXSETUP.exe.
4. Select Run as administrator.
5. Follow the installation wizard.
6. Restart Windows after setup completes.
7. Launch the affected game or application again.

Do not run only the first downloaded executable and assume the runtime has been installed. The offline package first extracts the installer files. DXSETUP.exe is the component installer that must run afterward.

How to tell whether it worked

The repair is successful when:

• The original xinput1_2.dll error no longer appears.
• The game reaches its menu or main window.
• A controller-dependent feature starts working.
• The DirectX setup finishes without an error.

If the error changes to another file such as d3dx9_*.dll, x3daudio*.dll, or xinput1_3.dll, that usually indicates the application needs additional legacy DirectX components. Run the same DirectX setup again, then verify the game’s files.

If the offline installer fails

Use Microsoft’s DirectX End-User Runtime Web Installer.

The web installer downloads the required legacy side-by-side components during setup.

1. Download dxwebsetup.exe from Microsoft.
2. Right-click it.
3. Select Run as administrator.
4. Accept the license terms.
5. Allow the installer to download its components.
6. Restart Windows.
7. Test the application again.

If the web installer cannot download files, returns a network error, or stops partway through, use the June 2010 offline package instead.

Fix 2: Run the game’s own DirectX prerequisite installer

Many older games include their own prerequisite files. They may be stored in a folder named:

Redist
DirectX
_CommonRedist
Prerequisites
Support
Installers

The exact folder varies by publisher and launcher.

Find the installer in Steam

1. Open Steam.
2. Select Library.
3. Right-click the affected game.
4. Select Manage.
5. Choose Browse local files.
6. Look for a DirectX or Redist folder.
7. Run DXSETUP.exe as administrator.
8. Restart Windows.
9. Launch the game again.

Steam games can also contain secondary installers for DirectX and other prerequisites. Steam’s launch troubleshooting guidance explains why a canceled or blocked prerequisite installation can prevent a game from launching.

Find the installer in Epic Games Launcher

1. Open Epic Games Launcher.
2. Select Library.
3. Find the game.
4. Select the three dots beside its name.
5. Choose Manage.
6. Select Open install location, if available.
7. Search the game directory for DXSETUP.exe or a DirectX folder.
8. Run the installer as administrator.
9. Restart Windows.
10. Test the game.

Use the launcher’s repair or verification feature

If the local runtime files are missing or damaged, verify the game before reinstalling it.

For Steam:

1. Open Library.
2. Right-click the game.
3. Select Properties.
4. Open Installed Files.
5. Select Verify integrity of game files.
6. Wait for the process to finish.
7. Run any prerequisite installer included with the game.
8. Start the game again.

Steam’s file verification instructions describe this repair process.

For Epic Games Launcher:

1. Open Library.
2. Select the three dots beside the game.
3. Choose Manage.
4. Select Verify.
5. Wait for verification to complete.
6. Restart the launcher.
7. Try the game again.

For GOG Galaxy, open the game’s management menu and use its Verify / Repair option if available. If the launcher does not provide repair, reinstall the game from its legitimate installer and run the bundled DirectX prerequisite setup.

A game-specific repair is especially important when only one title fails. Windows may have a working runtime while that particular game directory contains a missing or incorrect application-local copy.

Fix 3: Check whether antivirus quarantined the file

Security software can quarantine a runtime file after a game update, repackaging event, or false detection. Do not restore a file simply because its filename is correct.

Check Windows Security Protection History

1. Open Start.
2. Type Windows Security.
3. Open the app.
4. Select Virus & threat protection.
5. Select Protection history.
6. Review recent actions.
7. Look for an entry involving the affected game directory or DirectX installer.
8. Expand the entry and inspect its path and detection details.

Restore or allow the file only when all of these are true:

• It came from the official Microsoft DirectX package or the game’s legitimate installer.
• The file path belongs to the expected installation.
• The source is trustworthy.
• The file has a valid Microsoft or publisher signature where one is expected.

If the quarantined file came from an unofficial DLL download, leave it quarantined and remove the associated download. Downloading another copy from the same source does not solve the security problem.

Microsoft explains how Protection History works in Windows Security.

After restoring a legitimate file, run the game’s verification process. That ensures the launcher can replace missing or altered files from its own trusted package.

Fix 4: Check for an incorrect DLL beside the game

Windows normally searches the application directory before searching system directories. This means a bad xinput1_2.dll placed beside a game executable can override a valid runtime elsewhere.

Inspect the game directory

1. Open the launcher.
2. Browse to the game’s local files.
3. Find the folder containing the main .exe file.
4. Search for xinput1_2.dll.
5. Right-click the file.
6. Select Properties.
7. Review the Digital Signatures tab if present.
8. Open Details and check the file description, publisher, and version information.

Do not judge a file only by its name. A file with the correct name can still be an incompatible wrapper, a damaged copy, or malware.

If the file is unexpected:

1. Close the game and launcher.
2. Rename the file to something such as:

text
xinput1_2.dll.old

1. Run the launcher’s file verification.
2. Run the game’s bundled DirectX installer.
3. Test the game.

Renaming is safer than immediately deleting the file because it preserves a recoverable copy while you test. If verification restores a clean file, remove the renamed copy later.

If the file is inside an x360ce or controller-emulation folder, it may be a wrapper rather than Microsoft’s original runtime. Controller wrappers can use alternate XInput filenames. Remove or reconfigure the wrapper only after closing the game, then verify the game files.

Fix 5: Check 32-bit and 64-bit compatibility

Architecture mismatch is a common reason for a DLL error that persists after copying a file.

A 32-bit application needs a 32-bit version of the dependency. A 64-bit application needs a 64-bit version. A 64-bit Windows installation can run both kinds of applications, but it keeps their system files in different locations.

On 64-bit Windows:

• System32 contains native 64-bit system files.
• SysWOW64 contains 32-bit system files.

The names are confusing, so do not use the folder name as a shortcut for choosing a DLL. Microsoft documents this behavior in its file system redirector documentation.

Check whether the program is 32-bit or 64-bit

There is no universal label for every older executable, but these methods help:

1. Open Task Manager while the program is running.
2. Select Details.
3. Right-click the column headings.
4. Select Select columns.
5. Enable Platform, if available.
6. Look for a 32-bit indicator beside the process.

You can also inspect the game publisher’s system requirements or determine whether the game is an older title that predates widespread 64-bit support. Many older games are 32-bit even when installed on 64-bit Windows.

The safest solution is to install the DirectX runtime normally and let its installer place the required architecture-specific components. Do not download one DLL and move it between System32, SysWOW64, and the game directory.

Fix 6: Do not use regsvr32 for this file

regsvr32 is used for self-registering OLE, COM, and ActiveX libraries. It is not a general-purpose DLL repair command.

xinput1_2.dll is an API runtime library, not an ActiveX control. Running this command is not an appropriate fix:

regsvr32 xinput1_2.dll

It may produce an error stating that the module was loaded but the entry point was not found, or that the DLL is not compatible with registration. That result does not mean the DirectX runtime needs registration.

Microsoft’s Regsvr32 troubleshooting guidance explains which kinds of DLLs can be registered and why ordinary API libraries can fail with this tool.

Install or repair the owning DirectX runtime instead.

Fix 7: Avoid standalone DLL downloads

Do not download xinput1_2.dll from a random DLL website and copy it into System32, SysWOW64, or the game directory.

A standalone download can be:

• Malware disguised with a familiar filename.
• The wrong architecture.
• The wrong build for the application.
• Missing required dependencies.
• An unofficial wrapper that changes controller behavior.
• A file that is blocked again by antivirus.
• A replacement that hides the actual damaged game installation.

It can also make troubleshooting harder because Windows searches the application directory before other locations. An incorrect local copy may override a valid runtime.

Use one of these sources instead:

• Microsoft’s DirectX End-User Runtime Web Installer.
• Microsoft’s DirectX End-User Runtimes June 2010 package.
• The game’s original installer or launcher prerequisite package.

Manual copying is appropriate only when a legitimate game publisher explicitly supplies an exact, signed, architecture-correct application-local file. Even then, repairing or verifying the game is preferable.

Never rename xinput1_3.dll or xinput1_4.dll to xinput1_2.dll. Similar names do not mean the libraries are interchangeable.

Fix 8: Install Windows updates

Windows updates do not normally install the legacy xinput1_2.dll package, but an outdated or damaged Windows installation can cause broader compatibility and servicing problems.

Windows 11

1. Open Start.
2. Select Settings.
3. Choose Windows Update.
4. Select Check for updates.
5. Install available updates.
6. Restart when requested.
7. Check for updates again until none remain.
8. Test the affected application.

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.
7. Restart Windows.
8. Test the program again.

Microsoft’s Windows Update instructions cover the standard update process.

If the DirectX installer says that a newer version is already installed, do not treat that message as proof that xinput1_2.dll is present. The installed modern DirectX version and the legacy side-by-side runtime are separate components. Run the June 2010 package or the game’s own DXSETUP.exe.

Fix 9: Repair Windows components with DISM and SFC

Use Windows component repair when:

• Several unrelated applications report missing DLLs.
• Windows itself shows damaged-component errors.
• DirectX setup crashes or refuses to complete.
• The problem began after an interrupted update.
• The file exists but produces a bad-image error.
• File verification and the official DirectX installer do not help.

Open an elevated Command Prompt:

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. Run:

text
DISM.exe /Online /Cleanup-image /Restorehealth

1. Wait for it to finish.
2. Then run:

text
sfc /scannow

1. Wait until verification reaches 100 percent.
2. Restart Windows.
3. Run the DirectX installer again.
4. Test the affected application.

Microsoft recommends running DISM before SFC in its System File Checker instructions.

Success means DISM completes without an unrepaired error and SFC reports that it repaired corrupted files or found no integrity violations. If SFC reports that it could not repair some files, restart and run the sequence once more. Persistent component-store errors may require Windows repair installation rather than repeated DLL copying.

When manually running DISM and SFC becomes a cycle of long scans with unclear results, Outbyte PC Repair can scan for the specific repair issues involved and show what it found; repair actions are performed by the full version, and it is not required for every xinput1_2.dll case.

Fix 10: Check drivers only when the symptom points to hardware

A graphics or controller driver can cause crashes, input failures, or a game that closes after launch. It normally does not restore a missing legacy DirectX DLL.

Use Device Manager when:

• The controller is not detected at all.
• Device Manager shows a warning icon.
• The game starts but input does not work.
• The problem began after a graphics or controller driver change.
• Other games show the same hardware behavior.

Check devices in Device Manager

1. Right-click Start.
2. Select Device Manager.
3. Expand Display adapters.
4. Expand Human Interface Devices.
5. Expand Xbox Peripherals, if present.
6. Look for a yellow warning icon.
7. Right-click the affected device.
8. Select Properties.
9. Open the General tab.
10. Read the device status.

To check for a driver update:

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

For a driver that was recently updated:

1. Right-click the device.
2. Select Properties.
3. Open the Driver tab.
4. Select Roll Back Driver, if available.
5. Restart Windows.
6. Test the game.

For a clean reinstall:

1. Right-click the affected device.
2. Select Uninstall device.
3. Enable the option to remove the driver package only if Windows presents it and you have the correct replacement available.
4. Restart Windows.
5. Install the driver from the hardware manufacturer or Windows Update.
6. Restart again.

When identifying stale drivers across several device categories becomes tedious, Outbyte Driver Updater can scan the system and identify driver versions; the full version performs driver installation, and it is not a substitute for the DirectX repair when the missing file belongs to a specific game.

After a driver repair, run the DirectX installer and verify the game if xinput1_2.dll is still missing.

Fix 11: Check Windows Features only for separate legacy requirements

Windows Features is not where you normally install xinput1_2.dll. Do not expect enabling a random optional feature to restore the file.

Some very old games also require DirectPlay. That is a separate Windows compatibility component.

To check it:

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

Enabling DirectPlay will not replace the DirectX June 2010 runtime. If the error still names xinput1_2.dll, install the official DirectX package and verify the game.

Fix 12: Investigate a dependency when the file exists

“The specified module could not be found” does not always mean that xinput1_2.dll itself is absent. Windows may have found the named DLL but failed to load one of its dependencies.

This is more likely when:

• The file is visibly present.
• The game still reports the same error.
• The message says “specified module” rather than simply “file not found.”
• The file has the wrong architecture.
• The file is damaged or unsigned.
• The game directory contains several manually copied DLLs.

Check the following:

1. Confirm the file path.
2. Check its digital signature.
3. Run the launcher’s verification.
4. Run the official DirectX installer.
5. Remove unexpected application-local DLLs by renaming them.
6. Confirm that the game and runtime architecture match.
7. Run DISM and SFC if other applications also fail.

Do not replace every DLL in the folder one at a time. That can create a mixed set of incompatible files and make the dependency chain harder to diagnose.

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

Fix 13: Scan for malware only when the evidence supports it

Malware is possible, but one missing-DLL message does not prove an infection.

Run a full scan when:

• The file appeared in an unexpected folder.
• The file is unsigned or has a suspicious publisher.
• Windows Security reports a detection.
• Multiple system files change or disappear.
• Browser redirects, unknown startup entries, or other suspicious behavior are present.

Run a full Windows Security scan

1. Open Windows Security.
2. Select Virus & threat protection.
3. Select Scan options.
4. Choose Full scan.
5. Select Scan now.
6. Leave the computer powered on until the scan completes.
7. Review the results.

If compromise is suspected, use Microsoft Defender Offline scan from the same Scan options page. Microsoft’s Virus and threat protection guidance explains the available scan types.

After removing a threat, reinstall the affected game or DirectX runtime from a trusted source rather than restoring an unknown DLL.

Fix 14: Use System Restore after a clear system change

System Restore is appropriate when the error began immediately after:

• A driver installation.
• A system update.
• A game modification.
• A security-software change.
• An installer or cleanup operation.

It is not the first choice for a missing runtime on a clean Windows installation.

Start System Restore

1. Press Win + R.
2. Enter:

text
rstrui.exe

1. Press Enter.
2. Select Next.
3. Choose a restore point from before the problem began.
4. Select Scan for affected programs, if available.
5. Review the changes.
6. Select Next.
7. Select Finish.
8. Allow Windows to restart.

System Restore normally affects system files, registry settings, drivers, and installed programs, not personal documents. Microsoft describes the process in its System Restore documentation.

After restoring, install the official DirectX runtime again if the game still needs it.

Why reinstalling the game sometimes fails

Reinstalling the game is not always enough because the missing file may belong to a separate prerequisite package.

Common reasons include:

• The game installer skips prerequisites already marked as installed.
• The DirectX setup was canceled during the first installation.
• Antivirus quarantined the file after installation.
• The game launcher restored the executable but not its redistributables.
• A migration copied the game folder without its prerequisite installers.
• A bad application-local DLL remained in the directory.
• The installer requires administrator permission.
• The installer is incompatible with the current Windows account or path.

Before reinstalling:

1. Use the launcher’s repair or verification feature.
2. Look for DXSETUP.exe.
3. Run the official June 2010 DirectX package.
4. Check Windows Security Protection History.
5. Check the game folder for suspicious local DLLs.

If reinstalling is necessary, uninstall the game through its normal launcher, restart Windows, reinstall it from the legitimate source, and run its prerequisite installer as administrator.

Is xinput1_2.dll part of Visual C++ or .NET

No. Visual C++ Redistributables provide C and C++ runtime libraries. .NET provides a managed application runtime. Neither is the normal owner of xinput1_2.dll.

Install Visual C++ or .NET only when the error names a file belonging to those runtimes or the application’s own documentation requires them. Microsoft maintains separate documentation for Visual C++ Redistributables and .NET on Windows.

If the error changes from xinput1_2.dll to a Visual C++ runtime file after the DirectX repair, address that new dependency separately. Do not install unrelated runtimes simply because a DLL error appeared.

Frequently asked questions

Does Windows 11 include xinput1_2.dll by default?

Treat it as a legacy DirectX redistributable component rather than a normal Windows 11 inbox DLL. Windows 11 includes modern DirectX components, but older applications can require optional side-by-side files from the DirectX June 2010 runtime.

Does DirectX 12 replace xinput1_2.dll?

No. DirectX 12 being installed does not guarantee that every legacy XInput or DirectX helper library is present. Install the June 2010 runtime for applications that require older components.

Should I copy the file into System32?

No. Install the runtime normally. Manual copying can create an architecture mismatch, bypass the game’s repair process, or place an untrusted DLL where Windows may load it.

Can I rename xinput1_3.dll to xinput1_2.dll?

No. Similar filenames do not make the libraries interchangeable.

Does regsvr32 fix the error?

No. regsvr32 is for self-registering COM, OLE, and ActiveX DLLs. It is not the correct repair for this XInput API library.

What if the game says “not designed to run on Windows”?

Check the file’s path, architecture, digital signature, and source. Remove or rename an unexpected local copy, verify the game files, and reinstall the official DirectX runtime. If several applications show bad-image errors, run DISM and SFC.

What if the error changes to another DirectX DLL?

That usually confirms that the game needs more legacy DirectX components. Run the complete June 2010 DirectX setup and verify the game files instead of downloading each missing filename separately.

What if only one game fails?

Start with the game’s launcher verification, its Redist or DirectX folder, and Protection History. A one-game failure is more likely to involve local game files or a bundled prerequisite than a damaged Windows installation.

What if every game that uses a controller fails?

Install the official DirectX runtime first. Then check for architecture mismatches, controller wrappers, antivirus quarantine, and broader Windows component corruption. Update the controller driver only when Device Manager shows a hardware or driver problem.

Should I enable DirectPlay?

Only if the game specifically requires it. DirectPlay is a separate legacy compatibility feature and does not install xinput1_2.dll.

When should I repair or reinstall Windows?

Consider Windows repair only after the official DirectX package, game verification, antivirus checks, architecture checks, DISM, and SFC have failed, especially when multiple unrelated programs report missing or damaged system files. A single old game error normally does not justify reinstalling Windows.

What is the correct repair order?

Use this order:

1. Install the official DirectX June 2010 runtime.
2. Run the game’s bundled DXSETUP.exe.
3. Verify or repair the game through its launcher.
4. Check antivirus Protection History.
5. Inspect the game directory for an incorrect local DLL.
6. Check 32-bit and 64-bit compatibility.
7. Install Windows updates.
8. Run DISM, then SFC.
9. Check drivers only for hardware symptoms.
10. Use malware scanning or System Restore when the evidence supports it.

This sequence restores the owning runtime first and reserves deeper Windows repair for cases where the evidence points beyond one missing legacy DirectX file.

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.