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

[DaveF]

Hi, The problems I'm having appear in part to be nearly identical to the ones posted in the January, 2011 thread: http://www.sevenforums.com/windows-...rade-fails-install-after-kb976902-update.html

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:

=================================
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.

 

[gregrocker]

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

 

[DaveF]

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.

 

[Golden]

Dave : I'll ask Noel and/or Tom to follow this up for you. They are our update specialists here.

 

[NoelDP]

I'm on it

 

[NoelDP]

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.

 

[DaveF]

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

 

[NoelDP]

Unfortunately, the upload contained everything EXCEPT for the registry hives - presumably because they were all locked.

Please run the following command in an Elevated Command Prompt (it won't work in a std user one)
Copy C:\Windows\System32\config\components %userprofile%\desktop

This will create a copy of the file on your desktop - compress that, and upload it, then post a new link

 

[DaveF]

Okay, doing that. Thanks.

 

[DaveF]

I kept trying and Windows complained files couldn't be copied because they were in use, then I created an ERD and booted from it. When I copied the directory tree it seems to have gotten saved as a single monolithic file; I'm not sure whether directory information is contained? I hope it can be properly extracted. I can always try again I suppose but I don't want to waste your time.

I very much appreciate your effort.

Uploaded as davef.zip (11 May, as opposed to the previous attempt, davef-components.zip, 9 May) to
https://www.dropbox.com/sh/ousx8f4edax8rel/8MzulVh-CL

 

[NoelDP]

That command should only have copied a single file - the COMPONENTS file - to the desktop. Typical size is around 40MB before compression.
Yours appears to be rather larger - 83MB!
I could have fun here

 

[NoelDP]

Not as bad as I thought - although I've not checked anything else apart from the known errors....


I've uploaded a file - dfcaa.zip - to my SkyDrive at Noel's SkyDrive
Please download and save it to your desktop. (that's important!)
Right-click on the downloaded file, and select Extract all…
Extract to the default location - which will create a new folder dfcaa in the same place.

Now open an Elevated Command Prompt, and run the following commands...

reg unload hklm\components
REN C:\Windows\System32\config\COMPONENTS COMPONENTS.old
COPY %userprofile%\desktop\dfcaa\COMPONENTS C:\Windows\System32\config

If the first fails with a 'could not unload' message, it will mean trying the commands while in Safe Mode, and the file is loaded to the registry, and windows is attempting to repair it.
If it fails with a 'parameter is incorrect' message, then the other two should complete OK.

If it succeeds, then the others should run OK

Once complete, reboot, and run another CheckSUR scan and we'll see how many I missed, and what else has been brought to light.

 

[DaveF]

Hey! It got way smaller.

Now I have:

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.21645
Package Version 18.0
2013-05-13 17:01

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f)    CSI C Mark Deployment Missing    0x00000000    c!07e07bbd6d0..323a83baf0d_31bf3856al364e35_8.0.7600.20861_30d8585b5e610801    amd64_07e07bbd6d0d872aab85f323a83baf0d_31bf3856ad364e35_8.0.7600.20861_none_30d8585b5e610801    
(f)    CSI C Mark Deployment Missing    0x00000000    c!d648a20335a..279ce750b68_31bf3856ad364e35_8.0.7600.16722_13d7036358635523    amd64_d648a20335a7bf43995a2279ce750b68_31bf3856ad364e35_8.0.7600.16722_none_13d7036350635523    
(f)    CSI C Mark Deployment Missing    0x00000000    c!d648a20335a..279ce750b68_31bf3856ad364e35_8.0.7600.16722_13d7036358635523    x86_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_8.0.7600.20861_none_1d14d3eb933996fc    
(f)    CSI C Mark Deployment Missing    0x00000000    c!fef5b2c062a..4d7632e6f44_31bf3856ad364e35_8.0.7600.16722_6ffad108d51fe423    x86_microsoft-windows-ie-runtimeutilities_31bf3856ad364e35_8.0.7600.16722_none_62722df664abbf22    
(f)    CSI C Mark Deployment Missing    0x00000000    c!07e07bbd6d0..323a83baf0d_39bf3856al364e35_8.0.7600.20861_30d8585b5e610801    amd64_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_8.0.7600.20861_none_79336f6f4b970832    
(f)    CSI C Mark Deployment Missing    0x00000000    c!d648a20335a..279ce750b68_31bf3856ad364e35_8.0.7600.16722_13d7036350635523    x86_microsoft-windows-i..ersandsecurityzones_31bf3856ad364e35_8.0.7600.16722_none_cfb19b78aef17a32    
(f)    CSI C Mark Deployment Missing    0x00000000    c!d648a20335a..279ce750b68_31bf3856ad364e35_8.0.7600.16722_13d7036350635523    amd64_microsoft-windows-i..ersandsecurityzones_31bf3856ad364e35_8.0.7600.16722_none_2bd036fc674eeb68    

Summary:
Seconds executed: 192
 Found 7 errors
  CSI C Mark Deployment Missing Total count: 7

I haven't done anything other than replace the config per your instructions and run the SUR tool. Haven't tried another winup nor sfc.

I await further instructions, with renewed hope and enthusiasm.

 

[gregrocker]

Is this the original Asus factory preinstalled Win7? Because that is a badly corrupt OS due to poorly written Asus software which duplicates and interferes with much better versions built into Win7. This is frequently the cause of these kinds of problems.

You said you dread getting the vastly superior Clean Reinstall - Factory OEM Windows 7 but did you read it as no one who has tried it has lost any software that came preinstalled that they still needed. We can help you with any of these that you are concerned with.

Since you came here to the top resource on the web for this specialty then why not get the best possible install instead of the worst one which you have if you have preinstalled Asus Win7? It will truly be better than getting a new PC under the circumstances.

 

[DaveF]

I would not buy an Acer. This is an Asus. I'm not interested in the bloat which came preinstalled - other than the many hardware-specific drivers.

Since Noel offered "we'll see how many I missed, and what else has been brought to light" I was hopeful the remaining orphan component store references could be removed or repaired. No dice?


Any opinion on whether I ought now to try SFC and/or Windows Update? or could such attempts diminish my chances at repair?

I will still consider a fresh clean install in any event. Though I was hoping first to have the cash for decent backup and for additional software, etc.

 

[gregrocker]

Yeah I was referring to Asus preintalled software which is poorly written. Do you still have that corrupt install?

Noel can help you with Updates but there will be other issues as long as you have an install that corrupted by bloatware. Even if you follow the steps to safeguard System files when you Clean Up Factory Bloatware it is never comparable to a Clean Reinstall.

 

[DaveF]

I have read your tutorials and they are fantastic, Greg. And I don't doubt you when you say that a clean OEM install offers much benefit over the in-place. I'm sure that I'll be going that route at some point.

In your bloatware clean-up document you make a recommendation for a defrag program. I would offer that it may be helpful in addition to advise owners of SSD hardware particularly never to defrag since it is unnecessary and will shorten the life of such drives.

I have disabled much of the autostart software other than video, audio & touchpad, and I replaced other drivers - wireless and chipset - because they appeared to be better than that which Asus provides and at least as applicable to my system.

 

[NoelDP]

So far, so good

I'll work on the version I already have, and see if I can works out the problems in that - inn the meantime, please do NOT attempt to install any updates (it's patch Tuesday today! - it may be a good idea to switch WU off for the moment)

 

[DaveF]

Not a problem, and no rush, and THANK YOU, NOEL and everyone at sevenforums, you are all so great to be helping me and others.

 

[DaveF]

Greg, I never answered your question. Sorry!

Do you still have that corrupt install?

I think I probably have a couple.

I have a 2-byte file in my Windows partition root:

05/07/2013  06:28 PM                 2 $UpgDrv$

and these files:

04/11/2008  10:07 AM             3,820 eula.1028.txt
04/11/2008  10:07 AM            15,428 eula.1031.txt
04/11/2008  10:07 AM            10,058 eula.1033.txt
04/11/2008  10:07 AM            12,246 eula.1036.txt
04/11/2008  10:07 AM            13,912 eula.1040.txt
04/11/2008  10:07 AM             5,868 eula.1041.txt
04/11/2008  10:07 AM             5,970 eula.1042.txt
04/11/2008  10:07 AM            10,134 eula.1049.txt
04/11/2008  10:07 AM             3,814 eula.2052.txt
04/11/2008  10:07 AM            12,936 eula.3082.txt
04/11/2008  08:03 AM            76,304 install.res.1028.dll
04/11/2008  08:03 AM            96,272 install.res.1031.dll
04/11/2008  08:03 AM            91,152 install.res.1033.dll
04/11/2008  08:03 AM            97,296 install.res.1036.dll
04/11/2008  08:03 AM            95,248 install.res.1040.dll
04/11/2008  08:03 AM            81,424 install.res.1041.dll
04/11/2008  08:03 AM            79,888 install.res.1042.dll
04/11/2008  10:09 AM            93,200 install.res.1049.dll
04/11/2008  08:03 AM            75,792 install.res.2052.dll
04/11/2008  08:03 AM            96,272 install.res.3082.dll
12/21/2011  09:14 AM                 7 RECOVERY.DAT
04/11/2008  10:07 AM             5,686 vcredist.bmp
04/11/2008  10:09 AM         3,797,292 VC_RED.cab
04/11/2008  10:11 AM           233,472 VC_RED.MSI

And I have these directory entries in root:

05/07/2013  06:29 PM    <DIR>          $UPGRADE.~OS
05/07/2013  06:26 PM    <DIR>          $WINDOWS.~BT
05/07/2013  06:28 PM    <DIR>          $WINDOWS.~LS
04/27/2013  10:40 PM    <DIR>          aa3e7fb72c9517be37ba3a
11/15/2012  07:56 AM    <DIR>          b957d06e05233314a6a0