New
#11
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 :)
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 :)
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.
Hey! It got way smaller.
Now I have: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.Code:================================= 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 await further instructions, with renewed hope and enthusiasm.
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.
Last edited by gregrocker; 13 May 2013 at 18:21.
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.
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.
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.
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)
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.
Greg, I never answered your question. Sorry!
I think I probably have a couple.
I have a 2-byte file in my Windows partition root:and these files:Code:05/07/2013 06:28 PM 2 $UpgDrv$And I have these directory entries in root:Code: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.MSICode: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
Last edited by DaveF; 14 May 2013 at 16:21. Reason: removed irrelevant file-listing referencing a driver install