Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

9
  • OH... That makes sense now... Any way I can create a user-local version of "Run with PowerShell" that runs the script without setting process level execution policy? Commented Jun 27, 2024 at 21:15
  • @charlesz, yes, as (now) noted in the answer, you can create equivalent definitions in the HKEY_CURRENT_USER registry hive. Commented Jun 27, 2024 at 21:17
  • 1
    "but it was decided not to change that in the interest of backward compatibility" a constant thorn in the way of PowerShell progress.. Commented Jun 27, 2024 at 21:19
  • @mklement0 Yes. I am on Windows 10. Let me try next time I work on this. Commented Jun 28, 2024 at 19:46
  • 1
    Made it work now. Thanks! @mklement0 Only caveat is that I use VS Code so it needed to be under "VSCode.ps1" instead of "Microsoft.PowerShellScript.1". "0" could be anything, and as long as it has a default value set, it uses that value as the context menu text. Commented Jun 29, 2024 at 6:54