Broadband Tech > Security > Security > Microsoft Security Bulletin Summary for October 13, 2009

reply to Steely

Re: KB953297 failed to install!

reply to Steely
I ended up calling Microsoft 866-PCSAFETY
After 1hour 30 min yesterday and 1 hour 50 today, they got it fixed. Not sure why uninstalling .net 1 was so difficult.

Of course I did, I spent over an hour on this site and others learning, and trying different things. Tried using the Windows removal tool, other stuff, still would not work.

So, the removal tool on Aaron Stebner's site didn't work? Did you then contact him by email? I hope you did if for no other reason than to report your problems with the tool. He welcomes email contact in difficult cases so that not only can he attempt to help you on a one to one basis but he can learn more about .NET problems which helps him help people more effectively. Aaron Stebner knows more about .NET that just about anyone else at Microsoft and certainly more than the folks at PC-SAFETY.
--
When governments fear people, there is liberty. When the people fear the government, there is tyranny. Thomas Jefferson

reply to NICK ADSL UK

Re: Microsoft Security Bulletin Summary for October 13, 2009

%systemroot%\Microsoft.NET\Framework
 

reply to NICK ADSL UK
I meant to post earlier. On XPHomeSP3 I reluctantly updated the Net Framework 1.1. It installed successfully. It's the only Net Framework installed on this computer with the Hotfix. Now add/remove shows Net Framework 1.1 and the hotifx listing has been replaced by this latest update.

Caff, I checked %systemroot%\Microsoft.NET\Framework and I only have v.1.0.3705 and v. 1.1.4322.

Sincerely, Libra

reply to HnLA

Re: KB953297 failed to install!

Just to confirm - same problem with this KB953297 as described countless times above. Following Analyzer's suggestion, I downloaded dotnetfx.exe, installed it (no reboot), then re-ran the windows update. This time KB953297 installed properly.

Rod

reply to Analyzer
I am not that technically savvy and I read through this thread and thought your suggestion to just reinstall the NET 1.1 seemed the least difficult. I followed your link, reinstalled, and now the update works!! Took all of 5 minutes. So am just writing to thank you for your post! Susan

reply to Steely
I posted a possible fix here: »social.answers.microsoft.com/For···required

Reproduced below:

I solved it by carefully reading the log file of the patch. It was looking for another .msp that was actually KB927366 which was gone from the Installer directory. I downloaded the KB927366 patch and applied it and then the KB953297 worked fine.

This is a general approach you can take for a fix:

If you run msiexec /p kb953297.msp /l*v c:\patch.log (obviously replace "kb953297.msp" with the proper path) and then check the .log file, you will most probably notice that it fails to find either a .msi or a .msp file. These have random names for each machine -- mine was 1d2cbae.msp -- so it's no use googling for them. Instead, search your registry for the name (in my case 1d2cbae.msp) and you will stumble upon a GUID (in my case A9E0D1D8997C82D4E99200161D6EE634). Go into the registry to "HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Patches" (if it was a .msp file) or to "HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products" (if it was a .msi) and search for that GUID you found earlier. Once found, expand the key and you will most probably find a value within the subkeys that contains the proper KBxxxxxx name for that .msp/.msi file (in my case, it was under "Source List\Media" and hinted to KB927366). Go to Microsoft Download Center and download the KB in question and install it (in my case, KB927366). If you're lucky, everything will work and then you'll be able to install the pesky KB953297.

The above is a fix for an incredible number of .msi or .msp failures. You'd be surprised.

Cheers