7

When I go to Run and type cmd, it takes about 7-8 seconds for the command prompt to appear.

I have a Core i5 with 3GB of RAM running Windows 7 x86.

I really need the command prompt to run instantly because I use a lot of scripts to improve productivity. When the command prompt itself takes 7 seconds to load, the whole point is lost.

Does anyone have ideas as to what might be causing these delays?

Improve this question
3
  • 1
    If your goal is efficiency, why not pin the command prompt to the taskbar and start it with Win+Number hotkeys or a single mouse click?
    – Oliver Salzburg
    Commented Jul 28, 2012 at 13:58
  • As @OliverSalzburg suggested you is the best way but still we need little bit more information as this happens only when you launch the 'cmd' through Run command or the same problem when you launch it from the start menu?
    – avirk
    Commented Jul 28, 2012 at 14:04
  • thank you for the answers. My issue is that cmd takes a long time to load, whether i load it through Run, or even by double clicking on cmd.exe or even if i execute any batch file. are there any monitoring tools i can use to check what's going on under the hood when cmd loads?
    – Nandun
    Commented Jul 30, 2012 at 14:37

3 Answers 3

Reset to default
7

  1. Download Process Monitor.

  2. Filter the output such that you're only looking at a Process Name of conhost.exe or cmd.exe.

    enter image description here

  3. Add the Duration column to the output.

    enter image description here enter image description here

  4. Fire up a cmd.exe and see what's going on.

Improve this answer
2
  • Nice edit, Oliver!
    – Simon Catlin
    Commented Jul 28, 2012 at 21:48
  • /@Oliver Salzburg. Wow, thanks you so much for a great answer. I will try these out now.
    – Nandun
    Commented Jul 30, 2012 at 14:40
0

I think this is related to your home drive. If you open cmd.exe and by default it takes you to a mapped network drive, that could be the issue.

Basically, when I was connected via a VPN that didn't allow my on-site network mappings, cmd.exe would take a good ~10 seconds to open up.

Improve this answer
0

user810816 had the correct answer for me. On VPN, I had a lag of up to 50 seconds before CMD would even open.

On the start menu, right click to show file location, then right click again and edit the properties to "start in" a local drive, such as c:. The default variables resulted in a slow-to-access network location...

The load time is now almost instantaneous.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .