Windows Vista 64Bit Defender Fail Error - 0x800106ba-0x80092003
I am using Windows Vista 64Bit. Recently after Windows Update I facing a weird error related to Windows Defender. It is not working at all. The error number is 0x800106ba-0x80092003 which appear on startup. I tried to find some information on this error remember on Microsoft Knowledge base. It was clearly mentioned that I have to remove and reinstall Defender to stop error. But I cannot locate option to remove and re-install stuff back again. There is no method available to perform the action. What should I do to get this error fixed. Thanks.
re: Windows Vista 64Bit Defender Fail Error - 0x800106ba-0x80092003
Some of the solutions which are mentioned above does not really work for Windows Vista 64bit. After last update in my system, I do not know how Defender started automatically. I am not using this at all. When I got the error 0x800106ba I did changes to Windows Update as mentioned above. But now I am getting a new error which is -- application failed to initialize: 0x800106ba. The RPC server is unavailable. Vista is getting more annoying now.
re: Windows Vista 64Bit Defender Fail Error - 0x800106ba-0x80092003
I solved my issue by removing Defender from msconfig startup. It is not working so there is no error on starutp. I keep my Windows update and hope in future I can get a proper fix for the same.
re: Windows Vista 64Bit Defender Fail Error - 0x800106ba-0x80092003
1 Go to control Panel and click on Administrative tools.
2 Click on services and a new windows will appear.
3 Look up for windows defender and right click on it, click on
properties and select automatic, it should be on manual, change it to
automatic and click apply then o.k. and will take you back to the
services windows.
4 Windows Defender should be highlighted and on the left hand side of
the services windows, should be 2 links, click restart.
5 Close all windows and open Windows Defender, it should work without a
problem and your popup window at start up will not be display any
longer
Three years on and it worked again!