Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Updater reopens DS4Windows as Adminstrator
See original GitHub issueHi,
In 2.0.10 and earlier versions, the updater requires Administrator privileges if DS4Windows installed system wide (ie: %ProgramW6432%\DS4Windows). This is necessary for the upgrade to be successful .
Upon the update completion, the updater reopens DS4Windows but not as the current logged-in user but as the Administrator user that was used to perform the upgrade.
The consequence to this is my Administrator user doesn’t have any profile installed and so, after the upgrade I need to close and reopen DS4Windows.
Applications like Firefox and VSCode reopen their applications as the logged-in user. It would be nice if this could be addressed.
Thank you.
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I opted to use the Explorer version as that is the only option from Managed code. The other version is a bit more indirect in case someone happens to be using a custom shell rather than Windows Explorer. I finally updated the DS4Updater to take an extra command line argument into account so it can use the Windows Explorer shell workaround when launching DS4Windows.
Unfortunately, that means that you will not see that change until after updating to DS4Windows 2.0.14. There is no planned date for its release as of yet.
Version 2.0.15 is now out and it looks like the routine is working as intended.