Jump to content

Cannot run cmd.exe


Recommended Posts

Posted

I have a Dell-8300 desktop with Windows XP Pro. The last time I was able to

run cmd.exe was about a month ago.

Today I found that I cannot run cmd.exe no matter where I tried it (I tried

to use Run and to double click the file under c:\windows\system32\cmd.exe).

In both cases I got the message "Windows cannot find

'C:\WINDOWS\SYSTEM32\cmd.exe'. Make sure you typed the name correctly, and

then try again. To search for a file, click the start button, and then click

Search". I replaced the cmd.exe from my backup disc but it didn't help. I

tried to copy and run the files at different locations, it did not help.

 

I later found out the same goes with regedit and msconfig. Others like

inetmgr still work by using Run or double-clicking. The interesting point is

that if I change the file names, for example from cmd.exe to cmdt.exe or from

regedit.exe to tregedit.exe, I can execute cmdt.exe and tregedit.exe using

Run or double-clicking within and outside (after copying) their default

directories.

 

I know this could be caused by virus and other software, but I just want to

know, based on the behavior described, which part of the windows components

has been affected and needs to be checked.

Posted

Re: Cannot run cmd.exe

 

Jikun wrote:

> I have a Dell-8300 desktop with Windows XP Pro. The last time I was able to

> run cmd.exe was about a month ago.

> Today I found that I cannot run cmd.exe no matter where I tried it (I tried

> to use Run and to double click the file under c:\windows\system32\cmd.exe).

> In both cases I got the message "Windows cannot find

> 'C:\WINDOWS\SYSTEM32\cmd.exe'. Make sure you typed the name correctly, and

> then try again. To search for a file, click the start button, and then click

> Search". I replaced the cmd.exe from my backup disc but it didn't help. I

> tried to copy and run the files at different locations, it did not help.

>

> I later found out the same goes with regedit and msconfig. Others like

> inetmgr still work by using Run or double-clicking. The interesting point is

> that if I change the file names, for example from cmd.exe to cmdt.exe or from

> regedit.exe to tregedit.exe, I can execute cmdt.exe and tregedit.exe using

> Run or double-clicking within and outside (after copying) their default

> directories.

>

> I know this could be caused by virus and other software, but I just want to

> know, based on the behavior described, which part of the windows components

> has been affected and needs to be checked.

 

if you start command.com, can you run them from there?

Posted

Re: Cannot run cmd.exe

 

I can run command.com from Run with the following prompt shown:

========================

Microsoft® Windows DOS

©Copyright Microsoft Corp 1990-2001.

 

C:\DOCUME~1\JIkun~1>

==========================

 

"jorgen" wrote:

> Jikun wrote:

> > I have a Dell-8300 desktop with Windows XP Pro. The last time I was able to

> > run cmd.exe was about a month ago.

> > Today I found that I cannot run cmd.exe no matter where I tried it (I tried

> > to use Run and to double click the file under c:\windows\system32\cmd.exe).

> > In both cases I got the message "Windows cannot find

> > 'C:\WINDOWS\SYSTEM32\cmd.exe'. Make sure you typed the name correctly, and

> > then try again. To search for a file, click the start button, and then click

> > Search". I replaced the cmd.exe from my backup disc but it didn't help. I

> > tried to copy and run the files at different locations, it did not help.

> >

> > I later found out the same goes with regedit and msconfig. Others like

> > inetmgr still work by using Run or double-clicking. The interesting point is

> > that if I change the file names, for example from cmd.exe to cmdt.exe or from

> > regedit.exe to tregedit.exe, I can execute cmdt.exe and tregedit.exe using

> > Run or double-clicking within and outside (after copying) their default

> > directories.

> >

> > I know this could be caused by virus and other software, but I just want to

> > know, based on the behavior described, which part of the windows components

> > has been affected and needs to be checked.

>

> if you start command.com, can you run them from there?

>

Posted

Re: Cannot run cmd.exe

 

Sorry, I forgot to mention that I tried regedit.exe, msconfig.exe and cmd.exe

using the command.exe prompt window. All did not bring up anything. However I

also tried the inetmgr command and it also did not bring up anything.

 

"Jikun" wrote:

> I can run command.com from Run with the following prompt shown:

> ========================

> Microsoft® Windows DOS

> ©Copyright Microsoft Corp 1990-2001.

>

> C:\DOCUME~1\JIkun~1>

> ==========================

>

> "jorgen" wrote:

>

> > Jikun wrote:

> > > I have a Dell-8300 desktop with Windows XP Pro. The last time I was able to

> > > run cmd.exe was about a month ago.

> > > Today I found that I cannot run cmd.exe no matter where I tried it (I tried

> > > to use Run and to double click the file under c:\windows\system32\cmd.exe).

> > > In both cases I got the message "Windows cannot find

> > > 'C:\WINDOWS\SYSTEM32\cmd.exe'. Make sure you typed the name correctly, and

> > > then try again. To search for a file, click the start button, and then click

> > > Search". I replaced the cmd.exe from my backup disc but it didn't help. I

> > > tried to copy and run the files at different locations, it did not help.

> > >

> > > I later found out the same goes with regedit and msconfig. Others like

> > > inetmgr still work by using Run or double-clicking. The interesting point is

> > > that if I change the file names, for example from cmd.exe to cmdt.exe or from

> > > regedit.exe to tregedit.exe, I can execute cmdt.exe and tregedit.exe using

> > > Run or double-clicking within and outside (after copying) their default

> > > directories.

> > >

> > > I know this could be caused by virus and other software, but I just want to

> > > know, based on the behavior described, which part of the windows components

> > > has been affected and needs to be checked.

> >

> > if you start command.com, can you run them from there?

> >

Posted

Re: Cannot run cmd.exe

 

Jikun wrote:

>

> I later found out the same goes with regedit and msconfig. Others like

> inetmgr still work by using Run or double-clicking. The interesting point is

> that if I change the file names, for example from cmd.exe to cmdt.exe or from

> regedit.exe to tregedit.exe, I can execute cmdt.exe and tregedit.exe using

> Run or double-clicking within and outside (after copying) their default

> directories.

 

Schedule a bootscan so Avast! can remove the threats before they take

control of a session.

> I know this could be caused by virus and other software, but I just want to

> know, based on the behavior described, which part of the windows components

> has been affected and needs to be checked.

 

The Registry. Since your av has been compromised by the malware, a scan

of the registry files won't really show anything.

 

--

Joe =o)

Posted

Re: Cannot run cmd.exe

 

Jikun wrote:

> I have a Dell-8300 desktop with Windows XP Pro. The last time I was

> able to run cmd.exe was about a month ago.

> Today I found that I cannot run cmd.exe no matter where I tried it (I

> tried to use Run and to double click the file under

> c:\windows\system32\cmd.exe). In both cases I got the message

> "Windows cannot find 'C:\WINDOWS\SYSTEM32\cmd.exe'. Make sure you

> typed the name correctly, and then try again. To search for a file,

> click the start button, and then click Search". I replaced the

> cmd.exe from my backup disc but it didn't help. I tried to copy and

> run the files at different locations, it did not help.

>

> I later found out the same goes with regedit and msconfig. Others like

> inetmgr still work by using Run or double-clicking. The interesting

> point is that if I change the file names, for example from cmd.exe to

> cmdt.exe or from regedit.exe to tregedit.exe, I can execute cmdt.exe

> and tregedit.exe using Run or double-clicking within and outside

> (after copying) their default directories.

>

> I know this could be caused by virus and other software, but I just

> want to know, based on the behavior described, which part of the

> windows components has been affected and needs to be checked.

 

Yes, you have been infected with something. However you can use emergency

copies of these commands while you clean your system.

 

Emer. copies can be downloaded here:

http://www.kellys-korner-xp.com/xp_tweaks.htm

Line 35 left hand side.

 

After you clean your system run the edit on line 275 left hand side, I

believe this one will restore the original funtions.

Note: cmd.,regeit and taskmgr are not gone,whatever nasty you have just

disabled your access to them. Line 275 should restore this.

 

Here is a link for virus/trojan scanners

http://virusall.com/downscan.html

 

Good luck!

 

--

Mike Pawlak

Posted

Re: Cannot run cmd.exe

 

I tried the bootscan and avast!. It cleaned up some viruses. Thanks!

But the problems still remain.

 

"Elmo" wrote:

> Jikun wrote:

> >

> > I later found out the same goes with regedit and msconfig. Others like

> > inetmgr still work by using Run or double-clicking. The interesting point is

> > that if I change the file names, for example from cmd.exe to cmdt.exe or from

> > regedit.exe to tregedit.exe, I can execute cmdt.exe and tregedit.exe using

> > Run or double-clicking within and outside (after copying) their default

> > directories.

>

> Schedule a bootscan so Avast! can remove the threats before they take

> control of a session.

>

> > I know this could be caused by virus and other software, but I just want to

> > know, based on the behavior described, which part of the windows components

> > has been affected and needs to be checked.

>

> The Registry. Since your av has been compromised by the malware, a scan

> of the registry files won't really show anything.

>

> --

> Joe =o)

>

Posted

Re: Cannot run cmd.exe

 

After clearned up the system, I tried the script file you refered to - line

275 on the left side (Lift Restrictions - TM, Regedit and CMD). I really

hoped this would solved the problems, but the problems remain. It seems to me

that the system has been set in such a way that the specified command names

can not been recognized or executed. But I don't know how to reverse it.

 

"MAP" wrote:

> Jikun wrote:

> > I have a Dell-8300 desktop with Windows XP Pro. The last time I was

> > able to run cmd.exe was about a month ago.

> > Today I found that I cannot run cmd.exe no matter where I tried it (I

> > tried to use Run and to double click the file under

> > c:\windows\system32\cmd.exe). In both cases I got the message

> > "Windows cannot find 'C:\WINDOWS\SYSTEM32\cmd.exe'. Make sure you

> > typed the name correctly, and then try again. To search for a file,

> > click the start button, and then click Search". I replaced the

> > cmd.exe from my backup disc but it didn't help. I tried to copy and

> > run the files at different locations, it did not help.

> >

> > I later found out the same goes with regedit and msconfig. Others like

> > inetmgr still work by using Run or double-clicking. The interesting

> > point is that if I change the file names, for example from cmd.exe to

> > cmdt.exe or from regedit.exe to tregedit.exe, I can execute cmdt.exe

> > and tregedit.exe using Run or double-clicking within and outside

> > (after copying) their default directories.

> >

> > I know this could be caused by virus and other software, but I just

> > want to know, based on the behavior described, which part of the

> > windows components has been affected and needs to be checked.

>

> Yes, you have been infected with something. However you can use emergency

> copies of these commands while you clean your system.

>

> Emer. copies can be downloaded here:

> http://www.kellys-korner-xp.com/xp_tweaks.htm

> Line 35 left hand side.

>

> After you clean your system run the edit on line 275 left hand side, I

> believe this one will restore the original funtions.

> Note: cmd.,regeit and taskmgr are not gone,whatever nasty you have just

> disabled your access to them. Line 275 should restore this.

>

> Here is a link for virus/trojan scanners

> http://virusall.com/downscan.html

>

> Good luck!

>

> --

> Mike Pawlak

>

>

>

Guest Pegasus \(MVP\)
Posted

Re: Cannot run cmd.exe

 

How come your own virus scanner did not detect the

viruses? Did not have one?

 

If you want a really stable machine then you should back

up all your important documents, then re-install Windows,

allowing the disk to be formatted in the process.

 

If you prefer to live on the edge then you could scan your

system with the "House Call" option of Trend

(http://us.trendmicro.com/us/home/index.html). It may or

may not undo the damage done by your viruses.

 

 

"Jikun" <Jikun@discussions.microsoft.com> wrote in message

news:E8F190F2-EB9C-45F1-92C2-C800EB23DBA3@microsoft.com...

>I tried the bootscan and avast!. It cleaned up some viruses. Thanks!

> But the problems still remain.

>

> "Elmo" wrote:

>

>> Jikun wrote:

>> >

>> > I later found out the same goes with regedit and msconfig. Others like

>> > inetmgr still work by using Run or double-clicking. The interesting

>> > point is

>> > that if I change the file names, for example from cmd.exe to cmdt.exe

>> > or from

>> > regedit.exe to tregedit.exe, I can execute cmdt.exe and tregedit.exe

>> > using

>> > Run or double-clicking within and outside (after copying) their default

>> > directories.

>>

>> Schedule a bootscan so Avast! can remove the threats before they take

>> control of a session.

>>

>> > I know this could be caused by virus and other software, but I just

>> > want to

>> > know, based on the behavior described, which part of the windows

>> > components

>> > has been affected and needs to be checked.

>>

>> The Registry. Since your av has been compromised by the malware, a scan

>> of the registry files won't really show anything.

>>

>> --

>> Joe =o)

>>

Posted

Re: Cannot run cmd.exe

 

=?Utf-8?B?SmlrdW4=?= wrote:

>

> I have a Dell-8300 desktop with Windows XP Pro. The last time I was able to

> run cmd.exe was about a month ago.

> Today I found that I cannot run cmd.exe no matter where I tried it (I tried

> to use Run and to double click the file under c:\windows\system32\cmd.exe).

> In both cases I got the message "Windows cannot find

> 'C:\WINDOWS\SYSTEM32\cmd.exe'. Make sure you typed the name correctly, and

> then try again. To search for a file, click the start button, and then click

> Search". I replaced the cmd.exe from my backup disc but it didn't help. I

> tried to copy and run the files at different locations, it did not help.

>

> I later found out the same goes with regedit and msconfig. Others like

> inetmgr still work by using Run or double-clicking. The interesting point is

> that if I change the file names, for example from cmd.exe to cmdt.exe or from

> regedit.exe to tregedit.exe, I can execute cmdt.exe and tregedit.exe using

> Run or double-clicking within and outside (after copying) their default

> directories.

 

An indication that you are infected with spyware or a virus, I dont

remember which, but I do recall that some sort of malware creates

exactly the same problem.

 

 

--

http://www.bootdisk.com/

Posted

Re: Cannot run cmd.exe

 

 

"Plato" <|@|.|> wrote in message

news:46e07e36$1$271$bb4e3ad8@newscene.com...

> =?Utf-8?B?SmlrdW4=?= wrote:

>>

>> I have a Dell-8300 desktop with Windows XP Pro. The last time I was able

>> to

>> run cmd.exe was about a month ago.

>> Today I found that I cannot run cmd.exe no matter where I tried it (I

>> tried

>> to use Run and to double click the file under

>> c:\windows\system32\cmd.exe).

>> In both cases I got the message "Windows cannot find

>> 'C:\WINDOWS\SYSTEM32\cmd.exe'. Make sure you typed the name correctly,

>> and

>> then try again. To search for a file, click the start button, and then

>> click

>> Search". I replaced the cmd.exe from my backup disc but it didn't help. I

>> tried to copy and run the files at different locations, it did not help.

>>

>> I later found out the same goes with regedit and msconfig. Others like

>> inetmgr still work by using Run or double-clicking. The interesting point

>> is

>> that if I change the file names, for example from cmd.exe to cmdt.exe or

>> from

>> regedit.exe to tregedit.exe, I can execute cmdt.exe and tregedit.exe

>> using

>> Run or double-clicking within and outside (after copying) their default

>> directories.

>

> An indication that you are infected with spyware or a virus, I dont

> remember which, but I do recall that some sort of malware creates

> exactly the same problem.

 

Reads like a call for David Lippman's multiAV.

 

http://www.elephantboycomputers.com/page2.html#Viruses_Malware

Posted

Re: Cannot run cmd.exe

 

Found the virus that caused the problem. Virus description and solution can

be found here:

http://www.trendmicro.com/vinfo/virusencyclo/default5.asp?VName=BKDR%5FDELF%2EGAX&VSect=Sn

 

Thanks all

Jikun

 

"Frank" wrote:

>

> "Plato" <|@|.|> wrote in message

> news:46e07e36$1$271$bb4e3ad8@newscene.com...

> > =?Utf-8?B?SmlrdW4=?= wrote:

> >>

> >> I have a Dell-8300 desktop with Windows XP Pro. The last time I was able

> >> to

> >> run cmd.exe was about a month ago.

> >> Today I found that I cannot run cmd.exe no matter where I tried it (I

> >> tried

> >> to use Run and to double click the file under

> >> c:\windows\system32\cmd.exe).

> >> In both cases I got the message "Windows cannot find

> >> 'C:\WINDOWS\SYSTEM32\cmd.exe'. Make sure you typed the name correctly,

> >> and

> >> then try again. To search for a file, click the start button, and then

> >> click

> >> Search". I replaced the cmd.exe from my backup disc but it didn't help. I

> >> tried to copy and run the files at different locations, it did not help.

> >>

> >> I later found out the same goes with regedit and msconfig. Others like

> >> inetmgr still work by using Run or double-clicking. The interesting point

> >> is

> >> that if I change the file names, for example from cmd.exe to cmdt.exe or

> >> from

> >> regedit.exe to tregedit.exe, I can execute cmdt.exe and tregedit.exe

> >> using

> >> Run or double-clicking within and outside (after copying) their default

> >> directories.

> >

> > An indication that you are infected with spyware or a virus, I dont

> > remember which, but I do recall that some sort of malware creates

> > exactly the same problem.

>

> Reads like a call for David Lippman's multiAV.

>

> http://www.elephantboycomputers.com/page2.html#Viruses_Malware

>

>

>

>

Posted

Re: Cannot run cmd.exe

 

I used the House Call, but it hung all the time. Only after I found out the

virus, I knew that I have to turn off the system restore to let House Call to

do the scan in this case. But I still had to clean it up manually based on

the solution given by Trend Micro.

 

"Pegasus (MVP)" wrote:

> How come your own virus scanner did not detect the

> viruses? Did not have one?

>

> If you want a really stable machine then you should back

> up all your important documents, then re-install Windows,

> allowing the disk to be formatted in the process.

>

> If you prefer to live on the edge then you could scan your

> system with the "House Call" option of Trend

> (http://us.trendmicro.com/us/home/index.html). It may or

> may not undo the damage done by your viruses.

>

>

> "Jikun" <Jikun@discussions.microsoft.com> wrote in message

> news:E8F190F2-EB9C-45F1-92C2-C800EB23DBA3@microsoft.com...

> >I tried the bootscan and avast!. It cleaned up some viruses. Thanks!

> > But the problems still remain.

> >

> > "Elmo" wrote:

> >

> >> Jikun wrote:

> >> >

> >> > I later found out the same goes with regedit and msconfig. Others like

> >> > inetmgr still work by using Run or double-clicking. The interesting

> >> > point is

> >> > that if I change the file names, for example from cmd.exe to cmdt.exe

> >> > or from

> >> > regedit.exe to tregedit.exe, I can execute cmdt.exe and tregedit.exe

> >> > using

> >> > Run or double-clicking within and outside (after copying) their default

> >> > directories.

> >>

> >> Schedule a bootscan so Avast! can remove the threats before they take

> >> control of a session.

> >>

> >> > I know this could be caused by virus and other software, but I just

> >> > want to

> >> > know, based on the behavior described, which part of the windows

> >> > components

> >> > has been affected and needs to be checked.

> >>

> >> The Registry. Since your av has been compromised by the malware, a scan

> >> of the registry files won't really show anything.

> >>

> >> --

> >> Joe =o)

> >>

>

>

>


×
×
  • Create New...