RE: KB928365 and KB928366 PROBLEM SOLVED READ!!!!

[hstokar@stokar.com]

Only this one worked for me....withall of the damned reboots and running no
other programs than this calls for (found elsewhere in these threads):

1. Download and install this
http://download.microsoft.com/downlo...BD/msicuu2.exe
2. Run it (Windows Installer Clean Up) from the start menu
and look for/remove .NET Framework.
3. Reboot.
4. Download/install this
http://download.microsoft.com/downlo...6/dotnetfx.exe
5. Reboot.
6. Download/install this:

http://download.microsoft.com/downlo...867460-X86.exe
7. Reboot.
8. Download/install this
http://www.download.windowsupdate.co...d81a178b15.exe
9. Reboot.

Visit http://windowsupdate.microsoft.com/ and scan
for/install critical updates.

[Don Burnette]

I just tried the below, NDP1 will not install for me, says it cannot verify
the patch or something like that.

Glad to see this works for some, but certainly is not getting it for me. I
went ahead and tried visiting windows update again, still no go.

MS, has screwed up royally, with this update. I just hope I am not screwing
something on my system, but doing all of this...





--
Don


"hstokar@stokar.com" <hstokarstokarcom@discussions.microsoft.com> wrote in
message news:B6BADF05-82F5-43DC-A614-EDD1920435ED@microsoft.com...
> Only this one worked for me....withall of the damned reboots and running
> no
> other programs than this calls for (found elsewhere in these threads):
>
> 1. Download and install this:
> http://download.microsoft.com/downlo...BD/msicuu2.exe
> 2. Run it (Windows Installer Clean Up) from the start menu
> and look for/remove .NET Framework.
> 3. Reboot.
> 4. Download/install this:
> http://download.microsoft.com/downlo...6/dotnetfx.exe
> 5. Reboot.
> 6. Download/install this:
>
> http://download.microsoft.com/downlo...867460-X86.exe
> 7. Reboot.
> 8. Download/install this:
> http://www.download.windowsupdate.co...d81a178b15.exe
> 9. Reboot.
>
> Visit http://windowsupdate.microsoft.com/ and scan
> for/install critical updates.
>

[Ashvajit]

Hi George, I'm trying to live happily ever after BUT ... have hit a snag. I
wonder if you can help?

I've deleted all the .NET installations, installed dotnetfx.exe, and then
I've tried to install the NDP.1 exe file. I then get the following message:

"The upgrade patch cannot be installed by Windows Installer Service because
the program to be upgraded may be missing, or the upgrade patch may update a
different version of the program. Verify that the program to be updated
exists on your computer and that you have the correct upgrade patch."

I'm best at following instructions rather than working things out for
myself, so can you suggest what's to be done here?

Mike

> Here is EXACTLY what you do to solve this problem for Windows XP 32
> bit. If you happen to have a rarer 64 bit version, server OS, or
> SOMETHING else follow the same general instructions but get the
> version of the files appropriate for your system but first, Microsoft
> has pissed me off beyond belief. I looked in my log and this same
> thing happened 6/2006...thanks MSFT for torturing us again this year.
> I thought it was a familiar feeling...nice branding...this is a huge
> humiliation for their .NET team in my opinion or perhaps we should
> start calling them the .NOT team...anyway....
>
> Steps:
> 1) Go to the control panel and select the add/remove software tool
> then TRY and remove everything with .NET in the name. If you can
> remove everything go to step 3. If you cannot remove everything go to
> step 2.
>
> 2) Go and download the windows installer clean up tool at:
> http://support.microsoft.com/kb/290301
>
> run the windows installer clean up tool and BE CAREFUL to only select
> the .NET items from the list and remove them. Note: this will likely
> leave the names as "dead links" in the Add/Remove Software list
> (ahhh ...Microsoft thoroughness at its best) but not to worry they
> will do no harm and will get fixed when we finish. It's possible to
> clean them up but let's stay out of the registry :-)
>
> 3) Go and get the file "dotnetfx.exe" this is ".NET 1.1" from:
>
> http://www.microsoft.com/downloads/d...displaylang=en
>
> install it.
>
> 4) Go and get the file "NDP1.1sp1-KB867460-X86.exe" this is the ".NET
> 1.1 service pack 1" from: my personal website (JUST KIDDING,
> RELAX...get everything of course from a microsoft.com domain)
>
> http://www.microsoft.com/downloads/d...displaylang=en
>
> install it.
>
> 5) Install the SECURITY patch, the dreaded KB928366, we have all grown
> to hate. You can install it from the Windows Update program (be sure
> to ONLY select the KB928366 patch and NOTHING else, we dont want to
> put back 2.0 or 3.0 yet). It's OK go ahead and click ...it will be
> alright...you can do it...it's just one more time... :-)
>
> 6) Re-run the Windows Update and you can add back in .NET 2.0 and 3.0
>
> 7) Post to thank me...
>
> Now WHY hasn't Microsoft posted instructions yet? .... What is UP?!
>
> Good night!
>
> George

[PA Bear]

1. Uninstall the .NET Framework version(s) in question;

2. Download and run this Uninstall Clean-up tool:
http://www.microsoft.com/downloads/d...4-97BD16967A09

3. Search the MS Download Center
http://www.microsoft.com/downloads/Search.aspx) for the .NET Framework
version(s) you need to reinstall, then download & install them;

4. Download/install the update(s) via Windows Update or Automatic Updates.
--
~Robear Dyer (PA Bear)
MS MVP-Windows (IE, OE, Security, Shell/User)
AumHa VSOP & Admin; DTS-L.org

Ashvajit wrote:
> Hi George, I'm trying to live happily ever after BUT ... have hit a snag.
> I
> wonder if you can help?
>
> I've deleted all the .NET installations, installed dotnetfx.exe, and then
> I've tried to install the NDP.1 exe file. I then get the following
> message:
>
> "The upgrade patch cannot be installed by Windows Installer Service
> because
> the program to be upgraded may be missing, or the upgrade patch may update
> a
> different version of the program. Verify that the program to be updated
> exists on your computer and that you have the correct upgrade patch."
>
> I'm best at following instructions rather than working things out for
> myself, so can you suggest what's to be done here?
>
> Mike
>
>> Here is EXACTLY what you do to solve this problem for Windows XP 32
>> bit. If you happen to have a rarer 64 bit version, server OS, or
>> SOMETHING else follow the same general instructions but get the
>> version of the files appropriate for your system but first, Microsoft
>> has pissed me off beyond belief. I looked in my log and this same
>> thing happened 6/2006...thanks MSFT for torturing us again this year.
>> I thought it was a familiar feeling...nice branding...this is a huge
>> humiliation for their .NET team in my opinion or perhaps we should
>> start calling them the .NOT team...anyway....
>>
>> Steps:
>> 1) Go to the control panel and select the add/remove software tool
>> then TRY and remove everything with .NET in the name. If you can
>> remove everything go to step 3. If you cannot remove everything go to
>> step 2.
>>
>> 2) Go and download the windows installer clean up tool at:
>> http://support.microsoft.com/kb/290301
>>
>> run the windows installer clean up tool and BE CAREFUL to only select
>> the .NET items from the list and remove them. Note: this will likely
>> leave the names as "dead links" in the Add/Remove Software list
>> (ahhh ...Microsoft thoroughness at its best) but not to worry they
>> will do no harm and will get fixed when we finish. It's possible to
>> clean them up but let's stay out of the registry :-)
>>
>> 3) Go and get the file "dotnetfx.exe" this is ".NET 1.1" from:
>>
>> http://www.microsoft.com/downloads/d...displaylang=en
>>
>> install it.
>>
>> 4) Go and get the file "NDP1.1sp1-KB867460-X86.exe" this is the ".NET
>> 1.1 service pack 1" from: my personal website (JUST KIDDING,
>> RELAX...get everything of course from a microsoft.com domain)
>>
>> http://www.microsoft.com/downloads/d...displaylang=en
>>
>> install it.
>>
>> 5) Install the SECURITY patch, the dreaded KB928366, we have all grown
>> to hate. You can install it from the Windows Update program (be sure
>> to ONLY select the KB928366 patch and NOTHING else, we dont want to
>> put back 2.0 or 3.0 yet). It's OK go ahead and click ...it will be
>> alright...you can do it...it's just one more time... :-)
>>
>> 6) Re-run the Windows Update and you can add back in .NET 2.0 and 3.0
>>
>> 7) Post to thank me...
>>
>> Now WHY hasn't Microsoft posted instructions yet? .... What is UP?!
>>
>> Good night!
>>
>> George

[Jim]

As of this writing I still don't have the KB928366 update issue resolved. In
the past 3 weeks I have had 3 different support techs and none have been able
to fix this problem. Most of the solutions they gave me were the same ones
George had posted. The latest one completely cleaned all NET Framework files
but now I am unable to open the Windows OneCare Live. Someone questioned even
installing NET Framework, I don't know what other programs use it other than
Windows OneCare Live. One time I had problems with it and had to remove all
NET Framework programs and reinstall them. I can't help but think that the
money spent paying the 3 support techs would have been better spent if
Microsoft had designed another update to update the update. My confidence
level in Microsoft drops with each passing day !!!!!!!!!!!!!!!!!!!

"rayso1" wrote:

> georgelaz7@yahoo.com "YOU" are the man! (it worked great first time)
>
> thanks ray.
>
>
>
> "georgelaz7@yahoo.com" wrote:
>
> >
> > Here is EXACTLY what you do to solve this problem for Windows XP 32
> > bit. If you happen to have a rarer 64 bit version, server OS, or
> > SOMETHING else follow the same general instructions but get the
> > version of the files appropriate for your system but first, Microsoft
> > has pissed me off beyond belief. I looked in my log and this same
> > thing happened 6/2006...thanks MSFT for torturing us again this year.
> > I thought it was a familiar feeling...nice branding...this is a huge
> > humiliation for their .NET team in my opinion or perhaps we should
> > start calling them the .NOT team...anyway....
> >
> > Steps:
> > 1) Go to the control panel and select the add/remove software tool
> > then TRY and remove everything with .NET in the name. If you can
> > remove everything go to step 3. If you cannot remove everything go to
> > step 2.
> >
> > 2) Go and download the windows installer clean up tool at:
> > http://support.microsoft.com/kb/290301
> >
> > run the windows installer clean up tool and BE CAREFUL to only select
> > the .NET items from the list and remove them. Note: this will likely
> > leave the names as "dead links" in the Add/Remove Software list
> > (ahhh ...Microsoft thoroughness at its best) but not to worry they
> > will do no harm and will get fixed when we finish. It's possible to
> > clean them up but let's stay out of the registry :-)
> >
> > 3) Go and get the file "dotnetfx.exe" this is ".NET 1.1" from:
> >
> > http://www.microsoft.com/downloads/d...displaylang=en
> >
> > install it.
> >
> > 4) Go and get the file "NDP1.1sp1-KB867460-X86.exe" this is the ".NET
> > 1.1 service pack 1" from: my personal website (JUST KIDDING,
> > RELAX...get everything of course from a microsoft.com domain)
> >
> > http://www.microsoft.com/downloads/d...displaylang=en
> >
> > install it.
> >
> > 5) Install the SECURITY patch, the dreaded KB928366, we have all grown
> > to hate. You can install it from the Windows Update program (be sure
> > to ONLY select the KB928366 patch and NOTHING else, we dont want to
> > put back 2.0 or 3.0 yet). It's OK go ahead and click ...it will be
> > alright...you can do it...it's just one more time... :-)
> >
> > 6) Re-run the Windows Update and you can add back in .NET 2.0 and 3.0
> >
> > 7) Post to thank me...
> >
> > Now WHY hasn't Microsoft posted instructions yet? .... What is UP?!
> >
> > Good night!
> >
> > George
> >
> >

[Old Crow]

Thanks George,
You should be paid by Microsoft.
I wish I had found this post sooner.
Crow

"georgelaz7@yahoo.com" wrote:

> On Jul 12, 1:45 am, vc <vcolo...@hotmail.com> wrote:
> > Go to the windows update page. Unchecked the updates and expand the tree
> > (click on + sign). Choose to hide these updates. YOU DON'T NEED THAT
> > CRAP ANYWAY.
> > Live happily ever after.
> >
> > Peace
> > Shagg
>
> Here is EXACTLY what you do to solve this problem for Windows XP 32
> bit. If you happen to have a rarer 64 bit version, server OS, or
> SOMETHING else follow the same general instructions but get the
> version of the files appropriate for your system but first, Microsoft
> has pissed me off beyond belief. I looked in my log and this same
> thing happened 6/2006...thanks MSFT for torturing us again this year.
> I thought it was a familiar feeling...nice branding...this is a huge
> humiliation for their .NET team in my opinion or perhaps we should
> start calling them the .NOT team...anyway....
>
> Steps:
> 1) Go to the control panel and select the add/remove software tool
> then TRY and remove everything with .NET in the name. If you can
> remove everything go to step 3. If you cannot remove everything go to
> step 2.
>
> 2) Go and download the windows installer clean up tool at:
> http://support.microsoft.com/kb/290301
>
> run the windows installer clean up tool and BE CAREFUL to only select
> the .NET items from the list and remove them. Note: this will likely
> leave the names as "dead links" in the Add/Remove Software list
> (ahhh ...Microsoft thoroughness at its best) but not to worry they
> will do no harm and will get fixed when we finish. It's possible to
> clean them up but let's stay out of the registry :-)
>
> 3) Go and get the file "dotnetfx.exe" this is ".NET 1.1" from:
>
> http://www.microsoft.com/downloads/d...displaylang=en
>
> install it.
>
> 4) Go and get the file "NDP1.1sp1-KB867460-X86.exe" this is the ".NET
> 1.1 service pack 1" from: my personal website (JUST KIDDING,
> RELAX...get everything of course from a microsoft.com domain)
>
> http://www.microsoft.com/downloads/d...displaylang=en
>
> install it.
>
> 5) Install the SECURITY patch, the dreaded KB928366, we have all grown
> to hate. You can install it from the Windows Update program (be sure
> to ONLY select the KB928366 patch and NOTHING else, we dont want to
> put back 2.0 or 3.0 yet). It's OK go ahead and click ...it will be
> alright...you can do it...it's just one more time... :-)
>
> 6) Re-run the Windows Update and you can add back in .NET 2.0 and 3.0
>
> 7) Post to thank me...
>
> Now WHY hasn't Microsoft posted instructions yet? .... What is UP?!
>
> Good night!
>
> George
>
>

[margfan@gmail.com]

On Aug 3, 8:14 pm, Jim <j...@discussions.microsoft.com> wrote:
> As of this writing I still don't have the KB928366 update issue resolved. In
> the past 3 weeks I have had 3 different support techs and none have been able
> to fix this problem. Most of the solutions they gave me were the same ones
> George had posted. The latest one completely cleaned all NET Framework files
> but now I am unable to open the Windows OneCare Live. Someone questioned even
> installing NET Framework, I don't know what other programs use it other than
> Windows OneCare Live. One time I had problems with it and had to remove all
> NET Framework programs and reinstall them. I can't help but think that the
> money spent paying the 3 support techs would have been better spent if
> Microsoft had designed another update to update the update. My confidence
> level in Microsoft drops with each passing day !!!!!!!!!!!!!!!!!!!
>
>
>
>

At work I have discovered installing a Windows Installed update
(KB893803), I could install KB928365 without uninstalling any .NET
files. It has worked on several machines.

http://www.microsoft.com/downloads/d...displaylang=en

http://support.microsoft.com/kb/893803

Hope this helps.

[abertil.a@telia.com]

georgel...@yahoo.com skrev:
> On Jul 12, 1:45 am, vc <vcolo...@hotmail.com> wrote:
> > Go to the windows update page. Unchecked the updates and expand the tree
> > (click on + sign). Choose to hide these updates. YOU DON'T NEED THAT
> > CRAP ANYWAY.
> > Live happily ever after.
> >
> > Peace
> > Shagg
>
> Here is EXACTLY what you do to solve this problem for Windows XP 32
> bit. If you happen to have a rarer 64 bit version, server OS, or
> SOMETHING else follow the same general instructions but get the
> version of the files appropriate for your system but first, Microsoft
> has pissed me off beyond belief. I looked in my log and this same
> thing happened 6/2006...thanks MSFT for torturing us again this year.
> I thought it was a familiar feeling...nice branding...this is a huge
> humiliation for their .NET team in my opinion or perhaps we should
> start calling them the .NOT team...anyway....
>
> Steps:
> 1) Go to the control panel and select the add/remove software tool
> then TRY and remove everything with .NET in the name. If you can
> remove everything go to step 3. If you cannot remove everything go to
> step 2.
>
> 2) Go and download the windows installer clean up tool at:
> http://support.microsoft.com/kb/290301
>
> run the windows installer clean up tool and BE CAREFUL to only select
> the .NET items from the list and remove them. Note: this will likely
> leave the names as "dead links" in the Add/Remove Software list
> (ahhh ...Microsoft thoroughness at its best) but not to worry they
> will do no harm and will get fixed when we finish. It's possible to
> clean them up but let's stay out of the registry :-)
>
> 3) Go and get the file "dotnetfx.exe" this is ".NET 1.1" from:
>
> http://www.microsoft.com/downloads/d...displaylang=en
>
> install it.
>
> 4) Go and get the file "NDP1.1sp1-KB867460-X86.exe" this is the ".NET
> 1.1 service pack 1" from: my personal website (JUST KIDDING,
> RELAX...get everything of course from a microsoft.com domain)
>
> http://www.microsoft.com/downloads/d...displaylang=en
>
> install it.
>
> 5) Install the SECURITY patch, the dreaded KB928366, we have all grown
> to hate. You can install it from the Windows Update program (be sure
> to ONLY select the KB928366 patch and NOTHING else, we dont want to
> put back 2.0 or 3.0 yet). It's OK go ahead and click ...it will be
> alright...you can do it...it's just one more time... :-)
>
> 6) Re-run the Windows Update and you can add back in .NET 2.0 and 3.0
>
> 7) Post to thank me...
>
> Now WHY hasn't Microsoft posted instructions yet? .... What is UP?!
>
> Good night!
>
> George

Hi George!

Your solution certainly made my day!

For more than a month I've been very annoyed by those icons popping up
and telling me that there is an update KB928366 which I need to have.
You bet I've tried to update but the icon still comes back. Looking in
the log of updates there is a number of green checkmarks from medio
July, but apperently something didn't get right. After applying your
solution everythings seems OK.

Again, thanks!

Bertila

[krazed]

thanks george. solved my problem. toobad m.s. couldn't. they are pathetic !!!
--
krazed


"georgelaz7@yahoo.com" wrote:

> On Jul 12, 1:45 am, vc <vcolo...@hotmail.com> wrote:
> > Go to the windows update page. Unchecked the updates and expand the tree
> > (click on + sign). Choose to hide these updates. YOU DON'T NEED THAT
> > CRAP ANYWAY.
> > Live happily ever after.
> >
> > Peace
> > Shagg
>
> Here is EXACTLY what you do to solve this problem for Windows XP 32
> bit. If you happen to have a rarer 64 bit version, server OS, or
> SOMETHING else follow the same general instructions but get the
> version of the files appropriate for your system but first, Microsoft
> has pissed me off beyond belief. I looked in my log and this same
> thing happened 6/2006...thanks MSFT for torturing us again this year.
> I thought it was a familiar feeling...nice branding...this is a huge
> humiliation for their .NET team in my opinion or perhaps we should
> start calling them the .NOT team...anyway....
>
> Steps:
> 1) Go to the control panel and select the add/remove software tool
> then TRY and remove everything with .NET in the name. If you can
> remove everything go to step 3. If you cannot remove everything go to
> step 2.
>
> 2) Go and download the windows installer clean up tool at:
> http://support.microsoft.com/kb/290301
>
> run the windows installer clean up tool and BE CAREFUL to only select
> the .NET items from the list and remove them. Note: this will likely
> leave the names as "dead links" in the Add/Remove Software list
> (ahhh ...Microsoft thoroughness at its best) but not to worry they
> will do no harm and will get fixed when we finish. It's possible to
> clean them up but let's stay out of the registry :-)
>
> 3) Go and get the file "dotnetfx.exe" this is ".NET 1.1" from:
>
> http://www.microsoft.com/downloads/d...displaylang=en
>
> install it.
>
> 4) Go and get the file "NDP1.1sp1-KB867460-X86.exe" this is the ".NET
> 1.1 service pack 1" from: my personal website (JUST KIDDING,
> RELAX...get everything of course from a microsoft.com domain)
>
> http://www.microsoft.com/downloads/d...displaylang=en
>
> install it.
>
> 5) Install the SECURITY patch, the dreaded KB928366, we have all grown
> to hate. You can install it from the Windows Update program (be sure
> to ONLY select the KB928366 patch and NOTHING else, we dont want to
> put back 2.0 or 3.0 yet). It's OK go ahead and click ...it will be
> alright...you can do it...it's just one more time... :-)
>
> 6) Re-run the Windows Update and you can add back in .NET 2.0 and 3.0
>
> 7) Post to thank me...
>
> Now WHY hasn't Microsoft posted instructions yet? .... What is UP?!
>
> Good night!
>
> George
>
>

[zcurves]

George,

You are the man!! Thank you, Thank you!!

Regards,
Andrew

"georgelaz7@yahoo.com" wrote:

> On Jul 12, 1:45 am, vc <vcolo...@hotmail.com> wrote:
> > Go to the windows update page. Unchecked the updates and expand the tree
> > (click on + sign). Choose to hide these updates. YOU DON'T NEED THAT
> > CRAP ANYWAY.
> > Live happily ever after.
> >
> > Peace
> > Shagg
>
> Here is EXACTLY what you do to solve this problem for Windows XP 32
> bit. If you happen to have a rarer 64 bit version, server OS, or
> SOMETHING else follow the same general instructions but get the
> version of the files appropriate for your system but first, Microsoft
> has pissed me off beyond belief. I looked in my log and this same
> thing happened 6/2006...thanks MSFT for torturing us again this year.
> I thought it was a familiar feeling...nice branding...this is a huge
> humiliation for their .NET team in my opinion or perhaps we should
> start calling them the .NOT team...anyway....
>
> Steps:
> 1) Go to the control panel and select the add/remove software tool
> then TRY and remove everything with .NET in the name. If you can
> remove everything go to step 3. If you cannot remove everything go to
> step 2.
>
> 2) Go and download the windows installer clean up tool at:
> http://support.microsoft.com/kb/290301
>
> run the windows installer clean up tool and BE CAREFUL to only select
> the .NET items from the list and remove them. Note: this will likely
> leave the names as "dead links" in the Add/Remove Software list
> (ahhh ...Microsoft thoroughness at its best) but not to worry they
> will do no harm and will get fixed when we finish. It's possible to
> clean them up but let's stay out of the registry :-)
>
> 3) Go and get the file "dotnetfx.exe" this is ".NET 1.1" from:
>
> http://www.microsoft.com/downloads/d...displaylang=en
>
> install it.
>
> 4) Go and get the file "NDP1.1sp1-KB867460-X86.exe" this is the ".NET
> 1.1 service pack 1" from: my personal website (JUST KIDDING,
> RELAX...get everything of course from a microsoft.com domain)
>
> http://www.microsoft.com/downloads/d...displaylang=en
>
> install it.
>
> 5) Install the SECURITY patch, the dreaded KB928366, we have all grown
> to hate. You can install it from the Windows Update program (be sure
> to ONLY select the KB928366 patch and NOTHING else, we dont want to
> put back 2.0 or 3.0 yet). It's OK go ahead and click ...it will be
> alright...you can do it...it's just one more time... :-)
>
> 6) Re-run the Windows Update and you can add back in .NET 2.0 and 3.0
>
> 7) Post to thank me...
>
> Now WHY hasn't Microsoft posted instructions yet? .... What is UP?!
>
> Good night!
>
> George
>
>