Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations John Tel on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Command Prompt won't close

Status
Not open for further replies.

snootalope

IS-IT--Management
Jun 28, 2001
1,706
US
I've had this ongoing issue when I open a command prompt window. When I type Exit or even just hit the X in the top right, the window doesn't close. However, the taskmgr doesn't even show the CMD.EXE process running still. The window stays there with the blinking cursor and i can't do anything with it. Can't type in it, hitting the X repeatedly does nothing.

I'm at SP3 now, but it was also doing this at SP2.

I can't even restart the machine when this happens. If i do start | Shutdown | Restart/Shutdown - it never does anything. I can continue to work as normal, but it'll never restart. The only way to get the window to disappear is holding the power button till it turns off.

It doesn't do this everytime, just every now and then. Really, really annoying.

Done numerous virus scans and the system is clean.

Anyone else ever experience this?
 
What happens if you open a second or third Cmd.exe, and then, if you can, close the later cmd.exes?

This is my version of cmd.exe on SP3, how does it compare to yours?

C:\WINDOWS\system32
5.1.2600.5512
380 KB (389,120 bytes)

It sounds to me that the cdm.exe is not actually loading correctly in the first place when this problem occurs.

You could try replacing the cmd.exe in System32 with another one from a similar system. You probably have to do such a maneuver outside of the Windows environment.

Replacing missing dll file
thread779-1503492
 
Yo.

Once a console window freezes up, I can open as many other command windows and they'll all close except the one that's stuck.

file version:

C:\WINDOWS\system32
5.1.2600.5512
380 KB (389,120 bytes)
(xpsp.080413-2111)

Good thinking about trying another executable.. I'll give a whirl.
 
sounds more like an Explorer issue than the CMD.EXE issue...

grab your XP CD and have it handy...

then in the RUN BOX or a CMD window type the following command: SFC /SCANNOW

this will ensure that all your system files are not corrupted and if they are will get replaced with ones that are not... insert the xp cd when prompted...



Ben

"If it works don't fix it! If it doesn't use a sledgehammer..."
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top