Error 8050800c - still on Beta 2

[Guest]

Hi All

Since installing Microsoft Defender Beta 1 I have been having the error
message above (8050800c) appear about 1/2 way through a scan, it then stops
and will not complete it.

Even after installing Beta 2 the other day I still get the same error. I am
not sure if Beta 2 was supposed to fix this error or not.

Any advice on what I can do to make Microsoft Defender work would be
appreciated.

 

[Bill Sanderson MVP]

Can you go to Help, about, and look at the Windows Defender version?

I'm not certain from your description that you are on the newest code which
is 1.1.1347

 

[Guest]

Hi Bill

I think I am on the newest version as I downloaded and installed it only a
couple of days ago.

In any case I went to the help about and copied it below. It looks like I
am on the newest version.

Any ideas as to what it might be?

Thanks!


Windows Defender Version: 1.1.1347.0
Engine Version: 1.1.1303.0
Definition Version: 1.14.1396.12

Support
-------
For more information on the Windows Defender (Beta) product, visit the
Microsoft Spyware page at http://go.microsoft.com/fwlink/?LinkId=55273.

Assisted support for this beta product is not available. Once the final
release of Windows Defender has been made publicly available, customers will
be able to contact Product Support Services for help. In the meantime, we
have provided online support resources to help you try out the Windows
Defender beta.

Please visit one or all of these peer-to-peer newsgroups at
http://go.microsoft.com/fwlink/?LinkId=55403

 

[Guest]

I have the same problem with the latest version (v 1.1.1347.0) and it always
aborts when it encounters C:\Windows\system32\wowexec.exe

 

[Bill Sanderson MVP]

OK - both of you are still seeing a scan failure which is due to an
underlying design choice--not sure I can call this a bug. At any rate, Mike
Treit is interested in gathering more information about the circumstances in
which this message is still seen: Please send email to Mike Treit, of
Microsoft:

mtreit @ microsoft.com
(remove the spaces)

and let him know the error you are seeing in the subject header, and that
you are on 1347.

Thanks for helping out with the beta!

--

 

[Guest]

What do you mean by "an underlying design choice--not sure I can call this a
bug."

As a designer of software for over 16 years, I certainly would call this a
bug: a basic use case that generates an error dialog that cannot be
circumvented.

 

[Bill Sanderson MVP]

It's a beta product. I didn't want to call it a bug because the choice to
have the scan stop with an error message in certain cases was intentional,
as I understand it--not an unforseen event.

The application has been refined over the course of the beta so that events
causing these cryptic error messages are seen less frequently than in the
original builds--i.e. the most frequent cases have been handled better--and
as I understand it, the intent is also to refine the error message for the
cases which remain.
--