Re: removing cmd.exe
From: Karl Levinson [x y] mvp (levinson_k@excite.com)
Date: 02/20/03
- Next message: Karl Levinson [x y] mvp: "Re: Is this to say email source is not all it is cracked up to be?"
- Previous message: |{evin: "Re: firewall protection"
- In reply to: richard: "removing cmd.exe"
- Next in thread: Mark Strelecki, ACP: "Re: removing cmd.exe"
- Reply: Mark Strelecki, ACP: "Re: removing cmd.exe"
- Reply: Ryan: "Re: removing cmd.exe"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "Karl Levinson [x y] mvp" <levinson_k@excite.com> Date: Wed, 19 Feb 2003 22:27:43 -0500
Yeah, that's a problem with the Windows 2000 system file checker feature.
You can disable that feature, but personally I like having it on as it
monitors file versions and replaces some of the missing ones.
You can get rid of the file [for now anyways] by deleting the file first
from the hidden \dllcache\ folder [believe it's
windowsroot\system32\dllcache\ if I remember correctly] and then deleting
the actual file in the location you're aware of [usually the system32
folder]. Depending on your system file checker settings, you may keep
getting messages in your log file about the missing file, and you may even
get one or many popups about it. Also, the file might be reinstalled later,
for example by a future service pack or security patch. It might make sense
to keep the file but prevent everyone from reading or executing it
[especially IUSR, localsystem, users, guests, and maybe even
administrators]. That way, the permissions stay, even if the file is
replaced or overwritten at a later date without your knowledge.
Searching www.microsoft.com/support will give you more information about how
the SFC feature works, but I don't believe there's a good way for you to
control it very well, besides being able to turn it off completely or launch
a scan for missing files.
"richard" <rodierfl@hotmail.com> wrote in message
news:022a01c2d874$135d4200$a501280a@phx.gbl...
> hello all,
>
> i need to remove cmd.exe for security reasons.
> when i remove it w2k keeps putting it back in. i have
> removed it from other systems and the o/s would ask if i
> was sure i want to remove it, allowing me to confirrm the
> removal.
>
> how can i force the cmd.exe to stay gone?
>
> thank you
>
> richard
>
- Next message: Karl Levinson [x y] mvp: "Re: Is this to say email source is not all it is cracked up to be?"
- Previous message: |{evin: "Re: firewall protection"
- In reply to: richard: "removing cmd.exe"
- Next in thread: Mark Strelecki, ACP: "Re: removing cmd.exe"
- Reply: Mark Strelecki, ACP: "Re: removing cmd.exe"
- Reply: Ryan: "Re: removing cmd.exe"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
