New
#31
I'll fire up a VM and see - can't recall off-hand (just remember always turning that off as it sometimes breaks the installation - it's probably a driver check - off the top of my head)
Well, level 2 technician said it was a compatibility issue between the Creators Update and my Gigabyte motherboard (GA-H81M-DS2V)... and he was right! I did a final clean install of the Anniversary Update and everything is now working fine. I don't know if Gigabyte will ever release working drivers for Creators Update, but as long as everything is fine, so am I. Thanks to everyone who took time out of their day to help me, it's really reassuring to know that there's a community I can ask for help whenever I need it.
Question for @Superfly.
Can the set command,
Set-ExecutionPolicy RemoteSigned
be added to the script as first command or does it need to be run separately for any reason. Additionally should something be run after the wureset.zip script to undo this "Set" command for security reasons.
So many posts on Updates failing this could be very handy and I will always note origin. Thanks for posting. Let us know about set command and the undo.
Ken
@Caledon Ken
The execution policy is intened to protect against scripts being run - thus it won't execute a policy change from within a script if the restriction to run scripts are in place. It will have to be set in the PS admin console:
Set-ExecutionPolicy RemoteSigned CurrentUser
after which it can be reset back to default::
Set-ExecutionPolicy Restricted CurrentUser
Set-ExecutionPolicy Restricted LocalMachine