Unable to Install Windows 7 SP1 or IE9 using Windows Update

[jmak18]

Hi there, as you can tell by the title, I've been having this problem for quite a while (several years now) now but haven't had the time or knew where to go to get help until now. I've tried installing both updates together and individually, but whichever way I do it the updates fail to install. I've also tried installing IE9 in the past from the Microsoft website, but that also failed to install.

Other than these two particular updates, I've never had another failed update that wasn't able to resolve itself after a computer restart for example.

I followed all the steps as per the Windows Update Posting Instructions including installing SURT from the provided link, running the SFC scan (3 times in total after being notified in the first scan that there were corrupted files that weren't fixed), and jotting down the error codes produced after the failed installations. I have attached the CBS log to this post.

The error code produced after attempting to install Windows 7 SP1 was Code 2.
The error code produced after attempting to install IE9 was Code 490.

Both errors are followed by the statement: "Windows Update encountered an unknown error"

If there's anything else you need please post and I'll post it up her ASAP. Thank for your help

EDIT: I also forgot to mention that the system I have is an Acer laptop with Windows 7 Home Premium, 3 GB of memory with NIS 2014.

 

[NoelDP]

You have a large number of corrupt servicing Package files (here's half the list)

Unavailable repair files:
 servicing\packages\Microsoft-Media-Foundation-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-Anytime-Upgrade-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-Anytime-Upgrade-Results-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-Backup-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-BLB-Client-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-Branding-HomePremium-Client-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-Branding-Professional-Client-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-Branding-Ultimate-Client-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-BusinessScanning-Feature-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-Client-Drivers-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-Client-Wired-Network-Drivers-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-ClipsInTheLibrary-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-CodecPack-Basic-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-Common-Drivers-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-Common-Modem-Drivers-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-Disk-Diagnosis-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-Gadget-Platform-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-GPUPipeline-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-GroupPolicy-ClientExtensions-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-GroupPolicy-ClientTools-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-Help-CoreClientUAHP-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-Help-CoreClientUAPS-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-Help-CoreClientUAUE-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-Help-Customization-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-ICM-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-IE-Troubleshooters-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-IIS-WebServer-AddOn-2-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-IIS-WebServer-AddOn-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-IIS-WebServer-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-Indexing-Service-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-InternetExplorer-Optional-Package~31bf3856ad364e35~amd64~fr-FR~8.0.7600.16385.mum
 servicing\packages\Microsoft-Windows-InternetExplorer-Package~31bf3856ad364e35~amd64~fr-FR~8.0.7600.16385.mum
 servicing\packages\Microsoft-Windows-Links-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-Media-Format-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-MediaCenter-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-MediaPlayback-OC-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-MediaPlayer-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-MobilePC-Client-Basic-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-MobilePC-Client-Premium-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-MobilePC-Client-Sensors-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-MobilePC-Client-SideShow-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-MSMQ-Client-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-NetFx3-OC-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-NFS-ClientSKU-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-OfflineFiles-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-OpticalMediaDisc-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-ParentalControls-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-PeerDist-Client-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-PeerToPeer-Full-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-PhotoBasicPackage~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-PhotoPremiumPackage~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-Printer-Drivers-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-Printing-Foundation-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-Printing-PremiumTools-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-Printing-XPSServices-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-RasRip-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-RDC-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-RecDisc-SDP-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-RemoteAssistance-Package-Client~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-SearchEngine-Client-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-SecureStartup-Basic-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-SecureStartup-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-ShareMedia-ControlPanel-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-Shell-HomeGroup-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-Shell-InboxGames-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-Shell-MultiplayerInboxGames-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-Shell-PremiumInboxGames-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-SimpleTCP-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-SnippingTool-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-SNMP-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-StickyNotes-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-StorageService-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-SUA-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-SystemRestore-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-TabletPC-OC-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-Telnet-Client-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-Telnet-Server-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-TerminalServices-CommandLineTools-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-TerminalServices-MiscRedirection-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-TerminalServices-Publishing-WMIProvider-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-TerminalServices-RemoteApplications-Client-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-TerminalServices-UsbRedirector-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-TerminalServices-WMIProvider-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-TFTP-Client-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-VirtualPC-USB-RPM-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-WindowsFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-WindowsMediaPlayer-Troubleshooters-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-WinOcr-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-WMI-SNMP-Provider-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-WMPNetworkSharingService-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-Xps-Foundation-Client-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Package_11_for_KB979916~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_11_for_KB983590~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_14_for_KB2416471~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_38_for_KB2443685~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_75_for_KB2443685~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Server-Help-Package.ClientHomePremium~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Server-Help-Package.ClientProfessional~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Server-Help-Package.ClientUltimate~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum

You also have a fairly critical file missing, according to SFC -

 Line 13663: 2014-05-28 20:56:56, Info                  CSI    00000303 [SR] Repairing 1 components
 Line 13664: 2014-05-28 20:56:56, Info                  CSI    00000304 [SR] Beginning Verify and Repair transaction
 Line 13667: 2014-05-28 20:56:56, Info                  CSI    00000306 [SR] Cannot repair member file [l:22{11}]"autochk.exe" of Microsoft-Windows-Autochk, 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 in the store, hash mismatch

I'll post the SFC correction first - and the CheckSUR later.

 

[NoelDP]

I've uploaded a file - jmkaa.zip - to my OneDrive at Noel's OneDrive
Please download and save it.

Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract
Close all windows (it would be a good idea to print these instructions!)

Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.

Pick the option to use a Command Prompt
At the prompt type
DIR C:\jmkaa
hit the enter key - if you get a 'Not Found' error try
DIR D:\jmkaa
or
DIR E:\jmkaa

The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...

XCOPY <drive>:\jmkaa <drive>:\windows\winsxs /y /i /s /v /h

(e.g. XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )

run the command (it should take almost no time) and when the prompt returns, type
EXIT
and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.

Now run SFC /SCANNOW in an Elevated Command Prompt
then reboot and upload the new CBS.log file to your reply

 

[jmak18]

Hey thanks for the reply NoelDP,

I followed your instructions and I got the "Not Found" error with the C: drive, as you said, so I used D: and it worked. I ran the SFC scan again and it reported that "Windows Resource Protection did not find any integrity violations". I am attaching the new CBS log, but does this mean that there are no more problems and that I should be able to download the updates now? Forgive me if I am getting ahead of myself

 

[NoelDP]

The SFC fix seems to have worked - but we have a lot more work to do before we should try to install any more updates.
I'll post the fix protocol for the CheckSUR errors a bit later.
(Gotta eat sometime!)

 

[jmak18]

lol I understand, I've yet to eat lunch myself.

 

[NoelDP]

Hmm - I failed to take account of the fact that you are using a French version of Windows. - this should fix almost all of the remaining problems, but it may miss a few....



I've uploaded a file - jmkab.zip - to my OneDrive at Noel's OneDrive
Please download and save it.
Right-click on the downloaded file, and select Extract all…
Extract to the default location - which will create a new folder jmkab in the same place.
Open this folder - there should be one folder inside it (Packages)

Copy the content of the Packages folder to the folder
C:\Windows\Temp\CheckSur\Servicing\Packages


Now run the CheckSUR tool again (it may take a while)

Post the new CheckSUR.log file, and the CheckSUR.persist.log file.

 

[jmak18]

Sorry, but what do you mean by the "French" version of Windows? Pretty much everything on my computer is written in English?

 

[NoelDP]

Almost all the files involved here are tagged with the 'fr-FR' marker, meaning that they are for the French/France regionalised version of Windows - they don't exist in a purely English system. Their presence may be the result of having had a localisation option at installation (I gather most Canadian/Quebec-market machines have such an option), or for other reasons.

 

[jmak18]

Hey sorry for the wait Noel,

I copied all the files from the "Packages" folder and ran the CheckSUR. I'm attaching the whole CBS.zip folder, hopefully you'll find everything you need in there. Let me know if there's anything else I should do. Thanks.

 

[NoelDP]

The CheckSUR log shows the following remaining problems...

Unavailable repair files:
 servicing\packages\Microsoft-Windows-GroupPolicy-ClientTools-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-Indexing-Service-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-InternetExplorer-Optional-Package~31bf3856ad364e35~amd64~fr-FR~8.0.7600.16385.mum
 servicing\packages\Microsoft-Windows-OpticalMediaDisc-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.mum
 servicing\packages\Microsoft-Windows-Indexing-Service-Package~31bf3856ad364e35~amd64~fr-FR~6.1.7600.16385.cat

These are pretty much expected - I'll post a fix protocol for them as soon as I get myself organised

 

[NoelDP]

I've uploaded a file - jmkac.zip - to my OneDrive at Noel's OneDrive
Please download and save it.
Right-click on the downloaded file, and select Extract all…
Extract to the default location - which will create a new folder jmkac in the same place.
Open this folder - there should be one folder inside it (Packages)

Copy the content of the Packages folder to the folder
C:\Windows\Temp\CheckSur\Servicing\Packages


Now run the CheckSUR tool again (it may take a while)

Post the new CheckSUR.log file, and the CheckSUR.persist.log file.

 

[jmak18]

When I do this it says that "there is already a file with the same name in this location", also saying there are 7 other conflicts. What should I do? Copy/Replace, Keep both, or not copy? I've attached a screenshot in case.

 

[NoelDP]

OK - that means that the problem is a little different, and lies within the registry rather than the file system.

abandon that for the moment.



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 OneDrive) and post a link.

 

[jmak18]

Haven't used Dropbox for a long time. Forgot how to link for a moment lol. Here it is:

https://www.dropbox.com/s/d9h9vzkcuzcakpj/COMPONENTS.zip

 

[jmak18]

Also I just had a couple of quick questions that doing all this has brought to my attention.

The first one would be whether doing things like SFC and CheckSUR's can help with computer performance in general, and in that case whether it would be recommended that the average computer user use these tools as part of regular maintenance. And the second one (perhaps rooted more in paranoia than just curiosity :shock is how these errors and file corruptions could have happened, as in could a virus have caused this or is it just some normal thing that happens to all computers. I'm asking this since you mentioned earlier that I was missing some critical files as well as recently having a virus scare on my other computer.

Other than that really appreciate you doing all this, I can imagine how stressful doing stuff like this can be sometimes

 

[NoelDP]

It looks to me as if someone has been using some form of registry cleaner - and because there were errors in the registry, the cleaner, rather than repairing things, has comprehensively trashed them.
I don't think there's a lot I'm going to be able to do with it, apart from recommend a repair install

As to what caused the initial error, the common causes are BSOD during updating, power-out during updating, registry cleaners, malware, etc., etc..

I'm going to ask someone else to have a look and see if he can come up with a better prognosis for you, but it may be a couple of days before he can free the time to get back to you.

Don't run away!

 

[jmak18]

By registry cleaner do you mean something like CCleaner, because that's the only form of Registry Cleaner I have, although I haven't used it for a while.

I also have CCleaner backups files which were created after each Registry run, if I could get these restored is it possible to not have to do a repair install?

 

[NoelDP]

CCLeaner is safer than most - I was more worried about anything from the Wise or IOBit stables.

A System Restore and/or restores from CCleaner's backups is worth a try, although I suspect they won't repair all the damage.

 

[jmak18]

Nope never even heard of the other two, CCleaner is the only Registry Cleaner I've ever used. Anyways, I merged all the backups from the CCleaner Backup Files folder, which it reported was successful. The files are still there in the folder. Not sure if that's just normal or whether they were supposed to disappear after merging. Anyways, I then restarted the computer after which everything seemed to be normal. I proceeded to do your previously mentioned instructions of copying the COMPONENTS file and am posting the dropbox link to the new one.

https://www.dropbox.com/s/d9h9vzkcuzcakpj/COMPONENTS.zip

I'm kind of curious why this wouldn't repair all the damage though since I kept a backup of every registry cleaning I did. Unless you're saying someone was directly tampering with it?