Extremely slow startup

[empz]

I've upgraded from version 1.3.6.678 to latest 1.3.11.843 and the startup is painfully slow. More than 5s.

I've even tried downloading a fresh copy of the mini release and put it into my C: drive (which is a Samsung 960 EVO) and it's the same.

Previous version loaded almost instantly.

[hed0n1st]

@eparizzi : are you a windows insider ? actually i have the same issue, and i actually wonder if its not related to windows itself... some of my programs accessible via right-click ( open with... ) are now pretty slow to launch ( eg. for IDEs or archives programs ). On the other side the cmd/powershell shift/right-click works pretty well.
Also i had activated the sandbox for windows defender, disabling it reduced the launchs...
( sorry for mistakes, english not primary )

[daxgames]

they are virtually the same for me:

[daxgames]

If I add /f to cmd::Cmder task 1.3.11is actually 1 second faster than1.3.6`

[SpeedySparrow]

@daxgames Could you provide a little more info on where exactly you put /f. I have tried several scenarios but all fail.

[daxgames]

@SpeedySparrow it's all In the README.md

[SpeedySparrow]

Thanks. It did improve my startup, not quite with your impressive results but still better.

[daxgames]

You can also do a /t and it will give you an exact time it takes to start. How long does it take?

[SpeedySparrow]

Aah, that's where you got that timer from:-). Well, my readings doesn't make much sense to me. 3 times with and without /f. Using Launchy but directly from C:\cmder seems to yield the same weird measures.

Without /f
Elapsed Time: 39:30:34.00 (142234.00s total)
Elapsed Time: 15:28:34.00 (55714.00s total)
Elapsed Time: 69:27:42.00 (250062.00s total)

With /f
Elapsed Time: 17:22:32.00 (62552.00s total)
Elapsed Time: 65:22:7.00 (235327.00s total)
Elapsed Time: 22:21:45.00 (80505.00s total)

[daxgames]

That is still crazy slow even with /f

[daxgames]

@SpeedySparrow do you have an antivirus/antimalware you can disable and try again. These could be slowing it down. If they are you might be able to exclude cmder from on access scans and get it back to full speed.

Just curious what hardware you running this on, processor, hdd type, and memory?

[daxgames]

Those times can't be right the fastest says it took 15+ minutes to start

[SpeedySparrow]

True, something must be wrong with the timings. In real time:-) it's more like 5-6 seconds. I am on a Lenovo T460s with:
Win10 - ver. 1511
i5-6300U @ 2.4 GHz
20 GB RAM
But is a corporate computer with all sorts of anti-virus and what have we that I can't disable. Guess I just have to live with it.

Still weird with the timings:-)

[daxgames]

@SpeedySparrow I personally know others with corporate laptops that have the similar complaints. Sorry not anything we can do about that.

[p1va]

I also noticed slowness on my corporate laptop but after disconnecting the network drives i saw a huge improvement in startup time when opening new bash consoles.
Hope it helps.