I seem to have solved the problem on my computer. I am installing Windows 7 Home Premium, but reading through this thread, the symptoms look similar enough. Please let me know if this also works for you.
The basic premise seems to be that the IE9 installer that is online in Windows Update and even the IE9 consumer site is bad. So if we try to pull the installer from these online sources after April 10, we would always get a bad copy, whether it's from
Windows Update or from a manual installation. You would know you have a bad installation if the version number in the "About Internet Explorer" dialog does not match the version number stored in the iexplore.exe executable. A good installation would have the
version number displayed for both as 9.0.8112.16421. On my other computer with an old installation that updated without problems, this is indeed the version number being displayed.
Based on this observation and taking a cue from Spectrum7glr's post about installations prior to April 10 working perfectly, I tried to locate an installer that would have binaries before April 10. Luckily, I was able to find one from Microsoft's Download
Center. Here's a link to the version for Windows 7 and Windows Server 2008 R2, 64-bit:
http://www.microsoft.com/download/en/details.aspx?id=23332
Instructions:
- Uninstall IE9, if you already have it installed, and restart the computer.
- Download the installer.
- Disconnect from the internet. This is important because the installer attempts to download the latest, bad binaries from Windows Update.
- Let the install finish, and restart.
- Reconnect to the internet and check Windows Update. If all went well, you should be able to see the Cumulative Update for IE9, instead of IE9 itself.
Again, the key is to install without any internet connection, to prevent the installer from fetching the latest and bad binaries.
Let me know if this works for you. I need to step out now, but will return later to perform further confirmation.
Thanks and regards! Good luck to us.
The above steps solved this problem according to another similar thread. It turns out to be caused by the bad IE9 installer. Using an earlier known good installer worked.
Thanks
Zhang
-
Edited by
Boo_MonstersIncMicrosoft contingent staff, Moderator
Friday, April 13, 2012 4:48 AM
-
Proposed as answer by
Meinolf WeberMVP
Friday, April 13, 2012 6:19 AM
-
Marked as answer by
Boo_MonstersIncMicrosoft contingent staff, Moderator
Thursday, April 19, 2012 4:15 AM