0x800700B6 error message

I'm trying to perform updates on a friend's laptop, but whenever I try to use Windows Update, it begins to scan for updates, but then fails and goes to the Windows Update error page. I tried using Windows Update version 5 also, but it also has an error. v5 gives the error code 0x800700B6, but I can't figure out anything about what this means; I can't find a reference to it anywhere.

"cheesebyproduct" <> wrote in message
news:8F1B4793-B56D-484F-9783-...
> I'm trying to perform updates on a friend's laptop, but whenever I try to
> use Windows Update, it begins to scan for updates, but then fails and
> goes to the Windows Update error page. I tried using Windows Update
> version 5 also, but it also has an error. v5 gives the error code
> 0x800700B6, but I can't figure out anything about what this means;
> I can't find a reference to it anywhere.

Do you have the context for that code in your logs?

You could also try searching for the decimal equivalent of that hex value.
Unfortunately nobody will tell me whether the hex value is to be interpreted
as a DWord (which was the case in V4) or as a QWord (which I have
seen some evidence of in V5). Therefore you should try searching for
both:
DW(800700B6) == -2147024714 (notice the sign)
QW(800700B6) == 2147942582

Usually the decimal value is used in the XML logs.


Another thing that couldn't hurt is using the troubleshooter to search for
articles which refer to codes starting with 8007 and then trying the tests
and actions recommended for them.


HTH

Robert Aldwinckle
---

On Mon, 2 Aug 2004 18:35:20 -0400, "Robert Aldwinckle" <>
wrote:

>You could also try searching for the decimal equivalent of that hex value.
>Unfortunately nobody will tell me whether the hex value is to be interpreted
>as a DWord (which was the case in V4) or as a QWord (which I have
>seen some evidence of in V5). Therefore you should try searching for
>both:
> DW(800700B6) == -2147024714 (notice the sign)
> QW(800700B6) == 2147942582
>
>Usually the decimal value is used in the XML logs.

Not a definitive answer, by any means, but in my personal experiences the hex
values have all been DWords, and the decimal values were all signed as negative.

--
dak

"dak" <microsoft-public-> wrote in message
news:...
> On Mon, 2 Aug 2004 18:35:20 -0400, "Robert Aldwinckle" <>
> wrote:
>
>>You could also try searching for the decimal equivalent of that hex value.
>>Unfortunately nobody will tell me whether the hex value is to be interpreted
>>as a DWord (which was the case in V4) or as a QWord (which I have
>>seen some evidence of in V5).
....

> Not a definitive answer, by any means, but in my personal experiences the hex
> values have all been DWords, and the decimal values were all signed as negative.


Until this that is what I would have said too:

news:
Subject: Re: Background Intelligent Transfer Service
Date: Tue, 27 Jul 2004 05:49:42 -0400

Perhaps it's a BITS-only feature but it's pretty clear that the decimal
equivalent being documented in that incident is not signed.


FYI

Robert
---

On Wed, 4 Aug 2004 13:54:04 -0400, "Robert Aldwinckle" <>
wrote:

>> Not a definitive answer, by any means, but in my personal experiences the hex
>> values have all been DWords, and the decimal values were all signed as negative.
>>
>Until this that is what I would have said too:
>
>news:
>Subject: Re: Background Intelligent Transfer Service
>Date: Tue, 27 Jul 2004 05:49:42 -0400
>
>Perhaps it's a BITS-only feature but it's pretty clear that the decimal
>equivalent being documented in that incident is not signed.

You're right about that. I just hadn't run into it yet, which is why I
qualified my statement with "in my personal experiences." )
Thanks for pointing that out.

--
dak