Chocolatey GUI crashes when started from another working-directory
See original GitHub issueChocolateyGUI instantly crashes when opened from another directory - i.e. cwd is C:\
- then the call to C:\Program Files (x86)\ChocolateyGUI\ChocolateyGui.exe
results in the exception above.
When ChocolatyGUI is started from another process, and the StartupInfo.WorkingDirectory
(in whatever language) is set to 'C:\Program Files (x86)\ChocolateyGUI` everything works as expected.
version is current develop (eb464a1)
Issue Analytics
- State:
- Created 6 years ago
- Comments:11 (8 by maintainers)
Top Results From Across the Web
Chocolatey GUI v0.15.0 released
... #450 Chocolatey GUI crashes when started from another working-directory; #449 Chocolatey GUI crashes when closed while still loading ...
Read more >Chocolatey Software Docs | Known Issues
When this happens, Chocolatey GUI determines that there are no more packages on the server to request. The result is that not all...
Read more >Chocolatey GUI crash after trying to install Elixir
This looks like a known issue with the 0.13.x release of ChocolateyGUI. We currently have a pre-release version of ChocolateyGUI that will ...
Read more >Your Python Coding Environment on Windows: Setup Guide
With this opinionated guide to setting up a basic, fully featured and flexible setup for Python coding and open source contributing when working...
Read more >Release Notes - Remote Desktop Manager
Fixed possible crash when linking documentation pages. Fixed possible free Edge (WebView2) freezing RDM when started with RunAs.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The issue that was affecting @drfrpjr should be resolved. And I think I have a fix for the original issue. Will issue a PR later.
working in latest dev 😃