If DS5Windows or DualSenseX keeps crashing on Windows 11, the cause may be a damaged installation, an application setting, a missing runtime, or a conflict with other controller software. The right fix depends on when the crash happens.
For example, an app that closes immediately after launch needs a different approach from one that crashes only after connecting a DualSense controller or switching profiles.
Before reinstalling drivers or changing Windows security settings, work through the checks below in order.
1. Identify When DSX Crashes
Start by narrowing down the problem.
- DSX closes immediately after launch: Check the installation, any error message, and the required runtime.
- DSX crashes when you click Start: Check the application version, controller connection, and other controller software.
- DSX crashes when you change a profile: Investigate the profile or application settings.
- DSX crashes only after connecting a controller: Test USB and Bluetooth separately and close other controller utilities.
- DSX stopped working after an update: Verify the application files and check whether the update changed the software or driver setup.
If Windows displays an error message, write down the exact wording. A .NET runtime error, a missing DLL message, and a controller-driver problem are different issues and should not be treated as interchangeable.
2. Restart DSX and Check for Conflicting Software
Before changing drivers, close DSX and other programs that may be managing the same controller.
These may include DS4Windows, other controller remappers, or applications that create virtual gamepads.
Then:
- Disconnect the DualSense controller.
- Close DSX and other controller-mapping applications.
- Restart Windows.
- Open DSX by itself.
- Check whether it crashes before reconnecting the controller.
- If it remains open, reconnect the controller and test again.
If DSX works until another controller application starts, the conflict may be related to overlapping input handling rather than a damaged DSX installation.
You do not need to uninstall every controller utility immediately. First establish whether another application is involved.
3. Verify the DSX Installation Through Steam
If you use the current Steam version of DSX, verify its installed files before manually deleting folders or reinstalling drivers.
- Open Steam.
- Go to your Library.
- Right-click DSX.
- Open Properties.
- Find the installed-files section.
- Select Verify integrity of game files, if available.
- Allow Steam to finish checking the installation.
- Launch DSX again.
Steam can check its managed installation and replace missing or damaged files when needed.
This is a sensible early step if DSX started crashing after an update or if some application files may be damaged.
Important: This procedure applies to the Steam installation. If you are using the older GitHub release, its files and troubleshooting steps may be different.
4. Check Whether a .NET Runtime Error Is Actually Present
Some Windows applications depend on a specific Microsoft .NET runtime. However, you should not assume that every DSX crash is caused by .NET or that every installation needs the same runtime version.
If Windows displays a .NET error when DSX starts, note the runtime version or missing component mentioned in the message.
Then:
- Check the runtime requirement for your specific DSX version.
- Open Microsoft’s official .NET download page.
- Download the runtime that matches the application’s requirement.
- Choose the Desktop Runtime when the application specifically requires it, rather than downloading the SDK by mistake.
- Select the appropriate architecture, usually x64 for a typical 64-bit Windows installation.
- Install or repair the runtime if Microsoft’s installer offers that option.
- Restart Windows and try launching DSX again.
Official download page: Microsoft .NET downloads.
Do not install .NET 8 simply because an older guide recommends it. The required version depends on the application build. If the error names a different version, follow that specific requirement.
If DSX crashes without a runtime error, verify the application files and test the controller connection before assuming .NET is responsible.
5. Test Whether a Profile or Setting Is Causing the Crash
If DSX launches normally but crashes when you edit a profile, change a setting, or connect a controller, an application setting or profile may be involved.
Start with the least destructive option:
- Open DSX if it stays open long enough.
- Look for a built-in option to reset the relevant setting or application configuration.
- If the problem is limited to one profile, test another profile if the application allows it.
- Restart DSX and check whether the crash returns.
If DSX closes before you can change anything, check the documentation for your exact version to identify where it stores its settings.
Do not assume that every DSX installation uses C:\Temp\DualSenseX\ or an AppData folder. Paths can differ between versions and installation methods.
If you locate a configuration file that may be damaged, close DSX and make a backup before renaming or moving it. Avoid deleting the entire application folder, because it may contain settings or other data you want to keep.
A clean configuration can help diagnose a settings-related problem, but it is not a guaranteed fix for every crash.
6. Check ViGEmBus Only If Your Setup Uses It
ViGEmBus is associated with virtual gamepad emulation in older controller-mapping setups. It is not a universal requirement for every current Steam DSX installation or every game that uses a DualSense controller.
The ViGEmBus project has been retired, and its repository is archived. That status alone does not prove that ViGEmBus is causing your crash or that you need to replace it immediately.
Official project: ViGEmBus on GitHub.
If you use an older DSX setup that relies on ViGEmBus and suspect the installation is damaged:
- Confirm that your version actually uses ViGEmBus.
- Check whether Windows or DSX reports a specific virtual-controller error.
- Review the relevant driver instructions before removing anything.
- If reinstalling is appropriate, use the official project information and restart Windows when instructed.
- Test the controller again before making additional changes.
Do not uninstall ViGEmBus simply because DSX crashes. Removing a virtual-controller component can stop an existing emulation setup from working, and it may not address the real cause.
For more information about the project’s retirement, see the ViGEm End-of-Life notice.
7. Test USB and Bluetooth Separately
A crash that happens only when a controller connects may involve the connection method, the controller itself, or another application trying to access it.
Try a USB connection first:
- Close DSX.
- Disconnect the controller.
- Connect it using a USB-C cable that supports data transfer.
- Launch DSX and check whether it stays open.
- If it works, test Bluetooth separately.
If the problem happens only over Bluetooth, remove and pair the controller again through Windows Bluetooth settings. You can also check whether other Bluetooth devices are working normally.
If DSX crashes with both USB and Bluetooth, look beyond the connection method. Check the application files, error messages, and other controller software.
For more connection help, see our Controller Troubleshooting Guide.
8. Avoid Running DSX as Administrator Unless There Is a Specific Reason
Running an application as administrator is sometimes suggested as a general fix for controller problems. It should not be the first step for every DSX crash.
Start by checking the application files, the exact error message, and whether the problem occurs without the controller connected.
If you have evidence of a specific permissions issue, you can test elevated permissions temporarily. Use administrator mode only when necessary, and avoid making it a permanent setting without understanding why it is required.
A crash caused by damaged files, an incompatible runtime, or a profile issue will not necessarily be fixed by running DSX with elevated privileges.
9. Check Windows Event Viewer for More Details
If DSX closes without showing a useful error message, Windows Event Viewer may contain additional information.
- Press Win + R.
- Type
eventvwr.mscand press Enter. - Open Windows Logs → Application.
- Look for an error recorded at the time DSX crashed.
- Check the faulting application, faulting module, and any exception information shown.
The details may help distinguish an application crash from a runtime or module error. However, a faulting module name by itself does not always identify the root cause.
If you need help diagnosing the problem, record the error details and your DSX version before changing more settings.
10. Why Windows 11 May Seem to Be Involved
If DSX worked on Windows 10 but began crashing after an upgrade to Windows 11, the timing is worth investigating. It does not automatically mean Windows 11 security features are responsible.
An upgrade can coincide with changes to drivers, runtimes, Bluetooth behavior, application files, or other software. The crash could also be caused by a DSX update or a change in the controller setup.
Instead of disabling Windows security features or reinstalling every driver, identify what changed and test the simplest working configuration first.
If the problem started immediately after a particular update, record the update and error details. This information is more useful than assuming that Windows 11’s security settings are the cause.
11. When Should You Reinstall DSX?
Consider reinstalling the application if:
- Steam’s file verification does not resolve the problem.
- DSX continues crashing on launch.
- The installation appears damaged.
- The same crash occurs after checking the relevant runtime and configuration.
Before reinstalling, make a backup of any profiles or settings you want to keep, where applicable.
If you use the Steam version, manage the application through Steam. If you use the older GitHub build, remember that it is a separate, discontinued version with different installation details.
Do not automatically remove ViGEmBus, HidHide, or other driver components during a DSX reinstall. First confirm which components your setup uses and whether they are related to the crash.
12. How to Reduce the Chance of Future Crashes
Once DSX is working again, a few habits can make future troubleshooting easier:
- Keep track of which DSX version you use.
- Avoid running multiple controller-mapping applications simultaneously unless your setup specifically requires them.
- Back up profiles before resetting settings.
- Use the official distribution channel for your version.
- Install only the runtimes and drivers that your setup actually requires.
- Record error messages instead of relying on vague descriptions such as “DSX stopped working.”
- After a major update, test DSX and your controller before changing additional settings.
These steps will not prevent every crash, but they make it easier to identify what changed if a problem returns.
Frequently Asked Questions
Why does DSX close immediately after I open it?
Possible causes include damaged application files, a missing runtime required by that version, or a problem with the current configuration. Start by verifying the Steam installation and checking any Windows error message.
Do I need to install .NET 8 to fix every DSX crash?
No. Install or repair a .NET runtime when the error or the requirements for your specific application version indicate that it is needed. The correct version should not be guessed.
Should I reinstall ViGEmBus when DSX crashes?
Not automatically. ViGEmBus is relevant to older virtual-controller configurations, but it is not a universal dependency for every current DSX setup. Check whether your installation uses it and whether the error points to that component.
Can I delete the DSX configuration folder?
Do not delete a folder based on a path from an unrelated guide. First confirm the settings location for your version, close DSX, and back up the relevant files before making changes.
Is Windows 11 the reason DSX keeps crashing?
Not necessarily. Windows 11 may be part of the circumstances, particularly after an upgrade, but the crash could also involve application files, runtimes, configuration, drivers, or other controller software.
What information should I collect if DSX still crashes?
Record your Windows version, DSX version, the action that triggers the crash, whether USB and Bluetooth behave differently, and the exact error message. Event Viewer may provide additional details if no message appears on screen.
Still Having Problems?
If DSX continues crashing, start with our Troubleshooting Guide for controller detection, connection, and duplicate-input problems. Our Drivers Guide explains the role of supporting components and why requirements differ between older and current setups.
The main rule is simple: identify when the crash happens, check the evidence, and change one thing at a time. Reinstalling every driver or disabling Windows security without a clear reason can create additional problems without fixing the original one.