WinDefend Service Failed to start - FIX!?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

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.
 
Hi David!
You are GREAT!!!
I did the same here and I could start the service succesfull afterwards!
Thank you VERY much!!!!
Kindest regards,
Eric
 
Hi David!
I just discovered that your solution does not survive a reboot... You will
have to perform the same trick after a reboot because the service abends at
system startup with the same 0x800106ba.
However, we have a temporary solution thanks to you!
Kindest regards,
Eric
 
Hi David and Eric-
Yep, this method works for me also, thanks for the solution! I also have to
do the same routine everytime I logon to the computer, but at least it will
start. I'm beginning to suspect that maybe one of the problems may be how
one logons to Win 2000-maybe hitting those ctl-alt-del keys before entering a
password resets the permissions or something...anyways, I'm glad I can get it
running for now-thanks again.
 
Thanks ever-so-much for your assistance. This WAS the fix that got me over
the hump.

Peace
Jemsws
 
Thankyou for the fix!

I also have to redo this procedure after rebooting, the fix doesn't stick...
To logon, I do not need to press ctrl+alt+del, so that is not the problem.

Hopefully MS will release a new version that corrects this bug.

Is this a problem only for people with non-english versions of Windows 2000
Pro??
 
I haven't noticed the rebooting problem, but wouldn't doubt it. I've only
put it on servers so we haven't had any reboots in a while. Glad it could
help out a little bit for everyone though.
 
David,

You are the bomb!!!! It worked!! I've been fighting with the machine for a
couple of hours and came across this thread. Thanks!!!
 
david network admin emailed this:
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.

Thanks for the fix -- I got the service to start this way BUT no icon
appears so no way to start a scan or control updates. If, after I've
started the service using your fix, I click on 'Defender' to try and get
the icon, I get an error 'Application failed to initialize: 0x800106ba A
problem caused Win Defender service to stop'... and the service stops.

Any ideas?

Thanks,

MS
 
I too was getting this problem. Chaning the service to logon as Administrator
and then back to local account got round the problem of installing Windows
Defender on my machine. However, when trying to update the definition files I
get this error message:- "Windows Defender was unable to complete the update:
0x80240022. The wong diskette is in the drive. Insert %2 (volume serial
number: %3) into drive %1"
I too am using Win 2000 SP4 - Me thinks Microsoft haven't tested the product
 
Have you, in fact, applied the update mentioned by DrewMathers in the
adjacent message? Is your machine current with all critical updates, as
defined by WindowsUpdate? Can you update Windows Defender definitions via
Windows Update?

--
 
Yes, Windows 2000 Update Rollup 1 and all updates from Microsoft Update site
have been applied.

Windows defender does update the definition files from Windows update site
(or automatic updates). However, since applying the latest version of Win
defender Beta 2, the service fails to start each time the computer is
restarted. There are several posts about this - the problem can be overcome
by seting the service to log on as an Administrator and then setting back to
logon as the local system account, but the problem comes back after every
re-boot. This is obviously not a satisfactory situation.
 
So much for that M$ ppl BS

(Wanna know the REAL solution for this issue? Read on...)

The problem isn't that some MS programmer has done bad, actually they did that in accordance with MS policy
smile_confused.gif
. This company and its employees are so full of BS that they did it on purpose, in order to force W2K users to upgrade to XP or Vista (even if that wasn't your intention in the first place); so they coded a "time-delay bomb" into WinDefend b2, set to go off dec 31th - after that date, it'll stop working, and even have you figure out why (not even a friendly message to let us know what happened and why - it took me a handful of good minutes to figure out why my WinDefend service wouldn't start; and that's because I know my way around computers, imagine this happening for a person who's computer illiterate, trying to figure out why "WinDefend Service Failed To Start"!!).
And upgrading to the Final version will give you a nice "This Program Cannot Be Installed" message if you try to install it into W2K (we'll adress that issue again in a minute... as I said, read on
smile_wink.gif
).

And it gets even worse: did you know that uninstalling WinDefend b2 will leave a lot of junk in you computer? The WinDefend service will still be listed in your computer's services list, and you will have to disable it manually (imagine how's that for someone who's computer illiterate??), and the only way to completely remove it is by searching your machine's registry, finding every single "Windows Defender" and "WinDefend" entry and deleting them manually (and even that is a pain in the @ss, because these entries won't go away, unless you use Regedt32 to edit them, and set Full Control in "Security > Permissions", in order to be able to DELETE THE ENTRIES, for CRISSAKE!!)

Well, after you successfully go past that pile of junk left over by WinDefend, you may wanna install WinDefend Final in your W2K machine ("But how?? WinDefend said it won't install on W2K!!" - oh yes, it will... just do some googling and you'll find that there are plenty of sources for a workaround solution, that will even show you a bit more how MS ppl and 'ol BG are nothing but a bunch of SOBs - WinDefend Final WILL install and run on every computer, regardless of OS, AFTER you fix it yourself - all you need is the right tool at hand. Happy googling...
smile_teeth.gif
)

"And what about the solution for the 'WinDefend Failed To Start' error?"
Well, I got that error on my machine, while trying to install WinDefend Final on it. After looking into this forum and watching so many so-called "MS Specialists" (MVP, MCSE, MSD, and whatnot) stalling us with stupid nonsense, I decided to go after a real solution - and found it: If you are running W2K and goin' thru this issue, check whether you have Update Rollup 1 for SP4 on your machine - set Windows Update to find for it, or go to
http://www.microsoft.com/downloads/...FamilyID=B54730CF-8850-4531-B52B-BF28B324C662 to download the install package.

After installing this update and rebooting, that worked for me, and it should work for everyone else too. None of that "During installation, try setting the logon properties for the WinDefend service to start with an admin account" sh*t... go for a real fix.

The day M$ will tell us what to do with OUR machines is gone bye-bye. Good luck everyone. Peace out!
smile_teeth.gif
 
Thanks a lot! Your way indeed works....It causes me lots of headache
recently...

Thanks again.
 
david network admin said:
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.

Hi David,
I couldn't find the WinDefend service in the administrative tools(control
panel) services link section. Could you help me on this. I am using Windows
XP professional.

thanks
Ajeet
 
Start, run, services.msc <enter>

(use caution!)

Ajeet N said:
Hi David,
I couldn't find the WinDefend service in the administrative tools(control
panel) services link section. Could you help me on this. I am using
Windows
XP professional.

thanks
Ajeet
 
Back
Top