Internet Explorer 10 will not roll back to IE-9. Help!

UsernameIssues said:

Condorito said:

~~~
Note: This thread was originally posted in updates section of the forum, as it was my own creeping suspicion, but it was moved here.

How funny. I was thinking about hitting the report button and asking that it be moved to the updates section before I even posted. (clip)

I think somebody over there just read the title and already did that to send the thread here. :)

I seem to be getting an update on SUR (KB947821). Still waiting for it to finish. Thanks so far.

I don't know, this is turning into a saga, and I really can't stick around anymore today watching a little blue rectangle conveying across under the "Checking for updates" message. I will look into it again tomorrow. Thanks for the help so far.

So. Patience.

The CheckSUR tool can 'install' for anything up to 4 or more hours - just let it do its thing and it should eventually complete, and the logs will be available.

NoelDP said:

The CheckSUR tool can 'install' for anything up to 4 or more hours - just let it do its thing and it should eventually complete, and the logs will be available.

Took your sound advice. Here's the new log. Unfortunately, it does not seem to have been able to repair anything.

Condorito said:

So, Internet Explorer woes. Let me organize my thoughts so that my issue is as clear as possible to potential readers / kindly helpful members...

Rule 1 obeyed; try to do it yourself / Google is your friend, etcetera, etcetera.

THE ISSUE:

I have (had) IE-10 installed as an update on Windows 7 64 bit Home Premium. Note: the updates themselves have been an issue in the past, though mostly resolved by adherence to Rule 1. For a work application, I require IE-9 (imagine a company - a reputable French Aviation company by the way - basing its technical data reference on an obsolescent browser usable in only one OS?).

The short story;

The system will not roll-back to it upon uninstalling EI-10 and nor it will IE-9 install from a downloaded "IE9-Windows7-x64-enu" installer (from MS, of course). Attempts to install it give me this rather contradictory information in a message box;

Internet Explorer did not finish installing
Internet Explorer 9 is already installed on this system.

So, where is it, then? A search through the folders leads me to "iexplore.exe" in "Program Files (x86)/Internet Explorer", and in "Program Files/Internet Explorer" but these still launch IE-10.

Longer story (ie; more details);

How did I unistall IE-10 is an obvious question I would be asked. Here are the answers.

First, through "Installed Updates". I got this, after the obligatory "Updates are being uninstalled. This may take several minutes" message;

An error has occurred. Not all of the updates were successfully uninstalled.

So, then I attempted to forcibly remove it through the command line, as administrator, with this recommended method;

FORFILES /P %WINDIR%\servicing\Packages /M Microsoft-Windows-InternetExplorer-*10.*.mum /c "cmd /c echo Uninstalling package @fname && start /w pkgmgr /up:@fname /quiet /norestart"

Still no joy. Some echo lines run through the command line saying that the "package" (heheh! Very Linux) is being uninstalled. After this procedure, there was no more Internet Explorer option of any description at all in the Programs Startup list, but the "iexplore.exe" was still in the folders mentioned above. Opening it this way launched IE-10 again, despite it being "uninstalled". What's the joke?

Sooo. I went to "Programs->Turn Windows features on or off", unchecked Internet Explorer 10, and re-ran the command in administrator command line...

FORFILES /P %WINDIR%\servicing\Packages /M Microsoft-Windows-InternetExplorer-*10.*.mum /c "cmd /c echo Uninstalling package @fname && start /w pkgmgr /up:@fname /quiet /norestart"

The same business with "Package removal" echo lines, and upon completion I checked again for "iexplore.exe" and it had gone completely. Good, I thought, and attempted to install "IE9-Windows7-x64-enu". Same contradictory message about it not being installed and it being already installed. What the heck?

Now, I am beginning to think this needs a more brute force approach (and yes, I have rebooted on several occasions during this procedure), and as I have not been a Windows "power user" since Win 95 and before, when I was a dapper-hand at DOS, I am reticent about proceeding from here.

Obviously, IE-9 is NOT installed, but the system is convinced it IS installed. I am thinking Registry here. Should all traces of IE-10 and IE-9 be purged out, and all Internet Explorer folders be manually deleted, so that I can do a fresh install of IE-9?

Help me out here, please. As I said, it is for work, not play.

Sounds like there are some either some program files left behind by the previous installs of ie; and/or there are still registry entries pointing at ie.

The CheckSUR is at least more readable now :)
The remaining problems are mostly registry-based

Code:

Checking Package Watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~0.0.0.0 Package_54_for_KB2791765~31bf3856ad364e35~amd64~~6.1.1.2 Package registry presence failed, possibly an orphaned package on package watchlist
Checking Component Watchlist
(f) CBS Watchlist Component Missing 0x80070002 amd64_microsoft-windows-a..ence-mitigations-c1_31bf3856ad364e35_0.0.0.0_none_8c1ac95af2d41939 Package_54_for_KB2791765~31bf3856ad364e35~amd64~~6.1.1.2 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Component Missing 0x80070002 amd64_microsoft-windows-a..ence-mitigations-c1_31bf3856ad364e35_0.0.0.0_none_8c1ac95af2d41939 Package_54_for_KB2791765~31bf3856ad364e35~amd64~~6.1.1.2 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Component Missing 0x80070002 amd64_microsoft-windows-a..ence-mitigations-c3_31bf3856ad364e35_0.0.0.0_none_8c1cc9eef2d24be7 Package_54_for_KB2791765~31bf3856ad364e35~amd64~~6.1.1.2 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Component Missing 0x80070002 amd64_microsoft-windows-a..ence-mitigations-c3_31bf3856ad364e35_0.0.0.0_none_8c1cc9eef2d24be7 Package_54_for_KB2791765~31bf3856ad364e35~amd64~~6.1.1.2 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Component Missing 0x80070002 amd64_microsoft-windows-a..ence-mitigations-c4_31bf3856ad364e35_0.0.0.0_none_8c1dca38f2d1653e Package_54_for_KB2791765~31bf3856ad364e35~amd64~~6.1.1.2 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Component Missing 0x80070002 amd64_microsoft-windows-a..ence-mitigations-c4_31bf3856ad364e35_0.0.0.0_none_8c1dca38f2d1653e Package_54_for_KB2791765~31bf3856ad364e35~amd64~~6.1.1.2 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Component Missing 0x80070002 amd64_microsoft-windows-crypt32-dll_31bf3856ad364e35_0.0.0.0_none_db68530cde5b7446 Package_75_for_B2813430~31bf3856ad364e35~amd64~~6.1.1.4 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Component Missing 0x80070002 wow64_microsoft-windows-a..ence-mitigations-c1_31bf3856ad364e35_0.0.0.0_none_966f73ad2734db34 Package_54_for_KB2791765~31bf3856ad364e35~amd64~~6.1.1.2 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Component Missing 0x80070002 wow64_microsoft-windows-a..ence-mitigations-c1_31bf3856ad364e35_0.0.0.0_none_966f73ad2734db34 Package_54_for_KB2791765~31bf3856ad364e35~amd64~~6.1.1.2 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Component Missing 0x80070002 x86_microsoft-windows-a..ence-mitigations-c3_31bf3856ad364e35_0.0.0.0_none_2ffe2e6b3a74dab1 Package_54_for_KB2791765~31bf3856ad364e35~amd64~~6.1.1.2 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Component Missing 0x80070002 x86_microsoft-windows-a..ence-mitigations-c3_31bf3856ad364e35_0.0.0.0_none_2ffe2e6b3a74dab1 Package_54_for_KB2791765~31bf3856ad364e35~amd64~~6.1.1.2 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Component Missing 0x80070002 x86_microsoft-windows-a..ence-mitigations-c4_31bf3856ad364e35_0.0.0.0_none_2fff2eb53a73f408 Package_54_for_KB2791765~31bf3856ad364e35~amd64~~6.1.1.2 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Component Missing 0x80070002 x86_microsoft-windows-a..ence-mitigations-c4_31bf3856ad364e35_0.0.0.0_none_2fff2eb53a73f408 Package_54_for_KB2791765~31bf3856ad364e35~amd64~~6.1.1.2 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Component Missing 0x80070002 x86_microsoft-windows-crypt32-dll.resources_31bf3856ad364e35_0.0.0.0_ar-sa_5d612fbc3d6e26f5 Package75_for_KB2813430~31bf3856ad364e35~amd64~~6.1.1.4 Package registry presence failed, possibly an orphaned package on package watchlist
Checking Packages
Checking Component Store
(f) CSI Manifest and S256H Do Not Match 0x00000000 winsxs\Manifests\x86_microsoft-windows-thumbnailcache_31bf3856ad364e35_6.1.7600.16385_none_3ef0dc807a7abc55.manifest x86_microsoft-windows-thumbnailcache_31bf3856ad364e35_6.1.7600.16385_none_3ef0dc807a7abc55 
(w) CSI Located Replacement: Invalid (S256H) 0x00000000 Temp\CheckSUR\winsxs\Manifests\x86_microsoft-windows-thumbnailcache_31bf3856ad364e35_6.1.7600.16385_none_3ef0dc807a7abc55.manifest x86_microsoft-windows-thumbnailcache_31bf3856ad364e35_6.1.7600.16385_none_3ef0dc807a7abc55 
(w) CSI Located Replacement: Invalid (S256H) 0x00000000 Temp\CheckSUR\winsxs\Manifests\x86_microsoft-windows-thumbnailcache_31bf3856ad364e35_6.1.7600.16385_none_3ef0dc807a7abc55.manifest x86_microsoft-windows-thumbnailcache_31bf3856ad364e35_6.1.7600.16385_none_3ef0dc807a7abc55 
(w) CSI Located Replacement: Invalid (S256H) 0x00000000 Temp\CheckSUR\winsxs\Manifests\x86_microsoft-windows-thumbnailcache_31bf3856ad364e35_6.1.7600.16385_none_3ef0dc807a7abc55.manifest x86_microsoft-windows-thumbnailcache_31bf3856ad364e35_6.1.7600.16385_none_3ef0dc807a7abc55 
(w) CSI Located Replacement: Invalid (S256H) 0x00000000 Temp\CheckSUR\winsxs\Manifests\x86_microsoft-windows-thumbnailcache_31bf3856ad364e35_6.1.7600.16385_none_3ef0dc807a7abc55.manifest x86_microsoft-windows-thumbnailcache_31bf3856ad364e35_6.1.7600.16385_none_3ef0dc807a7abc55 
(w) CSI Located Replacement: Invalid (S256H) 0x00000000 Temp\CheckSUR\winsxs\Manifests\x86_microsoft-windows-thumbnailcache_31bf3856ad364e35_6.1.7600.16385_none_3ef0dc807a7abc55.manifest x86_microsoft-windows-thumbnailcache_31bf3856ad364e35_6.1.7600.16385_none_3ef0dc807a7abc55 
(w) CSI Located Replacement: Invalid (S256H) 0x00000000 Temp\CheckSUR\winsxs\Manifests\x86_microsoft-windows-thumbnailcache_31bf3856ad364e35_6.1.7600.16385_none_3ef0dc807a7abc55.manifest x86_microsoft-windows-thumbnailcache_31bf3856ad364e35_6.1.7600.16385_none_3ef0dc807a7abc55 
(w) CSI Located Replacement: Invalid (S256H) 0x00000000 Temp\CheckSUR\winsxs\Manifests\x86_microsoft-windows-thumbnailcache_31bf3856ad364e35_6.1.7600.16385_none_3ef0dc807a7abc55.manifest x86_microsoft-windows-thumbnailcache_31bf3856ad364e35_6.1.7600.16385_none_3ef0dc807a7abc55 
(w) CSI Located Replacement: Invalid (S256H) 0x00000000 Temp\CheckSUR\winsxs\Manifests\x86_microsoft-windows-thumbnailcache_31bf3856ad364e35_6.1.7600.16385_none_3ef0dc807a7abc55.manifest x86_microsoft-windows-thumbnailcache_31bf3856ad364e35_6.1.7600.16385_none_3ef0dc807a7abc55 
(w) CSI Located Replacement: Invalid (S256H) 0x00000000 Temp\CheckSUR\winsxs\Manifests\x86_microsoft-windows-thumbnailcache_31bf3856ad364e35_6.1.7600.16385_none_3ef0dc807a7abc55.manifest x86_microsoft-windows-thumbnailcache_31bf3856ad364e35_6.1.7600.16385_none_3ef0dc807a7abc55 
(w) CSI Located Replacement: Invalid (S256H) 0x00000000 Temp\CheckSUR\winsxs\Manifests\x86_microsoft-windows-thumbnailcache_31bf3856ad364e35_6.1.7600.16385_none_3ef0dc807a7abc55.manifest x86_microsoft-windows-thumbnailcache_31bf3856ad364e35_6.1.7600.16385_none_3ef0dc807a7abc55 
(w) CSI Located Replacement: Invalid (S256H) 0x00000000 Temp\CheckSUR\winsxs\Manifests\x86_microsoft-windows-thumbnailcache_31bf3856ad364e35_6.1.7600.16385_none_3ef0dc807a7abc55.manifest x86_microsoft-windows-thumbnailcache_31bf3856ad364e35_6.1.7600.16385_none_3ef0dc807a7abc55 
(w) CSI Located Replacement: Invalid (S256H) 0x00000000 Temp\CheckSUR\winsxs\Manifests\x86_microsoft-windows-thumbnailcache_31bf3856ad364e35_6.1.7600.16385_none_3ef0dc807a7abc55.manifest x86_microsoft-windows-thumbnailcache_31bf3856ad364e35_6.1.7600.16385_none_3ef0dc807a7abc55 
(f) CSI Mismatched Identity 0x00000000 appid f9c4e7508a4..1926bed4094_31bf3856ad364e35_6.1.7600.16724_abd1091d17f710b1 appid and keyform do not match; appid is wrong.
(f) CSI Corrupt Deployment Keyform 0x00000000 appid fbef931f7d6..54409e8ca34_31bf3856ad364e35_6.1.7600.16724_e0ec013ff9bf06!c appid and keyform do not match; keyform is wrong.
(f) CSI Missing Deployment Key 0x00000000 fbef931f7d6..54409e8ca34_31bf3856ad364e35_6.1.7600.16724_e0ec013ff9bf06ac HKLM\Components\CanonicalData\Deployments 
(f) CSI Corrupt Component Keyform 0x00000000 identity amd64_7d10b606604754856&bb2d4120348a01_31bf3856ad364e35_6.1.7601.17610_none_d7a70692e0fa6bde identity and keyform do not match; keyform is wrong.
(f) CSI Corrupt Component Keyform 0x00000000 identity amd64_68286775a"b9d2f5ad6b41dbb01d07af_31bf3856ad364e35_6.1.7601.22010_none_e3b73d25cfd2d0ec identity and keyform do not match; keyform is wrong.
(f) CSI Missing Deployment Key 0x00000000 microsoft-w..-deployment_31bf3856ad364e35_6.1.7600.16385_86f5b67405fdc54f HKLM\Components\CanonicalData\Deployments 
(f) CSI C Mark Deployment Missing 0x00000000 c!windowsfoundation_31bf3856ad364e35_6.1.7600.16385_5f2ecc1aaa4!c3b2 x86_microsoft-windows-m..mdac-odbc-jet-exl32_31bf3856ad364e35_6.1.7600.16385_none_96080debd81157d3 
(f) CSI C Mark Deployment Missing 0x00000000 c!windowsfounda4ion_31bf3856ad364e35_6.1.7600.16385_5f2ecc1aaa4ac3b2 amd64_microsoft-windows-i..tional-codepage-500_31bf3856ad364e35_6.1.7600.16385_none_2af89cb8b4ced494

These can be pretty daunting things to fix, and I need to work out the best order in which to do it, as the wrong order will mean unnecessary work on your part.

While I work that out, let's see if we can clear some of the easier registry errors...

I need to have a look at your COMPONENTS registry hive

Please copy the C:\Windows\System32\config\COMPONENTS file (no extension) to your desktop and then compress it - upload the compressed file to your favoured fileshare site (preferably Dropbox or SkyDrive) and post a link.

matts6887 said:

Sounds like there are some either some program files left behind by the previous installs of ie; and/or there are still registry entries pointing at ie.

Something along those lines, I thought myself also, though I remained skeptical as to the integrity of the updates mechanism from the beginning, despite the SFC scan promise there were no "violations". Seem to be on the right track here, though, with many thanks to NoelDP.

NoelDP said:

These can be pretty daunting things to fix, and I need to work out the best order in which to do it, as the wrong order will mean unnecessary work on your part.

While I work that out, let's see if we can clear some of the easier registry errors...

I need to have a look at your COMPONENTS registry hive

Please copy the C:\Windows\System32\config\COMPONENTS file (no extension) to your desktop and then compress it - upload the compressed file to your favoured fileshare site (preferably Dropbox or SkyDrive) and post a link.

Okay, first thing's first. Some information regarding this components file, in case it is important. I was unable to copy/compress it from the specified folder while Windows was itself the running OS, as I was informed upon attempting that it was "open" and "in use". Therefore, I have retrieved the file through my other Linux OS on the same computer. There are several components logs in that directory, but here is the one without an extension, as requested.

Enough said. Here's the file.

The problems with accessing the file are probably due to Windows having loaded it for some reason - it's usually only loaded when Windows is updating, or changing options.
It may be that the corruption is such that it's never being fully loaded to complete whatever's needed. Usually, booting in Safe Mode will allow access.

Back after I've had a chance to look at it :)

Here's the file back again - mostly fixed :) -


I've uploaded a file - ctoaa.zip - to my SkyDrive at Noel's SkyDrive
Please download and save it to your desktop.
Right-click on the file and select Extract All, and save to the default destination (which should be a folder on the desktop)

Create a new System Restore point

Open an Elevated Command Prompt, and run the following commands.

REN C:\Windows\System32\config\COMPONENTS COMPONENTS.OLD1
COPY %userprofile%\desktop\ctoaa\COMPONENTS C:\Windows\System32\config

If you get an error with either command, STOP THERE - do not reboot! - post for instructions.

Assuming both commands go OK, reboot, and run another CheckSUR scan - post the new CheckSUR.log file.

(You may want to do it in Safe Mode, or use Linux for the rename/swap)

....it may take a while for the file to appear, with my abysmally low upload speed! try again every ten minutes or so.

"Oscar-Mike". Thanks, will be right back.