Add Edit with PowerShell ISE as administrator in Windows 10  

    Add Edit with PowerShell ISE as administrator in Windows 10

    Add Edit with PowerShell ISE as administrator in Windows 10

    How to Add Edit with PowerShell ISE as administrator context menu in Windows 10
    Published by Category: Customization
    15 Jun 2021
    Designer Media Ltd



    How to Add "Edit with PowerShell ISE as administrator" context menu in Windows 10


    The Windows PowerShell Integrated Scripting Environment (ISE) is one of two hosts for the Windows PowerShell engine and language. With it you can write, run, and test scripts in ways that are not available in the Windows PowerShell Console. The ISE adds syntax-coloring, tab completion, IntelliSense, visual debugging, and context sensitive Help.

    The ISE lets you run commands in a console pane, but it also supports panes that you can use to simultaneously view the source code of your script and other tools that can plug into the ISE. You can even open up multiple script windows at the same time, which is especially helpful when you are debugging a script that uses functions defined in other scripts or modules.

    For more details about Windows PowerShell ISE, see:

    This tutorial will show you how to add or remove a Edit with PowerShell ISE as administrator context menu for PS1 files for all users in Windows 10.

    You must be signed in as an administrator to add, remove, or use the "Edit with PowerShell ISE as administrator" context menu.

    The "Edit with PowerShell ISE as administrator" context menu will be available when you right click or shift + right click on a PS1 file.



    EXAMPLE: "Edit with PowerShell ISE as administrator" context menu
    Add Edit with PowerShell ISE as administrator in Windows 10-edit_with_powershelli_ise_as_administrator_context_menu.jpg Add Edit with PowerShell ISE as administrator in Windows 10-elevated_powershell_ise.jpg



    Here's How:

    1 Do step 2 (add-right click), step 3 (add-Shift+right click) , or step 4 (remove) below for what you would like to do.


    2 To Add Right Click "Edit with PowerShell ISE as administrator" Context Menu

    The .reg file in this step also includes the contents of the ps1.reg file here to restore the default associations for .ps1.


    A) Click/tap on the Download button below to download the file below, and go to step 5 below.

    Add_Edit_with_PowerShell_ISE_as_administrator_context_menu.reg

    Download


    3 To Add Shift + Right Click "Edit with PowerShell ISE as administrator" Context Menu

    The .reg file in this step also includes the contents of the ps1.reg file here to restore the default associations for .ps1.


    A) Click/tap on the Download button below to download the file below, and go to step 5 below.

    Add_Shift+Edit_with_PowerShell_ISE_as_administrator_context_menu.reg

    Download


    4 To Remove "Edit with PowerShell ISE as administrator" Context Menu

    This is the default setting

    A) Click/tap on the Download button below to download the file below, and go to step 5 below.

    Remove_Open_with_Windows_PowerShell_ISE_as_administrator_context_menu.reg

    Download

    5 Save the .reg file to your desktop.

    6 Double click/tap on the downloaded .reg file to merge it.

    7 When prompted, click/tap on Run, Yes (UAC), Yes, and OK to approve the merge.

    8 You can now delete the downloaded .reg file if you like.


    That's it,
    Shawn Brink






  1. Posts : 4
    Windows 10
       #1

    Much appreciated Brink. I'm not sure if I did something wrong or if it's just me, but I get this message.
    Add Edit with PowerShell ISE as administrator in Windows 10-ps.jpg
      My Computer


  2. Posts : 64,539
    64-bit Windows 11 Pro for Workstations
    Thread Starter
       #2

    @michaeljt

    That was from the file having a space in its name. I'll see if I can update this to compensate for that, and will post back.

    EDIT:

    Hmm, I'm having a hard time remembering how to do this with a space in the file name, but I'll keep hunting.

    Is there anyone that can remind me how?
    Last edited by Brink; 17 Jul 2018 at 15:18.
      My Computers


  3. Posts : 64,539
    64-bit Windows 11 Pro for Workstations
    Thread Starter
       #3

    Ok @michaeljt,

    The fog has lifted. The updated .reg files in the tutorial will now work with files that have spaces in their names.

    You would just need to download and merge the new .reg file currently in the tutorial to update the context menu.
      My Computers


  4. Posts : 4
    Windows 10
       #4

    Working great thank you very much!
      My Computer


  5. Posts : 64,539
    64-bit Windows 11 Pro for Workstations
    Thread Starter
       #5

    You're most welcome.
      My Computers


  6. Posts : 2
    Window 10
       #6

    This doesn't appear to be working in Windows 1909
      My Computer


  7. Posts : 64,539
    64-bit Windows 11 Pro for Workstations
    Thread Starter
       #7

    yannduran said:
    This doesn't appear to be working in Windows 1909
    Hello yannduran, and welcome to Ten Forums.

    I have updated the .reg files in the tutorial to include restoring the default associations of .ps1 files so the context menu will work again now.

    You will just need to download and merge the new .reg file in the tutorial.
      My Computers


  8. Posts : 1
    Microsoft Windows Version 10.0.19041.1083
       #8

    Hi Brink,

    If I select three files and choose the context menu option, it only opens one ISE editor with a single file. How can I get three distinct ISE instances (or as many as the files I selected)?

    Sincerely,
    The Crumpler
      My Computer


  9. Posts : 64,539
    64-bit Windows 11 Pro for Workstations
    Thread Starter
       #9

    The Crumpler said:
    Hi Brink,

    If I select three files and choose the context menu option, it only opens one ISE editor with a single file. How can I get three distinct ISE instances (or as many as the files I selected)?

    Sincerely,
    The Crumpler
    Hello The Crumpler, and welcome to Ten Forums.

    I'm afraid it's the method used to "Run as administrator" preventing it from opening an ISE instance per file.
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 09:25.
Find Us




Windows 10 Forums