7 Home Premium in-place setup cancels itself, cannot sfc nor wupdate

Hi, The problems I'm having appear in part to be nearly identical to the ones posted in the January, 2011 thread: Upgrade Fails Install After KB976902 Update

I lost Windows Update functionality, and also that of SFC. Like that other poster, I am on an Asus ultrabook which may have an oddball chipset. At some point, an MS update seems likely to have mistaken my architecture for AMD 64 or Itanium. At one point I booted from a rescue disc produced on this machine and when I tried to access Emergency Repair command console I got a message saying I had the wrong Windows version. So maybe, I'm thinking, it had the 32-bit cmd executable.

Anyhow I've been at trying to repair this for a very long time now, and I need to stop speculating. I'd be enormously grateful to follow some expert guidance, as seems to be available here.

I can provide CBS logs and cabs if necessary, here's my System Update Readiness log:

Code:

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.21645
Package Version 18.0
2013-05-07 21:35

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    f171a4ce71b..49f5034e794_31bf3856ad364e35_8.0.7600.20861_36024ffb9b479b82    
(f)    CSI C Mark Deployment Missing    0x00000000    c!07e07bbd6d0..323a83baf0d_31bf3856al364e35_8.0.7600.20861_38d8585b5e610801    amd64_07e07bbd6d0d872aab85f323a83baf0d_31bf3856ad364e35_8.0.7600.20861_none_30d8585b5e610801    
(f)    CSI C Mark Deployment Missing    0x00000000    c!d648a20335a..279ce750b68_31bf3856ad364e35_0.0.7600&16722_1;d7036358635523    amd64_d648a20335a7bf43995a2279ce750b68_31bf3856ad364e35_8.0.7600.16722_none_13d7036350635523    
(f)    CSI C Mark Deployment Missing    0x00000000    c!07e07bbd6d0..323a83baf0d_31bf3856al364e35_0.0.7600.20861_30d8585b5e610801    x86_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_8.0.7600.20861_none_1d14d3eb933996fc    
(f)    CSI C Mark Deployment Missing    0x00000000    c!fen5b2c062a..4d7632e6f44_39bf3856ad364e35_8.0.7600.16722_6nfad108d51fe423    x86_microsoft-windows-ie-runtimeutilities_31bf3856ad364e35_8.0.7600.16722_none_62722df664abbf22    
(f)    CSI C Mark Deployment Missing    0x00000000    c!3c6102bcce0..c0fd58e3f08_31bf3856ad364e35_0.0.7600&16722_0188ecb35a0e7c0b    amd64_3c6102bcce8a3b3e4d423c0fd50e3f08_31bf3856ad364e35_8.0.7600.16722_none_0188ecb35a0e7c0b    
(f)    CSI C Mark Deployment Missing    0x00000000    c!cad8acd35ad..f8056f98e50_31bf3856ad364e35_8.0.7600&20861_2l5d0664d=3a2c09    amd64_cad8acd35ad0079957fd6f8056f98e50_31bf3856ad364e35_8.0.7600.20861_none_2d5d0664d53a2c09    
(f)    CSI C Mark Deployment Missing    0x00000000    c!07e07bbd6d8..323a83baf0d_39bf3856al364e35_8.0.7600.20861_30d8585b5m610801    amd64_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_8.0.7600.20861_none_79336f6f4b970832    
(f)    CSI C Mark Deployment Missing    0x00000000    c!cal8acd35ad..f8056f98e50_31bf3856ad364e35_8.0.7600.20861_2d5d0664d53a2c09    x86_microsoft-windows-i..ersandsecurityzones_31bf3856ad364e35_8.0.7600.20861_none_d00ef849c8307069    
(f)    CSI C Mark Deployment Missing    0x00000000    c!3c6102bcce8..c0fd58e3f08_39bf3856al364e35_8.0.7600&16722_0188ecb35a0e7c0b    amd64_microsoft-windows-ie-runtimeutilities_31bf3856ad364e35_8.0.7600.16722_none_be90c97a1d093058    
(f)    CSI C Mark Deployment Missing    0x00000000    c!d648a20335a..279ce750b68_39bf3856ad364e35_0.0.7600.16722_13d7036358635523    x86_microsoft-windows-i..ersandsecurityzones_31bf3856ad364e35_8.0.7600.16722_none_cfb19b78aef17a32    
(f)    CSI C Mark Deployment Missing    0x00000000    c!e0eb5dd9801..eccf38a9a0d_31bf3856ad364e35_8.0.7600.16722_c2f96360c7b3baa9    x86_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_8.0.7600.16722_none_1cb7771a79faa0c5    
(f)    CSI C Mark Deployment Missing    0x00000000    c!cad8acd35ad..f8056f98e50_31bf3856ad364e35_8.0.7600&20861_2d5d0664d=3a2c09    amd64_microsoft-windows-i..ersandsecurityzones_31bf3856ad364e35_8.0.7600.20861_none_2c2d93cd808de19f    
(f)    CSI C Mark Deployment Missing    0x00000000    c!d648a20335a..279ce750b68_31bf3856ad364e35_8.0.7600&16722_1;d7036358635523    amd64_microsoft-windows-i..ersandsecurityzones_31bf3856ad364e35_8.0.7600.16722_none_2bd036fc674eeb68    
(f)    CSI C Mark Deployment Missing    0x00000000    c!e0mb5dd9809..eccf38a9a0d_31bf3856al364e35_0.0.7600.16722_c:f96360c7b3baa9    amd64_e0eb5dd9809a00d3b4e2feccf38a9a0d_31bf3856ad364e35_8.0.7600.16722_none_c2f96360c7b3baa9    

Summary:
Seconds executed: 235
 Found 15 errors
  CSI Missing Identity Total count: 1
  CSI C Mark Deployment Missing Total count: 14

Can anyone help? Please let me know. Many thanks.

Can you Clean Install Windows 7? This would assure the install completes as well as rid the corruption that's obviously present.

Boot the DVD, during Custom install delete all partitions, create New as you wish, format and install.

Tips to get a perfect install same as here: Clean Reinstall - Factory OEM Windows 7

Hi, Greg.

That's a very last resort for me due to time considerations and since a backup/restore would lose all the software for which I no longer have installation media. And really, my only big problem is an inability to receive Microsoft updates. I ought to be able to do an in-place upgrade (from/to the OS I own). It appears the solution provided by means of an emergency or installation disk is only available to those who are not in need of it. Rather arrogant on Microsoft's part. As I informed the man from Mumbai who cost me an extra $160 to restate things back to me (whereas in a sane business model he would be paying me) if I have to format I will end up installing a Linux distribution, either Gentoo or Ubuntu.

But I thought this was somehow fixable, Microsoft's efforts to the contrary notwithstanding.

Anyhow thanks for the quick reply. I'm not giving up quite yet.

NoelDP said:

The problem here appears to be corruption in the registry - there are a number of bitflips evident in the errors posted.

Dave - please copy the following file to your desktop, and then Zip it. Upload the zipped file to SkyDrive/Dropbox or other favoured fileshare site, and post a link.

C:\Windows\system32\config\COMPONENTS (no extension)


I'll try and find/fix the errors, and post it back for you.

Done! Link to Dropbox public folder:
https://www.dropbox.com/sh/ousx8f4edax8rel/8MzulVh-CL

Okay, doing that. Thanks.