Chuckster Posted March 17, 2010 Posted March 17, 2010 Has anyone had a spate of workstations failing to install Microsoft .NET Framework 2.0 Services Pack 2 Security Update for Windows 2000, Windows Server 2003 and Windows XP? This update only fails if I rebuild a machine. Every update installs successfully.
tommccann Posted March 17, 2010 Posted March 17, 2010 i always have problems with framework, try downloadin it by the update number then self installing it
Chuckster Posted March 17, 2010 Author Posted March 17, 2010 I can't afford to go around to every workstation that fails to install this update. In WSUS I get the following error reported: Installation Failure: Windows failed to install the following update with error 0x80070643: Microsoft .NET Framework 2.0 Service Pack 2 Security Update for Windows 2000, Windows Server 2003, and Windows XP (KB974417). I've seen a few forums where people have stated this problem and none of which were in relation to networked PCs.
tommccann Posted March 17, 2010 Posted March 17, 2010 msi the installation file, then use gpo to roll it out
Chuckster Posted March 17, 2010 Author Posted March 17, 2010 When manually trying to install this update it fails over and says there's nothing to update! If that's the case then why do workstations download this update from WSUS? Can I remove 'approve' for any Frameworks that are version 1 and 2 and leave version 3? By doing so would it break anything?
tommccann Posted March 17, 2010 Posted March 17, 2010 yea i would, and if you require framework in the future for somthing fututr v4 or somthing then try it again
denon101 Posted March 17, 2010 Posted March 17, 2010 (edited) I have had a similar problem. I just can not get this update to install. I have tried everything. I have not settled with declining that update in WSUS and will worry about it when it may need updating in the future. Still a pain in the behind though. Edited March 17, 2010 by denon101
laserblazer Posted March 18, 2010 Posted March 18, 2010 I've been having no end of update fails of late. Try this: from the command line - net stop wuauserv rename the SoftwareDistribution folder in the Windows directory net start wuauserv run updates. It seems the update database can get corrupted.
K.C.Leblanc Posted March 19, 2010 Posted March 19, 2010 I would like to chip in the I have the current problem, and have tryed the following with no success; Deleting the local updates database as Laserblazer suggested. Removing .net and letting WSUS reinstall it. Removing .net, cleaning it with the .net cleanup utility. Rebuilding the PC. Getting really cross, and then a bit emotional.
Popular Post broc Posted March 19, 2010 Popular Post Posted March 19, 2010 I came across an item on the www about this yesterday that said: 1) uninstall KB976569 2) install KB974417 3) re-install KB976569 It worked for me..... 7
K.C.Leblanc Posted March 19, 2010 Posted March 19, 2010 I came across an item on the www about this yesterday that said: 1) uninstall KB976569 2) install KB974417 3) re-install KB976569 It worked for me..... Just trying this, managed to pick the school's slowest laptop.
broc Posted March 19, 2010 Posted March 19, 2010 Broc, you're a genius. I wish You have to give credit to the power of Google.....
Chuckster Posted March 23, 2010 Author Posted March 23, 2010 I've kept an eye on this thread since I first created it. After following the advice given by Broc (my saviour!), I can say his method works. Just rebuilt a machine and, I'm glad to say, it worked!
ShaneK0378 Posted March 29, 2010 Posted March 29, 2010 I came across an item on the www about this yesterday that said: 1) uninstall KB976569 2) install KB974417 3) re-install KB976569 It worked for me..... Awesome, worked for me, had to register to let you know. I searched Google and this is where it landed me!
Polpot Posted May 21, 2010 Posted May 21, 2010 This may help another novice to resolve a KB974417 installation problem. The solution that worked for me on a stand-alone WinXP Pro SP3 machine goes like this. Using Add/Remove programs, remove all instances of .NET framework beginning with the latest version first. Reboot. Next use MS Update to check for updates and install the offerred updates, lowest version no's first, then security updates etc. ONE AT A TIME, REBOOTING BEWTEEN EACH UPDATE. I know this is cumbersome but MS Update will only offer some updates once the preceding ones are already installed. About 8 reboots were required I think.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now