Re: Windows Defender error 0x800106ba
- From: Ray <Ray@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 12 Jan 2009 13:28:00 -0800
Thank you for this information
Hey guys I found a really crappy workaround for this. This is NOT a
fix, but I've tried a bunch of stuff suggested in this
and other various forums, done hours of research and
tinkering and this is the only solution I've found
that will get Windows Defender to fire up.
Go to Admin Tools, Services.
Locate the WD service (if it's not stopped, stop it).
Change it's startup type to Automatic.
Click the Log On Tab
Select Local System Account and check the box that
says Allow service to interact with desktop
Click the Recovery Tab and ensure that First and
Second failures are set to Restart the Service.
Go to the General Tab again
Now go back to Ctrl Pannel and start up Windows
Defender ... should fire up. I checked for updates and
there were none.
Notes: I did a reboot and checked out the service.
It's stuck in a 'stopping' state and of course
WinDefend isn't working. I used the Task Manager
clicked the Services tab and found the service name
that was stuck in the stopping state (WinDefend). I
then right clicked it and chose go to process (make
sure you choose show processes from all users). That
took me to the svchost.exe instance that was hung up.
I ended the process. Now I disabled the service and
Once my reboot was complete I went back to the service
and put it in manual mode (leaving everything else I
changed earlier alone) Tried to start it but it
wouldn't start because no active processes needed the
service. At this point I went back to ctrl panel and
started windows defender. I got the dialog box
indicating it was off and clicked the link to turn it
on. It fired back up. Again checked for updates and
there were none.
So now I reboot leaving the service in manual mode.
I'm back to where I started. Same original error. The
service however is not stuck in a 'stopping' state.
It's just stopped. I was able to start it sucessfully.
and Windows Defender opened up normally when I fired
it back up. VERY VERY WEIRD
A final word on this pain in the a$$ error, I have not
been successful using the Automatic delayed start
option. I get an error indicating that the parameter
isn't correct. Go figure.
Posted via http://www.vistaheads.com
- Prev by Date: Re: Spyware are possible?
- Next by Date: UAC causes Access Errors
- Previous by thread: Firewall Driver (mdsdrv.sys)
- Next by thread: UAC causes Access Errors