Sean Thompson <sea...@newsgroups.nospam> wrote: > Yip. cant install. > Just hangs. > WE WANT ANSWERS
The answers have been posted many many times in this newsgroup - a simple search on 917283 would have found the many threads devoted to this topic. The following is a revised version of an earlier post by TKang:
Note: a. Some ATI VGA users may need to disable/exit the Catalyst Control Center (which uses .NET) before updating the framework. b. Users of Windows Live OneCare must disable that application before removing or updating the Framework.
3: Use control panel Add/Remove Programs to uninstall Microsoft .NET Framework, Version 2.0 and reboot. Do not touch .NET Framework 1.1.
3a: see note below at step 7.
4: Install Microsoft .NET Framework, Version 2.0 (for 32-bit: dotnetfx.exe 3/22/2006) or (for 64-bit: NetFx64.exe 3/30/2006) and reboot.
5: Then run MS Update (and install KB917283) then reboot.
6: Turn automatic updates on (assuming that is your preference).
7. If this procedure failed to allow update 917283 to work, then repeat the procedure, adding the following at step 3a: Download http://astebner.sts.winisp.net/Tools/dotnetfx_cleanup_tool.zip and unzip it. Run the enclosed application, and select to clean up .NET Framework 2.0. Now continue above from step 4.
>> Yip. cant install. >> Just hangs. >> WE WANT ANSWERS
> The answers have been posted many many times in this newsgroup - a simple > search on 917283 would have found the many threads devoted to this topic. > The following is a revised version of an earlier post by TKang:
> Note: > a. Some ATI VGA users may need to disable/exit the Catalyst Control Center > (which uses .NET) before updating the framework. > b. Users of Windows Live OneCare must disable that application before > removing or updating the Framework.
> 3: Use control panel Add/Remove Programs to uninstall Microsoft .NET > Framework, Version 2.0 and reboot. Do not touch .NET Framework 1.1.
> 3a: see note below at step 7.
> 4: Install Microsoft .NET Framework, Version 2.0 (for 32-bit: dotnetfx.exe > 3/22/2006) or (for 64-bit: NetFx64.exe 3/30/2006) and reboot.
> 5: Then run MS Update (and install KB917283) then reboot.
> 6: Turn automatic updates on (assuming that is your preference).
> 7. If this procedure failed to allow update 917283 to work, then repeat > the procedure, adding the following at step 3a: > Download http://astebner.sts.winisp.net/Tools/dotnetfx_cleanup_tool.zip > and unzip it. Run the enclosed application, and select to clean up .NET > Framework 2.0. Now continue above from step 4.
> -- > Robin Walker [MVP Networking] > r...@cam.ac.uk
>> Yip. cant install. >> Just hangs. >> WE WANT ANSWERS
> The answers have been posted many many times in this newsgroup - a simple > search on 917283 would have found the many threads devoted to this topic. The > following is a revised version of an earlier post by TKang:
> Note: > a. Some ATI VGA users may need to disable/exit the Catalyst Control Center > (which uses .NET) before updating the framework. > b. Users of Windows Live OneCare must disable that application before removing > or updating the Framework.
> 3: Use control panel Add/Remove Programs to uninstall Microsoft .NET > Framework, Version 2.0 and reboot. Do not touch .NET Framework 1.1.
> 3a: see note below at step 7.
> 4: Install Microsoft .NET Framework, Version 2.0 (for 32-bit: dotnetfx.exe > 3/22/2006) or (for 64-bit: NetFx64.exe 3/30/2006) and reboot.
> 5: Then run MS Update (and install KB917283) then reboot.
> 6: Turn automatic updates on (assuming that is your preference).
> 7. If this procedure failed to allow update 917283 to work, then repeat the > procedure, adding the following at step 3a: > Download http://astebner.sts.winisp.net/Tools/dotnetfx_cleanup_tool.zip and > unzip it. Run the enclosed application, and select to clean up .NET Framework > 2.0. Now continue above from step 4.
What we have ran into (alot) in a number of gaming communities is the .NET 2.0 was not the MS FEB06 release on their PC's. I have seen issues (corrupted .NET) from reinstalling/overwriting .NET framework; including VGA Card install discs and a couple outdated download sites (not MS). For whatever reason... MS seemingly has not caught it through automatic updates. To correct the situation is to completely uninstall v2.0 and reinstall it. KB917283 apparently needs to the FEB06 .NET update to install.
I might add that the Windows Live Safety Center "is a new, free service designed to help ensure the health of your PC." http://safety.live.com/site/en-us/default.htm You might run the Free Full Service Scan to clean up the registry before reinstalling .NET 2.0...
TKang <TK...@discussions.microsoft.com> wrote: > I might add that the Windows Live Safety Center "is a new, free > service designed to help ensure the health of your PC." > http://safety.live.com/site/en-us/default.htm > You might run the Free Full Service Scan to clean up the registry > before reinstalling .NET 2.0...
Please don't. That site permanently damages your registry so that no Office updates can be installed.
>> Yip. cant install. >> Just hangs. >> WE WANT ANSWERS
> The answers have been posted many many times in this newsgroup - a simple > search on 917283 would have found the many threads devoted to this topic. The > following is a revised version of an earlier post by TKang:
> Note: > a. Some ATI VGA users may need to disable/exit the Catalyst Control Center > (which uses .NET) before updating the framework. > b. Users of Windows Live OneCare must disable that application before removing > or updating the Framework.
> 3: Use control panel Add/Remove Programs to uninstall Microsoft .NET > Framework, Version 2.0 and reboot. Do not touch .NET Framework 1.1.
> 3a: see note below at step 7.
> 4: Install Microsoft .NET Framework, Version 2.0 (for 32-bit: dotnetfx.exe > 3/22/2006) or (for 64-bit: NetFx64.exe 3/30/2006) and reboot.
> 5: Then run MS Update (and install KB917283) then reboot.
> 6: Turn automatic updates on (assuming that is your preference).
> 7. If this procedure failed to allow update 917283 to work, then repeat the > procedure, adding the following at step 3a: > Download http://astebner.sts.winisp.net/Tools/dotnetfx_cleanup_tool.zip and > unzip it. Run the enclosed application, and select to clean up .NET Framework > 2.0. Now continue above from step 4.
The second one indicates that you have an application on your PC which is using .NET 2.0, and therefore .NET 2.0 cannot be uninstalled unless that application is first disabled (or uninstalled). Typical examples are: the new control panel for ATI video cards, or Windows OneCare anti-virus.
The third one is a consequence of the second.
It is possible that you have a beta version of .NET 2.0 currently installed, as a side-effect of installing an application that wanted .NET 2.0 itself, such as a game, or the above-mentioned applications. The updates on Windows Update will not touch the beta versions, only the proper release. You would only have installed the proper release by download from MS: it was never a critical update, only an optional update.
It seems to me that you have two alternative routes forward:
1. Try to identify and remove all application that are dependent on .NET 2.0, then remove .NET 2.0, and re-install with the general release of .NET 2.0.
2. Just try re-installing the general release version of .NET 2.0 on top of whatever you have at the moment, without first uninstalling.
> The second one indicates that you have an application on your PC which is > using .NET 2.0, and therefore .NET 2.0 cannot be uninstalled unless that > application is first disabled (or uninstalled). Typical examples are: the new > control panel for ATI video cards, or Windows OneCare anti-virus.
> The third one is a consequence of the second.
> It is possible that you have a beta version of .NET 2.0 currently installed, > as a side-effect of installing an application that wanted .NET 2.0 itself, > such as a game, or the above-mentioned applications. The updates on Windows > Update will not touch the beta versions, only the proper release. You would > only have installed the proper release by download from MS: it was never a > critical update, only an optional update.
> It seems to me that you have two alternative routes forward:
> 1. Try to identify and remove all application that are dependent on .NET 2.0, > then remove .NET 2.0, and re-install with the general release of .NET 2.0.
> 2. Just try re-installing the general release version of .NET 2.0 on top of > whatever you have at the moment, without first uninstalling.
> The second one indicates that you have an application on your PC which is > using .NET 2.0, and therefore .NET 2.0 cannot be uninstalled unless that > application is first disabled (or uninstalled). Typical examples are: the new > control panel for ATI video cards, or Windows OneCare anti-virus.
> The third one is a consequence of the second.
> It is possible that you have a beta version of .NET 2.0 currently installed, > as a side-effect of installing an application that wanted .NET 2.0 itself, > such as a game, or the above-mentioned applications. The updates on Windows > Update will not touch the beta versions, only the proper release. You would > only have installed the proper release by download from MS: it was never a > critical update, only an optional update.
> It seems to me that you have two alternative routes forward:
> 1. Try to identify and remove all application that are dependent on .NET 2.0, > then remove .NET 2.0, and re-install with the general release of .NET 2.0.
> 2. Just try re-installing the general release version of .NET 2.0 on top of > whatever you have at the moment, without first uninstalling.
> it appears that I do have a beta version installed
That explains where the problem came from.
Now, given that you do not know which specific application is using .NET 2.0, we are going to disable all start-up items so that you can boot XP with no extras. This will leave you temporarily without any third-party anti-virus or firewall, so disconnect from the internet while you do this.
1. Click Start->Run, and type in msconfig
2. Click the "Startup" tab. Note your current selections if you already have some disabled items, then click "Disable all".
3. Click the "Services" tab. Check "Hide all Microsoft Services". Again note the current selections if there are already disabled items, then disable all (non-Microsoft) Services by unchecking the tick-box for each one.
4. Click OK and restart Windows.
Windows should now restart in a clean state with no extras running. You should now be able to uninstall .NET 2.0 and install the proper non-Beta version which you previously downloaded from Microsoft.
When that is done, use msconfig again to restore the settings the way they were before steps 2 and 3 above, and restart again. When you get a dialog from msconfig saying that you are running a custom start-up configuration, check the box to "do not show this again" and click OK. You should now have all yourthird-party add-ons running again.
>> it appears that I do have a beta version installed
> That explains where the problem came from.
> Now, given that you do not know which specific application is using .NET 2.0, > we are going to disable all start-up items so that you can boot XP with no > extras. This will leave you temporarily without any third-party anti-virus or > firewall, so disconnect from the internet while you do this.
> 1. Click Start->Run, and type in > msconfig
> 2. Click the "Startup" tab. Note your current selections if you already have > some disabled items, then click "Disable all".
> 3. Click the "Services" tab. Check "Hide all Microsoft Services". Again note > the current selections if there are already disabled items, then disable all > (non-Microsoft) Services by unchecking the tick-box for each one.
> 4. Click OK and restart Windows.
> Windows should now restart in a clean state with no extras running. You > should now be able to uninstall .NET 2.0 and install the proper non-Beta > version which you previously downloaded from Microsoft.
> When that is done, use msconfig again to restore the settings the way they > were before steps 2 and 3 above, and restart again. When you get a dialog > from msconfig saying that you are running a custom start-up configuration, > check the box to "do not show this again" and click OK. You should now have > all yourthird-party add-ons running again.
> would it save time if I simply boot into safe mood?
I like the idea of a safe mood - maybe it comes from sipping all that green tea.
Yes, try it, and let us know. At this stage, I don't know whether the uninstall and re-install of the .NET Framework will work under Safe Mode. We just need someone to try and report back.
|
