Re: KB896688 Update
- From: "NoNoBadDog!" <no_@xxxxxxxxxxxxxxxx>
- Date: Sun, 13 Nov 2005 16:53:13 -1000
While is may cause problems for *YOU*; I have installed WU VS. on dozens of
computers without a single problem. I Suspect there is a common thread to
the problem you and the others are having, such as BIOS, hardware, etc.
Since the majority seems to not have an issue with the update, it is neither
defective nor unconsionable. It should not be pulled to satisfy the few who
do have problems (like yourself). Again, I have installed the update on
over 200 computers with no problems.
Bobby
"Marcus" <sashago@xxxxxxxxxxx> wrote in message
news:CYKdnUP11fNOWOreRVn-jw@xxxxxxxxxxxxxx
> Really.......don't you think they should put that information up front,
> like
> in an ad, or at least remove the defective update as well? Why is it our
> responsibility to research Microsoft's slip-shod "updates." Why should we
> have to discover the problem after it has butchered our registry and
> disabled other applications? Isn't YOUR time worth anything to YOU? The
> whole thing is so confusing, including that article in the Knowledge Base
> you refer to. Apparently, according to one NG contributor (Freudi), this
> fix
> does not work with every OS: I didn't see any reference to that issue in
> that article. So what happens? You go in their blind, changing the
> registry
> only to find out that the fix doesn't apply to your OS! What a waste of
> time.
>
> It is time that we who use and are dependent on the integrity of this
> software start getting serious about demanding that Gates and his cronies
> get their act together and take responsibility for their repeated
> screw-ups.
> After all, it is their product and their responsibility to see that it
> actually WORKS before haphazardly launching it into cyberspace. God forbid
> if these clowns were rocket engineers or nuclear scientists.
>
> Marcus
>
>
> "Lawrence Garvin [MVP]" <onsitechsolutions@xxxxxxxxxxxxxx> wrote in
> message
> news:%23DPXnoJ6FHA.3136@xxxxxxxxxxxxxxxxxxxxxxx
> If you were to go to the Microsoft Knowledge Base and search for the
> keyword
> "896688", you would have found this KB article, along with a couple of
> others,
> listed for over two weeks. :-)
>
> On top of that, it's only been discussed in /this/ newsgroup every day
> since
> October 13th. A simple search on this newsgroup for keyword "896688" would
> also have turned up /several/ references to this fix. :-)
>
>
> "Brian" <Brian@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:4025AE5A-B7C5-4B81-93BF-217C874334E3@xxxxxxxxxxxxxxxx
>> Thank you so much for posting this!
>> Microsoft has killed their own updater with that update, along with
> ActiveX,
>> so they can't even fix it for you.
>> Perhaps they should take out some ad space to let people know how to fix
>> this. It seems fairly widespread.
>> Regards,
>> Brian
>>
>> "Lawrence Garvin [MVP]" wrote:
>>
>>> The 'fix' for issues caused by KB896688 is documented in KB909889 --
>>> http://support.microsoft.com/kb/909889
>>> ActiveX controls may not load as expected in Internet Explorer due to
>>> defense
>>> in depth changes introduced in cumulative security update 896688
> (MS05-052)
>>>
>>>
>>> "Marcus" <sashago@xxxxxxxxxxx> wrote in message
>>> news:A-ednSow74v9ROveRVn-pw@xxxxxxxxxxxxxx
>>> >
>>> >
>>> > Anyone know what's going on with Microsoft's fix for the problems
> caused
>>> > by
>>> > this problem ridden October update?
>>> >
>>> > Marcus
>>> >
>>> >
>>>
>>>
>>>
>
>
>
.
- Follow-Ups:
- Re: KB896688 Update
- From: Marcus
- Re: KB896688 Update
- References:
- KB896688 Update
- From: Marcus
- Re: KB896688 Update
- From: Lawrence Garvin [MVP]
- Re: KB896688 Update
- From: Lawrence Garvin [MVP]
- KB896688 Update
- Prev by Date: Re: Absolutely TERRIFIED of 896688 !!!!
- Next by Date: Re: KB896688 Update
- Previous by thread: Re: KB896688 Update
- Next by thread: Re: KB896688 Update
- Index(es):
Relevant Pages
|
