I've seen a few posts in the General news group regarding this
issue but nothing from Microsoft yet as to a possible fix, or for
that matter whether or not they are even aware of this problem.

For those of us that don't use a scheduled scan , but rather use
this Beta as an occasional scanner this error is very annoying.

Since a picture is worth a thousand words, the problem arises when one clicks:
http://users.mikrotec.com/danadell/w.../defender1.gif

Where upon one receives this error message:
http://users.mikrotec.com/danadell/w.../defender2.gif

While it's true that one can work around this issue by selecting a scan
method(Quick Scan||Full Scan||Custom Scan) from the drop down menu to
get it to scan, it would be nice it someone from MS would address this
issue publicly in one of the posts made already regarding this problem.

To wit:

a.) Are you(MS) aware of this problem?
b.) Do you(MS) have a temporary fix worked out for it?

I've had no problems updating definitions or experienced any other problems
with the install with the exception of this 0x80004003 error.

The program is installed in it's default location, on a Windows XP SP2 machine.

Donald Anadell

Hi Donald,

I just verified our fix for this bug, though I'm afraid we won't be able to
get it to you until we ship our next update on the UI. Thanks for your
excellent report.

Regards,
Joe

"Donald Anadell" wrote:

> I've seen a few posts in the General news group regarding this
> issue but nothing from Microsoft yet as to a possible fix, or for
> that matter whether or not they are even aware of this problem.
>
> For those of us that don't use a scheduled scan , but rather use
> this Beta as an occasional scanner this error is very annoying.
>
> Since a picture is worth a thousand words, the problem arises when one clicks:
> http://users.mikrotec.com/danadell/w.../defender1.gif
>
> Where upon one receives this error message:
> http://users.mikrotec.com/danadell/w.../defender2.gif
>
> While it's true that one can work around this issue by selecting a scan
> method(Quick Scan||Full Scan||Custom Scan) from the drop down menu to
> get it to scan, it would be nice it someone from MS would address this
> issue publicly in one of the posts made already regarding this problem.
>
> To wit:
>
> a.) Are you(MS) aware of this problem?
> b.) Do you(MS) have a temporary fix worked out for it?
>
> I've had no problems updating definitions or experienced any other problems
> with the install with the exception of this 0x80004003 error.
>
> The program is installed in it's default location, on a Windows XP SP2 machine.
>
> Donald Anadell
>
>
>
>

Hi Joe,

Thank you for responding Joe, and thanks for ironing out this bug.
Looking forward to the update for the UI.

Donald Anadell


"Joe Faulhaber [MSFT]" <(E-Mail Removed)> wrote in message
news:9DFC07DA-45D4-4CF2-A9C8-(E-Mail Removed)...
> Hi Donald,
>
> I just verified our fix for this bug, though I'm afraid we won't be able to
> get it to you until we ship our next update on the UI. Thanks for your
> excellent report.
>
> Regards,
> Joe
>
> "Donald Anadell" wrote:
>
>> I've seen a few posts in the General news group regarding this
>> issue but nothing from Microsoft yet as to a possible fix, or for
>> that matter whether or not they are even aware of this problem.
>>
>> For those of us that don't use a scheduled scan , but rather use
>> this Beta as an occasional scanner this error is very annoying.
>>
>> Since a picture is worth a thousand words, the problem arises when one clicks:
>> http://users.mikrotec.com/danadell/w.../defender1.gif
>>
>> Where upon one receives this error message:
>> http://users.mikrotec.com/danadell/w.../defender2.gif
>>
>> While it's true that one can work around this issue by selecting a scan
>> method(Quick Scan||Full Scan||Custom Scan) from the drop down menu to
>> get it to scan, it would be nice it someone from MS would address this
>> issue publicly in one of the posts made already regarding this problem.
>>
>> To wit:
>>
>> a.) Are you(MS) aware of this problem?
>> b.) Do you(MS) have a temporary fix worked out for it?
>>
>> I've had no problems updating definitions or experienced any other problems
>> with the install with the exception of this 0x80004003 error.
>>
>> The program is installed in it's default location, on a Windows XP SP2 machine.
>>
>> Donald Anadell
>>
>>
>>
>>