winutil
winutil copied to clipboard
Chocolatey not installing
Describe the bug Chocolatey will not install. Unable to install software afterwards.
To Reproduce Steps to reproduce the behavior:
- Launch powershell as admin
- get the error Expected behavior
- Launch powershell as admin
- install choco
- install software and enjoy
Additional context Im on a debloated Win 10 iso. I used the "lite" preset with NTLITE.
can you provide a screenshoot of the errors you are getting?
sure

Have you tried rebooting? I think something in windows hasn't updated yet.
yes i tried to reboot and also everything is up2date. its on my local machine and on the vm too.
Interesting, can you try running a winget install manually?
IE something like this
winget install brave.brave
yeah this is working after i accept the terms of transaction.
Interesting, can you try installing something through winutil one more time? Something you have not installed yet.
Okay.. i reinstalled right now Windows 10 Edu and made a new iso with ntlite. Again i used the lite Templates and now i get the same message but im now able to Install some things. I would like to use chrome but after the download nothing happens.. its a bit strange and maybe only related to winget?
Yeah, that's one of the reasons for the idea to implement other cli tools as winget can be unstable at times. Sometimes you have to run the install a couple times to get it to work in my experience.
I have the same issue.
I have installed several apps via winget and CTT tool Upgraded apps that were out of date Tried all 3 different methods of running the script as on GitHUB I got it to work by going to https://christitus.com/win, copying the script into Powershell ISE and clicking run
This has consistently worked, as I removed chocolatey and repeated all steps as previously. The only one that consistently works is copying the script into Powershell ISE and clicking run. I am not sure why it does this.
Is there any way I can help troubleshoot further?
EDIT:
I should also specify it's not exactly the same as I am not on a debloated windows.
I tried on a fresh Windows 10 Pro and Windows 11 Pro after all updated were installed, and used winget at least once to get past the EULA
I am able to replicate the issue on a fresh Win11 install. I will update with what I find