The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →jabo_dinput.dll errors usually appear when Project64 cannot find or load its controller input plugin. You may see messages such as:
- “failed to load: …jabo_DInput.dll”
- “failed to load plugin… jabo_dinput.dll”
- “the default or selected input plugin is missing or invalid”
- “jabo_dinput.dll is missing”
- “jabo_dinput.dll was not found”
- “Cannot find jabo_dinput.dll”
- “This application failed to start because jabo_dinput.dll was not found”
The 60-second answer
Do not download this DLL from a random file site, copy it into System32, or run regsvr32 against it.
As an Amazon Associate I earn from qualifying purchases.
Close Project64, reinstall the complete matching Project64 package from the official Project64 downloads page, and keep the emulator executable and its plugin folder together. If the file was quarantined, verify the package before restoring it. If the DLL exists but still will not load, check for an incompatible plugin, missing dependency, or damaged Project64 installation.
Free tools Windows power users keep installed
One-click scans. No signup required.
What is jabo_dinput.dll?
jabo_dinput.dll is Jabo’s DirectInput Plugin for Project64, a Nintendo 64 emulator for Windows. It is a third-party application DLL used by Project64’s plugin system to handle controller input.
#1 Best Overall
- Use the generic standard USB port, if your program or application accepts USB controller input, it can be used natively without drivers or patches, JUST PLUG AND PLAY!
- Supported Operating system: Windows 98, ME, Vista, 2000, 2003, XP, 7, 8, 8.1, 10; Linux UBUNTU, Linux Mint, Android Linux (via an USB OTG cable); Mac OS X and beyond; Retrogaming operating systems: RetroPie, Recalbox, Happi Game Center, Lakka, ChameleonPi, Piplay.
- Supported Device (With USB storage device): PC, Notebook Computer, Laptop Computer; Android Smartphone: connect via an USB OTG cable; Raspberry Pi (RPI, Raspberry pie): Raspberry Pi 1 Model B, Model A, Raspberry Pi 1 Model B+, Raspberry Pi Zero, Raspberry Pi 2, Raspberry Pi 3 Model B, Raspberry Pi 3, Retro Pie. --- Note: NOT SUPPORT Android TV BOX.
- Supported Game Emulators: Current: Project64, 1964, MAME (MESS), Mupen64Plus, Sixtyforce, CEN64; Historical: Project Unreality, Corn, UltraHLE, Nemu64.
- Super sensitive buttons for precision control. Third party controller, not original Nintendo 64 controller. But it works phenomenal with the Raspberry Pi game emulation and so on. Cord is approx 5.9 ft. Long.
It is not:
- A Windows system component
- A core DirectX system DLL
- A general-purpose controller driver
- A file that belongs in
C:WindowsSystem32 - A DLL that normally needs registration with Windows
Older Project64 installations commonly stored it in a folder resembling:
C:Program FilesProject64 1.6plugin
Your installation may use a different location. Newer Project64 releases may also use a different input plugin or folder layout.
Public file metadata identifies this DLL as a Win32 or x86 file. That means it belongs with a compatible 32-bit Project64 installation. A 64-bit version of Windows can run a 32-bit application, but Windows’ 32-bit compatibility does not mean you should manually place the plugin in System32 or SysWOW64.
What the error usually means
| Message or symptom | Most likely explanation |
|---|---|
| DLL is missing or not found | The file or plugin folder was deleted, moved, or never extracted |
| Default input plugin is missing or invalid | Project64 points to a plugin that is absent or incompatible |
| Failed to load while the file exists | A dependency is missing, the DLL is blocked, or the build is incompatible |
| Procedure entry point was not found | The wrong plugin version or an incompatible DLL was selected |
| Specified module could not be found | The named DLL or one of its dependencies cannot be loaded |
| Error began after antivirus activity | Windows Security may have quarantined the plugin |
| Error began after moving Project64.exe | Relative paths to the plugin folder may have broken |
Fix 1: Reinstall the complete Project64 package
This is the safest and most likely solution.
Step 1: Close Project64
- Close Project64.
- Press
Ctrl+Shift+Esc. - In Task Manager, look for
Project64.exe. - If it is still running, select it and choose End task.
Step 2: Back up saves and settings
Before removing anything, search for your Project64 save files and copy them to another folder.
Look for files with extensions such as:
.n64
.z64
.v64
.sra
.fla
.eep
The exact location depends on the Project64 version and its configuration. Also back up configuration files if you have customized controller mappings or emulator settings.
Step 3: Remove the damaged installation
Use the normal Windows uninstall screen:
- Press
Windows+I. - Select Apps.
- Choose Installed apps on Windows 11, or Apps & features on Windows 10.
- Search for Project64.
- Select the three-dot menu or the program entry.
- Choose Uninstall.
- Follow the uninstall wizard.
If Project64 is a portable or ZIP-based installation and does not appear in the list, close it and move the old installation folder aside instead of immediately deleting it.
Step 4: Obtain the complete official package
Use the official Project64 Windows downloads page. Download the release intended for Windows and avoid repackaged emulator bundles.
If the package is a ZIP archive:
- Right-click the archive.
- Choose Extract All.
- Extract the entire folder.
- Do not run only
Project64.exefrom inside the archive. - Preserve the included subfolders, including any
plugindirectory.
If the package is an installer, allow it to install the complete application rather than copying a single executable from another computer.
Step 5: Start Project64 and check the plugin
- Open the newly installed Project64 folder.
- Right-click
Project64.exe. - Choose Run as administrator for the first test.
- Open the emulator’s settings or plugin configuration screen.
- Open the input-plugin selection menu.
- Select an installed compatible input plugin.
- Apply the setting and restart Project64 normally.
A successful repair is indicated by Project64 opening without the missing-plugin message and displaying an available input plugin. Test a controller only after the emulator starts cleanly.
Rank #2
- Plug & Play: Standard USB controller; no drivers needed for compatible devices
- Compatible with Windows PC, macOS, Linux and Raspberry Pi
- Iconic original M-shaped configuration, featuring 10 action buttons, a precision analog Control Stick, and an 8-way D-pad.
- The 3D analog stick provides nuanced control for precise movements and enhanced gameplay comfort.
- Features a 6-foot (1.8 m) cable for comfortable gameplay.
Fix 2: Check whether antivirus quarantined the file
Older emulator plugins can attract antivirus attention because they are uncommon, old, unsigned, or packaged in unusual ways. Do not disable antivirus protection just to force the DLL back into place.
Windows Security steps
- Open the Start menu.
- Type Windows Security.
- Open it.
- Select Virus & threat protection.
- Choose Protection history.
- Review entries related to Project64 or
jabo_dinput.dll. - Expand the detection and inspect the original file path.
If the file came from the official Project64 package and the path is inside that installation, verify the installer or archive source before taking action. If the file appeared in a temporary folder, a download folder, or an unrelated application directory, do not restore it automatically.
Recommended Free Tools
If you restore a verified file:
- Select the relevant Protection History entry.
- Choose Actions.
- Select Allow on device or Restore, if Windows offers that option.
- Reinstall the complete Project64 package afterward if the plugin remains absent.
- Run a full scan from Virus & threat protection.
The filename alone does not prove that a file is safe or malicious. Provenance, location, and the package it came from matter.
Fix 3: Confirm the plugin path and file location
Project64 normally loads input plugins from its own configured plugin directory. It does not search the entire computer for a suitable copy.
Find the Project64 installation
- Right-click the Project64 shortcut.
- Select Properties.
- Open the Shortcut tab.
- Read the Start in field or choose Open File Location.
- Look for a folder named
plugin,Plugins, or a similar application subfolder.
A legacy installation may look like this:
C:Program FilesProject64 1.6plugin
The spelling and capitalization may differ.
Check the file
- Open the plugin directory.
- Search for
jabo_dinput.dll. - If File Explorer hides extensions, select View → Show → File name extensions.
- Confirm that the file has not been renamed to
jabo_dinput.dll.dll. - Right-click the file and select Properties.
- If an Unblock checkbox appears on the General tab, review the file’s origin before selecting it.
- Click Apply, then OK.
If the file is absent, restore it through the complete Project64 installer or archive. Do not use a random DLL download as a replacement.
If the file is present in another Project64 folder, do not copy it blindly. First check whether that copy belongs to the same Project64 release and architecture.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Fix 4: Select another compatible input plugin
The Jabo plugin is associated with older Project64 installations. A current Project64 release may use a different supported input plugin, and restoring this legacy DLL may not be the correct long-term solution.
- Open Project64.
- Select Options.
- Open Settings or the plugin configuration screen.
- Find the Input or Controller plugin list.
- Select a plugin that is already installed and listed as compatible.
- Apply the change.
- Restart Project64.
- Open the controller configuration and map the buttons again.
If the list is empty, reinstall the complete Project64 package. If the list contains a plugin but Project64 reports that it is invalid, do not mix DLLs from unrelated emulator builds.
Fix 5: Check for a missing dependency
Windows can report that a requested module is missing even when jabo_dinput.dll is visibly present. In that situation, another library required by the plugin may be absent.
Rank #3
- Wireless controller fully compatible with Switch 1 / Switch 2 and N64 console
- Lag-Free 2.4 GHz wireless, 10m/33ft range, no delay, plug & play
- Built-in rumble vibration for immersive gameplay. No Extra Rumble Pak Required
- Built-in rechargeable battery, 10-hour runtime
- The 3D analog stick provides nuanced control for precise movements and enhanced gameplay comfort.
Start with these steps:
- Reinstall Project64 from its official package.
- Restart Windows.
- Start Project64 again.
- If the error remains, note the exact wording.
- Check the plugin’s original documentation or the package’s included readme for runtime requirements.
DirectX considerations
jabo_dinput.dll is a DirectInput controller plugin, but it is not itself a Windows DirectX system DLL. Windows provides the core DirectInput functionality. Installing a modern graphics driver or copying a DirectX DLL from another computer is not a reliable repair.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesSome older software needs legacy side-by-side DirectX components. Microsoft provides the DirectX End-User Runtime Web Installer for that purpose. Install it only from Microsoft, restart Windows, and test Project64 again.
This runtime does not replace Windows’ core DirectInput subsystem, and there is no verified basis for treating it as the universal fix for every Jabo plugin build.
Visual C++ considerations
Some older Project64 plugins document a dependency on the Microsoft Visual C++ 2010 SP1 Redistributable x86 package. That documentation applies to those plugins and does not prove that every historical Jabo build requires the same runtime.
If Project64 or its plugin documentation identifies a Visual C++ dependency:
- Use Microsoft’s Visual C++ redistributable documentation to identify the appropriate package.
- Match the architecture to the application.
- Install the x86 package when the affected Project64 build is 32-bit.
- Restart Windows.
- Test Project64 again.
Do not install every Visual C++ package at random. Installing both x86 and x64 packages is not automatically necessary.
Fix 6: Repair Windows components only when other programs are affected
If only Project64 reports the problem, Windows system corruption is less likely. System File Checker does not normally restore a third-party emulator plugin.
Use Windows repair commands when several unrelated applications report damaged or missing Windows components.
Run DISM first
- Open Start.
- Type Command Prompt.
- Right-click it.
- Select Run as administrator.
- Run:
DISM.exe /Online /Cleanup-Image /RestoreHealth
- Wait for the operation to finish.
- Restart Windows.
Run SFC second
Open an elevated Command Prompt again and run:
sfc /scannow
Wait until verification reaches 100 percent, then restart Windows and test Project64.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteRank #4
- 🎮[Compatible ]Compatible with the original N64 system console, wired controller for enjoying old school Online N64 video games, perfectly for Mario Kart 64, Zelda n64, Mario party, Perfect Dark, Super Mario 64, ocarina of time 64,Super Smash Bros and many other N64 games.(Not for Windows PC Games)
- 🎮[Ergonomic Design]Tight and accurate analog control, the controller features 10 function buttons (including Left and Right shoulder functions and Z-trigger). Based on ergonomic and designed to fit your hands nicely, easier to grip than other controllers. It is a great replacement for old original N64 controller you have.
- 🎮[Rumble Pak & Memory Card ]: Compatible with most of game memory cards. you can use a memory card and transfer the game memory card save data. Upgraded 3D analog control stick commands your action with precision, perfectly compatible with N64 System console.
- 🎮[N64 Wired connection]The cord is approx. 1.7 meters (6ft), including a push-on N64 connector and easy to use. Use a N64 Controller Extension Cord Cables, you can play across the room. The joystick is removeable and replaceable.
- 🎮Third party controller, not original N64 controller(non-USB edition). The best gift for your families or friends, that will bring back those childhood memories when you are playing these classic N64 games.
If Windows reports that it repaired corrupted files, check whether other system problems have also improved. If SFC finds no problems, reinstall Project64 rather than repeating the command.
When you are hunting through Windows repair logs and repeating SFC or DISM without knowing what changed, Outbyte PC Repair can provide a scan that shows reported issues; repair actions are performed by the full version. It is optional, and reinstalling Project64 remains the definitive fix for this application-specific DLL.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Fix 7: Update or reinstall controller drivers
A controller that is not detected is different from a missing jabo_dinput.dll, but driver problems can appear at the same time.
Check Device Manager
- Press
Windows+X. - Select Device Manager.
- Expand Human Interface Devices.
- Expand Sound, video and game controllers.
- Expand Universal Serial Bus controllers.
- Look for a warning icon or an unrecognized device.
- Right-click the affected device.
- Choose Update driver.
- Select Search automatically for drivers.
If the device remains broken:
- Right-click it again.
- Choose Uninstall device.
- Disconnect the controller.
- Restart Windows.
- Reconnect the controller.
- Install the driver supplied by the controller manufacturer, if one is required.
Updating a controller driver will not recreate a missing Project64 plugin. It is relevant only when Project64 opens but cannot see or use the controller.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
If you are tired of hunting through Device Manager and guessing which of several drivers is stale, Outbyte Driver Updater can scan and identify reported driver issues; driver installation is performed by the full version. It is optional, and the correct Project64 package is still the definitive repair for jabo_dinput.dll.
Do not use regsvr32 for this plugin
regsvr32 is intended for DLLs that support Windows self-registration, commonly through COM or ActiveX registration. Project64 input plugins are normally loaded by the emulator through their plugin interface.
Running:
regsvr32 jabo_dinput.dll
will usually produce an error or change nothing. It does not place the plugin in Project64’s input list, repair a missing dependency, or configure the emulator.
Do not copy the file into either of these folders:
C:WindowsSystem32
C:WindowsSysWOW64
Those folders are for Windows and installed system components. Mixing an emulator plugin into them can create search-order problems and makes later troubleshooting harder.
If Project64 still will not load the DLL
Work through this final checklist:
- Confirm Project64 and its plugin folders are in the same installation tree.
- Confirm the configured input-plugin path points to that tree.
- Remove duplicate or randomly downloaded copies from other folders.
- Reinstall the complete official Project64 package.
- Try an installed replacement input plugin.
- Check Windows Security Protection History.
- Install only documented x86 dependencies for a 32-bit Project64 build.
- Check the exact error wording for a dependency or entry-point failure.
- Restore your saves and settings only after the clean installation starts correctly.
If the error began immediately after moving the emulator, move the complete installation folder back together rather than moving only Project64.exe.
System Restore is reasonable only when the file disappeared after a specific recent system change and reinstalling the application is not available. It should not be the first response to a missing third-party plugin.
Frequently asked questions
Is jabo_dinput.dll part of Windows?
No. It is Jabo’s DirectInput Plugin for Project64, supplied with or associated with an emulator installation.
Best Value
- Wireless controller fully compatible with Switch 1 / Switch 2 and N64 console
- Lag-Free 2.4 GHz wireless, 10m/33ft range, no delay, plug & play
- Built-in rumble vibration for immersive gameplay. No Extra Rumble Pak Required
- Built-in rechargeable battery, 10-hour runtime
- The 3D analog stick provides nuanced control for precise movements and enhanced gameplay comfort.
Is it a DirectX system DLL?
No. The plugin uses Windows controller APIs, but the file itself is an emulator plugin rather than a core DirectX component.
Is jabo_dinput.dll 32-bit or 64-bit?
Public metadata identifies it as Win32 or x86. Use it only with a compatible Project64 build. A 64-bit Windows computer can run a 32-bit emulator, but that does not justify copying the DLL into Windows system folders.
Should I download the DLL separately?
Generally no. A standalone download may be the wrong build, wrong architecture, incomplete, modified, or bundled with unwanted software. Restore the file from the matching official Project64 package instead.
Why does Windows say the module is missing when the file exists?
The missing module may be a dependency rather than jabo_dinput.dll itself. It can also indicate that the DLL is incompatible, blocked, or being loaded from the wrong directory.
Can DirectX fix the error?
Only if a legacy DirectX side-by-side component is the actual missing dependency. Installing DirectX is not a universal repair for this plugin.
Can Visual C++ fix it?
Possibly, if the particular Project64 plugin build requires a Visual C++ runtime. Install only the architecture and package identified by the application or plugin documentation.
Will SFC restore jabo_dinput.dll?
Normally no. SFC and DISM repair Windows components. They do not generally restore third-party Project64 files.
Is the DLL malware?
The name alone cannot answer that. Treat a copy found outside the Project64 installation with caution, inspect its source, review antivirus details, and replace it with a verified copy from the complete official emulator package.
Quick Recap
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.
