-
Notifications
You must be signed in to change notification settings - Fork 267
Open
Labels
0 - BacklogIssue is accepted, but is not ready to be worked on or not in current sprint.Issue is accepted, but is not ready to be worked on or not in current sprint.EnhancementIssues that introduce new functionality to the project, or enhances/updates existing functionality.Issues that introduce new functionality to the project, or enhances/updates existing functionality.
Description
Checklist
- I have verified this is the correct repository for opening this issue.
- I have verified no other issues exist related to my problem.
- I have verified this is not an issue for a specific package.
- I have verified this issue is not security related.
What You Are Seeing?
Unable to load Chocolatey GUI assembly. The type initializer for 'ChocolateyGui.Common.Windows.Bootstrapper' threw an exception.
OK
What is Expected?
Chocolatey GUI should just launch
How Did You Get This To Happen?
- Installed Windows Sandbox
- Install Chocolatey GUI 1.1.1 in the Windows Sandbox
- Launch Chocolatey GUI from the Start Menu
System Details
- Operating System: Windows 10 2004 (Which is what Windows Sandbox comes with under Windows 10 Pro 21H2)
- Windows PowerShell version: 5.1.19041.2364
- Chocolatey CLI Version: Not Installed
- Chocolatey Licensed Extension version: N/A
- Chocolatey License type: Community
- Terminal/Emulator: conhost
Installed Packages
N/AOutput Log
Under C:\ProgramData there is no "Chocolatey" folder, and the "Chocolatey GUI" folder only has an empty folder named "Config"Additional Context
- Operating System: Windows 10 2004 (Which is what Windows Sandbox comes with under Windows 10 Pro 21H2)
- Windows PowerShell version: 5.1.19041.2364
- Chocolatey CLI Version: Not Installed
- Chocolatey Licensed Extension version: N/A
- Chocolatey License type: Community
- Terminal/Emulator: conhost
The error pops up several times, have to press OK each time.
If I then go ahead and install the CLI version of chocolatey then everything works fine. But isn't the whole point of a GUI application not to use CLI? So the GUI MSI installer should be installing the CLI version automatically.
rnarayana and AddictArts
Metadata
Metadata
Assignees
Labels
0 - BacklogIssue is accepted, but is not ready to be worked on or not in current sprint.Issue is accepted, but is not ready to be worked on or not in current sprint.EnhancementIssues that introduce new functionality to the project, or enhances/updates existing functionality.Issues that introduce new functionality to the project, or enhances/updates existing functionality.