KB928366 update fix @ ms

Anyone told of, or tried this fix?


Action:
***************************
Tried to install updates

Result:
***************************
Update KB928366 reoccurs in the computer

Cause:
**************************
Update reoccurring

Resolution:
**********************
Unchecked the update


Lee

Hello Lee,

Have a look at this article. It may be relevant to your prºblem.
http://www.microsoft.com/downloads/d...playlang=en&tm

There are a couple of interesting posts in this groups which may relate to
your problem -
To view these posts type KB928366 in the `Search for` box, select
the appropriate Newsgroup from the drop down menu and select Go.
-

I hope this post is helpful.

Let us know how it works ºut.
--
"LEE" wrote:

> Anyone told of, or tried this fix?
>
>
> Action:
> ***************************
> Tried to install updates
>
> Result:
> ***************************
> Update KB928366 reoccurs in the computer
>
> Cause:
> **************************
> Update reoccurring
>
> Resolution:
> **********************
> Unchecked the update
>
>
> Lee
>

Engel,

My problem with the "perpetual icon" HAS been resolved with the steps
provided below by the ms folks over the phone. I will still look at the link
you provided (even though this may cause me pain and incovenience a few
electrons) All the best. Thanks dood!

Lee

"Engel" wrote:

> Hello Lee,
>
> Have a look at this article. It may be relevant to your prºblem.
> http://www.microsoft.com/downloads/d...playlang=en&tm
>
> There are a couple of interesting posts in this groups which may relate to
> your problem -
> To view these posts type KB928366 in the `Search for` box, select
> the appropriate Newsgroup from the drop down menu and select Go.
> -
>
> I hope this post is helpful.
>
> Let us know how it works ºut.
> --
> "LEE" wrote:
>
> > Anyone told of, or tried this fix?
> >
> >
> > Action:
> > ***************************
> > Tried to install updates
> >
> > Result:
> > ***************************
> > Update KB928366 reoccurs in the computer
> >
> > Cause:
> > **************************
> > Update reoccurring
> >
> > Resolution:
> > **********************
> > Unchecked the update
> >
> >
> > Lee
> >

The windows update for .Net Framework has created considerable
problems for a lot of users. Those that have contacted Microsoft
prior
to July 12 or July 13 were given bad information on how to fix the
update. First, a bit of history: The update is for .Net Framework 1.1
service pack 1, not the original installation of .Net Framework 1.
The
service pack was an optional update that many users did not upload.
Hence the latest security update was doomed to fail. The security
update did not search for the right version prior to installation so
either you got a installation failure message or it "updated
sucessfully" only to reappear as a needed update a few minutes later.
If you were unfortunate enough to add .Net Framework version 2 or 3
without uploading your service pack to version 1 your headaches just
got worse. (Please note: there is a service pack out for version 2
and
the service pack for version 3 will be released this fall).

The fix advocated by level one support was to reset the update
catalog
by clearing the software distribution folder and reseting the
catroot2
folder. Of course you had to go stop a few services in order to
rename
the folder so the process seemed a bit complicated but if you took
that route you were on a fools errand. (Level one support has since
been re-educated). Downloading the files directly off the web site
did
not resolve the issue either, unless you got lucky and added service
pack 1 during the process and did not have version 2 or 3 on your
computer.


So, here is the fix:


Get rid of all the .Net Framework files and reinstall them one by
one,
updating each one as you go.


You need Windows Install Clean Up utitility to clear the installer
files, then you need the dotnetfix clean up utility to get rid of all
of the versions of .Net Framework, then you need to upload and
install
each version of Framework, including the service packs, one by one
until you are done, then do the updates. If you only need version
1.1,
then there is no reason to download version 2 and 3 along with their
numerous updates.


For those few are foiled at the first step: that is you run the
Windows Install Cleanup utility and you do not find any .Net
Framework
files listed, then you need to download the 1.1 package and install
it. That simply places it in the windows installer cache so it shows
up in the utility so you can then turn right around and delete it.


Here are the crib notes provided to the Microsoft support staff:


Download Windows Install Cleanup Utility by following the article
http://support.microsoft.com/kb/290301 and remove any other versions
of .Net framework showing up in cleanup utility.


Also download the Net Framework cleanup tool from
http://blogs.msdn.com/astebner/archi...08/406671.aspx and you
can download the tool from the left side of the page under the
section
"USEFUL TOOLS".


DOTNETFX (1.1)
http://www.microsoft.com/downloads/d...d=262D25E3-F58...


..NET FRAMEWORK 1.1 Service pack 1
http://www.microsoft.com/downloads/d...d=a8f5654f-088...


go to windowsupdate.microsoft.com and do the updates kb928366..


Good luck to all and please spread the word, Microsoft Support is
overwhelmed atm.


BTW: The windowsupdate.log and all of the usual stuff has no useful
information for this problem, this little update snafu was a doozy!
There is more to the story but enough said for now.

<> wrote in message
news: oups.com...
> The windows update for .Net Framework has created considerable
> problems for a lot of users. Those that have contacted Microsoft
> prior
> to July 12 or July 13 were given bad information on how to fix the
> update. First, a bit of history: The update is for .Net Framework 1.1
> service pack 1, not the original installation of .Net Framework 1.
> The
> service pack was an optional update that many users did not upload.
> Hence the latest security update was doomed to fail. The security
> update did not search for the right version prior to installation so
> either you got a installation failure message or it "updated
> sucessfully" only to reappear as a needed update a few minutes later.
> If you were unfortunate enough to add .Net Framework version 2 or 3
> without uploading your service pack to version 1 your headaches just
> got worse. (Please note: there is a service pack out for version 2
> and
> the service pack for version 3 will be released this fall).
>
> The fix advocated by level one support was to reset the update
> catalog
> by clearing the software distribution folder and reseting the
> catroot2
> folder. Of course you had to go stop a few services in order to
> rename
> the folder so the process seemed a bit complicated but if you took
> that route you were on a fools errand. (Level one support has since
> been re-educated). Downloading the files directly off the web site
> did
> not resolve the issue either, unless you got lucky and added service
> pack 1 during the process and did not have version 2 or 3 on your
> computer.
>
>
> So, here is the fix:

<snip>

What sounds even better to me, much better, would be for MS to fix the damn
issue, and put out an update that actually works.
Obviously, this is not a minor issue, it is affecting many many users. No
telling how many, that don't even know about usenet or how to find their way
to this forum...



--
Don

> "Don Burnette" wrote:
> <> wrote:
>> The windows update for .Net Framework has created considerable
>> problems for a lot of users. Those that have contacted Microsoft
>> prior
>> to July 12 or July 13 were given bad information on how to fix the
>> update. First, a bit of history: The update is for .Net Framework 1.1
>> service pack 1, not the original installation of .Net Framework 1.
>> The
>> service pack was an optional update that many users did not upload.
>> Hence the latest security update was doomed to fail. The security
>> update did not search for the right version prior to installation so
>> either you got a installation failure message or it "updated
>> successfully" only to reappear as a needed update a few minutes later.
>> If you were unfortunate enough to add .Net Framework version 2 or 3
>> without uploading your service pack to version 1 your headaches just
>> got worse. (Please note: there is a service pack out for version 2
>> and
>> the service pack for version 3 will be released this fall).
>>
>> The fix advocated by level one support was to reset the update
>> catalog
>> by clearing the software distribution folder and resetting the
>> catroot2
>> folder. Of course you had to go stop a few services in order to
>> rename
>> the folder so the process seemed a bit complicated but if you took
>> that route you were on a fools errand. (Level one support has since
>> been re-educated). Downloading the files directly off the web site
>> did
>> not resolve the issue either, unless you got lucky and added service
>> pack 1 during the process and did not have version 2 or 3 on your
>> computer.
>>
>>
>> So, here is the fix:
>
> <snip>
>
> What sounds even better to me, much better, would be for MS to fix the
> damn issue, and put out an update that actually works.
> Obviously, this is not a minor issue, it is affecting many many users. No
> telling how many, that don't even know about Usenet or how to find their
> way to this forum...

I agree entirely.

Worse part is I'm still one dial-up as I travel and sometimes need to use a
modem if no high-speed exists.

To spend two days downloading a bunch of NET (3 versions!) software for a
re-installation for an update is ridiculous to the max.

They blew this NET update nonsense a year ago and still are doing it.

B~

Why not just uninstall all this .net crap and be done with it forever. I've
read only a very few people use or need it anyway????

"B. Peg" wrote:

> > "Don Burnette" wrote:
> > <> wrote:
> >> The windows update for .Net Framework has created considerable
> >> problems for a lot of users. Those that have contacted Microsoft
> >> prior
> >> to July 12 or July 13 were given bad information on how to fix the
> >> update. First, a bit of history: The update is for .Net Framework 1.1
> >> service pack 1, not the original installation of .Net Framework 1.
> >> The
> >> service pack was an optional update that many users did not upload.
> >> Hence the latest security update was doomed to fail. The security
> >> update did not search for the right version prior to installation so
> >> either you got a installation failure message or it "updated
> >> successfully" only to reappear as a needed update a few minutes later.
> >> If you were unfortunate enough to add .Net Framework version 2 or 3
> >> without uploading your service pack to version 1 your headaches just
> >> got worse. (Please note: there is a service pack out for version 2
> >> and
> >> the service pack for version 3 will be released this fall).
> >>
> >> The fix advocated by level one support was to reset the update
> >> catalog
> >> by clearing the software distribution folder and resetting the
> >> catroot2
> >> folder. Of course you had to go stop a few services in order to
> >> rename
> >> the folder so the process seemed a bit complicated but if you took
> >> that route you were on a fools errand. (Level one support has since
> >> been re-educated). Downloading the files directly off the web site
> >> did
> >> not resolve the issue either, unless you got lucky and added service
> >> pack 1 during the process and did not have version 2 or 3 on your
> >> computer.
> >>
> >>
> >> So, here is the fix:
> >
> > <snip>
> >
> > What sounds even better to me, much better, would be for MS to fix the
> > damn issue, and put out an update that actually works.
> > Obviously, this is not a minor issue, it is affecting many many users. No
> > telling how many, that don't even know about Usenet or how to find their
> > way to this forum...
>
> I agree entirely.
>
> Worse part is I'm still one dial-up as I travel and sometimes need to use a
> modem if no high-speed exists.
>
> To spend two days downloading a bunch of NET (3 versions!) software for a
> re-installation for an update is ridiculous to the max.
>
> They blew this NET update nonsense a year ago and still are doing it.
>
> B~
>
>
>
>
>

Thank you for saying what a billion other computer users in the world must
be thinking!

Michael Dubar


"Don Burnette" wrote:

>
>
>
>
> <> wrote in message
> news: oups.com...
> > The windows update for .Net Framework has created considerable
> > problems for a lot of users. Those that have contacted Microsoft
> > prior
> > to July 12 or July 13 were given bad information on how to fix the
> > update. First, a bit of history: The update is for .Net Framework 1.1
> > service pack 1, not the original installation of .Net Framework 1.
> > The
> > service pack was an optional update that many users did not upload.
> > Hence the latest security update was doomed to fail. The security
> > update did not search for the right version prior to installation so
> > either you got a installation failure message or it "updated
> > sucessfully" only to reappear as a needed update a few minutes later.
> > If you were unfortunate enough to add .Net Framework version 2 or 3
> > without uploading your service pack to version 1 your headaches just
> > got worse. (Please note: there is a service pack out for version 2
> > and
> > the service pack for version 3 will be released this fall).
> >
> > The fix advocated by level one support was to reset the update
> > catalog
> > by clearing the software distribution folder and reseting the
> > catroot2
> > folder. Of course you had to go stop a few services in order to
> > rename
> > the folder so the process seemed a bit complicated but if you took
> > that route you were on a fools errand. (Level one support has since
> > been re-educated). Downloading the files directly off the web site
> > did
> > not resolve the issue either, unless you got lucky and added service
> > pack 1 during the process and did not have version 2 or 3 on your
> > computer.
> >
> >
> > So, here is the fix:
>
> <snip>
>
> What sounds even better to me, much better, would be for MS to fix the damn
> issue, and put out an update that actually works.
> Obviously, this is not a minor issue, it is affecting many many users. No
> telling how many, that don't even know about usenet or how to find their way
> to this forum...
>
>
>
> --
> Don
>
>
>
>

"B. Peg" <> wrote in message
news:yIYli.317716$...
>> "Don Burnette" wrote:
>> <> wrote:
>>> The windows update for .Net Framework has created considerable
>>> problems for a lot of users. Those that have contacted Microsoft
>>> prior
>>> to July 12 or July 13 were given bad information on how to fix the
>>> update. First, a bit of history: The update is for .Net Framework 1.1
>>> service pack 1, not the original installation of .Net Framework 1.
>>> The
>>> service pack was an optional update that many users did not upload.
>>> Hence the latest security update was doomed to fail. The security
>>> update did not search for the right version prior to installation so
>>> either you got a installation failure message or it "updated
>>> successfully" only to reappear as a needed update a few minutes later.
>>> If you were unfortunate enough to add .Net Framework version 2 or 3
>>> without uploading your service pack to version 1 your headaches just
>>> got worse. (Please note: there is a service pack out for version 2
>>> and
>>> the service pack for version 3 will be released this fall).
>>>
>>> The fix advocated by level one support was to reset the update
>>> catalog
>>> by clearing the software distribution folder and resetting the
>>> catroot2
>>> folder. Of course you had to go stop a few services in order to
>>> rename
>>> the folder so the process seemed a bit complicated but if you took
>>> that route you were on a fools errand. (Level one support has since
>>> been re-educated). Downloading the files directly off the web site
>>> did
>>> not resolve the issue either, unless you got lucky and added service
>>> pack 1 during the process and did not have version 2 or 3 on your
>>> computer.
>>>
>>>
>>> So, here is the fix:
>>
>> <snip>
>>
>> What sounds even better to me, much better, would be for MS to fix the
>> damn issue, and put out an update that actually works.
>> Obviously, this is not a minor issue, it is affecting many many users. No
>> telling how many, that don't even know about Usenet or how to find their
>> way to this forum...
>
> I agree entirely.
>
> Worse part is I'm still one dial-up as I travel and sometimes need to use
> a modem if no high-speed exists.
>
> To spend two days downloading a bunch of NET (3 versions!) software for a
> re-installation for an update is ridiculous to the max.
>
> They blew this NET update nonsense a year ago and still are doing it.
>
> B~
I've had it....I just sold my MS stock and put it all in AAPL .
Bob

For clarification, this is what I was trying to convey with my original post
and subsequent fix. This is copied and pasted from another post in this
discussion:


"I have had similar progress on this and managed to get the update stop
trying
to install by doing the following.

Open the install by clicking on the update shield icon in the tray.
Select custom install
deselect the install by clicking on the little tick
then close the window
A dialogue box should pop up asking you if you want to ignore this install,
just say yes.

(I think that if needed you can turn on all ignored updates again from the
automatic updates settings dialogue box on the security center)

Hopefully microsoft will sort out a fix for this whole problem as I cant
imagine that the fix supplied is within the concept of many PC users."