Re: services.exe nee fscan

From: Robert Moir (bofh@mvps.org)
Date: 12/19/02


From: "Robert Moir" <bofh@mvps.org>
Date: Thu, 19 Dec 2002 10:10:45 -0000

George Hester wrote:
> I have a file in C:\WINNT\system32\drivers it is called services.exe
> and it looks like it is being called at boot. I will investigate
> this further. I have broken down and installed a personal fireall
> and I see this was trying to connect. It was the first thing I
> noticed. Anyway I should get rid of this? What does it do other
> than scan ports?

c:\winnt\system32\drivers?

The services.exe in c:\winnt\system32 is very important for running system
services, would indeed be called at boot, and cause a lot of errors if
blocked. I can't imagine what this file would be doing in the \drivers
folder however.



Relevant Pages

  • Re: Remove file at boot?
    ... MoveOnBoot is simplicity itself and is excellent. ... >> I need to remove a file at boot because after the boot process it is a ... >> George Hester ... > torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway ...
    (microsoft.public.win2000.general)
  • Re: Why is SQLSERVERAGENT contacting MAPI32.DLL?
    ... Ugh that's what I thought and is why SQLSERVERAGENT no longer starts correctly at boot. ... > This is normal when you configure SQL Mail. ... > "George Hester" wrote in message ...
    (microsoft.public.sqlserver.server)
  • Re: services.exe nee fscan
    ... Yeah I know but there it was. ... George Hester ... >> and it looks like it is being called at boot. ... > folder however. ...
    (microsoft.public.security)
  • Re: STOP 0x000000ED UNMOUNTABLE_BOOT_VOLUME
    ... George Hester wrote: ... Anyway when I tried to boot it back up I got the message you see in my ... disk is a Seagate Cheatah 9.1 GB. ... Do you think based on the fact that the file system was ...
    (microsoft.public.windowsxp.general)
  • Re: services.exe nee fscan
    ... Yeah I know but there it was. ... > The services.exe in c:\winnt\system32 is very important for running system> services, would indeed be called at boot, and cause a lot of errors if> blocked. ... I can't imagine what this file would be doing in the \drivers> folder however. ...
    (microsoft.public.security)