xinput1_4.dll Missing: Choose the Right Windows Repair Path

If Windows reports that “XINPUT1_4.dll is missing from your computer,” the application cannot load the Microsoft controller-input component it requested. An xinput1_4.dll error can also appear as “The code execution cannot proceed because XINPUT1_4.dll was not found” or as a “bad image” loader error.

The 60-second answer

xinput1_4.dll is the Windows system implementation of XInput 1.4, Microsoft’s API for Xbox-compatible controller input. It is an operating-system component introduced with Windows 8, not normally a separately downloaded game runtime. Microsoft documents XInput 1.4 as an inbox Windows component.

As an Amazon Associate I earn from qualifying purchases.

The correct repair depends first on your Windows version:

• On Windows 8, 8.1, 10, or 11, install pending updates, restart, then run DISM followed by SFC.
• If only one game or application fails, repair or verify that application afterward.
• On Windows 7 or Vista, XInput 1.4 is not the normal native component. Use a compatible application build or upgrade Windows.
• Do not download an isolated DLL from a random DLL website.
• Do not rename xinput1_3.dll to xinput1_4.dll.
• Do not copy an arbitrary DLL into System32 or SysWOW64.
• The DirectX End-User Runtimes June 2010 package installs legacy XInput 1.3, not XInput 1.4.

If the error names a DLL inside the game directory, start with the game launcher’s repair or verification feature. If it names %WINDIR%\System32\XInput1_4.dll, repair Windows first.

What xinput1_4.dll actually is

XInput is Microsoft’s controller-input API for Xbox-compatible controllers and other devices that expose compatible input behavior. The xinput1_4.dll file provides the XInput 1.4 implementation used by applications that link specifically to that version.

It is not:

• An NVIDIA, AMD, Intel, or motherboard graphics driver
• A controller manufacturer’s driver package
• A Visual C++ runtime
• A standalone DirectX 12 download
• A file that should normally be downloaded from a third-party DLL library

Microsoft supplies XInput 1.4 as part of Windows 8 and later. The application’s imported DLL name determines which XInput generation it expects. XInput 1.4, XInput 1.3, and XInput 9.1.0 are related APIs, but they are not interchangeable file names.

This distinction matters because many older troubleshooting pages describe every xinput file as part of the same DirectX redistributable. That is not accurate. The DirectX End-User Runtimes June 2010 package supplies legacy XInput 1.3 and other side-by-side DirectX libraries. It does not install or replace the Windows XInput 1.4 component. Microsoft’s package page identifies the June 2010 runtime as a legacy component package.

Which Windows versions include XInput 1.4

Windows version	Relevant XInput component
Windows Vista and Windows 7	XInput 9.1.0 is built in; XInput 1.4 is not the normal system component
Windows 8 and 8.1	XInput 1.4 is built in
Windows 10 and Windows 11	XInput 1.4 is a Windows system component

Microsoft’s documentation says applications targeting Windows 7 or earlier should use XInput 9.1.0 or explicitly redistribute XInput 1.3 instead of linking to XInput 1.4. See Microsoft’s XInput version guidance.

That makes Windows 7 the most important compatibility branch. If a modern application requires XINPUT1_4.dll on Windows 7, repeatedly installing DirectX, Visual C++, graphics drivers, or controller drivers will not add the missing Windows 8-era component. The application needs a Windows 7-compatible build, or the operating system needs to be upgraded.

Where Windows normally stores the file

On 64-bit Windows, the normal locations are:

%WINDIR%\System32\XInput1_4.dll
%WINDIR%\SysWOW64\XInput1_4.dll

The names are counterintuitive:

• System32 normally contains the native 64-bit system copy on 64-bit Windows.
• SysWOW64 normally contains the 32-bit system copy used by 32-bit applications.

WOW64 redirects 32-bit processes to the appropriate 32-bit system directory. Microsoft explains this behavior in its File System Redirector documentation.

Check whether the expected files exist with Command Prompt:

dir "%WINDIR%\System32\XInput1_4.dll"
dir "%WINDIR%\SysWOW64\XInput1_4.dll"

A missing file is useful evidence, but a present file is not proof that it is valid. It could be corrupted, unsigned, the wrong architecture, or different from a private copy that the application loads from its own directory.

There is no single universal file version or file size to publish. Windows servicing changes system binaries by operating-system build and architecture.

To inspect the file without downloading a replacement, open PowerShell and run:

Get-Item "$env:WINDIR\System32\XInput1_4.dll" |
  Select-Object FullName, Length,
    @{Name="FileVersion";Expression={$_.VersionInfo.FileVersion}},
    @{Name="ProductVersion";Expression={$_.VersionInfo.ProductVersion}}

Get-AuthenticodeSignature "$env:WINDIR\System32\XInput1_4.dll"

Get-FileHash "$env:WINDIR\System32\XInput1_4.dll"

Repeat the inspection with SysWOW64 if the failing application is 32-bit:

Get-Item "$env:WINDIR\SysWOW64\XInput1_4.dll" |
  Select-Object FullName, Length,
    @{Name="FileVersion";Expression={$_.VersionInfo.FileVersion}},
    @{Name="ProductVersion";Expression={$_.VersionInfo.ProductVersion}}

Get-AuthenticodeSignature "$env:WINDIR\SysWOW64\XInput1_4.dll"

Do not treat a particular hash, version, or file size found on another computer as a universal target.

What the different error messages mean

The wording varies by Windows version, application, loader, and failure type.

“The program can’t start because XINPUT1_4.dll is missing from your computer”

This usually means the application requested the DLL and the loader could not find a usable copy in the relevant search locations.

The next question is where the application expected the file:

• If the error names C:\Windows\System32\XINPUT1_4.dll, repair Windows.
• If the error names the game or application directory, repair or verify that application.
• If no path is shown, inspect both the Windows system locations and the application directory.

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

This is another missing-module message. It does not necessarily prove that the file is absent from every location. A 32-bit application may need the 32-bit copy in SysWOW64, while a 64-bit application uses the native system directory.

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

This is commonly called a bad-image error. It may be accompanied by a status such as 0xc000007b or 0xc000012f.

The status alone does not prove that xinput1_4.dll itself is the root cause. Possible causes include:

• A corrupted Windows component
• A wrong-architecture private DLL
• An invalid or modified file beside the application
• A missing dependency
• A damaged application installation
• A mismatch between the application and the operating system

“The specified module could not be found”

This message can be misleading. The named DLL may exist while one of its dependencies is missing. Microsoft notes that “specified module could not be found” can refer to a dependency in the loading chain, not only the file named in the message. See Microsoft’s explanation of this loader error.

Repair Windows and the application before using specialist dependency-analysis tools.

Fix 1: Confirm the Windows compatibility branch

Before changing files or installing packages, confirm the operating system.

1. Press Win+R.
2. Type winver.
3. Press Enter.
4. Note the Windows edition and version shown.

You can also open:

Start > Settings > System > About

Check whether the failing program is designed for your Windows version. If you are using Windows 7 or Vista and the application explicitly requires XINPUT1_4.dll, the definitive choices are:

• Install a build of the application that targets XInput 9.1.0.
• Install a build that redistributes XInput 1.3 where the publisher supports that arrangement.
• Upgrade Windows to a version that includes XInput 1.4.

Do not expect SFC, a DirectX installer, or a controller-driver reinstall to create a Windows component that the operating system never shipped.

On Windows 8, 8.1, 10, and 11, continue with the Windows repair path below.

Fix 2: Install Windows updates, then repair system files

This is the main repair path when the error names the Windows copy or multiple applications fail.

Install pending updates

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

Microsoft’s Windows Update guidance is relevant because system files can be restored or serviced as part of the operating-system update process.

Run DISM

1. Select Start.
2. Type Command Prompt.
3. Right-click Command Prompt.
4. Select Run as administrator.
5. Approve the User Account Control prompt.
6. Run:

DISM.exe /Online /Cleanup-Image /RestoreHealth

Wait for the command to finish. Depending on the state of the component store, it may take some time. Do not close the window simply because progress appears to pause.

DISM repairs the Windows component store that SFC uses as a source. Microsoft specifically recommends DISM before SFC for corrupted Windows files.

If DISM reports that the repair source cannot be found, first confirm that Windows Update is working. Microsoft also documents using a known-good repair source when Windows Update cannot supply the required files. See Microsoft’s Windows image repair documentation.

For additional diagnosis, these commands inspect the component store without immediately performing the full repair:

DISM.exe /Online /Cleanup-Image /CheckHealth
DISM.exe /Online /Cleanup-Image /ScanHealth

Run SFC

After DISM completes, run:

sfc /scannow

Leave the administrator Command Prompt open until verification reaches 100 percent.

Possible results include:

• Windows Resource Protection did not find any integrity violations: SFC found no damaged protected files.
• Windows Resource Protection found corrupt files and successfully repaired them: restart Windows and retry the application.
• Windows Resource Protection found corrupt files but was unable to fix some of them: run DISM again, restart, and run SFC again. If it still cannot repair the system, continue to System Restore or in-place repair.
• Windows Resource Protection could not start the repair service: restart Windows and repeat the command from an administrator terminal.

Restart after a successful repair, then launch the affected program. If it still fails, repair the application as described below.

Manually comparing component versions and repeating DISM and SFC without knowing what changed can be tedious. Outbyte PC Repair can scan for system issues and show what it identifies; repairs are performed by the full version, and it is optional rather than required for this Windows repair path.

Fix 3: Repair or reinstall the affected application

If only one program fails, especially when other games and applications still launch, the application installation is a stronger suspect than Windows.

For a normal Windows desktop application:

1. Select Start > Settings.
2. Select Apps.
3. Open Installed apps.
4. Find the affected application.
5. Select its three-dot menu.
6. Choose Advanced options, if available.
7. Select Repair.
8. Launch the application again.

The exact options vary by application. Microsoft documents the Windows app-repair process here.

If Repair is unavailable or does not help:

1. Return to the application’s entry in Installed apps.
2. Select Uninstall.
3. Restart Windows if the uninstaller requests it.
4. Download or run the installer supplied by the application’s official publisher.
5. Install the program again.
6. Launch it before adding modifications, unofficial patches, or custom DLL files.

A reinstall is particularly important when the error points to a private XInput1_4.dll beside the application executable. The application directory can take precedence in the DLL search order, so an invalid private copy may be loaded before the Windows system copy. Microsoft documents application-directory precedence in the DLL search order.

Fix 4: Verify the game files through its launcher

A game may contain its own private DLL or supporting files. In that case, SFC cannot repair the game directory.

Steam

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

Steam describes this verification process in its support documentation.

Verification can restore a deleted or corrupted game-local file. It cannot repair a missing Windows system component.

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 Verify.
7. Wait for the process to finish.
8. Launch the game again.

Epic documents these verification steps here.

Other launchers usually provide a similarly named Verify, Repair, or Scan and repair command. Use the publisher’s launcher rather than replacing files manually.

Fix 5: Install legacy DirectX only when the error names a legacy component

Windows 10 and Windows 11 include modern DirectX, but older games can still require optional side-by-side libraries from the DirectX End-User Runtime.

The official packages include:

• dxwebsetup.exe, the DirectX End-User Runtime Web Installer
• directx_Jun2010_redist.exe, the DirectX End-User Runtimes June 2010 package

The official DirectX End-User Runtime Web Installer or the June 2010 redistributable may help when the error names files such as:

• xinput1_3.dll
• d3dx9_*.dll
• xaudio2_7.dll
• Other legacy DirectX side-by-side libraries listed by Microsoft

They are not the authoritative fix for a missing xinput1_4.dll. The June 2010 package supplies XInput 1.3, not XInput 1.4.

Before installing a legacy package, read the exact filename in the error. Installing DirectX 1.3 components because the message names XInput 1.4 can send troubleshooting in the wrong direction.

Never rename xinput1_3.dll to xinput1_4.dll. The two versions are not interchangeable.

Fix 6: Check Windows Security quarantine

Windows Security may quarantine a file after detecting or suspecting tampering. It can also remove a game-local file that the launcher later needs.

1. Open Start.
2. Type Windows Security.
3. Open the application.
4. Select Virus & threat protection.
5. Select Protection history.
6. Review recent detections.
7. Open an item to inspect its path, detection name, and action.

Do not restore a file merely because a game wants it. First check:

• Whether the path is a legitimate Windows system directory or an expected game directory
• Whether the file has a valid Microsoft or publisher signature
• Whether the detection is current
• Whether a scan identifies related threats

Microsoft explains Protection History and restoration behavior.

If the file is in a temporary folder, user-profile folder, modified-game directory, or unexpected application location and lacks a valid signature, do not blindly allow it. Run a scan instead:

1. Open Windows Security.
2. Select Virus & threat protection.
3. Select Scan options.
4. Start with Full scan.
5. If malware is suspected or the problem persists, consider Microsoft Defender Offline scan.

Microsoft’s virus and threat protection guidance covers these scan choices.

After removing a false positive or restoring a verified file, repair the application through its official installer or launcher. If the quarantined path was the Windows system directory, use DISM and SFC rather than copying an external DLL into place.

Fix 7: Check the application architecture and private DLL copies

A 32-bit application and a 64-bit application do not load the same system copy.

On 64-bit Windows:

• A native 64-bit application normally uses System32.
• A 32-bit application normally uses the redirected 32-bit system directory, SysWOW64.

Check both locations:

dir "%WINDIR%\System32\XInput1_4.dll"
dir "%WINDIR%\SysWOW64\XInput1_4.dll"

If one file is missing, do not download a replacement. Repair Windows through Windows Update, DISM, and SFC.

Also inspect the directory containing the application executable. A private copy beside the executable may be loaded before the system copy. A private file can be:

• The wrong architecture
• Damaged
• Modified by a third-party patch
• Unsigned
• Intended for a different application version

The safest repair is to use the launcher’s verification function or reinstall the application. If you manually find a suspicious private DLL, do not replace it with a file from a DLL download site.

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

Fix 8: Repair related Visual C++ runtimes only when the error names them

Visual C++ is not the normal source of xinput1_4.dll.

Repair or install a Visual C++ Redistributable when the error also names files such as:

• VCRUNTIME140.dll
• MSVCP140.dll
• VCRUNTIME140_1.dll
• Other Microsoft Visual C++ runtime files

Microsoft’s supported packages include:

• vc_redist.x86.exe
• vc_redist.x64.exe
• vc_redist.arm64.exe

A 32-bit application needs the x86 runtime even on 64-bit Windows. Microsoft lists the current supported Visual C++ Redistributable packages and architectures here.

Do not remove every Visual C++ entry in Installed apps. Older applications can depend on different runtime generations. Repair the specific architecture and generation indicated by the application, preferably using Microsoft’s supported download page or the application publisher’s installer.

Fix 9: Update drivers only for the symptoms drivers can cause

A controller or graphics driver can cause input or rendering problems after the DLL loads. It is not normally the cause of a missing Windows xinput1_4.dll.

Use Device Manager when the application starts but the controller, display, or related hardware behaves incorrectly.

Update a controller driver

1. Right-click Start.
2. Select Device Manager.
3. Expand Xbox Peripherals, Human Interface Devices, or Sound, video and game controllers.
4. Right-click the relevant controller.
5. Select Update driver.
6. Choose Search automatically for drivers.
7. Restart Windows if prompted.

Update a graphics driver

1. Open Device Manager.
2. Expand Display adapters.
3. Right-click the graphics device.
4. Select Update driver.
5. Choose Search automatically for drivers.
6. Restart Windows.

For a clean, vendor-supported graphics-driver update, use the graphics manufacturer’s official support channel. Do not treat a graphics-driver update as a replacement for Windows component repair when the application reports that XINPUT1_4.dll is missing.

Manually checking several hardware categories and comparing driver versions can take time, especially when it is unclear which device is involved. Outbyte Driver Updater can scan for stale drivers and identify what it finds; driver installation through the full version is optional, and it does not replace repairing a game that owns the failing private DLL.

Do not use Windows Features to add XInput 1.4

The Windows Features dialog is not the normal installation path for XInput 1.4.

You can inspect it here:

1. Press Win+R.
2. Type:

optionalfeatures

1. Press Enter.

This opens Turn Windows features on or off. There is no standard optional feature that you should enable to install xinput1_4.dll. Do not randomly enable legacy components in the hope that they will provide this file.

If a particular application specifically requires another Windows feature, follow that application’s documented requirements. That is separate from repairing XInput 1.4.

Do not use regsvr32 for this file

regsvr32 is designed for DLLs that support self-registration through an exported DllRegisterServer function, typically COM or ActiveX components. Microsoft describes this self-registration model.

xinput1_4.dll is a Windows API component, not a normal self-registering COM library. Running commands such as these is not a repair:

regsvr32 XInput1_4.dll
regsvr32 "%WINDIR%\System32\XInput1_4.dll"

They may produce an error about a missing entry point or an invalid registration target. Registering the file does not repair its contents, architecture, dependencies, or Windows component-store state.

Use Windows Update, DISM, SFC, System Restore, or an in-place Windows repair instead.

Fix 10: Use System Restore if the failure began after a change

System Restore is useful when the error started immediately after:

• A Windows update
• A cleanup utility
• A driver installation
• A program installation
• A system modification

To open it:

1. Press Win+R.
2. Type:

rstrui.exe

1. Press Enter.
2. Select Next.
3. Choose a restore point created before the problem began.
4. Select Scan for affected programs, if available.
5. Confirm the restore point.
6. Allow Windows to restart.

System Restore rolls back system files, settings, and installed programs while normally leaving personal files untouched. Microsoft’s System Restore documentation explains the process and limitations.

If the failure affects only one game, System Restore may be unnecessary. Verify or reinstall that game first. If several unrelated programs fail after a system change, System Restore becomes more relevant.

Fix 11: Perform an in-place Windows repair

If Windows Update, DISM, and SFC cannot restore the component, use Microsoft’s repair-installation path before considering a full reset.

On supported Windows 11 installations, the option may appear here:

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

Microsoft describes this process as reinstalling the current Windows version while preserving apps, files, and settings when the option is available. See Microsoft’s current Windows repair guidance.

If the option is unavailable, use Microsoft’s supported installation media or setup procedure and read each screen carefully. Back up important files before any major operating-system repair.

An in-place repair is appropriate when:

• The file is missing from the Windows system location
• DISM cannot repair the component store
• SFC repeatedly reports unrepaired corruption
• Several unrelated applications fail
• The problem began after system corruption or an interrupted update

Why downloading the DLL is unsafe

Searching for xinput1_4.dll download produces many pages offering isolated copies. That is not a safe repair method.

A downloaded DLL may be:

• Malware or a modified file
• The wrong architecture
• From an unrelated Windows build
• Unsigned or falsely labeled
• Missing its own dependencies
• Placed in the wrong directory
• A private game DLL rather than the Windows component

It may also hide the real cause, such as Windows component corruption, an incomplete game installation, or an incompatible Windows version.

The safe sources are:

• Windows Update
• DISM and SFC
• Microsoft’s Windows repair options
• The affected application’s official installer
• Steam, Epic, or another official launcher’s verification function
• Microsoft’s official DirectX packages when the error names a legacy DirectX file
• Microsoft’s official Visual C++ packages when the error names a C++ runtime file

Do not copy a random DLL into System32 or SysWOW64, even if the filename looks correct.

A practical diagnosis table

What you observe	Most likely direction	Correct next step
Windows 7 or Vista reports missing XINPUT1_4.dll	Application requires an API not normally supplied by the operating system	Use a compatible application build or upgrade Windows
Several unrelated programs fail	Windows component corruption, malware, storage trouble, or a bad update	Windows Update, DISM, SFC, security scans, then System Restore or in-place repair
Only one game fails and the path is the game folder	Damaged or quarantined game-local file	Verify or repair the game through its launcher
Error names System32\XInput1_4.dll on Windows 10 or 11	Missing or damaged Windows component	Update Windows, run DISM, then SFC
Error names xinput1_3.dll	Legacy DirectX dependency	Use the official DirectX End-User Runtime package
Error names VCRUNTIME140.dll or MSVCP140.dll	Visual C++ runtime problem	Repair the correct Microsoft Visual C++ architecture
File exists but produces “bad image”	Corruption, wrong architecture, dependency failure, or private DLL conflict	Check signature and location, verify the application, then repair Windows
Controller fails only after the program starts	Possible controller, USB, or application configuration problem	Check Device Manager and the application’s controller settings
Error began after cleanup software or a driver install	System change may have damaged or removed a component	Use System Restore if available

Final checklist for unresolved cases

Before asking for further help, record:

• Windows edition and version from winver
• Whether Windows is 32-bit or 64-bit
• The exact error text
• Any status code such as 0xc000007b
• The application or game name
• The launcher, such as Steam or Epic
• The path shown in the error
• Whether the problem affects one program or several
• Whether XInput1_4.dll exists in System32
• Whether it exists in SysWOW64
• The result of Get-AuthenticodeSignature
• The result of Windows Update
• The final DISM message
• The final SFC message
• Whether Windows Security shows a quarantine event
• Whether the problem began after an update, driver change, cleanup utility, or installation

The platform split remains decisive: on Windows 8, 8.1, 10, and 11, repair Windows components and then repair the affected application. On Windows 7 or Vista, use an application that supports XInput 9.1.0 or XInput 1.3, or upgrade Windows.

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.