I checked a little further:
Running in Integrated Environment:
True
C:\Program Files (x86)\Universal\Universal.Server.exe
Major Minor Patch PreReleaseLabel BuildLabel
----- ----- ----- --------------- ----------
7 5 0
Running in Powershell 7 Environment:
True
C:\Program Files (x86)\Universal\Hosts\7.5\PowerShellUniversal.Host.exe
Major Minor Patch PreReleaseLabel BuildLabel
----- ----- ----- --------------- ----------
7 5 0
Running in Powershell 5.1 Environment:
True
C:\Program Files (x86)\Universal\Hosts\5.1\PowerShellUniversal.Host.exe
Major Minor Build Revision
----- ----- ----- --------
5 1 17763 7009
Running in Custom 32bit Environment (%SystemRoot%\SysWOW64\WindowsPowerShell\v1.0\powershell.exe):
True
C:\Program Files (x86)\Universal\Hosts\5.1\PowerShellUniversal.Host.exe
Major Minor Build Revision
----- ----- ----- --------
5 1 17763 7009
Running in custom 64bit Environment (C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe):
True
C:\Program Files (x86)\Universal\Hosts\5.1\PowerShellUniversal.Host.exe
Major Minor Build Revision
----- ----- ----- --------
5 1 17763 7009
So the environment definitely changes something, it just doesn’t properly launch alternative powershell paths.
Starting %SystemRoot%\SysWOW64\WindowsPowerShell\v1.0\powershell.exe (by copying and pasting this in explorer) and running the same commands gives us the following outputs:
PS C:\Windows\system32> [Environment]::Is64BitProcess
False
PS C:\Windows\system32> [Diagnostics.Process]::GetCurrentProcess().Path
C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe
PS C:\Windows\system32> Write-Output $PSVersionTable.PSVersion
Major Minor Build Revision
----- ----- ----- --------
5 1 17763 7009