|
|
|
|
|
by bitcrazed
2883 days ago
|
|
You mention Hyper. Are you running PowerShell connected to Hyper or Console? If you're running Hyper, note that this alone takes 6s to (warm) start Cmd on my 16GB RAM Core-i7 Surface Pro 4. PowerShell takes ~1.2s to (warm) start connected to Console, while also starting a half dozen modules and scripts in my PowerShell user profile. PowerShell takes < .7s to start when run with `-NoProfile` |
|