Microsoft response to repeated install KB832894

I followed the experts' advice on this and another group (ie6) and contacted
Microsoft. I learnt that it does not support IE6, or Windows 2000 (prone to
this error), but the person helped me clear rubbish e.g. removing temp files
using services.msc, temp, %temp%, and perfetch. Also checked that automatic
updates were set to automatic.

This call cost me a lot (it's not a free number in the UK), so perhaps this
advice means others won't have to waste money doing the same. Person seemed
rather disinterested.

The download also installed, or rather didn't install, on my new XP pro
computer. On the other group, it was emphasised that it was an old update
(2004) and that it has been superceded. a complete waste of everyone's time.

Still concerned that the exercise messed up my registry. As a layperson, you
can't really be sure just what it's done.

Regards,

Ellen G <> wrote:

> On the other group, it was emphasised that it was an
> old update (2004) and that it has been superceded.

Ellen, it was reported earlier today that the problem with repeated
detection of 832894 had been fixed at Microsoft's end. Is it still
happening with you, or has it now stopped?

--
Robin Walker [MVP Networking]

Hi Robin,

No, this issue resolved itself on the same day. I'm just concerned about the
possible mess it's created in the registry etc. I can't find signs of it,
though WU review history says it installed succesfully on five occasions.

My new XP comuter is sturdy, my old windows 2000 laptop is struggling and
doens't need complications.

I hope that the advice I was given, e.g. removig temp files etc, did it no
harm. I usually just rely on 'clean disc' but found hundreds of temp files
using services*, temp etc.

Disappointed with microsoft's response, both in person and online.

Regards,

Ellen


"Robin Walker [MVP]" wrote:

> Ellen G <> wrote:
>
> > On the other group, it was emphasised that it was an
> > old update (2004) and that it has been superceded.
>
> Ellen, it was reported earlier today that the problem with repeated
> detection of 832894 had been fixed at Microsoft's end. Is it still
> happening with you, or has it now stopped?
>
> --
> Robin Walker [MVP Networking]
>
>
>
>

[Ellen, I replied to your related thread in IE6 Browser newsgroup.]

> No, this issue resolved itself on the same day. I'm just concerned about
> the
> possible mess it's created in the registry etc. I can't find signs of it,
> though WU review history says it installed succesfully on five occasions.

Don't worry about it now. All should be well.

> I hope that the advice I was given, e.g. removig temp files etc, did it
> no
> harm. I usually just rely on 'clean disc' but found hundreds of temp files
> using services*, temp etc.

None of the above would cause the machine any harm, Ellen.

> Disappointed with microsoft's response, both in person and online.

I hope you understand that the majority of posters here, including MS MVPs
such as Robin and myself, are neither Microsoft employees nor
representatives.
--
~Robear Dyer (PA Bear)
MS MVP-Windows (IE, OE, Security, Shell/User)
AumHa VSOP & Admin; DTS-L.org


Ellen G wrote:
> Hi Robin,
>
> No, this issue resolved itself on the same day. I'm just concerned about
> the
> possible mess it's created in the registry etc. I can't find signs of it,
> though WU review history says it installed succesfully on five occasions.
>
> My new XP comuter is sturdy, my old windows 2000 laptop is struggling and
> doens't need complications.
>
> I hope that the advice I was given, e.g. removig temp files etc, did it
> no
> harm. I usually just rely on 'clean disc' but found hundreds of temp files
> using services*, temp etc.
>
> Disappointed with microsoft's response, both in person and online.
>
> Regards,
>
> Ellen
>
>
> "Robin Walker [MVP]" wrote:
>
>> Ellen G <> wrote:
>>
>>> On the other group, it was emphasised that it was an
>>> old update (2004) and that it has been superceded.
>>
>> Ellen, it was reported earlier today that the problem with repeated
>> detection of 832894 had been fixed at Microsoft's end. Is it still
>> happening with you, or has it now stopped?
>>
>> --
>> Robin Walker [MVP Networking]
>>