"Open powershell window here as administrator" - throws errors now?

DisposableEmail · Jul 23, 2025

Hi everyone,

I've collected a bunch of "tips" to configure Windows each time I set up a new machine, or when Windows breaks everything with an update.

One of them is from the Windows 10 days - "open powershell window here as administrator" in the context menu.

It still works, but it throws an error now, so I don't want to use it. I don't understand the error and I'm not smart enough to fix it.

Does anyone know how to resolve this? Details in the tenforums thread below. Thank you.

Add Open PowerShell window here as administrator in Windows 10

LesFerch · Jul 23, 2025

What's the error?

DisposableEmail · Jul 23, 2025

It's in the thread.

Rollback_Jockey · Jul 23, 2025

So you're using a Windows 10 tweak on Windows 11?

Rollback_Jockey · Jul 23, 2025

DisposableEmail said:
It's in the thread.

I don't see it? You just stated it threw an error.

DisposableEmail · Jul 23, 2025

Rollback_Jockey said:
So you're using a Windows 10 tweak on Windows 11?

Thanks for your helpful reply.

DisposableEmail · Jul 23, 2025

Rollback_Jockey said:
I don't see it? You just stated it threw an error.

I shared a link to a long thread that discusses the error.

garlin · Jul 23, 2025

A screenshot would be useful, if you're not going to repeat the error message.

And the last post in the referenced TenForums thread is @LesFerch replying to my question.

DisposableEmail · Jul 23, 2025

If you can't be bothered to read that thread, it's unlikely you will be able to help resolve the problem.

garlin · Jul 23, 2025

And neither will we.

Rollback_Jockey · Jul 23, 2025

DisposableEmail said:
If you can't be bothered to read that thread, it's unlikely you will be able to help resolve the problem.

I don't have time to chase threads over the internet when you could have given a simple explanation.

Judging by your attitude so far i'm guessing this will stay unresolved.

LesFerch · Jul 23, 2025

@DisposableEmail I just tested the current reg file on the latest Windows 11 build and it worked just fine for me.

Perhaps you're using an older version of the reg file? If not, post the error you're seeing.

I did check the tutorial and saw that there were no new posts by you (or anyone else) so it makes no sense that we should wade through 10 pages for some error (among several) that someone else posted (and was resolved with the current reg file). As it stands, the current reg file works on a standard Windows 11 build. But other variables, such as third party AV, could make a difference. Post your error and we can help.

Another option for you: RightClickTools

antspants · Jul 23, 2025

DisposableEmail said:
One of them is from the Windows 10 days - "open powershell window here as administrator" in the context menu.

Tutorial and reg file here on Eleven Forums. Perhaps there is a difference.

Add or Remove "Open PowerShell window here" Context Menu in Windows 11

This tutorial will show you how to add or remove the "Open PowerShell window here" context menu for all users in Windows 11. Windows PowerShell is a task-based command-line shell and scripting language designed especially for system administration. Built on the .NET Framework, Windows...

www.elevenforum.com

antspants · Jul 23, 2025

There is also this

Add "Open in Terminal (Admin)" context menu in Windows 11

This tutorial will show you how to add or remove a Open in Terminal (Admin) context menu for all users in Windows 11. Windows Terminal is a modern host application for the command-line shells you already love, like Command Prompt, PowerShell, and bash (via Windows Subsystem for Linux (WSL))...

www.elevenforum.com

And you can add these by using Winaero Tweaker, as I recall?

Winaero Tweaker

The ultimate all-in-one tweaker for Windows 11, Windows 10, Windows 8, and Windows 7.

winaerotweaker.com

LesFerch · Jul 23, 2025

antspants said:
Tutorial and reg file here on Eleven Forums. Perhaps there is a difference.

Add or Remove "Open PowerShell window here" Context Menu in Windows 11

This tutorial will show you how to add or remove the "Open PowerShell window here" context menu for all users in Windows 11. Windows PowerShell is a task-based command-line shell and scripting language designed especially for system administration. Built on the .NET Framework, Windows...

www.elevenforum.com

I think that tutorial is just for a non-admin PowerShell here context menu.

The Windows 10 tutorial is also applicable to Windows 11 as per the comment here from @Brink:

Add or Remove "Open PowerShell window here" Context Menu in Windows 11

This tutorial will show you how to add or remove the "Open PowerShell window here" context menu for all users in Windows 11. Windows PowerShell is a task-based command-line shell and scripting language designed especially for system administration. Built on the .NET Framework, Windows...

www.elevenforum.com

There's also this tutorial for Windows Terminal (Admin):

Add "Open in Terminal (Admin)" context menu in Windows 11

This tutorial will show you how to add or remove a Open in Terminal (Admin) context menu for all users in Windows 11. Windows Terminal is a modern host application for the command-line shells you already love, like Command Prompt, PowerShell, and bash (via Windows Subsystem for Linux (WSL))...

www.elevenforum.com

antspants · Jul 23, 2025

LesFerch said:
I think that tutorial is just for a non-admin PowerShell here context menu

Yes, it is. But I noticed that there were steps to Change the permissions of the Powershell key to "Allow" Administrators "Full Control. I thought it may be relevant, I really don’t know.

LesFerch said:
There's also this tutorial for Windows Terminal (Admin):

Yes, that’s in my post. You may have been composing a reply when I added it, thanks, Les

garlin · Jul 23, 2025

antspants said:
Yes, it is. But I noticed that there were steps to Change the permissions of the Powershell key to "Allow" Administrators "Full Control. I thought it may be relevant, I really don’t know.

Those instructions are for changing the default permissions on the reg sub-tree, since it's protected from tampering. It doesn't grant the actual target of the context menu any special privileges.

tortadefrango97 · Feb 24, 2026

LesFerch said:
@DisposableEmail I just tested the current reg file on the latest Windows 11 build and it worked just fine for me.

Perhaps you're using an older version of the reg file? If not, post the error you're seeing.

I did check the tutorial and saw that there were no new posts by you (or anyone else) so it makes no sense that we should wade through 10 pages for some error (among several) that someone else posted (and was resolved with the current reg file). As it stands, the current reg file works on a standard Windows 11 build. But other variables, such as third party AV, could make a difference. Post your error and we can help.

Another option for you: RightClickTools

I believe I found the error he is referring to.
I tested it here on Windows 10 and 11, and it works in all scenarios except on the system’s local drives, such as C:

Edit:
I did more tests, and I discovered that the original Windows command itself is broken. It seems that Microsoft changed the command.

They used the powershell.exe -noexit -command Set-Location -literalPath '%V' comand before , and now they are using powershell.exe -noexit -WorkingDirectory "%V"

The new command handles Unicode characters well, but it doesn't work on the C: drive.

LesFerch · Feb 24, 2026

tortadefrango97 said:
I believe I found the error he is referring to.
I tested it here on Windows 10 and 11, and it works in all scenarios except on the system’s local drives, such as C:

I see! Thank you! On my machine, I only ever used it on a directory or directory background. If @DisposableEmail had posted the error this would have been fixed a long time ago. Anyhow, the fix is simple. We just need to append a backslash for the the "Drive" code, like this:

@Brink here's the fixed code for Drive:

Code:

[HKEY_CLASSES_ROOT\Drive\shell\PowerShellAsAdmin\command]
@="cmd /c reg add hkcu\\software\\_dir /d \"%v\\\" /f & start powershell -WindowS H -noP -c Start-Process -v RunAs powershell.exe '-noL -noE -c cd -literalP (gp hkcu:\\software\\_dir).\\\"\\\"\\\"(default)\\\"\\\"\\\"; ri hkcu:\\software\\_dir'"

tortadefrango97 · Feb 24, 2026

LesFerch said:
I see! Thank you! On my machine, I only ever used it on a directory or directory background. If @DisposableEmail had posted the error this would have been fixed a long time ago. Anyhow, the fix is simple. We just need to append a backslash for the the "Drive" code, like this:

@Brink here's the fixed code for Drive:

Code:

[HKEY_CLASSES_ROOT\Drive\shell\PowerShellAsAdmin\command] @="cmd /c reg add hkcu\\software\\_dir /d \"%v\\\" /f & start powershell -WindowS H -noP -c Start-Process -v RunAs powershell.exe '-noL -noE -c cd -literalP (gp hkcu:\\software\\_dir).\\\"\\\"\\\"(default)\\\"\\\"\\\"; ri hkcu:\\software\\_dir'"

Thank you for the fix.

But I believe the 'Directory\Background' key also needs to be changed, otherwise the error persists when clicking inside the c: folder.

"Open powershell window here as administrator" - throws errors now?

Member

My Computer

Well-known member

My Computer

Member

My Computer

Well-known member

My Computers

Well-known member

My Computers

Member

My Computer

Member

My Computer

Well-known member

My Computer

Member

My Computer

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computer

Like a rolling drone.

My Computers

Like a rolling drone.

My Computers

Well-known member

My Computer

Like a rolling drone.

My Computers

Well-known member

My Computer

New member

My Computer

Well-known member

My Computer

New member

My Computer

Similar threads