Failed to set permissions on "C:\ProgramData\pm2\home" about pm2-installer

[dev-syn]

I think it was a user permissions problem within ProgramData

[punowo]

@dev-syn How did you solve this ? Nothing seems to work.

[punowo]

"npm run setup" works on the old powershell started as a terminal but not on the new one.

[dev-syn]

"npm run setup" works on the old powershell started as a terminal but not on the new one.

Good to know to be honest I gave up because I thought it was a problem within my own computer with permissions. I did a reset recently and haven't touched permissions nor tried setting this up again but when I do I will try that

[punowo]

"npm run setup" works on the old powershell started as a terminal but not on the new one.

Good to know to be honest I gave up because I thought it was a problem within my own computer with permissions. I did a reset recently and haven't touched permissions nor tried setting this up again but when I do I will try that

I'm lucky enough to have to have full access to my work machine but I'm restricted to a windows environment due to certain factors so I ended up practically trying everything in a weekend.
I still encounter this #86 but once I change to "Local System Account" I didn't encounter any other problems except the one where pm2 doesn't care about 'npm' on Windows and you have to pass on the full npm-cli.js path as 'script' in the ecosystem file.

[Aki-Siponen]

I'm running PowerShell 7.3.4

The cause of this error is incompatibility of PowerShell Core (pwsh, version 7.x) and PowerShell (version 5.x) core modules, specifically Microsoft.PowerShell.Security.
npm runs the setup in PowerShell, not in PowerShell Core.
When you try to run setup from pwsh, what setup is doing is starting Command Prompt to start node to start Command Prompt to ... start PowerShell.
PowerShell is effectively running on top of pwsh. I guess that PowerShell does not support loading core modules in this situation. At least document here explains that (starting from PowerShell 7.1) core PowerShell modules cannot be loaded in compatibility mode.

You could get rid of the error by adding these lines to start of src/windows/setup.ps1:

# Write-Host "Checking how this all started."
# Get-Process -Id $PID
$wmi = Get-WmiObject Win32_Process -Filter "ProcessId=$($pid)"
do {
  $process = Get-Process -Id $wmi.ParentProcessId -ErrorAction SilentlyContinue
  # $process # for debugging
  if ($process.Name -eq 'pwsh') {
    Write-Host "The  setup cannot be started from PowerShell Core (pwsh, PowerShell version 7.x).`nPlease run the setup from Powershell (version 5.x)."
    exit(1)
  }
  $wmi = Get-WmiObject Win32_Process -Filter "ProcessId=$($wmi.ParentProcessId)" -ErrorAction SilentlyContinue
} until ($wmi.ParentProcessId -eq $null)

That would prevent setup running in PowerShell Core.

If you would want to run setup in PowerShell Core, you'd need to change "PowerShell" to "pwsh" in all package.json scripts.

[dev-syn]

I'm running PowerShell 7.3.4

The cause of this error is incompatibility of PowerShell Core (pwsh, version 7.x) and PowerShell (version 5.x) core modules, specifically Microsoft.PowerShell.Security. npm runs the setup in PowerShell, not in PowerShell Core. When you try to run setup from pwsh, what setup is doing is starting Command Prompt to start node to start Command Prompt to ... start PowerShell. PowerShell is effectively running on top of pwsh. I guess that PowerShell does not support loading core modules in this situation. At least document here explains that (starting from PowerShell 7.1) core PowerShell modules cannot be loaded in compatibility mode.

You could get rid of the error by adding these lines to start of src/windows/setup.ps1:

# Write-Host "Checking how this all started."
# Get-Process -Id $PID
$wmi = Get-WmiObject Win32_Process -Filter "ProcessId=$($pid)"
do {
  $process = Get-Process -Id $wmi.ParentProcessId -ErrorAction SilentlyContinue
  # $process # for debugging
  if ($process.Name -eq 'pwsh') {
    Write-Host "The  setup cannot be started from PowerShell Core (pwsh, PowerShell version 7.x).`nPlease run the setup from Powershell (version 5.x)."
    exit(1)
  }
  $wmi = Get-WmiObject Win32_Process -Filter "ProcessId=$($wmi.ParentProcessId)" -ErrorAction SilentlyContinue
} until ($wmi.ParentProcessId -eq $null)

That would prevent setup running in PowerShell Core.

If you would want to run setup in PowerShell Core, you'd need to change "PowerShell" to "pwsh" in all package.json scripts.

Thanks for pointing this out if I return to pm2 I will definitely remember this.