dinput.dll Is Missing: Safe Windows and Game Repair Steps

Start with these checks

dinput.dll is a Windows system file used by older games and programs for keyboard, mouse, joystick, game-controller, and force-feedback input. If Windows reports that dinput.dll is missing, not found, damaged, or could not be loaded, identify the failure before replacing anything.

Check these points first:

• Which game or program fails?
• Does the error appear immediately at launch, or only when a controller is connected?
• Does the problem affect one game or several unrelated programs?
• Does the message name dinput.dll, dinput8.dll, xinput1_3.dll, or another file?
• Does the error show a full path such as C:\Windows\System32\dinput.dll?
• Did the problem begin after installing a mod, wrapper, compatibility patch, game update, Windows update, or antivirus action?
• Is the affected game likely to be 32-bit or 64-bit?
• Is there another file named dinput.dll in the game’s own folder?

The exact filename matters. dinput.dll is not interchangeable with dinput8.dll, xinput1_3.dll, or a game modification that happens to use the same filename.

As an Amazon Associate I earn from qualifying purchases.

What dinput.dll does

dinput.dll is the Microsoft DirectInput runtime. DirectInput is an API layer that allows software to enumerate and read input devices, including keyboards, mice, joysticks, gamepads, and other controllers. It is software support for input devices, not the physical controller driver itself.

Microsoft documents DirectInput as part of the Windows API for input devices in its DirectInput overview.

That distinction prevents a common wrong turn. Reinstalling a graphics driver, sound driver, or controller driver does not normally recreate a missing Windows dinput.dll. Driver repair becomes relevant when the file exists but a controller is not detected or DirectInput cannot initialize the device.

The genuine Windows file is normally located here:

• On 64-bit Windows, %SystemRoot%\System32\dinput.dll is the 64-bit copy.
• On 64-bit Windows, %SystemRoot%\SysWOW64\dinput.dll is the 32-bit copy used by 32-bit programs.
• On 32-bit Windows, the 32-bit copy is in %SystemRoot%\System32.

The names are counterintuitive. On 64-bit Windows, System32 contains native 64-bit system files, while SysWOW64 contains 32-bit system files. Microsoft explains this behavior in its file-system redirector documentation.

A Windows file inventory identifies the file as:

• Description: Microsoft DirectInput
• Publisher: Microsoft Corporation
• Product: Microsoft Windows Operating System

Historical Windows builds have used different file versions and sizes. For example, inventories include both 32-bit and 64-bit builds from Windows releases with different version numbers. Do not use one version or size as a universal test for every Windows 10 or Windows 11 installation.

dinput.dll, dinput8.dll, and xinput1_3.dll are different

Old games often report DirectX-related errors, but the filenames point to different components.

dinput.dll

This is the older Windows DirectInput runtime. It is a Windows component and should normally be repaired through Windows servicing when the system copy is missing or corrupted.

dinput8.dll

This is a separate DirectInput 8 implementation. Microsoft states that the DirectInput 8 object is implemented in Dinput8.dll in its DirectInput8Create documentation.

If the error specifically says dinput8.dll, do not rename or substitute dinput.dll. Follow the application or legacy DirectX repair path instead.

xinput1_3.dll

This is an older XInput side-by-side runtime. It is commonly required by older games and is not the same file as dinput.dll.

Other common legacy DirectX files include:

• d3dx9_*.dll
• xactengine*.dll
• Older XAudio components
• Other files supplied by the legacy DirectX SDK

A current DirectX version in Windows does not prove that every older side-by-side DirectX SDK component is installed.

Fix 1: Install Windows updates and restart

Because dinput.dll belongs to Windows, start with Windows Update when the error identifies the system file or affects more than one program.

Windows 11

1. Open Start.
2. Select Settings.
3. Select Windows Update.
4. Select Check for updates.
5. Install every available update.
6. Restart the computer, even if Windows does not immediately require a restart.
7. Try the affected program again.

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

Microsoft provides its current Windows Update instructions. Current DirectX updates for Windows are delivered through Windows Update, so this is also the correct first update path for the Windows DirectInput component.

How to tell whether this worked

The repair worked if the program starts without the dinput.dll message and the expected keyboard, mouse, or controller input functions normally.

If the same error remains, continue with DISM and System File Checker. Do not download a replacement DLL yet.

Fix 2: Repair Windows with DISM and SFC

Use this path when:

• dinput.dll is missing from the expected Windows folder.
• The error names a Windows system path.
• Several unrelated programs fail.
• The problem followed a failed update, disk issue, malware event, or security action.
• Windows reports a damaged or invalid system image.
• The program reports a “Bad Image” error involving the Windows copy.

DISM repairs the Windows component store. SFC then checks protected system files and restores damaged files from that repaired source.

Run DISM

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. Enter this command:

DISM.exe /Online /Cleanup-Image /RestoreHealth

1. Press Enter.
2. Wait for the operation to finish.

The scan can take time and may appear to pause at a percentage. Leave the window open until DISM reports that the restore operation completed.

Run SFC

After DISM finishes successfully, enter:

sfc /scannow

Press Enter and wait for verification to reach 100 percent.

Restart Windows after SFC completes, then launch the affected program.

Microsoft documents this DISM-then-SFC sequence in its System File Checker guidance.

Read the result

SFC can report several outcomes:

• Windows Resource Protection did not find any integrity violations: Windows did not find a protected-file problem. Investigate the game folder, filename, architecture, or another dependency.
• Windows Resource Protection found corrupt files and successfully repaired them: restart and test the program.
• Windows Resource Protection found corrupt files but was unable to fix some of them: run DISM again, check the CBS log if necessary, and use a matching Windows repair source or an in-place repair.
• Windows Resource Protection could not perform the requested operation: restart and try again, or run the scan from Windows Recovery Environment if the system cannot repair files while Windows is running.

If DISM needs a repair source, Microsoft documents this general form:

DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:C:\RepairSource\Windows /LimitAccess

Replace the example path only with a matching, known-good Windows repair source for the installed edition and build. Do not use a random DLL as the source. Microsoft’s Repair a Windows Image documentation explains the source requirements.

Repeating SFC without checking what changed can leave you guessing which repair actually helped. Outbyte PC Repair can scan for system-file and Windows configuration problems and show what it identifies; its repair actions are handled by the full version, and it is optional rather than required for this fix.

Fix 3: Check whether a game-folder DLL is overriding Windows

A game can fail even when the genuine Windows copy is present. Windows normally searches the executable’s directory before the system directories, so a file named dinput.dll beside the game executable can take precedence over the Microsoft copy.

This is common after installing:

• A controller wrapper
• A compatibility patch
• A mod
• A ReShade or graphics wrapper
• A fan-made update
• An incomplete game update
• A DLL copied from another installation

Microsoft describes this behavior in its DLL search order documentation.

Inspect the game directory

1. Close the game and its launcher.
2. Open the game’s installation folder.
3. Look for dinput.dll.
4. Also look for dinput8.dll, xinput1_3.dll, or other recently added wrapper files.
5. Check the file’s Date modified, Properties, and Digital Signatures tab when available.
6. Think back to whether the file appeared after a mod, wrapper, or compatibility change.

Do not delete the Windows copy from System32 or SysWOW64.

If a suspicious dinput.dll is in the game directory, make a backup of that specific file and temporarily rename it, for example:

dinput.dll.disabled

Do not rename files in Windows system directories. Launch the game again.

What the result means

• If the game starts after the app-local file is renamed, the game-folder DLL was incompatible, damaged, or no longer needed.
• If the game stops with a different missing-file message, the wrapper or mod may have been part of a larger installation.
• If nothing changes, restore the original filename and continue with game verification.
• If the file came from a mod author or publisher and is intentional, obtain the correct build for the game’s architecture from that source.

A dinput.dll beside a game executable may be a third-party wrapper rather than Microsoft’s Windows file. Its filename alone does not prove its identity.

Fix 4: Verify or repair the game installation

Use this fix when only one game fails and other DirectInput programs work.

Steam

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 complete the verification.
8. Restart Steam if it reports that files were replaced.
9. Launch the game again.

The process is also described by Steam Support.

Epic Games Store

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

Epic documents this process in its game verification support instructions.

Other launchers and conventional programs

Use the launcher’s repair, verify, or scan function if it provides one. For a conventional Windows program:

• On Windows 11, open Settings > Apps > Installed apps.
• Select the program’s menu.
• Select Advanced options when available.
• Select Repair.
• If Repair does not help, use Reset only if you understand that it may remove application settings.
• In Control Panel, open Programs > Programs and Features.
• Right-click the program and choose Repair or Change when offered.

If repair fails, uninstall and reinstall the game or program from its official launcher, publisher, or original installation media. This is the definitive fix when the application’s own files are damaged.

Fix 5: Install the correct legacy DirectX components

Do not assume that “DirectX is installed” means an old game has every DirectX file it needs.

Windows includes the core DirectX runtime, including the Windows DirectInput component. Microsoft’s legacy DirectX packages install optional side-by-side SDK files used by older games. They do not replace the Windows-serviced core dinput.dll.

Use the official DirectX End-User Runtime Web Installer when the error names files such as:

• dinput8.dll
• xinput1_3.dll
• d3dx9_*.dll
• xactengine*.dll
• Other legacy DirectX SDK components

The web installer is named dxwebsetup.exe.

For a game that includes its own official prerequisite folder, look for DXSETUP.exe and run that installer. Do not manually copy individual DLLs into System32.

Use the June 2010 offline package

If the web installer cannot complete or the game’s installer requires the offline package:

1. Download the official DirectX End-User Runtimes (June 2010).
2. The downloaded file is named directx_Jun2010_redist.exe.
3. Run it and extract the files to a temporary folder.
4. Open the extracted folder.
5. Run DXSETUP.exe as administrator.
6. Accept the license terms.
7. Let setup complete.
8. Restart Windows if requested.
9. Test the game again.

The June 2010 package installs legacy side-by-side components and does not change the installed Windows DirectX version. It is primarily relevant to older files such as D3DX, XInput 1.3, and XACT components. It is not a general replacement for a missing Windows dinput.dll.

Check DirectX with DxDiag

1. Open Start.
2. Type dxdiag.
3. Open DirectX Diagnostic Tool.
4. Select the System tab.
5. Review the DirectX information shown there.
6. Select Save All Information if you need to provide a diagnostic report to support.

Microsoft explains this process in its DirectX diagnostic guidance.

Do not use the DirectX version number alone to decide whether a legacy game has every optional runtime file. The exact missing filename is more useful.

Fix 6: Enable legacy Windows features only when the game requires them

Some old games need a Windows legacy feature such as DirectPlay. That is separate from repairing dinput.dll, but enabling it can resolve a different compatibility error in the same game.

Windows 11 or Windows 10

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

Do not enable unrelated features merely because a game is old. DirectPlay does not restore a missing dinput.dll, and it will not correct a damaged Windows system file or an incompatible app-local wrapper.

Fix 7: Check Windows Security quarantine

Antivirus software can quarantine a game file, a wrapper, or, less commonly, a Windows component after a detection or false positive.

1. Open Start.
2. Type Windows Security.
3. Open Windows Security.
4. Select Virus & threat protection.
5. Select Protection history.
6. Review recent actions involving the game or dinput.dll.
7. Expand an item to see its path and detection details.

If the quarantined file belongs to a trusted application:

• Repair or verify the application first.
• Confirm that the file came from the original publisher or a known-good installation.
• Restore only a known-good application file.
• Use Allow on device only after establishing that the detection is not valid.

Microsoft warns that allowing a threat can expose the device and explains the available Restore and Allow actions in its Protection history guidance.

Never restore a dinput.dll downloaded from a random DLL website. If the file is genuinely part of a game, reinstalling or verifying the game is safer than importing an unknown binary.

Fix 8: Check architecture and “Bad Image” errors

A missing-file message is not always caused by a file being absent. Windows can also reject a file that is damaged, built for the wrong architecture, or incompatible with the process loading it.

Common clues include:

• “Bad Image”
• Error 0xc000007b
• Failure only in a 32-bit game
• Failure after copying a DLL from another computer
• Failure after installing an x86 or x64 mod
• A file in the game directory taking precedence over the Windows copy

On 64-bit Windows:

• System32 contains the 64-bit Windows copy.
• SysWOW64 contains the 32-bit Windows copy.

Do not “fix” an architecture error by copying a 32-bit DLL into System32, or a 64-bit DLL into SysWOW64. Do not replace a Windows file with a DLL from another Windows installation.

The safe repair is to:

1. Remove or rename the incompatible app-local file.
2. Verify or reinstall the game.
3. Install the correct x86 or x64 build of any official wrapper or mod.
4. Run DISM and SFC if the Windows copy itself appears damaged.
5. Restart and test again.

If the error identifies a game-folder path, repair the game. If it identifies a Windows system path and affects multiple programs, repair Windows.

Fix 9: Repair controller drivers when the file exists

A controller driver problem is relevant when:

• The game starts but does not detect the controller.
• Buttons or axes do not respond.
• The controller appears in Windows but DirectInput initialization fails.
• dinput.dll is present and Windows system repair reports no corruption.

This is not the normal repair for a missing dinput.dll.

Reinstall the affected device

1. Right-click Start.
2. Select Device Manager.
3. Expand Human Interface Devices.
4. Also check Sound, video and game controllers.
5. Find the affected controller.
6. Right-click it.
7. Select Uninstall device.
8. Confirm the removal.
9. Restart Windows.
10. Reconnect the controller if necessary.
11. Test it in the game.

Windows will attempt to reinstall the device driver after the restart. Microsoft provides related Device Manager driver guidance.

Update the graphics driver separately if the game has display problems, crashes during rendering, or reports a graphics dependency. A graphics-driver update can address graphics compatibility, but it does not normally recreate a missing system dinput.dll.

When several devices or drivers need attention, manually identifying the correct hardware, package, and architecture can become tedious. Outbyte Driver Updater can scan for outdated drivers and identify available driver updates; installation is handled by the full version, and it is not required when the problem is a missing Windows DLL or a game-specific file.

Fix 10: Do not use regsvr32 as a generic DLL repair

Do not run this as a default fix:

regsvr32 dinput.dll

regsvr32 is intended for self-registering OLE and COM DLLs that expose the required registration entry points. It is not a universal command for installing, repairing, or loading every DLL.

Microsoft explains the intended use and common errors in its Regsvr32 documentation.

Some builds of dinput.dll may contain registration-related exports, but that does not make registration the answer to:

• A missing file
• A corrupted file
• A wrong-architecture binary
• A missing DirectInput export
• A damaged Windows component store
• A game-folder wrapper conflict
• A missing legacy DirectX side-by-side component

Use Windows servicing, application repair, or the original publisher-supplied installer instead.

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

Fix 11: Consider System Restore or a Windows repair installation

Use System Restore when the problem began after a specific system change and a restore point exists.

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

rstrui.exe

1. Press Enter.
2. Select a restore point from before the failure began.
3. Review the affected programs and drivers.
4. Start the restore.
5. Let Windows restart and complete the process.

System Restore rolls back system files, registry settings, and installed programs without removing personal files. Microsoft describes the process in its System Restore guidance.

If System Restore is unavailable or does not help, use a supported in-place Windows repair or Windows Recovery Environment path. This is appropriate when DISM and SFC cannot restore a protected file and the problem is clearly system-wide.

Back up important files before major recovery work. Do not replace system DLLs manually during recovery.

Why random DLL downloads are a bad repair

Do not download dinput.dll from a generic DLL download sites website and copy it into:

• %SystemRoot%\System32
• %SystemRoot%\SysWOW64
• A game folder

That approach can introduce:

• Malware or tampered code
• The wrong Windows build
• The wrong architecture
• A mismatched export set
• An unsigned or untrusted binary
• Permission and servicing problems
• A false appearance of success while the real problem remains

It can also overwrite a protected Windows component and make future Windows servicing harder.

Use these sources instead:

• Windows Update for Windows components
• DISM and SFC for protected system files
• The official game launcher for game files
• The game publisher’s installer or original media
• Microsoft’s official DirectX End-User Runtime for legacy side-by-side DirectX files
• A clearly identified, verifiable publisher or mod-author wrapper when an app-local DLL is intentionally required

A manually supplied DLL is appropriate only in the narrow case where a publisher or mod author explicitly provides an app-local wrapper, identifies the exact game directory, supplies the correct architecture, and provides a way to verify the file.

Match the symptom to the repair

Symptom	Most likely path	First repair
Several unrelated programs report dinput.dll missing	Windows component problem	Windows Update, DISM, then SFC
Only one old game fails	Damaged game files or app-local DLL	Verify game files and inspect the game directory
Error names dinput8.dll	Separate DirectInput 8 component	Repair the application or install its official prerequisites
Error names xinput1_3.dll	Legacy XInput side-by-side runtime	Install the official DirectX End-User Runtime
Error names d3dx9_*.dll	Legacy D3DX component	Run the official DirectX installer or the game’s DXSETUP.exe
“Bad Image” or 0xc000007b	Wrong architecture or damaged binary	Restore original files and verify architecture
Game starts but controller is missing	Device or controller configuration	Check Device Manager and reconnect the device
Failure began after a mod	App-local wrapper conflict	Disable the mod and verify the game
Failure began after antivirus action	Quarantined file	Review Protection history and repair the application
Program works under another Windows account	Per-user configuration or profile issue	Test with a new account

This table is a starting point, not a claim about exact failure percentages. There is no reliable public statistic establishing one universal root-cause frequency for dinput.dll errors.

Frequently asked questions

Does dinput.dll come with Windows?

Yes. The Microsoft DirectInput runtime is part of Windows. It is not normally supplied by Visual C++ or by one particular game.

An old game may still include a DirectX setup program because it needs optional legacy files such as D3DX, XInput 1.3, XAudio, XACT, or related components.

Will DirectX 12 fix dinput.dll?

Not necessarily. Windows includes current DirectX components, but old games may require optional side-by-side DirectX SDK files. The June 2010 DirectX package can help with files such as d3dx9_*.dll and xinput1_3.dll.

It is not normally the direct repair for a missing or corrupted Windows core dinput.dll. Use Windows Update, DISM, and SFC for that system-file problem.

Will Visual C++ Redistributable fix dinput.dll?

Usually no. Visual C++ packages are relevant when the error names files such as msvcp*.dll, msvcr*.dll, or vcruntime*.dll.

A standalone dinput.dll error points to DirectInput or an application-local file, not normally to Visual C++.

Microsoft maintains the current Visual C++ Redistributable downloads.

Should I copy dinput.dll into System32?

No. Do not download and copy an unknown DLL into System32. Use DISM and SFC to restore the protected Windows copy.

On 64-bit Windows, do not confuse System32 and SysWOW64. The correct location depends on the file architecture and the process using it.

Can I copy dinput.dll from another PC?

Do not copy a system DLL from another PC as a general repair. Windows builds, servicing levels, architectures, and file signatures can differ.

Use Windows repair tools, matching official installation media, or a supported repair source instead.

Why does only one game show the error?

The game may have damaged files, an incomplete update, or an app-local dinput.dll that overrides the Windows copy. A mod or compatibility wrapper may also be incompatible with the current game executable.

Verify the game files, inspect its installation directory, and temporarily disable recently installed wrappers or mods.

What if the file exists but the error remains?

Check the full path named by the error. Then check:

• Whether the file is in the game directory and overriding Windows
• Whether the file architecture matches the program
• Whether the error actually names dinput8.dll or another dependency
• Whether SFC reports corruption
• Whether antivirus quarantined a related file
• Whether the game installation is damaged

A file being present does not prove that it is the correct binary or that Windows is loading it.

Is dinput.dll a controller driver?

No. It is an API layer that programs use to access input devices. The physical controller still depends on its device driver and Windows device configuration.

If the file exists but the controller is not detected, inspect Device Manager and the controller connection rather than replacing dinput.dll.

Should I enable DirectPlay?

Only when the game specifically requires it or reports a related legacy Windows feature error. DirectPlay is separate from DirectInput and does not repair a missing dinput.dll.

Should I run regsvr32 dinput.dll?

Not as a generic repair. Registration is not the solution to a missing, damaged, wrong-architecture, or incorrectly loaded DLL. Use Windows servicing or application repair.

What should I tell support?

Provide:

• The exact error text
• The exact filename named in the message
• The full path shown, if any
• The affected program and launcher
• Whether one program or several fail
• Whether the problem began after an update, mod, antivirus action, or driver change
• Whether the program is 32-bit or 64-bit
• The results of DISM and SFC
• Whether a same-named DLL exists in the application folder

That information usually identifies whether the repair belongs to Windows, the game, a legacy DirectX package, a controller driver, or an app-local wrapper.

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.