TaurArian, my opinion is that Microsoft has -- as you Aussies like to say --
stuffed up big-time, and it's not for the first time with its updates.
Moreover, I think the rectification should not be placed on the shoulders of
Microsoft's hapless users.
But, rather than Microsoft's admitting that it could possibly make (okay,
has made) a mistake, it just stonewalls. It's quite similar to the standard
line that MSFT likes to use in many of its KB articles: "This (bug) is by
design." Right.....
I have some personal experience with this tactic, as I was in Microsoft's
Product Support Services at one of its out-sourced call centers in the USA
in the mid-90's. I know all too well how the game is played, and what we
techs were explicitly told to say to the customers who called in for support
We were not told to lie, exactly. It was more what we were NOT allowed to
say about a situation that was a BIG problem and one that Microsoft had no
idea how to correct at that moment -- if ever.
Microsoft has the money and, presumably, the expertise to write software
that helps people enjoy their computers, not to have them scurrying around
like rats in a Skinner box trying to fix problems that are iatrogenically
introduced most patch Tuesdays.
My question is: Why doesn't Microsoft take the high road for a change?
Alan
"TaurArian" <> wrote in message
news:59FE3B4B-6C92-4ABE-A1FE-...
> Alan, why not provide your opinion of what is causing the problem and how
> to
> rectify the same.
>
> "Alan" wrote:
>
>> Ahhh, TaurArian, so you now have decided that "somehow the Framework
>> package
>> has become corrupted on the system."
>>
>> Do you still believe it's the result of users' not exercising due
>> diligence
>> regarding maintenance on their system?
>>
>> Alan
>>
>> "TaurArian" <> wrote in message
>> news:E608B2E9-94DE-4787-8A8A-...
>> > Basically the fix seems to be to uninstall and reinstall the Framework
>> > package as somehow the Framework package has become corrupted on the
>> > system.
>> >
>> > How to troubleshoot Microsoft .NET Framework 1.1 installation issues
>> > http://support.microsoft.com/default...b;en-us;824643
>> >
>> > How to troubleshoot Microsoft .NET Framework 2.0 installation issues
>> > http://support.microsoft.com/kb/908077/
>> >
>> > Your can either try repairing the original installation, try installing
>> > the
>> > original installation over itself or just remove Framework 1.1 and 2.00
>> > and
>> > then reinstall the Framework versions and patches.
>> >
>> > This has worked for a few but as usual, there are no guarantees it will
>> > work
>> > for you.
>> >
>> >
>> > "Rudy3343" wrote:
>> >
>> >> hey ppl, can anyone shed some light on why these security update are
>> >> not
>> >> installing.
>> >> Microsoft .NET Framework, Version 1.1 Service Pack 1 (KB928366). and
>> >> (.Net Framework 2.0) all failed to install.
>> >> Can anyone help?
>> >> i see there alot of other having the same problem
>> >> I microsoft can hurry and send a fix.
>> >> --
>> >> Thank alot ppl.
>>
>>
>>