3-Updates Fail KB928365, KB928366, & KB890830

I get these updates that will not install. They (all 3) always fail. Any
ideas?

Security Update for Microsoft .NET Framework, Version 2.0 (KB928365)
Security Update for Microsoft .NET Framework, Version 1.1 Service Pack 1
(KB928366)
Windows Malicious Software Removal Tool - July 2007 (KB890830)

Thanks

Do you see any other threads here about the .NET Framework updates? Have
you read through all of the (helpful) posts in them?

Start a free Windows Update support incident request:
https://support.microsoft.com/oas/de...spx?gprid=6527
--
~Robear Dyer (PA Bear)
MS MVP-Windows (IE, OE, Security, Shell/User)
AumHa VSOP & Admin; DTS-L

JCO wrote:
> I get these updates that will not install. They (all 3) always fail. Any
> ideas?
>
> Security Update for Microsoft .NET Framework, Version 2.0 (KB928365)
> Security Update for Microsoft .NET Framework, Version 1.1 Service Pack 1
> (KB928366)
> Windows Malicious Software Removal Tool - July 2007 (KB890830)
>
> Thanks

I got a better idea. Why don't they fix it? Why do we have to hunt and hunt
and hunt for fixes to problems we did not create?

"PA Bear" wrote:

> Do you see any other threads here about the .NET Framework updates? Have
> you read through all of the (helpful) posts in them?
>
> Start a free Windows Update support incident request:
> https://support.microsoft.com/oas/de...spx?gprid=6527
> --
> ~Robear Dyer (PA Bear)
> MS MVP-Windows (IE, OE, Security, Shell/User)
> AumHa VSOP & Admin; DTS-L
>
> JCO wrote:
> > I get these updates that will not install. They (all 3) always fail. Any
> > ideas?
> >
> > Security Update for Microsoft .NET Framework, Version 2.0 (KB928365)
> > Security Update for Microsoft .NET Framework, Version 1.1 Service Pack 1
> > (KB928366)
> > Windows Malicious Software Removal Tool - July 2007 (KB890830)
> >
> > Thanks
>
>

The framework update is failing due to corruption of the original
installation of the framework package. That to me appears to be a problem
with your computer not the update. Perhaps blame the person who looks after
the maintenance etc on your computer.


"Mark" wrote:

> I got a better idea. Why don't they fix it? Why do we have to hunt and hunt
> and hunt for fixes to problems we did not create?
>
> "PA Bear" wrote:
>
> > Do you see any other threads here about the .NET Framework updates? Have
> > you read through all of the (helpful) posts in them?
> >
> > Start a free Windows Update support incident request:
> > https://support.microsoft.com/oas/de...spx?gprid=6527
> > --
> > ~Robear Dyer (PA Bear)
> > MS MVP-Windows (IE, OE, Security, Shell/User)
> > AumHa VSOP & Admin; DTS-L
> >
> > JCO wrote:
> > > I get these updates that will not install. They (all 3) always fail. Any
> > > ideas?
> > >
> > > Security Update for Microsoft .NET Framework, Version 2.0 (KB928365)
> > > Security Update for Microsoft .NET Framework, Version 1.1 Service Pack 1
> > > (KB928366)
> > > Windows Malicious Software Removal Tool - July 2007 (KB890830)
> > >
> > > Thanks
> >
> >

oh, that's great ... blame us users ... all dozens and dozens if not
thousands who are having this problem ... certainly let's not blame the great
Microsoft often known for bad updates. Yeah, that's the ticket! <all
sarcasm intended>

"TaurArian" wrote:

> The framework update is failing due to corruption of the original
> installation of the framework package. That to me appears to be a problem
> with your computer not the update. Perhaps blame the person who looks after
> the maintenance etc on your computer.
>
>
> "Mark" wrote:
>
> > I got a better idea. Why don't they fix it? Why do we have to hunt and hunt
> > and hunt for fixes to problems we did not create?
> >
> > "PA Bear" wrote:
> >
> > > Do you see any other threads here about the .NET Framework updates? Have
> > > you read through all of the (helpful) posts in them?
> > >
> > > Start a free Windows Update support incident request:
> > > https://support.microsoft.com/oas/de...spx?gprid=6527
> > > --
> > > ~Robear Dyer (PA Bear)
> > > MS MVP-Windows (IE, OE, Security, Shell/User)
> > > AumHa VSOP & Admin; DTS-L
> > >
> > > JCO wrote:
> > > > I get these updates that will not install. They (all 3) always fail. Any
> > > > ideas?
> > > >
> > > > Security Update for Microsoft .NET Framework, Version 2.0 (KB928365)
> > > > Security Update for Microsoft .NET Framework, Version 1.1 Service Pack 1
> > > > (KB928366)
> > > > Windows Malicious Software Removal Tool - July 2007 (KB890830)
> > > >
> > > > Thanks
> > >
> > >

TaurArian,

That's a very glib and cavalier response. You seem to be very sure that the
problem so many people here are having is somehow THEIR fault, and not the
update itself.

Shouldn't someone from the number one Software company in the world who
writes -- and publishes -- an update for a prior installation that MAY
(according to you) be corrupt first test for that possible corruption?

And if it IS corrupt, shouldn't a well-written update try to fix the
corruption and then install? Or just not attempt to install.

I think a phrase from the Hippocratic Oath that all doctors pledge is apt
here: "To help, or at least to do no harm."

Alan

"TaurArian" <> wrote in message
news:4645EDDE-BA11-4369-B593-...
> The framework update is failing due to corruption of the original
> installation of the framework package. That to me appears to be a problem
> with your computer not the update. Perhaps blame the person who looks
> after
> the maintenance etc on your computer.
>
>
> "Mark" wrote:
>
>> I got a better idea. Why don't they fix it? Why do we have to hunt and
>> hunt
>> and hunt for fixes to problems we did not create?
>>
>> "PA Bear" wrote:
>>
>> > Do you see any other threads here about the .NET Framework updates?
>> > Have
>> > you read through all of the (helpful) posts in them?
>> >
>> > Start a free Windows Update support incident request:
>> > https://support.microsoft.com/oas/de...spx?gprid=6527
>> > --
>> > ~Robear Dyer (PA Bear)
>> > MS MVP-Windows (IE, OE, Security, Shell/User)
>> > AumHa VSOP & Admin; DTS-L
>> >
>> > JCO wrote:
>> > > I get these updates that will not install. They (all 3) always fail.
>> > > Any
>> > > ideas?
>> > >
>> > > Security Update for Microsoft .NET Framework, Version 2.0 (KB928365)
>> > > Security Update for Microsoft .NET Framework, Version 1.1 Service
>> > > Pack 1
>> > > (KB928366)
>> > > Windows Malicious Software Removal Tool - July 2007 (KB890830)
>> > >
>> > > Thanks
>> >
>> >

Maybe, anytime I have an update dealing with .NET Framework, I will set my
updates to ignore and not remind me of the update. It may save a lot of
headaches


"georgef" <> wrote in message
news:F4993C92-E804-48BF-AA3A-...
> oh, that's great ... blame us users ... all dozens and dozens if not
> thousands who are having this problem ... certainly let's not blame the
> great
> Microsoft often known for bad updates. Yeah, that's the ticket! <all
> sarcasm intended>
>
> "TaurArian" wrote:
>
>> The framework update is failing due to corruption of the original
>> installation of the framework package. That to me appears to be a problem
>> with your computer not the update. Perhaps blame the person who looks
>> after
>> the maintenance etc on your computer.
>>
>>
>> "Mark" wrote:
>>
>> > I got a better idea. Why don't they fix it? Why do we have to hunt
>> > and hunt
>> > and hunt for fixes to problems we did not create?
>> >
>> > "PA Bear" wrote:
>> >
>> > > Do you see any other threads here about the .NET Framework updates?
>> > > Have
>> > > you read through all of the (helpful) posts in them?
>> > >
>> > > Start a free Windows Update support incident request:
>> > > https://support.microsoft.com/oas/de...spx?gprid=6527
>> > > --
>> > > ~Robear Dyer (PA Bear)
>> > > MS MVP-Windows (IE, OE, Security, Shell/User)
>> > > AumHa VSOP & Admin; DTS-L
>> > >
>> > > JCO wrote:
>> > > > I get these updates that will not install. They (all 3) always
>> > > > fail. Any
>> > > > ideas?
>> > > >
>> > > > Security Update for Microsoft .NET Framework, Version 2.0
>> > > > (KB928365)
>> > > > Security Update for Microsoft .NET Framework, Version 1.1 Service
>> > > > Pack 1
>> > > > (KB928366)
>> > > > Windows Malicious Software Removal Tool - July 2007 (KB890830)
>> > > >
>> > > > Thanks
>> > >
>> > >

"Alan" wrote:

> TaurArian,
>
> That's a very glib and cavalier response. You seem to be very sure that the
> problem so many people here are having is somehow THEIR fault, and not the
> update itself.
>
> Shouldn't someone from the number one Software company in the world who
> writes -- and publishes -- an update for a prior installation that MAY
> (according to you) be corrupt first test for that possible corruption?
>
> And if it IS corrupt, shouldn't a well-written update try to fix the
> corruption and then install? Or just not attempt to install.
>
> I think a phrase from the Hippocratic Oath that all doctors pledge is apt
> here: "To help, or at least to do no harm."
>
> Alan
>
> "TaurArian" <> wrote in message
> news:4645EDDE-BA11-4369-B593-...
> > The framework update is failing due to corruption of the original
> > installation of the framework package. That to me appears to be a problem
> > with your computer not the update. Perhaps blame the person who looks
> > after
> > the maintenance etc on your computer.
> >
> >
> > "Mark" wrote:
> >
> >> I got a better idea. Why don't they fix it? Why do we have to hunt and
> >> hunt
> >> and hunt for fixes to problems we did not create?
> >>
> >> "PA Bear" wrote:
> >>
> >> > Do you see any other threads here about the .NET Framework updates?
> >> > Have
> >> > you read through all of the (helpful) posts in them?
> >> >
> >> > Start a free Windows Update support incident request:
> >> > https://support.microsoft.com/oas/de...spx?gprid=6527
> >> > --
> >> > ~Robear Dyer (PA Bear)
> >> > MS MVP-Windows (IE, OE, Security, Shell/User)
> >> > AumHa VSOP & Admin; DTS-L
> >> >
> >> > JCO wrote:
> >> > > I get these updates that will not install. They (all 3) always fail.
> >> > > Any
> >> > > ideas?
> >> > >
> >> > > Security Update for Microsoft .NET Framework, Version 2.0 (KB928365)
> >> > > Security Update for Microsoft .NET Framework, Version 1.1 Service
> >> > > Pack 1
> >> > > (KB928366)
> >> > > Windows Malicious Software Removal Tool - July 2007 (KB890830)
> >> > >
> >> > > Thanks
> >> >
> >> >
>
>
>

Another to TaurArian - you wrote "The framework update is failing due to
corruption of the original installation of the framework package. That to me
appears to be a problem with your computer not the update. Perhaps blame the
person who looks after the maintenance etc on your computer. " For those of
us not Geeky enough to know - how do we fix a corrupted framework package.
Until these failures I had no difficulty with installs.


"Alan" wrote:

> TaurArian,
>
> That's a very glib and cavalier response. You seem to be very sure that the
> problem so many people here are having is somehow THEIR fault, and not the
> update itself.
>
> Shouldn't someone from the number one Software company in the world who
> writes -- and publishes -- an update for a prior installation that MAY
> (according to you) be corrupt first test for that possible corruption?
>
> And if it IS corrupt, shouldn't a well-written update try to fix the
> corruption and then install? Or just not attempt to install.
>
> I think a phrase from the Hippocratic Oath that all doctors pledge is apt
> here: "To help, or at least to do no harm."
>
> Alan
>
> "TaurArian" <> wrote in message
> news:4645EDDE-BA11-4369-B593-...
> > The framework update is failing due to corruption of the original
> > installation of the framework package. That to me appears to be a problem
> > with your computer not the update. Perhaps blame the person who looks
> > after
> > the maintenance etc on your computer.
> >
> >
> > "Mark" wrote:
> >
> >> I got a better idea. Why don't they fix it? Why do we have to hunt and
> >> hunt
> >> and hunt for fixes to problems we did not create?
> >>
> >> "PA Bear" wrote:
> >>
> >> > Do you see any other threads here about the .NET Framework updates?
> >> > Have
> >> > you read through all of the (helpful) posts in them?
> >> >
> >> > Start a free Windows Update support incident request:
> >> > https://support.microsoft.com/oas/de...spx?gprid=6527
> >> > --
> >> > ~Robear Dyer (PA Bear)
> >> > MS MVP-Windows (IE, OE, Security, Shell/User)
> >> > AumHa VSOP & Admin; DTS-L
> >> >
> >> > JCO wrote:
> >> > > I get these updates that will not install. They (all 3) always fail.
> >> > > Any
> >> > > ideas?
> >> > >
> >> > > Security Update for Microsoft .NET Framework, Version 2.0 (KB928365)
> >> > > Security Update for Microsoft .NET Framework, Version 1.1 Service
> >> > > Pack 1
> >> > > (KB928366)
> >> > > Windows Malicious Software Removal Tool - July 2007 (KB890830)
> >> > >
> >> > > Thanks
> >> >
> >> >
>
>
>

Addendum - I get this message when the failure occurs - "SL36.tmp has
encountered a problem and needs to close." The name of the tmp file changes
with each try. Sometimes SL9.tmp, SL12.tmp etc. Does this help in the
diagnosis?

"jerryfrmmt" wrote:

> Another to TaurArian - you wrote "The framework update is failing due to
> corruption of the original installation of the framework package. That to me
> appears to be a problem with your computer not the update. Perhaps blame the
> person who looks after the maintenance etc on your computer. " For those of
> us not Geeky enough to know - how do we fix a corrupted framework package.
> Until these failures I had no difficulty with installs.
>
>
> "Alan" wrote:
>
> > TaurArian,
> >
> > That's a very glib and cavalier response. You seem to be very sure that the
> > problem so many people here are having is somehow THEIR fault, and not the
> > update itself.
> >
> > Shouldn't someone from the number one Software company in the world who
> > writes -- and publishes -- an update for a prior installation that MAY
> > (according to you) be corrupt first test for that possible corruption?
> >
> > And if it IS corrupt, shouldn't a well-written update try to fix the
> > corruption and then install? Or just not attempt to install.
> >
> > I think a phrase from the Hippocratic Oath that all doctors pledge is apt
> > here: "To help, or at least to do no harm."
> >
> > Alan
> >
> > "TaurArian" <> wrote in message
> > news:4645EDDE-BA11-4369-B593-...
> > > The framework update is failing due to corruption of the original
> > > installation of the framework package. That to me appears to be a problem
> > > with your computer not the update. Perhaps blame the person who looks
> > > after
> > > the maintenance etc on your computer.
> > >
> > >
> > > "Mark" wrote:
> > >
> > >> I got a better idea. Why don't they fix it? Why do we have to hunt and
> > >> hunt
> > >> and hunt for fixes to problems we did not create?
> > >>
> > >> "PA Bear" wrote:
> > >>
> > >> > Do you see any other threads here about the .NET Framework updates?
> > >> > Have
> > >> > you read through all of the (helpful) posts in them?
> > >> >
> > >> > Start a free Windows Update support incident request:
> > >> > https://support.microsoft.com/oas/de...spx?gprid=6527
> > >> > --
> > >> > ~Robear Dyer (PA Bear)
> > >> > MS MVP-Windows (IE, OE, Security, Shell/User)
> > >> > AumHa VSOP & Admin; DTS-L
> > >> >
> > >> > JCO wrote:
> > >> > > I get these updates that will not install. They (all 3) always fail.
> > >> > > Any
> > >> > > ideas?
> > >> > >
> > >> > > Security Update for Microsoft .NET Framework, Version 2.0 (KB928365)
> > >> > > Security Update for Microsoft .NET Framework, Version 1.1 Service
> > >> > > Pack 1
> > >> > > (KB928366)
> > >> > > Windows Malicious Software Removal Tool - July 2007 (KB890830)
> > >> > >
> > >> > > Thanks
> > >> >
> > >> >
> >
> >
> >