Windows 7: Windows 7 update fails and Windows not genuine message is appearing

Tom,
Thanks for your help, as well. Here is the checksur.persist log. I downloaded Drop box and have the components file in it. Not quite sure how to get it to you.



Noel,
I keep getting the same result when I run scannow. On the command line, it quickly finishes and doesn't make a new log file. It gives the same message that files are corrupted and it can't fix them. Tried 3 times with same result.

Post the CBS log anyhow - the errors should be interesting.

Noel,

I have placed the log file (CSC2) and the components file that Tom requested.Can you tell me how to share the components file with you and Tom? I have them in Dropbox, but I don't know how to proceed.

I'm not familiar with DropBox - but it should be somewhere in their Help files?
The basic idea is that you upload them to your storage area, and ensure that you are sharing them with everyone, then post a link.

Noel and Tom,

I think I figured it out. Hope this works. Thanks again for the help and being patient with an old guy (still willing to learn).


https://www.dropbox.com/s/3r5ve73zqswp8t7/CBS2.txt

https://www.dropbox.com/s/eruskrdvrpyyrmt/components

Noel,

I renamed the file to CBS2 to help me keep track of it. It is the latest.

That's fine - I'll leave you and Tom to sort it out, while I learn how to fix it for next time

Hello Louk,

I've never dealt with a more corrupt log in my life! It's taken me about an hour, but I've fixed everything that it physically possible to fix in your log. One entire section of your log doesn't include enough information to fix it, so I couldn't fix those in this post, I'll come to this later though.

@Noel

Would you mind checking if you have this key for me? If so, could you export it for me please?

[HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\microsoft-w..-deployment_31bf3856ad364e35_6.1.7600.16385_29db99ac4b4847df]

I don't seem to have it on this x86 laptop.

@Louk, on with the fix! I have fixed all of the corruption in your COMPONENTS hive, now we have to replace them.

Could you download this file please:

https://dl.dropbox.com/u/16537616/components.zip

Save it to your Desktop. Then right click > Extract All... and extract the contents to your Desktop. There should be one file, COMPONENTS (with no extension).

Then navigate to this folder:

C:\Windows\system32\config\

In that folder, rename the file COMPONENTS to COMPONENTS.bak

Then copy the COMPONENTS file from your Desktop to this folder.

Then reboot your computer please.

After your computer has rebooted, load the COMPONENTS hive by following Method 2 of this tutorial:

Accessing the COMPONENTS sub-hive | niemiro's Website

Now I would like you to download the second registry fix: louk1_SURT_Fix.reg

Save this to your Desktop, then right-click > Merge to run the fix. Accept any prompt you get about merging a file to the registry.

Now we've hopefully fixed everything that's physically possible to fix at this point. I would like you to run the System Update Readiness Tool again, then upload the CheckSUR.persist.log file as before please.

Lastly, I would like you to download this batch file: RegQuery.bat

Save this to your Desktop, then run it by double clicking on it. This will produce a file on your Desktop called tom982.txt, attach this to your next post please.

Tom

Found it - eventually!
Note that I changed the hive import name to 'testing' rather than COMPONENTS so you'll need to do a find/replace if you want to use it directly!


{edit} FWIW, it's in my x64 hive, and there are 3 references to it in the Catalogs key {/edit}

"WARNING, WILL ROBINSON!!"

The COMPONENTS file downloads as components.txt!
Surely it will need renaming before use??