FreeCommander Forum

Forez wrote: 24.07.2023, 23:17 Program or folder:

Code: Select all

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

Parameter:

Code: Select all

Start-Process ""C:\portables\! SCRIPTS\test.ps1"" -Verb runAs -WindowStyle Maximized

Start-Process powershell -Verb RunAs -ArgumentList "-WindowStyle Maximized -File 'C:\portables\! SCRIPTS\test.ps1'"

Define favorite toolbars > Define favorite toolbars > Run > With "Run as" dialog

• Option - With "Run As" dialog

• Program

  Code: Select all

  powershell.exe

• Parameter

  Code: Select all

  -WindowStyle Maximized -File "C:\portables\! SCRIPTS\test.ps1"

Forez wrote: 17.10.2023, 13:40 Somehow I am not able to get anything more than just the PowerShell window showing up with elevated rights

Using NameSpace System.Security.Principal

Write-Host -NoNewLine "Permissions: "
if ([WindowsPrincipal]::New([WindowsIdentity]::GetCurrent()).IsInRole([WindowsBuiltInRole]::Administrator)) {
  Write-Host -ForegroundColor "green" "elevated."
} else {
  Write-Host -ForegroundColor "red" "limited."
}

Using NameSpace System.Security.Principal

Write-Host -NoNewLine "Permissions: "
if ([WindowsPrincipal]::New([WindowsIdentity]::GetCurrent()).IsInRole([WindowsBuiltInRole]::Administrator)) {
  Write-Host -ForegroundColor "green" "elevated."
} else {
  Write-Host -ForegroundColor "red" "limited."
}

File C:\portables\! SCRIPTS\test.ps1 cannot be loaded because running scripts is disabled on this system. For more
information, see about_Execution_Policies at https:/go.microsoft.com/fwlink/?LinkID=135170.
+ CategoryInfo : SecurityError: (:) [], ParentContainsErrorRecordException
+ FullyQualifiedErrorId : UnauthorizedAccess
PS C:\Windows\system32>

TK87 wrote: 22.10.2023, 20:33 [...]
I thought you would be familiar with it
[...]

TK87 wrote: 22.10.2023, 20:33 If you have previously executed the scripts via context menu, there the execution policy got bypassed.

TK87 wrote: 22.10.2023, 20:33 You can also do this by adding "-ExecutionPolicy ByPass" to the parameters.

-ExecutionPolicy ByPass -NoLogo -NoExit -File "C:\portables\! SCRIPTS\test.ps1"

TK87 wrote: 22.10.2023, 20:33 However, it is recommended to set the execution policy to "RemoteSigned" once. This means your local scripts will be executed, but scripts downloaded from the Internet must be signed by a verified publisher.
[...]

Forez wrote: 23.10.2023, 19:55

TK87 wrote: 22.10.2023, 20:33 If you have previously executed the scripts via context menu, there the execution policy got bypassed.

You mean the shell menu of the operating system? So far I never had any script added to it

I have an A-OK working PowerShell script.

So Windows differentiates between downloaded files [and those copied from a e.g. thumbdrvive] based on I-forgot-how-it-is-called-as-I-vaguely-just-remembered-it-exists-at-all feature?

But how does the system validates a PS1 file? Is it not possible to just open PS1 file in Notepad to maliciously adjust it - and then put it on the Internet posing as Verified publisher?

TK87 wrote: 23.10.2023, 20:39

Forez wrote: 23.10.2023, 19:55

TK87 wrote: 22.10.2023, 20:33 If you have previously executed the scripts via context menu, there the execution policy got bypassed.

You mean the shell menu of the operating system? So far I never had any script added to it

You said...

I have an A-OK working PowerShell script.

... so how did you confirm that your script was working ok? Somehow you must have executed it before. I guessed that you used the option from the context menu to do this (right click on the .ps1 file and then "Run with Powershell").