DeveloperDurp

From what the comment is saying yes, you can try using "Windows Powershell" that's installed with Windows itself. Should look like this 

Not quite a bug, more of a feature of Windows Apps. Apps installed through the store are typically sandboxed and have limited access to the whole system, which is good...

Yeah, I don't think there is much we can do to resolve the sandboxed powershell session.

Apologies I completely missed that. What happens if you run this manually `curl.exe -ss "https://live.sysinternals.com/Autologon.exe" -o autologin.exe`

Chocolatey usually suggests to close the powershell window and reopen. This will need some logic added to prevent this from happening/work around it

Which tweaks did you run? Looks to be similar issue to #404 Edit: Nevermind think I found it. @ChrisTitusTech looks to be part of the Telemetry, not sure the reason...

I would say the security vulnerability is debatable. Normally I would use the built in administrator account similar to a linux root account and my user profile would be setup...

Security Account Manager (SAM) from my understanding all local accounts in Windows is susceptible to this kind of hack. Best example I can think of is there are bootable ISO...

You might need to reboot your computer and try again. Winget can be very temperamental at times.

Yeah it's something with winget, could be how it's installed through the script (IE not through the windows store) or something else entirely. Winget is nice but it doesn't seem...