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

[NoelDP]

That's a major advance for mankind, at least!
I'm getting a 404 error on your link?

 

[Condorito]

That's a major advance for mankind, at least!
I'm getting a 404 error on your link?

Indeed, so am I now, even though I tested it successfully when I first put it up. Perhaps it was assigned a temporary ID, or something, as the link I get for it from Dropbox now looks much more like it (before it gave me some odd numbers for the filename). Anyway, enough of that, here's the file.

Apologies for the inconvenience!

 

[NoelDP]

These things happen!
Interesting report!

 Line 231913: 2014-01-06 09:45:09, Info                  CSI    00000481 [SR] Repairing 7 components
 Line 231914: 2014-01-06 09:45:09, Info                  CSI    00000482 [SR] Beginning Verify and Repair transaction
 Line 231919: 2014-01-06 09:45:09, Info                  CSI    00000485 [SR] Cannot verify component files for Microsoft-Windows-Font-TrueType-Aparajita, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
 Line 231924: 2014-01-06 09:45:09, Info                  CSI    00000488 [SR] Cannot verify component files for Microsoft-Windows-Help-Firewall, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
 Line 231929: 2014-01-06 09:45:09, Info                  CSI    0000048b [SR] Cannot verify component files for Microsoft-Windows-LSA-MSPrivs.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"el-GR", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
 Line 231934: 2014-01-06 09:45:09, Info                  CSI    0000048e [SR] Cannot verify component files for Microsoft-Windows-Microsoft-Data-Access-Components-(MDAC)-Oledb-Rll, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
 Line 231939: 2014-01-06 09:45:09, Info                  CSI    00000491 [SR] Cannot verify component files for Microsoft-Windows-International-Keyboard-0001045d, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
 Line 231944: 2014-01-06 09:45:09, Info                  CSI    00000494 [SR] Recovered manifest from backup for Microsoft-Windows-Font-TrueType-Aparajita, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
 Line 231945: 2014-01-06 09:45:09, Info                  CSI    00000495 [SR] Repairing corrupted file [ml:48{24},l:46{23}]"\??\C:\Windows\SysWOW64"\[l:16{8}]"mfds.dll" from store
 Line 231946: 2014-01-06 09:45:09, Info                  CSI    00000496 [SR] Repairing corrupted file [ml:520{260},l:88{44}]"\??\C:\Program Files (x86)\Internet Explorer"\[l:34{17}]"ie9props.propdesc" from store
 Line 231961: 2014-01-06 09:45:09, Info                  CSI    00000498 [SR] Repair complete

PLease run a new SFC /SCANNOW, and we'll see if that comes up clear.

 

[Condorito]

Much smaller CBS log file now, I can attach it here.

If that font is a problem, maybe I should uninstall it? It looks like Sanskrit or something like that, and I highly doubt I will ever use it! I see IE9 is mentioned in there, too.

During the first attempt at the scan, the system BSOD'd suddenly, but as that is something that happens from time to time with my Windows 7, I greatly doubt it had anything to do with SFC. The second scan ran alright, and it still has the message about some corrupt elements.

 

[NoelDP]

Here's the new log summary - which is a little confusing, but at least suggests that we're getting somewhere!

 Line 9111: 2014-01-06 22:13:32, Info                  CSI    00000680 [SR] Repairing 5 components
 Line 9112: 2014-01-06 22:13:32, Info                  CSI    00000681 [SR] Beginning Verify and Repair transaction
 Line 9117: 2014-01-06 22:13:32, Info                  CSI    00000684 [SR] Cannot verify component files for Microsoft-Windows-Font-TrueType-Aparajita, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
 Line 9122: 2014-01-06 22:13:32, Info                  CSI    00000687 [SR] Cannot verify component files for Microsoft-Windows-Help-Firewall, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
 Line 9127: 2014-01-06 22:13:32, Info                  CSI    0000068a [SR] Cannot verify component files for Microsoft-Windows-LSA-MSPrivs.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"el-GR", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
 Line 9132: 2014-01-06 22:13:32, Info                  CSI    0000068d [SR] Cannot verify component files for Microsoft-Windows-Microsoft-Data-Access-Components-(MDAC)-Oledb-Rll, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
 Line 9137: 2014-01-06 22:13:32, Info                  CSI    00000690 [SR] Cannot verify component files for Microsoft-Windows-International-Keyboard-0001045d, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
 Line 9142: 2014-01-06 22:13:32, Info                  CSI    00000693 [SR] Recovered manifest from backup for Microsoft-Windows-Font-TrueType-Aparajita, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

There appear to be some damaged Manifest files - which are best repaired using CheckSUR, so please run that tool again, and post the new CheckSUR log and we'll see if there's anything else uncovered.

 

[Condorito]

Certainly looks a lot better than it was! Attached is the CheckSUR log. I also ran another SFC /scannow, and the new CBS log is attached, too.

 

[NoelDP]

Ah - I see what the problem is - it's in the registry
The hash values have been corrupted.

I need to have another look at your Components hive.

(just in case you've forgotten...)

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.

 

[Condorito]

Something different. I can now actually copy and compress this file while in windows. No need to revert to Linux and access the Windows drive to retrieve it, as before.

Here is the file.

 

[NoelDP]

Well - I found that error, at least

Here's the file back again - cdoac.zip

Same procedure to replace your file, then run another SFC scan and we'll see where we are.

 

[Condorito]

New CBS log attached...

 

[NoelDP]

Hmmmm

 Line 29727: 2014-01-08 17:43:19, Info                  CSI    00000323 [SR] Repairing 4 components
 Line 29728: 2014-01-08 17:43:19, Info                  CSI    00000324 [SR] Beginning Verify and Repair transaction
 Line 29733: 2014-01-08 17:43:19, Info                  CSI    00000327 [SR] Cannot verify component files for Microsoft-Windows-Help-Firewall, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
 Line 29738: 2014-01-08 17:43:19, Info                  CSI    0000032a [SR] Cannot verify component files for Microsoft-Windows-LSA-MSPrivs.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"el-GR", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
 Line 29743: 2014-01-08 17:43:19, Info                  CSI    0000032d [SR] Cannot verify component files for Microsoft-Windows-Microsoft-Data-Access-Components-(MDAC)-Oledb-Rll, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
 Line 29748: 2014-01-08 17:43:19, Info                  CSI    00000330 [SR] Cannot verify component files for Microsoft-Windows-International-Keyboard-0001045d, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
 Line 29753: 2014-01-08 17:43:19, Info                  CSI    00000332 [SR] Repair complete

Still the same errors

Aaaargh - there were two errors in the same data...
I'll post a revised file a bit later

 

[NoelDP]

OK - new version is up cdoad.zip

 

[Condorito]

Heh! You're The Man. Windows Resource Protection did not find any integrity violations. How does it look now?

 

[NoelDP]

YAY! - SFC is all clear!
The last error in the background CBS.log is

 Line 42093: 2014-01-09 22:59:53, Error                 CBS    Failed to initialize store parameters with boot drive: T: and windows directory: [URL="file://\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy14\Windows\"]\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy14\Windows\[/URL] [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

.. so hopefully that's all behind us now

Now here we have the bad news...

It's likely that the problems we've experienced have been caused by hardware faults - bitflips such as we had with the last few posts are often the result of RAM faults.

I would suggest checking the RAM with MemTest86++ ( www.memtest.org ) - run it for at least 6 passes unless you get errors beforehand..


Assuming that's OK, try Windows UPdate, and see what you can do with (un)installing versions of IE.

 

[Condorito]

It's likely that the problems we've experienced have been caused by hardware faults - bitflips such as we had with the last few posts are often the result of RAM faults.

I would suggest checking the RAM with MemTest86++ ( www.memtest.org ) - run it for at least 6 passes unless you get errors beforehand..

Now, if I am not mistaken, that is the sort of thing that would be causing those BSOD's, too. I always suspected those then whiz-bang Corsair dual channel DDR3's modules were not entirely to Windows 7's liking on my rig. I hardly ran them ganged for two months before some software requirements forced me to un-gang them to mazimize RAM. I now need even more, so I will probably be changing them this week, with something more humble and ordinary. I'll run the test on them, just the same, and report back.

Thanks so far, mate (from a fellow part-Scot - I am looking at your flag - living in the land of the Three-toed Sloth!), I owe you a virtual jar or two at your local. Hopefully they'll accept a PayPal deposit (when I get that issue sorted out soon) for drinks on me.

 

[Condorito]

OK; memtest86+ is installed as standard with many Linux distros. I just had to make the respective grub booter file executable and update grub to have it available (I had suppressed it previously). No errors to report, RAM-wise.

Updates working better than they ever have before, that's a cert. (Time for a system backup?)

No joy with IE-9 or IE-10, as yet. Says they are installed. There is no executable in the IE directory, however. As mentioned before; the update status on it registers it as still installed. Better said, IE-10 still exists on the installed update list, but will not "uninstall".

 

[Condorito]

Nope. I re-enabled EI-10 as a "turned on" Windows feature (I had disabled it). Rebooted. Checked that IE-10 was working to satisfaction. Then tried uninstalling to see if it would roll back to IE-9. Error; not all of the updates were uninstalled. Popped over to Linux, set up IE-9 on WINE in XP compatibility. It appears to work there, so I am going to try that solution to see if I can install the tech-data program via that method.

After all that effort, I would hate to say yet again; Linux +1 (more). My thanks for all the help, anyway. It was much appreciated.

Edit:

Even that does not work too well. I am not going to have to dig out XP, am I? Now does the 32 bit XP work on a 64 bit machine. I wonder. This is a tragedy.

However, bright side of things; updates all install apparently without the odd failure now, as was the case before, so that seems to be solved.

 

[NoelDP]

With IE10 turned on, please run SFC and CheckSUR again - post the logs (I have no idea whether this could/should change the output, but...)

 

[Condorito]

With IE10 turned on, please run SFC and CheckSUR again - post the logs (I have no idea whether this could/should change the output, but...)

...can't hurt to see, at this stage. Please find them attached.

 

[Condorito]

As an afterthought. Some time back, when this issue began, I ran some IE diagnostic tool, and it threw out some compressed file onto my desktop called IEDiag. It contains some text files with some info on the attempted intallation of IE-9. Is any of this any use? Would a new one help, perhaps?