cmd.exe repeats when typed

If you type:

cmd /d

....into the "Run" box on the 'Start Menu', does it still show the same
symptoms

==


Cheers, Tim Meddick, Peckham, London.


"ChapBell" <ChapBell.DeleteThis@discussions.microsoft.com> wrote in message
news:8BFFE274-049D-438E-86FB-628B7A139460@microsoft.com...
> HELP! when I go to run cmd.exe the window opens and then the command runs
> and
> repeats 120 times as if I've typed it repeatedly. At the top of the window
> it
> shows the command C:\Windows\System32\cmd.exe -
> C:\Windows\System32\cmd.exe -
> (repeated).
>
> Inside the window it shows: <C> Copyright 1985-2001 Microsoft Corp.
> Microsoft Windows XP [Version
> 5.1.2600]
> and this is what repeats 120 times.
>
> I have run Malware and NOrton Anti-Virus and neither shows any malware or
> virus or spyware.
>
> If I go to the file and click on it, the same thing happens.
>
> Can anyone help?

Does your registry key

HKEY_LOCAL_MACHINE\Software\Microsoft\Command Processor\AutoRun have
something in it?

Mine is blank. I had a coworker with a similiar problem and he had
c:\Windows\System32\cmd.exe

YES, that was the line (See reply to TIM MEDDICk below). That was the line
that had it running 256 times, I believe...and I changed or deleted...its
been so long I don't remember which...but now it works.

Thanks.

"kkocks" wrote:

>
> Does your registry key
>
> HKEY_LOCAL_MACHINE\Software\Microsoft\Command Processor\AutoRun have
> something in it?
>
> Mine is blank. I had a coworker with a similiar problem and he had
> c:\Windows\System32\cmd.exe
>
>
>

If the OP tested starting 'cmd.exe' from the "Run" box with the '/d'
switch thus :

cmd.exe /d

....this would disable any 'AutoRun' (registry) commands PLUS would also
prevent commands written into AUTOEXEC.NT and CONFIG.NT from executing.

This was the advice I gave in my first post in this thread.

If the symptoms STILL persisted while starting 'cmd.exe' in this way,
then the problem must be elsewhere.

Since the OP has not re-posted, we will probably never know anyway...


==

Cheers, Tim Meddick, Peckham, London.




"\" <kkocks.3vtwxm.DeleteThis@no.email.invalid> wrote in message
news:kkocks.3vtwxm@no.email.invalid...
>
> Does your registry key
>
> HKEY_LOCAL_MACHINE\Software\Microsoft\Command Processor\AutoRun have
> something in it?
>
> Mine is blank. I had a coworker with a similiar problem and he had
> c:\Windows\System32\cmd.exe
>
>

Sorry,
For some reason i wasn't getting any emails that anyone had responded. I
didn't try the "cmd.exe /d" because I didn't know to.

But I did trace it. In the regedit I discovered there was a line in it on my
laptop that told the command to repeat 256 times.

I'm sorry to say, i don't remember where it was. I only found it by taking a
computer without the problem and searching its registry and when I found that
the two entries weren't the same I changed the one on the corrupt machine to
be like the good machine and I've had no problems since.

I'm guessing a spyware or malware did that, but why it wasn't caught is
beyond me. But, thankfully it is fixed now. Sorry for the length in reply and
thanks for those who tried to help.

"Tim Meddick" wrote:

> If the OP tested starting 'cmd.exe' from the "Run" box with the '/d'
> switch thus :
>
> cmd.exe /d
>
> ....this would disable any 'AutoRun' (registry) commands PLUS would also
> prevent commands written into AUTOEXEC.NT and CONFIG.NT from executing.
>
> This was the advice I gave in my first post in this thread.
>
> If the symptoms STILL persisted while starting 'cmd.exe' in this way,
> then the problem must be elsewhere.
>
> Since the OP has not re-posted, we will probably never know anyway...
>
>
> ==
>
> Cheers, Tim Meddick, Peckham, London.
>
>
>
>
> "\" <kkocks.3vtwxm.RemoveThis@no.email.invalid> wrote in message
> news:kkocks.3vtwxm@no.email.invalid...
> >
> > Does your registry key
> >
> > HKEY_LOCAL_MACHINE\Software\Microsoft\Command Processor\AutoRun have
> > something in it?
> >
> > Mine is blank. I had a coworker with a similiar problem and he had
> > c:\Windows\System32\cmd.exe
> >
> >
>
>
>

Chap,
I'm sincerely glad that you have solved the problem.

Replies to posts appear in the group you made the original post to in
the first place - and NOT to your "inbox" (unless the reply *was* sent
to you directly which is not encouraged).

Thusly, you have to keep checking your post to see if any replies have
joined to it making it into a "thread".

I would just like to add to the information pointed out by "kkocks"
(totally unfortunate name) that in addition to the key :

[HKEY_LOCAL_MACHINE\Software\Microsoft\Command Processor]
"AutoRun"=


....there is a similar key in the current user section :


[HKEY_CURRENT_USER\Software\Microsoft\Command Processor]
"AutoRun"=


....finally, there are two files in your "C:\WINDOWS\system32" folder,
called :

AUTOEXEC.NT
CONFIG.NT

....that function in a similar way to the Autoexec.bat & Config.sys files
of the old days of DOS.

Any commands typed into the first of these (AUTOEXEC.NT) will be
executed automatically every time 'cmd.exe' is started. The other file
(CONFIG.NT) is slightly different as only commands specific it are read,
such as the one to load a 'device driver' e.g. :

device=c:\windows\system32\ansi.sys

....would load the driver 'ansi.sys'

It is useful to know what configures the 'Command Prompt', to both save
time by knowing where to place commands that you will need to run in
every 'cmd.exe' window, and to track down problems like the one you have
had recently.

==

Cheers, Tim Meddick, Peckham, London.




"ChapBell" <ChapBell DeleteThis @discussions.microsoft.com> wrote in message
news:F4F1247E-5AB3-4265-AFD0-0762571F7D39@microsoft.com...
> YES, that was the line (See reply to TIM MEDDICk below). That was the
> line
> that had it running 256 times, I believe...and I changed or
> deleted...its
> been so long I don't remember which...but now it works.
>
> Thanks.
>
> "kkocks" wrote:
>
>>
>> Does your registry key
>>
>> HKEY_LOCAL_MACHINE\Software\Microsoft\Command Processor\AutoRun have
>> something in it?
>>
>> Mine is blank. I had a coworker with a similiar problem and he had
>> c:\Windows\System32\cmd.exe
>>
>>
>>