|
#1
|
|||
|
|||
|
Had a customer come in with this problem:
Opens the Run window and types "CMD" It goes into an infinite loop requiring a Control C to stop it. The loop repeats "Copyright 1985-2001 Microsoft Windows XP version 5.1" Can't find any loops or nested loops causing this. Any ideas? |
|
#2
|
||||
|
||||
|
Could be in the shell registry key that has cmd.exe in it. You might try matching up the shell keys pertaining to cmd.exe in a good xp install with the one that is bad.
|
|
#3
|
||||
|
||||
|
Possibly something funky with the Autoexec.NT file.
__________________
Author of d7, and TONS of other FREE PC technician's tools. www.FoolishIT.com Checkout my videos on d7: An introduction to v6.6.x and Configuration Overview Also check out My Network Boot Setup details, and the comment thread. Boot diag CDs over the network / deploy Windows installs with updates, drivers, and pre-installed apps in minutes! |
|
#4
|
||||
|
||||
|
have him try "cmd /d" instead of "cmd"
see if that produces different results. |
|
#5
|
||||
|
||||
|
What about command.com?
__________________
put that in your pipe and grep it |
|
#6
|
|||
|
|||
|
Tried all the suggestion the only one that does not loop is "cmd /d"
Comparison of the shell registry with my own computer reveals nothing out of the ordinary. It's really weird. Typing "command" does not loop. |
|
#7
|
||||
|
||||
|
it's not the shell you have trouble with.
Check HKCU\Software\Microsoft\Command Processor for the presence of an Autorun value, and delete if found. Also check HKLM for the same.
__________________
Author of d7, and TONS of other FREE PC technician's tools. www.FoolishIT.com Checkout my videos on d7: An introduction to v6.6.x and Configuration Overview Also check out My Network Boot Setup details, and the comment thread. Boot diag CDs over the network / deploy Windows installs with updates, drivers, and pre-installed apps in minutes! |
|
#8
|
|||
|
|||
|
Have tried running sfc /scannow to make sure you got all the correct system files.
|
|
#9
|
|||
|
|||
|
Found the problem before logging on just now and noted the autorun solution from FoolishTech. It indeed was the autorun registry entry. I wiped it out
HKLM was clean. Contacted the customer who said he doesn't remember ever going into the registry and "changing" things around. Could be something he may have downloaded. Anyway thank all you guys for the inputs.
|
![]() |
| Thread Tools | |
| Display Modes | |
|
|