You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
when running pwsh it gets stuck occasionally on some machines when using the flag(s) -MTA or -STA after investigations it gets stuck on Interop+Shell32.SHGetKnownFolderPath .
This happens even on a script that runs pwsh.exe -MTA -NoProfile -Command "$PSVersionTable.PSVersion.ToString()"
This does not happen on all our developer machines (Running Win 10 22H2), so far we have not been able to pinpoint the difference.
Name Value
---------
PSVersion 7.4.1
PSEdition Core
GitCommitId 7.4.1
OS Microsoft Windows 10.0.19045
Platform Win32NT
PSCompatibleVersions {1.0,2.0,3.0,4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0
Visuals
No response
The text was updated successfully, but these errors were encountered:
for %%F in (CommonDocuments,CommonProgramFiles) do (
for %%O in (DoNotVerify,None) do (
pwsh.exe -c "[System.Environment]::GetFolderPath([System.Environment+SpecialFolder]::%%F,[System.Environment+SpecialFolderOption]::%%O)"
)
)
Prerequisites
Steps to reproduce
when running pwsh it gets stuck occasionally on some machines when using the flag(s)
-MTA
or-STA
after investigations it gets stuck on Interop+Shell32.SHGetKnownFolderPath .This happens even on a script that runs
pwsh.exe -MTA -NoProfile -Command "$PSVersionTable.PSVersion.ToString()"
This does not happen on all our developer machines (Running Win 10 22H2), so far we have not been able to pinpoint the difference.
Stacktrace:
Expected behavior
powershell should finish execution
Actual behavior
powershell gets stuck in a deadlock
Error details
No response
Environment data
Visuals
No response
The text was updated successfully, but these errors were encountered: