64 and 32 Bit PowerShell Execution Policies Stored Separately

Just stumbled upon this due to some confusion about the version of PowerShell I was running on my 64 bit Vista machine. I ran PowerShell from the start menu, using the context menu to bring it up as Administrator. Then I set the execution policy to RemoteSigned:

> Set-ExecutionPolicy RemoteSigned

I ran PowerShell as a normal user (through SlickRun - brought up the 32 bit PowerShell without me noticing at first), tried to run a script and it failed. Get-ExecutionPolicy still showed Restricted. Wtf? Turns out that the execution policies for 32 and 64 bit PowerShells are stored separately. I don’t know, I can’t figure out any value in this apart from the obvious “let’s fuck with their minds” conspiracy idea. Probably something that wasn’t really done on purpose, but still pretty important to know.

Sorry, this blog does not support comments.

I used various blog hosting services since this blog was established in 2005, but unfortunately they turned out to be unreliable in the long term and comment threads were lost in unavoidable transitions. At this time I don't want to enable third-party services for comments since it has become obvious in recent years that these providers invariably monetize information about their visitors and users.

Please use the links in the page footer to get in touch with me. I'm available for conversations on Keybase, Matrix, Mastodon or Twitter, as well as via email.