Defender errors coming out my ears

[Guest]

OK

1. WD was not working so I unisnstalled it and reinstalled hoping it would
fix. It did not.

2. It says it has updated defs but when I do a scan (it tells me I have not
scanned for 33 days!?) it fails with an error.

3. When I try to do scan I get an error about 'invalid pointer'

4. After unisnstall it and reinstall it seemed to be back to working but
then I did a scan which crashed out with an 'unexcpected error' - 0x8050800c.
I thought I had fixed this with a reinstall.

5. All in Defender has defended me 0 times. It has scanned my system without
error 0 times. It has successfully updated itself 0 times. It has been
reinstalled 1 times and still HAS NOT provided any useful function!!!!!

6. To surmise..... It wont scan without error. It wont update without error.
Reinstallation does not do anything to resolve this ergo this software is
crap!?

What it is good at is offering annoying reminders in the taskbar telling me
I need to do a scan!! Hoooray for Defender! Guess what. When I do a scan it
offers an error.

So I have spent quite a lot of time on this and it has not done anything of
any use for me.

WTF. Is this a MS joke?

Anyone else care to offer thoughts on what I might be doing wrong? thanks.

MS. This is a complete dog and you need to sort it quickly. It the worst MS
effort I have seen in a LONG time. For Beta 2 it is deplorable.

 

[Guest]

You could start by reading the updated Release Notes, and then use the
Newsgroups search function to search for each error code. Most of these
issues have already been fixed or workarounds have been developed here in the
newsgroups. I won't attempt to explain further. That's what I did and my
Defender works perfectly, but I don't know much because I am just a home
user, not a professional. Mine has been protecting, scanning and updating
properly since February 16th.

 

[Mike Treit [Msft]]

Hi Sandy.

For the error 0x8050800c, please see my earlier post entitled 'Explanation
of error 0x8050800c using engine build 1.1.1186.0' for a description of why
you are most likely hitting this problem. Basically, if your system drive is
a dynamic disk you will see this error until the next engine update happens.

If you are still seeing the "invalid pointer" error or other issues in
addition to 0x8050800c, I would really like to debug further to understand
what is happening. If you could send me an email I can send you some tools
that will help us to investigate.

Thanks

-Mike

 

[Guest]

Hi Mike

I know you are busy!

Well I have dynamic disks so, from what you say, I need to put up with this
error 0x8050800c until you fix it. It occurs after a few minutes of a scan.

Previously I used the fix "Msiexec /x
{A5CC2A09-E9D3-49EC-923D-03874BBD4C2C}" to remove previous defs. This never
produced any result so I uninstalled and reinstalled Defender and now I am
suffering from the first problem.

From what I can gather 0x8050800c means that a scan is cancelled and so I am
not actually protecetd with Defender. Is that right?

 

[Mike Treit [Msft]]

You are correct, the scan will not finish while this error is occuring, and
some spyware may not be detected.

Hopefully we will get a fix out soon; however, I don't currently have an
ETA.

Thanks

-Mike

 

[Guest]

Hi again Mike

Well. Thanks for your previous comments and your recent reply. I look
forward to the update.

I sincerely hope you have a happy and productive day!

Cheers.

SM