DS4Windows Not Opening, Failing to Start, or Not Saving Settings Issue
If DS4Windows is not opening, not launching, crashing soon after launch, or failing to start, and it also fails to save settings, stick to this page. Read from the top to the bottom and keep checking all the steps until, at the end of this guide, you are done solving your problem.
Fix 1 – Check That All Prerequisite Are Installed
To use your DualShock 4 and DualSense 5 on Windows 10/11, you have to install required drivers. Some are basic for controller detection, while others are optional for advanced features like lighting, vibration, and advanced input support.
DS4Windows will prompt you to install them automatically when you first launch the app. Follow the on-screen steps for setup!
DS4 Drivers
Virtual Gamepad Emulation Bus – ViGEmBus (Required)
The ViGEmBus Driver lets DS4Windows pretend your PlayStation controller is an Xbox or another PlayStation controller. This helps PC games recognize it properly, even if they don’t natively support PlayStation controllers.
If you have not installed this, your system will show an error message: “ViGEmBus Is Not Installed.” If you have installed it but the system is still showing the log message, uninstall this driver, restart your PC, and install it again.
The ViGEmBus driver may ask you to install Visual C++ 2017 runtime libraries. Make sure to install these too if prompted.
FakerInput (Optional)
FakerInput is like an invisible helper that lets DS4Windows trick stubborn games (like Valorant) into accepting keyboard/mouse inputs from your controller. You can even play games with strict anti-cheat systems that block controller commands.
HidHide (Optional)
The HidHide driver is used to hide your real controller to avoid double-input issues.
Microsoft 360 Driver
This is another driver that you need to install and configure to work with the DS4Windows tool. If you have already installed it to run an Xbox 360 controller, then there is no need to install it again.
Additional Requirements
Fix 2 – Make Sure That The DS4Windows Folder Is not write-protected
Write-protected files or programs are set to avoid accidental or intentional changes. If DS4Windows is in a write-protected folder like Program Files, the app can’t save profiles, settings, or updates unless you run it as an administrator. So, we advise you to move it to a normal folder like Documents to remove this restriction, so it works smoothly.
Here’s how to check if your DS4Windows folder is write-protected and fix it easily.
Check Where DS4Windows is Installed
Move the Folder (If Needed)
Avoid “C Drive” as a Main Location
Check Folder Permissions (Optional):
Run as Admin (Temporary Fix)
Fix 3 – Make Sure That The User Data Is Not Corrupted
When the tool’s user data gets corrupted, such as when it is damaged or altered in a way that the software cannot read, it causes errors. We can fix this by isolating the corrupted file, starting fresh, and testing each file individually.
This method acts like a detective. It systematically identifies the single corrupted file hiding among our data, restoring the software to work smoothly again once the troublemaker is removed.
Here’s how it helps:
Close the Software:
Stops the tool from actively using or locking the data files. This could worsen the corruption or hide the issue.
Backup First:
Backup is a precautionary step to prevent you from losing your data permanently if something goes wrong during the process.
Delete and Relaunch:
When we remove the original files, the software is forced to generate new, clean default files when restarted. This resets the environment, eliminating hidden conflicts or widespread corruption.
Restore Files One by One:
By adding back your old data files individually, you will test each file’s compatibility. The moment the tool fails again, you will find the corrupted file. Delete it to remove the bad data and keep the rest of your data safe.
Fix 4 – Inspect DS4Windows’ Log and Windows’ Event Viewer
DS4Windows relies on Windows tools like WMI, a built-in tool in DS4Windows, to communicate/talk with your controller. If WMI gets glitchy or corrupted, this communication breaks, and DS4Windows starts to malfunction.
All such issues are recorded in the log file of DS4Windows. The log file acts like a diary. It records problems so you know exactly what to fix. We can remove such glitches by resetting WMI and letting DS4Windows work smoothly again.
It’s like fixing a broken walkie-talkie so DS4Windows can talk to your controller properly.
Here’s how to do all the steps.
Find the Log Files
If both logs exist, check the one with the latest date.
Open the Log File
Reset Windows Management Instrumentation Tool (WMI):
If the error persists, use Windows installation media, like a USB or DVD with Windows setup, to repair your Windows installation.
Fix 5 – Check for Incompatible Applications
Some apps like MSI Afterburner or RivaTuner clash with DS4Windows (version 2.0+). These apps behave overly protective, and their detection feature takes DS4Windows as a program they need to control or block. As a result, both apps block DS4Win from starting properly or force it to crash.
We can fix this by disabling RivaTuner’s detection setting or uninstalling it to stop the interference.
Fix 6 – Uninstall Legacy ScpVBus Driver (If Installed)
The SCP Virtual Bus is an old driver used earlier to create virtual Xbox controllers. Now, it has been replaced by the ViGEmBus Driver, which is newer and better.
DS4Windows no longer needs ScpVBus, so if you have installed this, DS4 will ignore it. However, if you have both ScpVBus and ViGEmBus installed, they can cause problems and errors.
To avoid these issues, it’s best to uninstall the ScpVBus Driver (ScpToolkit) completely from your computer.
Fix 7 – Update Windows Operating System
