Checklist
What You Are Seeing?
When running the chocolatey install script in PowerShell 7, the installer for .NET Framework fails.
What is Expected?
Running the script should install .NET Framework.
How Did You Get This To Happen?
Open pwsh and run the install command from the website.
User Story
No response
System Details
- Operating System: Windows 10 LTSC 1809
- Windows PowerShell version: 7.6.0
- Chocolatey CLI Version: 2.6.0
- Chocolatey Licensed Extension version:
- Chocolatey License type:
- Terminal/Emulator:
Installed Packages
Output Log
Installing Chocolatey on the local machine
The registry key for .Net 4.8 was not found or this is forced
Installing 'C:\Users\<User>\AppData\Local\Temp\ndp48-x86-x64-allos-enu.exe' - this may take awhile with no output.
MethodInvocationException: Exception calling "Start" with "1" argument(s): "An error occurred trying to start process
'ndp48-x86-x64-allos-enu.exe' with working directory 'C:\Users\<User>\AppData\Local\Temp'. The system cannot find the
file specified."
InvalidOperation: You cannot call a method on a null-valued expression.
WARNING: Try #1 of .NET framework install failed with exit code ''. Trying again.
Additional Context
The problem is that the process start cannot find the installer executable. This seems to be caused by the change of the default value of UseShellExecute of True in PowerShell 5 to False in PowerShell 7. I would suggest setting UseShellExecute explicitly to True.
Acceptance Criteria
No response
Related Issues
No response
┆Issue is synchronized with this Clickup task by Unito
Checklist
What You Are Seeing?
When running the chocolatey install script in PowerShell 7, the installer for .NET Framework fails.
What is Expected?
Running the script should install .NET Framework.
How Did You Get This To Happen?
Open pwsh and run the install command from the website.
User Story
No response
System Details
Installed Packages
Output Log
Additional Context
The problem is that the process start cannot find the installer executable. This seems to be caused by the change of the default value of UseShellExecute of True in PowerShell 5 to False in PowerShell 7. I would suggest setting UseShellExecute explicitly to True.
Acceptance Criteria
No response
Related Issues
No response
┆Issue is synchronized with this Clickup task by Unito