error 0x80070006 in vista

[Guest]

Defender worked for awhile with Vista and then started getting this error.
I've seen it mentioned elsewhere, but no solution. Any suggestions would be
appreciated.

Thanks.

 

[Guest]

Hello Herb,

Whatever you do, (installing and updateting or unistalling) always as a
administrator.
This is the key!
The installation as an admin is not enough.
You needed to login as an Administrator.

Can you go to Windows Update, select Express (Get high-priority updates),
and apply all offered updates
http://update.microsoft.com

I hope this post is helpful.
Let us know how it works ºut.
Еиçеl

 

[Guest]

Nope. How does OneCare and Defender supposed to work together? Isn't
Defender the built-in (and free) tool?

 

[Bill Sanderson MVP]

OneCare in recent versions incorporated Defender's antispyware
directly--i.e. it supplants it. I haven't seen this on Vista so I'm not
sure what the behavior looks like on Vista.

I've not seen this issue on Vista, but I can imagine things that you might
try without too much effort or risk:

I'll apologize in advance by mentioning that the only Vista machine I have
available at the moment isn't running Windows Defender, so I can't test my
thinking directly. I should have some more Vista machines available within
the next few months.

I would suggest removing the definitions back to 1.0.0, and then updating
again.

at an elevated cmd prompt (right click "command prompt" and choose to run
elevated and click to agree to do that. If you are running as a limited
user, run as administrator.

Then \program files\window defender\mpcmdrun -RemoveDefinitions -All

If this succeeds, go to Microsoft Update and apply whatever is offered.

As I say--I'm not able to easily test this on Vista at the moment---so let
me know if this just plain isn't possible, but I think it will be.


Can you say more about the circumstances--just when does this error get
displayed?
--

 

[Guest]

I've done all these things and still get the annoying error message. I keep
searching and haven't found any solution on the net. I can do things like
"mpcmdrun -scan" and that works ok. It's just when the real app starts, the
error comes out. I don't know how to interpret the dos log files.

Still searching...

Herb

 

[Guest]

I had OneCare installed and have since removed it. I have this same problem.
I believe the issues started after installing OneCare. Is there a more
complete removal of OneCare available?

 

[Dave M]

Yes there is, see this post from the WLOC newsgroups:

http://forums.microsoft.com/WindowsOneCare/ShowPost.aspx?PostID=828910&SiteID=2