You launch DSX, and Windows displays a message such as “You must install .NET Desktop Runtime to run this application.” You install .NET, try again, and the same message appears.
This error usually means the application cannot find the runtime it needs. The cause may be a missing runtime, the wrong version or architecture, or an installation problem.
The important part is to check the exact runtime requested by the error before downloading anything. Different DSX versions may have different requirements, so do not assume every installation needs .NET 8.
Why Does DSX Ask for the .NET Desktop Runtime?
Some Windows applications are built on Microsoft’s .NET platform. They need the appropriate runtime installed to launch.
Several downloads on Microsoft’s website contain the words “.NET Runtime,” but they do different jobs:
- .NET Desktop Runtime: Runs supported Windows desktop applications that use desktop frameworks such as Windows Forms or WPF.
- .NET Runtime: Provides components for running certain .NET applications but does not include all desktop-specific components.
- ASP.NET Core Runtime: Runs supported web applications and services.
- .NET SDK: Includes tools for developers who build .NET applications.
Installing the SDK or ASP.NET Core Runtime alone may not resolve an application that specifically requires the Desktop Runtime.
Step 1: Check the Exact Error Message
Before installing anything, read the complete message displayed by Windows.
Look for details such as:
- The requested .NET version
- Whether it says .NET Desktop Runtime
- The application name or executable
- Any information about the required architecture
If the error explicitly requests .NET 8, follow the .NET 8 instructions below. If it requests another version, install the appropriate Desktop Runtime for that version instead.
Do not install multiple versions simply to see which one works.
Step 2: Download the Correct Desktop Runtime
Use Microsoft’s official download page:
If the error requests .NET 8, you can also go directly to the official .NET 8 download page.
Find the section labelled .NET Desktop Runtime and select the Windows installer matching your system and the application’s architecture.
Common Windows options include:
- x64: For compatible 64-bit Intel or AMD applications and systems.
- x86: For compatible 32-bit applications.
- Arm64: For compatible applications running on Windows on ARM.
Do not automatically choose x64 just because Windows is installed on a 64-bit computer. The required architecture can depend on the application itself.
Download the installer directly from Microsoft rather than using a third-party download site.
Step 3: Install the Runtime
Once you have downloaded the correct installer:
- Close DSX if it is running.
- Open the downloaded installer.
- Follow the installation prompts.
- Wait for the installer to finish.
- Restart Windows if the installer requests it.
- Open DSX and check whether the error has disappeared.
You normally do not need to uninstall other .NET versions first. Different .NET major versions can coexist on Windows, and removing a runtime may break another application that depends on it.
Only investigate a damaged installation or remove a component when you have a specific reason to do so.
Step 4: Check Which .NET Runtimes Are Installed
If the error persists, check whether the requested runtime is actually present.
Open Command Prompt and run:
dotnet --list-runtimes
This command lists the .NET runtimes visible to the installed dotnet host. If the command is not recognized, that does not by itself prove the Desktop Runtime is missing.
For a .NET 8 desktop application, look for an entry similar to:
Microsoft.WindowsDesktop.App 8.0.x
The exact patch number may differ.
If the required entry is missing, install the appropriate Desktop Runtime from Microsoft.
If it is present but DSX still displays the error, check the application’s architecture, requested version, and installation integrity instead of repeatedly reinstalling the same runtime.
Step 5: If DSX Is Installed Through Steam
The current Steam version of DSX and the older GitHub release should not be treated as identical applications. Their dependencies and installation processes can differ.
If you use the Steam version:
- Close DSX.
- Check the exact runtime version in the error message.
- Install the matching Desktop Runtime from Microsoft if it is missing.
- Restart Windows if needed.
- Try launching DSX again.
- If the error continues, use Steam’s file verification option to check the installed application files.
To verify the installation, open your Steam Library, right-click DSX, select Properties, open Installed Files, and choose Verify integrity of game files if that option is available.
Steam verification can repair missing or damaged application files. It should not be treated as a guarantee that every separately installed Windows runtime will be repaired.
You can find DSX on its official Steam store page.
Step 6: If the Runtime Is Installed but the Error Remains
If the correct runtime appears to be installed, work through these checks in order.
Confirm the Architecture
The installed runtime must be compatible with the application. If the error identifies a specific architecture, follow that requirement rather than guessing based on the Windows system type.
Check the Requested Version
Having .NET 8 installed does not necessarily satisfy an application that requests a different major version. Read the error carefully and install the version it actually requires.
Repair the Runtime Installation
If the required runtime is listed but the application cannot load it, run the official installer for that runtime again and use its repair option if offered.
Restart Windows afterward if needed.
Verify the Application Files
If the runtime is installed correctly but DSX still fails to start, verify the Steam installation or reinstall the application using its official distribution method.
Avoid downloading replacement DLL files from unrelated websites.
Check Whether Another Version of DSX Is Installed
If you have used both the older GitHub release and the Steam version, confirm which executable you are launching. Troubleshooting the wrong installation can make it appear that the runtime repair had no effect.
The older GitHub release, v1.4.9, is no longer supported or updated. You can review its historical releases through the Paliverse DualSenseX GitHub repository.
Do You Need ViGEmBus to Fix a .NET Error?
No. ViGEmBus and .NET serve different purposes.
- .NET Desktop Runtime allows compatible .NET desktop applications to run.
- ViGEmBus was used by the older DSX GitHub release for virtual-controller emulation.
Installing ViGEmBus will not normally resolve a missing .NET Desktop Runtime message. Likewise, a missing virtual-controller driver does not automatically mean .NET is broken.
Only troubleshoot ViGEmBus if DSX launches but a virtual-controller feature fails and your particular version requires that driver.
See the ViGEmBus project on GitHub for information about the legacy driver.
Common Mistakes to Avoid
When fixing a .NET Desktop Runtime error, avoid these approaches:
- Installing the SDK instead of the Desktop Runtime.
- Installing ASP.NET Core Runtime when the application requires desktop components.
- Assuming .NET 8 is required without reading the error.
- Choosing x64 without checking the application’s architecture.
- Uninstalling every existing .NET version.
- Downloading individual runtime DLL files from unofficial sites.
- Installing controller drivers to fix an application startup error.
- Assuming Steam file verification always installs every missing system dependency.
The quickest solution is usually to identify the requested runtime, install the matching official package, and test again.
Frequently Asked Questions
Does DSX always require .NET 8 Desktop Runtime?
Not necessarily. Requirements depend on the application version and how it was built. Follow the version and architecture specified in the actual error message or the documentation for your installed release.
I installed .NET 8, but DSX still will not open. What should I do?
Confirm that you installed the Desktop Runtime, not only the base .NET Runtime or SDK. Then check the required architecture and whether the application requests another version.
Should I uninstall older .NET runtimes?
Usually not. Multiple .NET versions can coexist, and other applications may depend on them. Remove a runtime only when you have a specific compatibility or repair reason.
Will installing ViGEmBus fix the .NET error?
No. ViGEmBus is a separate virtual-controller component associated with the older DSX setup. It does not replace the .NET Desktop Runtime.
DSX opens now, but my controller is not detected. Is that the same problem?
Not necessarily. A runtime error prevents the application from launching; controller detection is a separate issue. Once DSX opens, troubleshoot the connection, software version, and controller configuration separately.
Still Having Problems?
If the error remains after installing the correct runtime, note the exact error text, requested .NET version, Windows architecture, and DSX version. Those details help narrow down the cause without repeatedly installing unrelated components.
For controller detection or connection problems after DSX launches, see our DS5Windows/DualSenseX Troubleshooting Guide and Drivers Guide.
If you are deciding which version to install, our DS5Windows.dev homepage provides a broader overview and links to the official DSX distribution.