4 ms·
Not the person you responded to but I have the same experience with Powershell as them. I just checked again to be sure and it takes 20s to start and become usa
by Narishma 6y ago
Not the person you responded to but I have the same experience with Powershell as them. I just checked again to be sure and it takes 20s to start and become usable on my laptop. CMD.EXE, in comparison, starts instantly.
- Shared404 6y agoI'll be the next to confirm this, and on multiple machines. Maybe 1 in 5 that I try will be a reasonable startup time.
- vetinari 6y agoThat's interesting, it seems quite widespread. I'm getting 1-2s on my machines, both just plain powershell and powershell inside windows terminal. No enterprise crap running though, just Defender.
- Shared404 6y agoIt got bad enough I wrote a (now unused) script in batch instead of Powershell. Also having to explicitly enable scripting for each machine was a pain, though understandable.