This repository has been archived by the owner on Jan 1, 2024. It is now read-only.
forked from Jays2Kings/DS4Windows
Ds4 won't run unless Net 5.0 #2355
Comments
.....then do what it says and install .NET 64-bit? |
On Sun, Jul 25, 2021 at 4:38 PM Masamune3210 ***@***.***> wrote:
.....then do what it says and install .NET 64-bit?
well I left that part out because it goes without saying that would have
been the first thing to try. But even though I have it downloaded it’s not
acting like it and I’m not that tech savvy. I’m wondering if maybe I have
to move .NET into a different folder or something? I found a wired
alternative solution but DS4 was nice for the time.
… —
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2355 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AU66WPBAGODV4G6QCU3GQZLTZRY4FANCNFSM5A6W5LSA>
.
|
You need the Desktop version of the .net runtime, which probably is this version. If you already have it installed try reinstalling it. |
As Kanuan pointed out this problem is often because of users installing either 32bit x86 version of .NET runtime libaries or just the consoleApps or serverApps version of .NET 5.x libraries.
In 99.99999999% cases the error msg shown is because of those two mistakes. |
closed as inactive and the problem was probably user installing wrong version of .NET libraries |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Ds4 won't run upon opening
It happened after plugging in USB to play while charging controller.
'Microsoft.WindowsDesktop.App' version '5.0.0' was not found.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Regular Ds4 controller menu pops up.
I hit start and controller connects.
I play game like usual.
Screenshots and Logs
Also, please add the most
log file (ds4windows_log.txt) from the Logs folder in your DS4Windows config folder.
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: