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

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

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 ****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 George. I have gone through all the process up to and including
installing .NET 1.1 but I'm still wondering...

Do most people need .NET on their computers? It seems to be for developers,
although MS warns that some programs may not work but which programs rely on
..NET?
--
Lenny V


"" 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 ****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 VERY MUCH IT WAS EASY AFTER I READ WHAT YOU HAD TO SAY THANKS AGAIN
ONE HAPPY GREY SURFER..........

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

"YOU" are the man! (it worked great first time)

thanks ray.



"" 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 very much for the information. With this dial-up connection it looks I
won't get bored for the next couple days or so.

"" 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 ****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 !!! Looks like I will have plenty to do for a couple days or more with
this dial-up connection. Do you know if I should have .NET 3.0 ? it doesn't
show on the Add/Remove page. But then again .NET Framework 1.1 Service pack 1
doesn't show either and when I try to download and install it give me the
message that it is installed. Couldn't be a MS screw up !!!

"LennyV" wrote:

> Thanks George. I have gone through all the process up to and including
> installing .NET 1.1 but I'm still wondering...
>
> Do most people need .NET on their computers? It seems to be for developers,
> although MS warns that some programs may not work but which programs rely on
> .NET?
> --
> Lenny V
>
>
> "" 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 ****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 successfully applied George's alternative Posted As 'RE: KB928365 and
KB928366 PROBLEM SOLVED READ!!!!' Thus reinstalled dotnetfx (after msi
cleanup utility) 1.1 , then update net 1.12 with kb928366. Finally
reinstalled dotNet2.0 after which the update kb928365 was applied via ms
Update normally.
Thanks very much George

"vc" 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
>

On Jul 12, 2:25 am, georgel...@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 ****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...d=262D25E3-F58...
>
> 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...d=A8F5654F-088...
>
> 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

Indeed this worked, Thank You! I was so sick of the yellow
notification icon. I had like seven "successful" installations in my
history yet the icon. Thank you again!

Geez , everyone gives George the thanks, not me. and it was MY post. LOL

"vc" <> wrote in message
news:6ejli.13312$g44.6846@trnddc02...
> 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