1

Using powershell is almost impossible. It takes almost 6 minutes to load on a pretty fast computer.

enter image description here I think it might be relevant that I use cmder and scoop. It's also slow in cmder.

What can I do to solve it or at least find the cause?

It's a company pc and uses Sentinel One as antivirus, which I cannot modify.

enter image description here

13
  • Does this or this answer your question? Have you tried installing PowerShell 7 to see if there is any difference?
    – Ramhound
    Nov 2, 2021 at 13:58
  • @Ramhound sadly no, however I added some details in my question about antivirus
    – Thomas
    Nov 2, 2021 at 14:20
  • You should check what’s in the Powershell startup files. This answer could be of help.
    – Daniel B
    Nov 2, 2021 at 14:28
  • 1
    If all suggestions fail, with some skill, you can use the sysinternals process monitor to see what it is actually doing under the hood. The tool is frustrating to master but can tell you things that nothing else can. Nov 2, 2021 at 14:35
  • 1
    If your computer is domain joined, ask a collegue to log into your computer and let them start Powershell. This will determine if the problem is somewhere in your user profile or settings, or something local to your computer. Alternatively, if you are not domain joined, create a 2nd user, login with it and test there.
    – LPChip
    Nov 2, 2021 at 18:29

1 Answer 1

0

After debugging some time with our sysadmin we found out that the presence of %USERPROFILE%\scoop\apps in the psmodulepath Environment Variable for the user was the culprit.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.