up vote 1 down vote favorite
share [g+] share [fb]

cmd.exe and command.com doesn't open instantly - Instead I get a 5 second delay upon running them(either from clicking the files, or running them from 'run'). I tried Googling it, but alas. Finally I just accepted it.

So now I've started coding some basic stuff with MS Visual Studio and now the command prompt won't even open after compiling. Also, if I have MS Visual Studio running, I cannot run command prompt in any way. It just queues up as a process in the taskmgr.

Anyone got any relevant info/tips/fixes? Not only am I not able to code, but now I can't even do basic stuff in my command prompt like ping or tracert.

link|improve this question
Here's a prntscrn of my taskmgr. bildr.no/view/684709 – Aleks Jul 12 '10 at 14:30
1  
What exactly is "MS Visual"? – Hello71 Jul 12 '10 at 15:11
Microsoft Visual. In this case Microsoft Visual C++ 2010 Express. – Aleks Jul 12 '10 at 15:45
When you say "MS Visual running, I cannot run command prompt in any way" do you mean "When I'm debugging and are stopped on a breakpoint?" – Rowland Shaw Jul 12 '10 at 16:09
1  
Crosspost of superuser.com/questions/162699/… – Hello71 Jul 12 '10 at 16:16
feedback

2 Answers

up vote 1 down vote

You could try running another Sysinternals tool: Process Monitor. That will tell you about file and registry access (you will probably want to use filtering on the output, to reduce clutter).

Also have a look at this page which describes AutoRun settings for cmd.exe in the registry.

Possibly the following Registry keys have some commands which are being run when you start the command prompt:

HKEY_LOCAL_MACHINE\Software\Microsoft\Command Processor\AutoRun

or

HKEY_CURRENT_USER\Software\Microsoft\Command Processor\AutoRun
link|improve this answer
feedback
up vote 0 down vote

Fist thing that I would do is run Process Explorer check process tree and handles form cmd.exe . Kill unusual things from the process tree one by one and see what happens ;) (make sure you don't have any unsaved and important data open just in case you will kill some innocent program ;)

link|improve this answer
Well I'm only running like 7 processes(explorer.exe), and I see nothing malicious in process explorer. So yeah ;> No memory jam or CPU problems iether. My comp is running just fine, it's just the command prompt that is 'broken' :( – Aleks Jul 12 '10 at 19:08
feedback

Your Answer

 
or
required, but never shown
discard

Not the answer you're looking for? Browse other questions tagged or ask your own question.