[SOLVED] Windows7 Update not working

Hello again Gary :)

Sorry about the delay. You, unfortunately, have a really bad corruption. Instead of there just being a couple of keys/values corrupt, which is usually fixable, you have a corruption which pushes the entire file out of alignment. What this effectively means is that Windows cannot read any of the data below the corruption point, giving you apparent monumental damage. Whilst most of the data is still there, it cannot be read by Windows, hence your updating problems.

I have spent the last couple of days attempting to manually modify the repair the raw binary of your COMPONENTS hive. Unfortunately, I was not successful. I have tried absolutely everything I can think of, but I have not been able to fix it :(

I am really sorry. I think your best bet at this time is to try a Repair Install (https://www.sysnative.com/forums/windows-7-%7C-windows-vista-tutorials/3900-place-upgrade-install-windows-windows-7-windows-vista.html), especially if you have an SP1 DVD.

If the Repair Install fails, you could try to replace your current COMPONENTS hive with the one from the other computer, and try the Repair Install again. That is often enough to get it working.

If you are really not keen on re-installing, you could use the COMPONENTS sub-hive from the other machine. I cannot say how long it will work for before you run into problems, maybe not very long, maybe a long time, but to be honest you are running on borrowed time somewhat at the moment. But it may be worth a shot, see how long you get.

I am so sorry it ended like this. I really did try absolutely everything I could think of, and more, but it just wasn't enough :(

Richard
 
Thanks for your time and efort, i figured it must been damaged beyand recovery when i saw that hive only had 4 sub keys in it in comparesone to hive from my desk top i will try to see if i can use other hive and do in place ripairs maybe i be lucky enoth to get it working re instaliing windows from scratch always a teadios task and then all the software to be re install as well, just 1 quation do you know what can posebly corupt hive to thise extend ?
 
Gary said:
Thanks for your time and efort, i figured it must been damaged beyand recovery when i saw that hive only had 4 sub keys in it in comparesone to hive from my desk top i will try to see if i can use other hive and do in place ripairs maybe i be lucky enoth to get it working re instaliing windows from scratch always a teadios task and then all the software to be re install as well, just 1 quation do you know what can posebly corupt hive to thise extend ?
Click to expand...

No problem. Allow me to give you a very oversimplifed and ficticious example. Windows only sees four keys. In reality, the rest still remain in the file, but are not visible to Windows. I was trying to make them visible. The data has not been lost, just no longer available.

Let's assume that 00 is a special character which terminates a file. As soon as this character is reached, no further reading of the file is performed.

Now imagine a string of hexadecimal data: 8B 5F DE 56 01 E3 19 5C 72 F9 00

Windows sees this as: 8B 5F DE 56 01 E3 19 5C 72 F9

Now let's assume we have a single point corruption:

Old: i 8B 5F DE 56 01 E3 19 5C 72 F9
New: 8B 5F DE 56 00 E3 19 5C 72 F9

Now Windows sees it as: 8B 5F DE 56

The data E3 19 5C 72 F9 has not been lost, it just does not show up. There is only one tiny bit of real corruption. But on the surface, there appears to be massive corruption of over 50% of the data. There isn't, but that is what it looks like.

A very similar thing is happening here with you. I can see in raw binary format an almost perfect COMPONENTS hive with very little corruption.

Unfortunately, somewhere within lies a most tiny corruption which is throwing Windows off the rest of the file, hence only 4 keys show up. You only have a tiny corruption, but it was a very serious one.

I have spent ages trying to track down potentially a single misplaced 0 or 1, but was unable to find it to fix it. I am very sorry :(

Anyway, it could be anything from dying hardware, RAM quite possible, to just unluckiness. The vast majority of Windows Update issues I see are not caused by failing hardware. If you want me to tell you how to check hardware, I would be more than happy to, but I do not suspect it is necessary, unless you have other problems indicative of hardware failure. I think hardware failure is not likely here.

Richard
 
I dont think i do have hardware issues ether, however when I look in to system info to if see any hardware conflicts its empty, however when i run memory test from start up options on scan it does tell me some of hardware falier but its not telling me which, looking in to manager for hardware with in windows it shows all hardware functioning correctly and all drivers is up to date... All i can think of is when i run windows 8 compatebilety test it show me that some of my drivers from toshiba need it update, after installing updated drivers i start getting blue screeb error i uninstall all drivers that was updated to no avail still having ocasional blue screen crushing...
 
Gary said:
I dont think i do have hardware issues ether, however when I look in to system info to if see any hardware conflicts its empty, however when i run memory test from start up options on scan it does tell me some of hardware falier but its not telling me which, looking in to manager for hardware with in windows it shows all hardware functioning correctly and all drivers is up to date... All i can think of is when i run windows 8 compatebilety test it show me that some of my drivers from toshiba need it update, after installing updated drivers i start getting blue screeb error i uninstall all drivers that was updated to no avail still having ocasional blue screen crushing...
Click to expand...

Hmmmm. There might actually be an issue here after all.

The Windows Memory Test only scans one piece of hardware, the RAM. This could fit with exactly the type of corruption in your registry.

Can I suggest a second opinion? I would advise running MemTest86+, as outlined here: https://www.sysnative.com/forums/hardware-tutorials/3909-test-ram-memtest86.html

Can you please let me know whether you get any errors or not?

You might also want to create a new thread about your BSODs. We might be able to help you with that too. However, I suspect that they would also want you to run MemTest86+.

Richard
 
Well according to the tool you link me my entire memory seems to be corrupted, even tho I find that hard to believe sense my system set to run in memory and page only as needed, but my laptop is 5 years old and it is dew for new keyboard sense old one wading away, I will let repair shop examine my memory sticks and if they r bad I have them replaced.

Also new hive do let me check for updates and do find them, how ever I get different errors on frailer to install them & ones that do install revert on restart of system just thought to let u know

P.S. what is BSODs?
 

Attachments

  • WUError.png
    WUError.png
    19.5 KB · Views: 1
Gary said:
Well according to the tool you link me my entire memory seems to be corrupted, even tho I find that hard to believe sense my system set to run in memory and page only as needed, but my laptop is 5 years old and it is dew for new keyboard sense old one wading away, I will let repair shop examine my memory sticks and if they r bad I have them replaced.

Also new hive do let me check for updates and do find them, how ever I get different errors on frailer to install them & ones that do install revert on restart of system just thought to let u know

P.S. what is BSODs?
Click to expand...

Memtest86+ is probably reporting many errors at a small part of your memory. This completely fits with all the symptoms you have described. By the sounds of it, it needs some new memory (don't worry, it shouldn't be too expensive). I think it is a good idea to let the repair shop take a look. BSOD stands for Blue Screen of Death. I think you had some?? Anyway, it is probably caused by your memory again.

Please re-run System Update Readiness Tool and upload C:\Windows\Logs\CBS\CheckSUR.persist.log.

Thanks!
 
Well i end up totally re installing windows clean so far its working good keeping fingers crossed will see what happens so far all updates have been installed with out any problems thanks for all the help.
 
Gary said:
Well i end up totally re installing windows clean so far its working good keeping fingers crossed will see what happens so far all updates have been installed with out any problems thanks for all the help.
Click to expand...

That sounds like the best plan. It was beyond repair, I am afraid, and it needed to be done eventually. Best to get it over with, and I wish you and your computer well for the future.

However, I am still slightly concerned about your memory. Did the computer shop ever test/replace them? You had a whole bunch of symptoms relating to failing memory, + two separate tools report their failure. Its fate seems slightly sealed. Of course, there is never any absolute guaratee, but it really does seem to be stacking up.

Anyway, happy holidays. It has been a pleasure to work with you.

Richard
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top