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

tortadefrango97 said:

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.

Click to expand...

Hello,

I've updated the REG files below for this. Please try them now to see how it works for you.

Brink said:

Hello,

I've updated the REG files below for this. Please try them now to see how it works for you.

Add Open PowerShell window here as administrator in Windows 10

How to Add Open PowerShell window here as administrator context menu in Windows 10

www.tenforums.com

Click to expand...

The problem is that now it doesn't work in a normal folder. It only works in C:

tortadefrango97 said:

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.

Click to expand...

That's a bit of a pickle because adding a trailing backslash for directory background will fix the error when it's a drive window but will add an error for all folder windows. We'll need our thinking caps on this one.

Maybe we can fix it for Windows 11 using "-WorkingDirectory". I'll post more about that later. Right now, I have to shovel snow.

LesFerch said:

That's a bit of a pickle because adding a trailing backslash for directory background will fix the error when it's a drive window but will add an error for all folder windows. We'll need our thinking caps on this one.

Maybe we can fix it for Windows 11 using "-WorkingDirectory". I'll post more about that later. Right now, I have to shovel snow.

Click to expand...

oh ok, no worries. @Brink, better to roll back to how it was before for now...

@DisposableEmail

With out any tweaks, you should see Open in Terminal ...on Windows 11, on the right click menu.
It should open Terminal in Powershell (admin).

I'm on the "classic" Context Menu".
You can get that with this tutorial...



For example...

tortadefrango97 said:

The problem is that now it doesn't work in a normal folder. It only works in C:

Click to expand...

Well, it was worth a try. Restored.

Ghot said:

@DisposableEmail

With out any tweaks, you should see Open in Terminal ...on Windows 11, on the right click menu.
It should open Terminal in Powershell (admin).

Click to expand...

Admin?

LesFerch said:

Admin?

Click to expand...

I just figured this out too. You need to hold Ctrl+Shift while clicking.

LesFerch said:

Admin?

Click to expand...

I get this from the pic above... (left side)




As far as I know, I didn't ADD that to the Context Menu, in Win 10 or Win 11.
I don't have it on the Leader Board (Context Menu section), either.
I didn't add it in Winaero.
Even in the right click Start Menu... both Terminal and Terminal (Admin) "show" the same Terminal window. ??





Anyone have a harmless Powershell command that must be run as Admin, that I can test with?

@Brink and @tortadefrango97 Here's a new command that works in all scenarios, including the root drive and root background. This replaces the previous one-liners for directory, directory background, and drive. It works on Windows 10 and Windows 11:

Given that "-WorkingDirectory" is supported for the PowerShell.exe command line in the Windows 11 version of PowerShell 5.1, I can probably make a shorter version specifically for Windows 11.

LesFerch said:

@Brink and @tortadefrango97 Here's a new command that works in all scenarios, including the root drive and root background. This replaces the previous one-liners for directory, directory background, and drive. It works on Windows 10 and Windows 11:

Code:

@="cmd /c reg add hkcu\\software\\_dir /v p /d \"%v \" /f & start powershell -WindowS H -noP -c Start-Process -v RunAs powershell.exe '-noL -noE -c cd -literalP ((gp hkcu:\\software\\_dir).p).TrimEnd(); ri hkcu:\\software\\_dir'"

Given that "-WorkingDirectory" is supported for the PowerShell.exe command line in the Windows 11 version of PowerShell 5.1, I can probably make a shorter version specifically for Windows 11.

Click to expand...

Thank you. Works great. Now updated.

tortadefrango97 said:

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.

Click to expand...

Microsoft traded one glitch/limitation for another.

The old command, using literalPath, and single quotes, worked for everything except folders containing a single quote, such as Bob's Files.

The new command has the %V in double quotes and uses -WorkingDirectory which would be perfect except for registry character escaping. When you right-click drive C, %V is assigned the string C:\, but %V is inside double quotes, so you have a trailing \" which is the escape sequence for a double quote, so PowerShell gets passed C:".

Our PowerShell Admin command had the same issue. I worked around it by appending a space character to buffer between \ and " and prevent the unintended escape sequence. The trailing space is stripped off afterwards.

For Microsoft's baked in command to launch PowerShell a quick fix for the Drive command is to change it to:
powershell.exe -noexit -WorkingDirectory "%V\"

However, that won't work for the directory background entry because it will eliminate the error for a root view but add an error for all folder views.

Microsoft really screwed this up. I'll work on a fix. Stay tuned...

LesFerch said:

Microsoft traded one glitch/limitation for another.

The old command, using literalPath, and single quotes, worked for everything except folders containing a single quote, such as Bob's Files.

The new command has the %V in double quotes and uses -WorkingDirectory which would be perfect except for registry character escaping. When you right-click drive C, %V is assigned the string C:\, but %V is inside double quotes, so you have a trailing \" which is the escape sequence for a double quote, so PowerShell gets passed C:".

Our PowerShell Admin command had the same issue. I worked around it by appending a space character to buffer between \ and " and prevent the unintended escape sequence. The trailing space is stripped off afterwards.

For Microsoft's baked in command to launch PowerShell a quick fix for the Drive command is to change it to:
powershell.exe -noexit -WorkingDirectory "%V\"

However, that won't work for the directory background entry because it will eliminate the error for a root view but add an error for all folder views.

Microsoft really screwed this up. I'll work on a fix. Stay tuned...

Click to expand...

Thanks, good job.

I'm always amazed at how Microsoft manages to create new bugs while trying to fix existing ones haha

I spent a lot of time looking at the built in commands and the only way I can make it work without error for all folder names (including ones with single quotes) and root drives is to use the same method that we're using for open-powershell-window-here-as-administrator. That method uses Cmd so there's an extra console flash. That's not so bad when you're getting a UAC prompt anyhow, but it's not so desirable as a replacement for the direct opening of PowerShell in the User context. We need Microsoft to fix it. In the meantime, you can do this:

For the Drive registry entry, add a trailing backslash. This prevents the backslash in a root drive path (e.g. C:\) from being parsed as an escape sequence and works as long as the path ends in a backslash.

powershell.exe -noexit -WorkingDirectory "%V\"

The above "fix" cannot be used for the Directory Background registry entry because it will error when there isn't a trailing backslash (i.e. every folder except root drive views). So, you can either live with the error when it's a right-click on a directory background of a root drive or change it to the old "LiteralPath" code and have an error whenever the folder name contains an apostrophe (e.g. Bob's Files):

powershell.exe -noexit -command Set-Location -literalPath '%V'

If you wish to make either of those changes, you'll need to open RegEdit as TrustedInstaller. You can do that using Right-Click Tools or PowerRun or AdvancedRun etc.

When adding "conhost --headless" (to hide the flash) but Defender immediately flagged that reg file as a no-no.