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

[Condorito]

Okay. Some issues;

No apparent problems with the new COMPONENTS file. But there seems to be something amiss with running SUR now. The unit has spent all morning doing a "Check for Updates". As there is little way I can see to confirm that it is doing a SUR check, I had to assume that it was doing one. After it finished this check for updates, I looked for a new CheckSUR file, but it is still the same one as before.

Further, I downloaded and saved the "Windows6.1-KB947821-v31-x64" file directly and attempted to launch it. It gives me an error...

Installer encountered an error: 0x8007000d
The data is invalid.

So, I tried another "Check for updates" (as there are no new ones listed and it was this same action that triggered the SUR check results yesterday), but it is doing the same long-winded procedure of endlessly checking for updates again, which I am definitely not going to let it do a second time today.

Something's wrong.

 

[NoelDP]

That installer 00d error may simply be because of a bad download.

I'd try a second download from here Download System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [November 2013] from Official Microsoft Download Center (just in case you got it from somewhere else)

 

[Condorito]

Yes, that is the one I got (Nov 2013), from that same page. However, benefit of the doubt; it could have been corrupted. Trying again, thanks.

 

[Condorito]

Right; it worked properly this time, the way it should from the tool launcher and not through the Windows Update as it did the last time. I suspect, in fact, it was a sheer coincidence that it arrived as a "standard update" the very moment I needed it. Anyway, looking better, would you say?

I do have one question, though: After each of these checks Windows invariably seems to have a couple of "important updates" waiting to install upon shutdown. Should I inhibit the installation of these for the moment, until this issue is solved?

 

[NoelDP]

A lot better
We've got the easy stuff done now.
I was hoping (in vain) that it would also reduce the other errors a little - but it's not done so, which means that you have some work to do.
I'll post instructions later for the first set of fixes. In the meantime, please create a new System Restore point, and let me know what experience you have of working in the registry using Regedit.

 

[Condorito]

In the meantime, please create a new System Restore point, and let me know what experience you have of working in the registry using Regedit.

Done, and yes I can certainly use Regedit, provided I have a reference of what to go after. I expected it might end up in there right from the beginning. I will be "AFK" most of today, but will look in again this evening, my time. Thanks so far!

 

[NoelDP]

Oh goody! That'll save me reams of paper

back later.

 

[NoelDP]

Here's the first/odd one....

Open Regedit
Navigate to the following Key

[B]HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect\Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~0.0.0.0[/B]

Export the Key for safe-keeping, just in case

Find the entry in the key for

Package_54_for_KB2791765~31bf3856ad364e35~amd64~~6.1.1.2

Delete it
Close Regedit
reboot, and run another CheckSUR scan - post the log and we'll see how that went.
Create another System Restore Point.
The Missing Component errors are a little more complex, so I want to make sure of this one first.

 

[Condorito]

Okay, a problem straight off the bat. The referred to;

Package_54_for_KB2791765~31bf3856ad364e35~amd64~~6.1.1.2

...will not delete. I have run Regedit as and not as administrator, in and not in Safe Mode. No joy, I get this message;

Unable to delete all the specified values.

Far as I can see, this is an unsigned long integer variable (DWORD), though I might be premature in assuming some similarity to C / WinAPI (?). As far as Regedit is concerned, I seem to be unable to elevate the permissions (on that item), either. Is there another route to deleting it forcibly, or what do you recommend?

Also, for your information and my organization, any Registry exporting you direct me to perform I am storing identified by the number of the respective post you mention the procedure in. If at any stage you require me re-import something, please just mention the post in which the action was done, and I will be able to locate it with ease.

Thanks!

 

[NoelDP]

That probably means that the entry is corrupted - I'll have to work out a way to remove the corruption externally using a Hex editor.
The trick is going to be how to get the corrected hive back in.

Let's see if another route works - it may work better than the GUI interface...
(close Regedit if it's open)
Open an Elevated Command Prompt, and run the following command

REG DELETE "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect\Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~0.0.0.0" /v Package_54_for_KB2791765~31bf3856ad364e35~amd64~~6.1.1.2 
 
.

What response do you get?

 

[UsernameIssues]

That probably means that the entry is corrupted - I'll have to work out a way to remove the corruption externally using a Hex editor.
The trick is going to be how to get the corrected hive back in.

Let's see if another route works - it may work better than the GUI interface...
(close Regedit if it's open)
Open an Elevated Command Prompt, and run the following command

REG DELETE "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect\Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~0.0.0.0" /v Package_54_for_KB2791765~31bf3856ad364e35~amd64~~6.1.1.2 
 
.

What response do you get?

I don't think that a user can work in that area without taking ownership and assigning the correct permissions (full?). Once those two things are changed, the info can be removed. I would set the ownership back to SYSTEM and leave only the TrustedInstaller with full control after removing the info of interest.

I picked a registry value that I had for the screenshot below.
I used a virtual machine, so no risk involved.
I was able to change/remove the info once I owned the area and had full permissions.

 

[NoelDP]

I'm going to ask someone more expert than I to assist - it may take a couple of days for him to get back either to me or to the thread, as he may be off skiing somewhere....

Patience is a virtue

 

[Condorito]

I picked a registry value that I had for the screenshot below.
I used a virtual machine, so no risk involved.
I was able to change/remove the info once I owned the area and had full permissions.

Yes, that's what was missing; changing the user to myself/administrator. I was able to change the permissions after that. Thank you! The entry has now been deleted without any further issue.

Been "AFK" again today, but can run that CheckSUR now, at least.

 

[NoelDP]

Great - let's see what the CheckSUR says now before we go any further.

 

[Condorito]

Well, that was a lot faster; the entire CheckSUR from launch to culmination in less than 20 minutes. It was taking about five hours before.

New CheckSUR attached.

 

[NoelDP]

Can't guarantee it'll keep on improving

Good - that's cured one of the errors. I was hoping it may cascade down and fix some of the others as well, but we don't get that lucky

So now the hard work begins...

Please run the following commands, and note that a folder (npreg) is created on your desktop - this is a backup in case things go wrong, as well as being data for me to work with


MD %userprofile%\desktop\npreg
REG EXPORT "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-a..ence-mitigations-c1_31bf3856ad364e35_0.0.0.0_none_8c1ac95af2d41939" %userprofile%\desktop\npreg\nprega1.txt
REG EXPORT "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-a..ence-mitigations-c3_31bf3856ad364e35_0.0.0.0_none_8c1cc9eef2d24be7" %userprofile%\desktop\npreg\nprega3.txt
REG EXPORT "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-a..ence-mitigations-c4_31bf3856ad364e35_0.0.0.0_none_8c1dca38f2d1653e" %userprofile%\desktop\npreg\nprega4.txt
REG EXPORT "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-crypt32-dll_31bf3856ad364e35_0.0.0.0_none_db68530cde5b7446" %userprofile%\desktop\npreg\nprega5.txt
REG EXPORT "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\wow64_microsoft-windows-a..ence-mitigations-c1_31bf3856ad364e35_0.0.0.0_none_966f73ad2734db34" %userprofile%\desktop\npreg\npregx1.txt
REG EXPORT "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\x86_microsoft-windows-a..ence-mitigations-c3_31bf3856ad364e35_0.0.0.0_none_2ffe2e6b3a74dab" %userprofile%\desktop\npreg\npregx3.txt
REG EXPORT "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\x86_microsoft-windows-a..ence-mitigations-c4_31bf3856ad364e35_0.0.0.0_none_2fff2eb53a73f408" %userprofile%\desktop\npreg\npregx4.txt
REG EXPORT "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\x86_microsoft-windows-crypt32-dll.resources_31bf3856ad364e35_0.0.0.0_ar-sa_5d612fbc3d6e26f5" %userprofile%\desktop\npreg\npregx5.txt


Please zip the npreg folder up and post it in your reply.

 

[Condorito]

Done. Please note the following for your information, however; in attempting to export and create npregx3.txt , I get the following CL message;

The system was unable to find the specified registry key or value.

I took the liberty of checking this out. It turns out there is no

x86_microsoft-windows-a..ence-mitigations-c3_31bf3856ad364e35_0.0.0.0_none_2ffe2e6b3a74dab

but there was a

x86_microsoft-windows-a..ence-mitigations-c3_31bf3856ad364e35_0.0.0.0_none_2ffe2e6b3a74dab1

...at the specified location in the registry, which is the one I exported to the uploaded, zipped file. Hope it is the one you were thinking of (ie; looking for). I am letting you know here of the subtle difference, just the same, as it could be important. Ok?

 

[NoelDP]

That's an error in my copy/pasting - sorry about that!
It's midnight here at the moment, and too late for me to start with the instructions.
I'll get to it tomorrow, when I can find the time between computers - I'll do them in pairs since that's how they are in the report.

 

[Condorito]

So it was the right one? That was lucky, as I had my doubts about it possibly being a version 1 of something that was there before... which maybe should have been there but was updated and the other deleted and... well, you know what I mean. You never can tell, as a single difference like that can be a whole different kettle of fish (had the experiences, from days of olde to present!).

Many thanks!

 

[NoelDP]

So long as you follow the directions exactly, then we shouldn't go wrong.

(I've partaken of too many 'cups' today - back tomorrow, early!)