FAILED KB928365 and KB928366: ANSWER

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 ****ed 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

"" 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 ****ed 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
>
>

Doesn't work for me - fails at .NET2 installation - guess I will just have to
wait for a reply to my email to support.

"" 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 ****ed 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
>
>

I have got it now - had to reinstall .NET2 from add/remove programs then was
able to get the patch from UPDATE.

What a performance!

"" 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 ****ed 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
>
>

Hey George,

Worked for me - after twice trying to work it out myself.

Thanks for the detailed instructs - right on!

Doc



"" 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
>...
>
> Good night!
>
> George
>
>

Hey George.
An MS tech told me yesterday to install .NET framework 1.1, 2 and 3 all at
the same time. Then the KB928366 is already in the newer versions and you
don't have to deal with downloading it at all. He did that on my computer
(after deleting my .NET framework files) and everything worked! Relief!

"" 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 ****ed 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
>
>

Outstanding post george. Appreciate the help with this update snafu. Your
procedure worked perfectly.

Kevin

"" 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 ****ed 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
>
>

Well done George, nice to see that icon disappear so easy.

"" 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 ****ed 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
>
>

Thank you George - you're a marvel.. I'm not supremely technical but your
instructions were easy to follow and worked a treat - unlike Microsoft's
instructions..!!!?>?????

"" 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 ****ed 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
>
>

Thanks it worked. I will be forwarding this to the MS support professional
who was "helping" me with much less success...

"" 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 ****ed 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
>
>