Re: removing cmd.exe

From: Mark Strelecki, ACP (be6-508@nospam.strelecki.com)
Date: 02/20/03

  • Next message: Ryan: "Re: removing cmd.exe"
    From: " Mark Strelecki, ACP" <be6-508@nospam.strelecki.com>
    Date: Thu, 20 Feb 2003 00:22:38 -0500
    
    

    Hi, Karl -

    Are we talking about SFC (system file checker) or WFP (Windows file
    protection)?

    I thought SFC was a program you ran when you needed it, and not something
    you "turned off".

    WFP, on the other hand, is an OS "feature" that some would LOVE to just
    "turn off".

    Just checking with you, Beta Warrior.

    --
    Mark Strelecki,  ACP         BE6-508.XP2800.030111
    Atlanta, GA. - Computing and Programming Since 1975
    I MAKE IT GO!  ©
    http://www.strelecki.com/links.html
    --------------------------------------
    "I think the sole purpose of our inventions
    is to fill our needs to be mad at something."
    Paul Roussin, August, 2002
    "Karl Levinson [x y] mvp" <levinson_k@excite.com> wrote in message
    news:eOW25CJ2CHA.1640@TK2MSFTNGP10.phx.gbl...
    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.
    


    Relevant Pages

    • Re: removing cmd.exe
      ... SFC is the command line frontend that allows some control over the WFP ... > Are we talking about SFC (system file checker) or WFP (Windows file ... > WFP, on the other hand, is an OS "feature" that some would LOVE to just ...
      (microsoft.public.security)
    • Re: System Error
      ... Administrators group to run sfc", ... you should be asking Canon - not Microsoft - about this. ... zoombrowzer and photo edit utilities not the WIA drivers from the camera. ... > A question regarding your info on the system file checker. ...
      (microsoft.public.windowsxp.basics)
    • Re: Reinstalling Windows Components
      ... In the command prompt type: ... MicrosoftWindows XP Windows File Checker Version 5.1??? ... System File Checker (sfc) help... ... Description of Windows XP and Windows Server 2003 System File Checker ...
      (microsoft.public.windowsxp.newusers)
    • Re: SP2 broke my SFC
      ... > I've been struggling with a problem regarding the system file checker ... SFC worked fine prior to sp2 install. ... > and I did try each fix suggested there. ...
      (microsoft.public.windowsxp.basics)
    • Re: Event viewer & system health report issues
      ... SFC (System File Checker) It has been reconfigured under the hood a bit differently in Vista but works the same. ... Get an elevated cmd prompt by typing cmd in search above the start button>right click cmd when it pops up>run as administrator. ... If Startup Repair does not work, Run the bootrec.exe tool by using these switches. ...
      (microsoft.public.windows.vista.general)