Toolbar button, Start Path with Powershell

[wanderer]

The following starts PowerShell 1.0 but does not set the start path. Anybody knows why? Setting it to a fixed one, like "C:\Windows" works fine.

I tried the path with and without quotes, no luck. Also, this version of PS does not seem to support -WorkingDirectory command-line parameter. Is there another?

Code: Select all

TOTALCMD#BAR#DATA
C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe

C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe

%P:~0,-1

-1

[wanderer]

OK, to partly answer my question, a workaround is this:

Code: Select all

TOTALCMD#BAR#DATA
C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
-NoExit -Command "cd '%P:~0,-1'"
C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe



-1

Still, why the button in my OP does not work without a fixed location? Are parameters not supported in Start Path?

[ghisler(Author)]

Indeed parameters like %P are only supported in the "Parameter" field.

[wanderer]

Ah, ok, thanks for the clarification.

[Horst.Epp]

For me, the following button starts in the current TC dir without the need for any tricks.
Using the button context menu, I can also start it as Administrator.

Code: Select all

TOTALCMD#BAR#DATA
C:\Program Files\PowerShell\7\pwsh.exe
-NoExit
C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe
PowerShell in current path

0
-1

[Dalai]

To start something with the current path as working directory just leave the Start Path empty.

[wanderer]

To start something with the current path as working directory just leave the Start Path empty.

Yup. Nice, except if you want to start it "as admin" and you have put a * in front of the executable. Then you've lost...

[ghisler(Author)]

The current directory set via SetCurrentDirectory is not passed to programs run as administrator. This is true for all programs, not just for powershell.

[beb]

2wanderer
Use $pwd. It works both with the button context menu and with * in front of the executable.

Direct-action buttons examples with the asterisk (no as admin option in the context menu though) to run as admin in $pwd:

Code: Select all

TOTALCMD#BAR#DATA
*C:\Program Files\PowerShell\7\pwsh.exe -NoExit

C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe
PowerShell as admin in the current active pane path
cd $pwd
0
-1

Code: Select all

TOTALCMD#BAR#DATA
*C:\Program Files\PowerShell\7\pwsh.exe -NoExit
-c cd $pwd
C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe
PowerShell as admin in the current active pane path


-1

Contex-menu action button example to run As Admin in $pwd:

Code: Select all

TOTALCMD#BAR#DATA
C:\Program Files\PowerShell\7\pwsh.exe -NoExit

C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe
PowerShell as admin in the current active pane path
cd $pwd
0
-1

[Horst.Epp]

The current directory set via SetCurrentDirectory is not passed to programs run as administrator. This is true for all programs, not just for powershell.

And why does my button above works when I select "As Administrator" from the Button context menu ?
Also, when TC runs already enhanced, the button starts PowerShell as Administrator in the correct path.

[white]

To start something with the current path as working directory just leave the Start Path empty.

Yup. Nice, except if you want to start it "as admin" and you have put a * in front of the executable. Then you've lost...

The current directory set via SetCurrentDirectory is not passed to programs run as administrator. This is true for all programs, not just for powershell.

I found this not to be true, at least for my Windows 11 system. The current folder is set to c:\windows\system32 when running programs as administrator if the program is located in c:\windows or any of its subfolders. For programs outside c:\windows, the current folder is not changed. For example, the current folder is not set to c:\windows\system32 when running "C:\Program Files\IrfanView\i_view64.exe" as administrator. Nor when copying "cmd.exe" and "en-US\cmd.exe.mui" to a folder outside the windows folder and running cmd.exe located in that folder as administrator.

Edit: Also tested on Windows Vista where it works the same. It seems the behavior was always bound to program within the windows folder.