Windows Defender on Win2K

  • Thread starter Thread starter JMF
  • Start date Start date
J

JMF

I'm trying to install Defender on my Win2K machine.

I got past the hurdle of the GTI+, but now I'm on the next hurdle: it says
that the Windefend service failed to start, make sure you have enough
privileges.

Of course I *do* have sufficient privileges.

I looked around and saw that this is a known issue, but ... couldn't find
the solution anywhere. Has somebody seen it?

Thanks,

John
 
JMF said:
I'm trying to install Defender on my Win2K machine.

I got past the hurdle of the GTI+, but now I'm on the next hurdle: it says
that the Windefend service failed to start, make sure you have enough
privileges.

Of course I *do* have sufficient privileges.

I looked around and saw that this is a known issue, but ... couldn't find
the solution anywhere. Has somebody seen it?

Thanks,

John

Well, I just solved my own problem. For anybody who's interested, here's
what happened. I looked around some more and found this on one of the
forums:

"I may have a fix for the service failed errors everyone's getting on Win
2000.
I tried to install, got the WinDefend service failed to start error. While
it's in that error state, open up your services. Then open the defender
service and change it from local account to an administrator account on your
network. Try to start the service. Mine came back with "access denied."
Great. Now change it back to local account, and presto, it should work. At
least mine did anyway."

And, by golly, it worked for me, too. One of the strangest fixes I've ever
seen.

John
 
Installed fine for me with no fixes req

JMF said:
Well, I just solved my own problem. For anybody who's interested, here's
what happened. I looked around some more and found this on one of the
forums:

"I may have a fix for the service failed errors everyone's getting on Win
2000.
I tried to install, got the WinDefend service failed to start error. While
it's in that error state, open up your services. Then open the defender
service and change it from local account to an administrator account on your
network. Try to start the service. Mine came back with "access denied."
Great. Now change it back to local account, and presto, it should work. At
least mine did anyway."

And, by golly, it worked for me, too. One of the strangest fixes I've ever
seen.

John
 
Back
Top