Solved Windows 7 Update/Repair error 0x80070246, missing manifests+mum files

[NoelDP]

I cannot for the life of me see anything wrong with that data

Tom? what about you?

 

[lgladen]

Absent any reply from Tom - any objection to me trying the stand-alone SP1 install again? I've been waiting to see if we could get all the errors fixed, but the behavior of the system leads me to believe we might have shot down enough errors for it to work now.

 

[tom982]

Sorry for the delay guys, I've got so much revision to do and have barely any free time at the moment

I cannot for the life of me see anything wrong with that data

Tom? what about you?

Same problem

e625bfd228bdc702

Should be an e.

Absent any reply from Tom - any objection to me trying the stand-alone SP1 install again? I've been waiting to see if we could get all the errors fixed, but the behavior of the system leads me to believe we might have shot down enough errors for it to work now.

I'll upload you a fix in a few minutes!

 

[tom982]

Right, I've fixed the issue that was driving Noel mad, but I've left the others for now in the hope that the SURT will repair some of them for me - I've created the key, but I'm hoping it will populate them with the data rather than me reconstructing it all which will take hours.

Replace COMPONENTS Hive

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

1. Please download the below file, components.zip and save this to your Desktop.
2. Right-click on the file and select Extract All...
3. Tick the box labelled Show extracted files when complete then click Extract
4. A window will open showing a file: components (it has no file extension)
5. Then navigate to C:\Windows\system32\config and rename the file components to components.bak.
6. Copy (Ctrl+C) and Paste (Ctrl+V) the components file on your Desktop into this folder.
7. Run the System Update Readiness Tool (SURT) again and when it finishes installing, attach the log to your next post please:
   
   C:\Windows\Logs\CBS\CheckSUR.persist.log

Note: If, at any point, you are displayed an error saying the file is in use, or access denied, reboot and try again.

https://dl.dropboxusercontent.com/u/16537616/Fixes/COMPONENTS/lgladen/lgladen.zip

That should bring you down to 6 errors!

Tom

Note to self:

ff0d38463ab..6d96b512cbf_31bf3856ad364e35_8.0.7601.17874_87838c9921ee61b0
624d3ceedb5..19b5150e954_31bf3856ad364e35_8.0.7601.22032_45fe8b36a0fc0d39
f542e9a701d..5582ed6ac00_31bf3856ad364e35_8.0.7601.22032_7322f88dcb896c10
e5ae53fb5cd..b732906738b_31bf3856ad364e35_8.0.7601.17874_88322adc921259b1
a9f5599edd3..72a283380f7_31bf3856ad364e35_8.0.7601.22032_f57b7ad4b7455b4a
0c2e29793a6..d846f2e205b_31bf3856ad364e35_6.1.7601.21720_e625bfe228bdc702
f47634f38c1..8b375d54647_31bf3856ad364e35_8.0.7601.17874_2cc8c3f688eccffd

 

[lgladen]

OK, here's the new logs. BTW, no criticism at all was meant by my post - the fact that you're on here at all and willing to help is fantastic. I well know how the real world can get in the way at the most inconvenient times.
As to the logs, well... see for yourself. It's different, at least...?

 

[NoelDP]

Yeah
I'm about lost here, I think.
Unless Tom has a better idea, then I'm thinking in terms of a repair install.- give him at least until tomorrow before doing anything that drastic, though!

 

[tom982]

OK, here's the new logs. BTW, no criticism at all was meant by my post - the fact that you're on here at all and willing to help is fantastic. I well know how the real world can get in the way at the most inconvenient times.
As to the logs, well... see for yourself. It's different, at least...?

Hi lgladen,

I didn't read your post as criticising anything then, and I don't now

Okay, it's done a little bit of the work for us but the job is not done yet. The symptoms in the log don't look too disastrous and all stem from 6 problems, so I'm up for giving this a shot. Can you upload your components hive again please?

Tom

Edit: Just posting the log here for easy access:

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 22.0
2014-01-07 22:44

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f) CSI Missing Identity 0x00000000 appid ff0d38463ab..6d96b512cbf_31bf3856ad364e35_8.0.7601.17874_87838c9921ee61b0
(f) CSI Missing Identity 0x00000000 appid e5ae53fb5cd..b732906738b_31bf3856ad364e35_8.0.7601.17874_88322adc921259b1
(f) CSI Missing Identity 0x00000000 appid 624d3ceedb5..19b5150e954_31bf3856ad364e35_8.0.7601.22032_45fe8b36a0fc0d39
(f) CSI Missing Identity 0x00000000 appid a9f5599edd3..72a283380f7_31bf3856ad364e35_8.0.7601.22032_f57b7ad4b7455b4a
(f) CSI Missing Identity 0x00000000 appid f47634f38c1..8b375d54647_31bf3856ad364e35_8.0.7601.17874_2cc8c3f688eccffd
(f) CSI Missing Identity 0x00000000 appid f542e9a701d..5582ed6ac00_31bf3856ad364e35_8.0.7601.22032_7322f88dcb896c10
(fix) CSI Missing Identity CSI Registry Item Repaired ff0d38463ab..6d96b512cbf_31bf3856ad364e35_8.0.7601.17874_87838c9921ee61b0
(fix) CSI Missing Identity CSI Registry Item Repaired 624d3ceedb5..19b5150e954_31bf3856ad364e35_8.0.7601.22032_45fe8b36a0fc0d39
(fix) CSI Missing Identity CSI Registry Item Repaired f542e9a701d..5582ed6ac00_31bf3856ad364e35_8.0.7601.22032_7322f88dcb896c10
(fix) CSI Missing Identity CSI Registry Item Repaired e5ae53fb5cd..b732906738b_31bf3856ad364e35_8.0.7601.17874_88322adc921259b1
(fix) CSI Missing Identity CSI Registry Item Repaired a9f5599edd3..72a283380f7_31bf3856ad364e35_8.0.7601.22032_f57b7ad4b7455b4a
(fix) CSI Missing Identity CSI Registry Item Repaired f47634f38c1..8b375d54647_31bf3856ad364e35_8.0.7601.17874_2cc8c3f688eccffd
(f) CSI C Mark Deployment Not Marked 0x00000000 c!f47634f38c1..8b375d54647_31bf3856ad364e35_8.0.7601.17874_2cc8c3f688eccffd amd64_microsoft-windows-ie-runtimeutilities_31bf3856ad364e35_8.0.7601.17874_none_c0431d2a1a56521c
(f) CSI C Mark Deployment Not Marked 0x00000000 c!ff0d38463ab..6d96b512cbf_31bf3856ad364e35_8.0.7601.17874_87838c9921ee61b0 amd64_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_8.0.7601.17874_none_7a88664e2fa533bf
(f) CSI C Mark Deployment Not Marked 0x00000000 c!e5ae53fb5cd..b732906738b_31bf3856ad364e35_8.0.7601.17874_88322adc921259b1 x86_microsoft-windows-i..ersandsecurityzones_31bf3856ad364e35_8.0.7601.17874_none_d163ef28ac3e9bf6
(f) CSI C Mark Deployment Not Marked 0x00000000 c!a9f5599edd3..72a283380f7_31bf3856ad364e35_8.0.7601.22032_f57b7ad4b7455b4a amd64_microsoft-windows-i..ersandsecurityzones_31bf3856ad364e35_8.0.7601.22032_none_2e353eb57d9b3dc6
(f) CSI C Mark Deployment Not Marked 0x00000000 c!ff0d38463ab..6d96b512cbf_31bf3856ad364e35_8.0.7601.17874_87838c9921ee61b0 amd64_ff0d38463ab44b72781fb6d96b512cbf_31bf3856ad364e35_8.0.7601.17874_none_87838c9921ee61b0
(f) CSI C Mark Deployment Not Marked 0x00000000 c!f542e9a701d..5582ed6ac00_31bf3856ad364e35_8.0.7601.22032_7322f88dcb896c10 amd64_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_8.0.7601.22032_none_7b3b1a5748a46459
(f) CSI C Mark Deployment Not Marked 0x00000000 c!a9f5599edd3..72a283380f7_31bf3856ad364e35_8.0.7601.22032_f57b7ad4b7455b4a x86_microsoft-windows-i..ersandsecurityzones_31bf3856ad364e35_8.0.7601.22032_none_d216a331c53dcc90
(f) CSI C Mark Deployment Not Marked 0x00000000 c!624d3ceedb5..19b5150e954_31bf3856ad364e35_8.0.7601.22032_45fe8b36a0fc0d39 amd64_microsoft-windows-ie-runtimeutilities_31bf3856ad364e35_8.0.7601.22032_none_c0f5d133335582b6
(f) CSI C Mark Deployment Not Marked 0x00000000 c!f542e9a701d..5582ed6ac00_31bf3856ad364e35_8.0.7601.22032_7322f88dcb896c10 x86_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_8.0.7601.22032_none_1f1c7ed39046f323
(f) CSI C Mark Deployment Not Marked 0x00000000 c!624d3ceedb5..19b5150e954_31bf3856ad364e35_8.0.7601.22032_45fe8b36a0fc0d39 amd64_624d3ceedb5833e11ee7d19b5150e954_31bf3856ad364e35_8.0.7601.22032_none_45fe8b36a0fc0d39
(f) CSI C Mark Deployment Not Marked 0x00000000 c!e5ae53fb5cd..b732906738b_31bf3856ad364e35_8.0.7601.17874_88322adc921259b1 amd64_microsoft-windows-i..ersandsecurityzones_31bf3856ad364e35_8.0.7601.17874_none_2d828aac649c0d2c
(f) CSI C Mark Deployment Not Marked 0x00000000 c!f542e9a701d..5582ed6ac00_31bf3856ad364e35_8.0.7601.22032_7322f88dcb896c10 amd64_f542e9a701dac895266ad5582ed6ac00_31bf3856ad364e35_8.0.7601.22032_none_7322f88dcb896c10
(f) CSI C Mark Deployment Not Marked 0x00000000 c!e5ae53fb5cd..b732906738b_31bf3856ad364e35_8.0.7601.17874_88322adc921259b1 amd64_e5ae53fb5cd5d5e4e7e66b732906738b_31bf3856ad364e35_8.0.7601.17874_none_88322adc921259b1
(f) CSI C Mark Deployment Not Marked 0x00000000 c!ff0d38463ab..6d96b512cbf_31bf3856ad364e35_8.0.7601.17874_87838c9921ee61b0 x86_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_8.0.7601.17874_none_1e69caca7747c289
(f) CSI C Mark Deployment Not Marked 0x00000000 c!a9f5599edd3..72a283380f7_31bf3856ad364e35_8.0.7601.22032_f57b7ad4b7455b4a amd64_a9f5599edd375ac19110e72a283380f7_31bf3856ad364e35_8.0.7601.22032_none_f57b7ad4b7455b4a
(f) CSI C Mark Deployment Not Marked 0x00000000 c!f47634f38c1..8b375d54647_31bf3856ad364e35_8.0.7601.17874_2cc8c3f688eccffd amd64_f47634f38c1ed8b80925f8b375d54647_31bf3856ad364e35_8.0.7601.17874_none_2cc8c3f688eccffd

Summary:
Seconds executed: 965
Found 22 errors
Fixed 6 errors
CSI Missing Identity Total count: 6
Fixed: CSI Missing Identity. Total count: 6
CSI C Mark Deployment Not Marked Total count: 16

 

[lgladen]

Certainly. Here's the link to my skydrive with the latest components.zip
http://sdrv.ms/18VfsF2

 

[lgladen]

I hate to ask, but any progress with the latest COMPONENTS.zip? I only ask because it has now been a bit more than a week, and today is the start of the third week back in school for the laptop owner. She would really like to have it back in working order.

 

[NoelDP]

Never be afraid to ask!
I got somewhat overtaken by events - back asap ... but not tonight
Top of the list now - promise!

 

[lgladen]

You said never be afraid... Any luck at all? Should I perhaps just try repair install once more? Or take it out behind the barn and put it out of it's misery?

 

[NoelDP]

I did have a long look - and couldn't find anything wrong there
Meant to go back to it (and you).

Go for the repair install again - after uninstalling your AV and running any cleanup tool it may have.
Immediately afterwards - and before running Windows Updates - run an SFC /SCANNOW, and see what it has to say - post the results, and I'll take a look while you get to the updates.

As far as Updates are concerned, please install in this order

1) Security Updates for Windows
2) Security Updates for IE8 (but not IE9/10/11 yet!)
3) Other updates for Windows
4) .NET 3.5 updates
5) IE9
6) .NET 4.5
7) IE10
8) IE11

Each time followed by a reboot and a new Check for Updates - you can install anything higher up the list that either didn't install earlier, or has suddenly appeared.
You will get a few failures - nothing to worry about as a rule - just note them and carry on unless one keeps repeating.

 

[lgladen]

Woot! I think this worked! The repair install actually went through this time, instead of crashing out, and sfc /scannow reported no integrity violations. Now if the updates (including sp1) will install....fingers crossed!

 

[NoelDP]

Great!
Good luck with the updates.

 

[lgladen]

Absolute success. This computer was a goner without the help of you and Tom, Noel. Thank you very much. Without the repairs you did, the repair install would not have been able to run, and without that, I would have had to wipe it clean and reinstall from scratch. Since the owner didn't have most of her applications to re-install, it would have been a disaster for her. For the record, all updates installed perfectly, including sp1, and all applications seem to be intact and running properly. Once again, I cannot thank you both enough.

 

[NoelDP]

Great!
Nice to have got it fully fixed - even if it took a lot longer than any of us would have liked.

Good Luck!

 

[lgladen]

Yes, I would have never spent as much time as this on repair if the reinstall would not have been so very costly in terms of application replacement. Keep your product keys and cds in a safe place, people! Learn this lesson! And always Backup Backup Backup! Thanks again Noel. This forum is definitely going into my permanent bookmarks as a great resource.