Vrftjkry

I just got a new computer with plenty of horsepower and its works fast everywhere except PowerShell. Some of the symptoms, which seem to be consistent:

• Opening PowerShell shows the copyright info and hangs there for 2 minutes before showing the prompt.


• I start typing a command and it takes almost a minute for the text to appear


• Once the text appears I can modify the command and it's responsive.


• I enter a simple command such as echo 'hello' and hit enter, it takes about 45 seconds for 'hello' to appear on the screen and another 45 seconds to return to the prompt.


• Once at the prompt it's responsive again.


• Run the dir command in my home directory (few files/folders), about 2:30 before listing the directory, another 15 seconds to go back to the prompt.


• I have plenty of memory left and CPU is near idle while it's hanging.

Some attempted troubleshooting:

• PowerShell ISE: Takes about 5 minutes to get to prompt.


• PowerShell ISE (x86): It works!


• PowerShell legacy console: No change.


• Opening up a regular command line and running powershell -NoProfile: No change.


• sfc /scannow: No problems found.


• Disable network connections: No change.


• Run Sysinternals procmon: Nothing obvious, but it always seems to hang right after some of the "Thread Exit" operations.


• Look at thread stacks in Sysinternals procexp: When it's hanging the main thread is always at ntdll.dll ZwWaitForMultipleObjects.


• Uninstall WSL/Hyper-V: No change.


• Enable WinRM (winrm quickconfig): The service starts, but then it can't connect.
  
  
  
  
  • I can see port 5985 is being listened to by PID 4 when the service is started.
  
  
  • The Windows Firewall has the two "Windows Remote Management (HTTP-In)" entries for port 5985 (allow any remote address when in a private network/profile).
  
  
  • I can successfully telnet localhost 5985
    
  
  
  • After the WinRM service starts it takes about 7 minutes for it to respond with:
  
  
  
  

WSManFault
...

Error number: -2144108250 0x80338126
WinRM cannot complete the operation. Verify that the specified computer name is valid, that the computer is accessible over the
network, and that a firewall exception for the WinRM service is
enabled and allows access from this computer. By default, the WinRM
firewall exception for public profiles limits access to remote
computers within the same local subnet.

The consistency in the delays makes me think there is some type of attempted connection and timeout, but I'm at a loss as to what that may be. Any gurus out there with ideas?

Thanks to the antivirus comment at https://stackoverflow.com/questions/45021585/powershell-hangs-on-launch! I had Bitdefender Antivirus installed. Disabling it didn't fix the problem, but uninstalling did. I tried reinstalling and the problem reappeared. Adding all of C: to the exclusion list did not fix the issue.