Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

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?

share|improve this question

migrated from Jul 26 '12 at 1:15

This question came from our site for professional and enthusiast programmers.

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 Jul 28 '12 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 Jul 28 '12 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 Jul 30 '12 at 14:37

I'm guessing you mean that it takes a while for the actual link to show up rather than running cmd.

I also had this problem a while ago and it was because I had lots of files that the "Run" box trawls through in order to find a match. This link here helped a lot.

share|improve this answer
  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.

share|improve this answer
Nice edit, Oliver! – Simon Catlin Jul 28 '12 at 21:48
/@Oliver Salzburg. Wow, thanks you so much for a great answer. I will try these out now. – Nandun Jul 30 '12 at 14:40

You must log in to answer this question.

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