I'm seeing an oddity on one desktop whereby the two module paths for PS7 are concatenated rather than split by a comma and this results in modules not being loaded.
Steps to reproduce
[Environment]::GetEnvironmentVariable("PSModulePath", "Process") -split ';' | sort
Expected behavior
C:\Program Files\PowerShell\Modules\
c:\program files\powershell\7\Modules
Actual behavior
C:\Program Files\PowerShell\Modules\c:\program files\powershell\7\Modules
or in full:
C:\Users\Robin\Documents\PowerShell\Modules;C:\Program Files\PowerShell\Modules\c:\program files\powershell\7\Modules;;C:\Program Files\WindowsPowerShell\Modules\;C:\Windows\system32\WindowsPowerShell\v1.0\Modules;
Environment data
Name Value
---- -----
PSVersion 7.0.2
PSEdition Core
GitCommitId 7.0.2
OS Microsoft Windows 10.0.19041
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0
I'm seeing an oddity on one desktop whereby the two module paths for PS7 are concatenated rather than split by a comma and this results in modules not being loaded.
Steps to reproduce
Expected behavior
Actual behavior
or in full:
Environment data