cmd.exe causes loading of Windows XP to hang

[blazer]

After the user on the network logs in, the desktop doesn't
appear and the system seems to hang on the user's desktop
background but no icons appear nor does the start button.
If I go into Task Manager and end the process called
"cmd.exe", Windows loads up normally. Does anyone know
what could cause this to hang, or any way around this?
Thanks so much for your help.

 

[James Krawisz]

I saw something similar in our environment where cmd.exe nad net.exe would
hang the systems at login. We tracked it down to an extra drive mapping
that was being duplicated via first the login script and secondly by a GPO,
once either one had been removed, the issue cleared itself up.

Jim

 

[blazer]

Jim,

Thank you so much for your reply. Your situation sounds
very much like mine. I have also noticed that net.exe has
caused a program to hang once we entered into windows. So
the cmd.exe and net.exe could be very much connected as you
say. So, what would you suggest I do first to correct this
issue? How could I verify/check the "extra drive mapping"
you were describing? Also, what exactly am I looking for
as far as the GPO is concerned? Thank you so much for your
help!

 

[Alex Nichol]

Thank you so much for your reply. Your situation sounds
very much like mine. I have also noticed that net.exe has
caused a program to hang once we entered into windows. So
the cmd.exe and net.exe could be very much connected as you
say. So, what would you suggest I do first to correct this
issue?

CMD is the Dos Emulations command shell - what you run when you do an
All Programs - Accessories - Command Prompt. So it looks as if you have
something at startup trying to run through it;

Either it is to run net.exe if that is some old legacy version network
program, or else probably malware, there is no normal reason for it. So
Start - Run - MSConfig.exe, look on the Startup page for a line where
cmd.exe is in the Command column (and check what comes after in that
column, which is what it is being asked to run). Uncheck the line, exit
and reboot to see how things go.

I would then read up advice on cleaning and protecting at
http://rgharper.mvps.org/cleanit.htm