Skip to content
This repository has been archived by the owner on Sep 21, 2023. It is now read-only.

"Set-ExecutionPolicy Unrestricted -Force" may fail on a fresh version of windows #551

Open
CODEdragonCal opened this issue Feb 10, 2023 · 2 comments

Comments

@CODEdragonCal
Copy link

CODEdragonCal commented Feb 10, 2023

Has this happen to a few old Lenovo laptops running Celeron processors. Not much of a big deal but installing a few Windows drivers resolves the problem and restarting. By fresh I mean by just installed and ran the script straight away.

@MrFums
Copy link

MrFums commented Feb 21, 2023

Would you know what powershell version the machines were on // what version of windows it was ?

@lightzall
Copy link

I had to right Powershell ISE as admin from start menu then change directory but one could, I suppose, also run directly from within the ISE window. I could not get scripts to work right out the elevated command prompt as I did in the past. In fact, I landed here after similar tools I used failed. This seems to have worked. I totally forgot how utterly craptacular W10 was and is with cortana, xbox and stuff I dont want or neeed ever. I did everything but custom blocklist and the UI was slick. Nice work team. Running W10 on a X79 Sandy Bridge platform means even the smallestr reduction in bloat amounts to huge improvements. 21H2 is sunset in June so I went to 22H2 when my hdd died. The chore of installing comes after insllation trying to reign in the M$ pony circus.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants