I've ran 50k iterations on 7.2.5 without repro.
@g-chauvel what is the repro machine specs? Is it under high load from some other processes when the PS hang happens?

@anmenaga corporate managed PCs with monitoring services and antivirus. Happens at least on 2 different hardware with the same software environment, idle state.

@g-chauvel Have the PCs Internet connect? If no please try to disable new PowerShell version check and telemetry.

@iSazonov
I tried with

$env:POWERSHELL_CLI_TELEMETRY_OPTOUT=1
$env:POWERSHELL_TELEMETRY_OPTOUT=1
$env:POWERSHELL_UPDATECHECK="Off"
$env:POWERSHELL_UPDATECHECK_OPTOUT=1
$env:DOTNET_CLI_TELEMETRY_OPTOUT=1
$env:DOTNET_TELEMETRY_OPTOUT=1
$env:COMPlus_EnableDiagnostics=0

same behavior

For anyone else out there, we experienced similar issues but on Linux instead of Windows.

We built a private docker image with pwsh 7.2.6 installed. On our nonprod servers the image worked perfectly fine. When we executed 'pwsh' it showed the version and produced a powershell prompt. On our production server when we ran 'pwsh' it just hung indefinitely.

This gave us the hint it wasn't really to do with the image itself and more to do with the software running on the servers themselves. Problem was, there was no logs to help us identify what it was.

Just for debugging purposes we tried the public powershell images too. 'mcr.microsoft.com/powershell:7.2.2-ubuntu-18.04' hung indefinitely on the production server but pwsh executed fine on nonprod server. 'mcr.microsoft.com/powershell:7.1.0-ubuntu-18.04' worked perfectly fine on both environments. The same behaviour was found on images based off of alpine too.

When trying 'mcr.microsoft.com/powershell:7.3.0-preview.3-ubuntu-18.04' we actually found our issue... We had an error relating to 'Dynatrace OneAgent' which injects itself into Docker containers as part of its monitoring. We had already thought of this and disabled the software but seemingly this wasn't enough.... when we removed that package from the production server, our image with pwsh 7.2.6 (and others) all worked in production again.

So for us, the issue was Dynatrace. The version of dynatrace we were running in prod was different to nonprod and this was causing the issues.

I have the same problem with pwsh 7.2.x. Interestingly, it does not happen with any 7.3-preview/rc, but happens again with 7.3.0. Yet, with 7.3.0 it seems to occur less often than with older releases.

My setup is similar to the one of g-chauvel: corporate managed machine with antivirus (that I cannot disable for testing). No DynaTrace OneAgent here, but other monitoring SW.

@g-chauvel - Thank you for reporting this issue. The working group is unable to repro this problem - as @anmenaga reported. In order to progress, the Working Group needs more information about the process, you may be able to collect the needed logs using Dotnet-dump. Contact https://support.microsoft.com/en-US for more assistance.

Microsoft Support

Microsoft support is here to help you with Microsoft products. Find how-to articles, videos, and training for Microsoft 365, Windows, Surface, and more.

Hi, I have the same issue on a corporate managed Windows 10 machine. Powershell 7.3.8 and Powershell 7.3.7 stucks infinite on launch. But 7.3.7 was running in the past. I don't know what changed.
If I have some spare time I will contact the support. But it would be much faster if someone can shortly show how to use dotnet-dump to collect the logs...

@theJasonHelmick
I encountered the same issue on my side, when I mount samba address to my windows as a virtual driver, the pwsh always attempt to perform the InitializeDefaultDrives operation on the 'FileSystem' provider when I launch a new pwsh tab or window, it will stuck and have nothing notice, until I stop and unmount the virtual dirvers, it will throw a Attempting to perform the InitializeDefaultDrives operation on the 'FileSystem' provider failed. failed message.

If anyone whom encounter the same issue, maybe cause by the same scene with me.

@g-chauvel - Thank you for this issue. We ran tests on 7.2.18, 7.3.11, 7.4.1, 7.5-preview 2 and were not able to reproduce on these current versions. If you wish to troubleshoot further and provide information using botnet dump, here are the docs to help: https://learn.microsoft.com/en-us/dotnet/core/diagnostics/dotnet-dump

dotnet-dump diagnostic tool - .NET CLI - .NET

Learn how to install and use the dotnet-dump CLI tool to collect and analyze Windows and Linux dumps without any native debugger.

The environnement where pwsh.exe is executed has changed since 2022.
I no longer face this problem : different antivirus, some monitoring services are no longer running, not the same Windows version/build, group policies, etc...

7.2.19 is not stuck. I bet 7.2.0 to 7.2.5 also aren't.

📣 Hey @g-chauvel, how did we do? We would love to hear your feedback with the link below! 🗣️

🔗 https://aka.ms/PSRepoFeedback

Microsoft Forms