New
#11
Danny - please start your OWN NEW thread and follow the Windows Update Posting Instructions posting the requested data
Danny - please start your OWN NEW thread and follow the Windows Update Posting Instructions posting the requested data
Drip - sorry about the wait, I must have missed the notification somehow.
Your report shows considerable corruption
Here's the CheckSUR data (the important bits)
I'll post a fix protocol for the files later - hopefully that'll help get the rest fixed :)Code:Summary: Seconds executed: 844 Found 408 errors Fixed 386 errors CSI Could Not Open file Total count: 2 CSI Manifest and S256H Do Not Match Total count: 3 CSI Missing Component Key Total count: 21 Fixed: CSI Missing Component Key. Total count: 21 CSI Missing Pinned Component Key Total count: 112 Fixed: CSI Missing Pinned Component Key. Total count: 112 CSI Missing Deployment Key Total count: 1 CSI Missing Identity Total count: 138 Fixed: CSI Missing Identity. Total count: 136 CSI Corrupt Identity Total count: 2 CSI Mismatched Identity Total count: 1 CSI Missing C Mark Total count: 218 Fixed: CSI Missing C Mark. Total count: 218 CSI C Mark Deployment Missing Total count: 2 CSI Located Replacement: Invalid (S256H) Total count: 21 CSI Replacement File: CreateFile Failed Total count: 22 CSI F Mark Value Wrong Total count: 3 Fixed: CSI F Mark Value Wrong. Total count: 3 CSI F Mark Missing Total count: 8 Fixed: CSI F Mark Missing. Total count: 8 CBS Registry Error Total count: 2 CBS Watchlist Package Missing Total count: 3 CBS Watchlist Component Missing Total count: 4 Unavailable repair files: winsxs\manifests\amd64_mdmgsm.inf_31bf3856ad364e35_6.1.7600.16385_none_bfea4aadd362bbb1.manifest winsxs\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7600.16385_none_fa645303170382f6.manifest winsxs\manifests\amd64_mdmgatew.inf_31bf3856ad364e35_6.1.7600.16385_none_e996a8c57d55e098.manifest winsxs\manifests\amd64_>b5819de>00853a41507704bd68a01d1_31bf3856ad364e35_6.1.7680.21062_none_47a2301a55d7684a.manifest winsxs\manifests\amd64_mdmgen.inf_31bf3856ad364e35_6.1.7600.16305_none_:40ed8e2:9603af8.manifest
Hmmm - there's a few complications here...
You appear to have registry corruption which is calling for non-existent files, at least in two of the above cases.
Let me try and isolate the problem areas....
The following are non-existent files, called from corrupt registry entries
The corrupt entries areCode:Line 597: (f) CSI Could Not Open file 0x0000007B winsxs\Manifests\amd64_>b5819de>00853a41507704bd68a01d1_31bf3856ad364e35_6.1.7680.21062_none_47a2301a55d7684a.manifest amd64_>b5819de>00853a41507704bd68a01d1_31bf3856ad364e35_6.1.7680.21062_none_47a2301a55d7684a Line 611: (f) CSI Could Not Open file 0x0000007B winsxs\Manifests\amd64_mdmgen.inf_31bf3856ad364e35_6.1.7600.16305_none_:40ed8e2:9603af8.manifest amd64_mdmgen.inf_31bf3856ad364e35_6.1.7600.16305_none_:40ed8e2:9603af8
...more later :)Code:Line 475: (f) CSI Corrupt Identity 0xC0150017 mdmgatew.inf, Culture=neutral, Type=driverUpdate, Version=>.1.7600.16385, PublicKeqToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS amd64_mdmgatew.inf_31bf3856ad364e35_6.1.7600.16385_none_e996a8c57d55e098 Bad identity Line 596: (f) CSI Corrupt Identity 0xC0150017 6b5819de600853a49507704bd68a01d1, Culture=neutral, Version=6.1.7600.21062, PublicKmyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS amd64_>b5819de>00853a41507704bd68a01d1_31bf3856ad364e35_6.1.7680.21062_none_47a2301a55d7684a Bad identity
Danny,
From what I've seen on other posts (Windows Update failing with Error codes: 8007371B, 800736B3, 80070246, second page) this fix could be very specific. It sounds like you have some stuff going on that I do not ie Control Panel buttons. I'm still waiting on a suggestion from somebody on what to do here.. If I dont here back soon I'm gonna try another forum then get back to you Danny but for now we're hanging tight! Good luck to you brother!
*Edit* Just saw ur response Noel!
HA 2nd *Edit* I didn't even see the new page! PROGRESS!!
Not in this area you don't :)
I'm not sure I understand it well enough myself, as there are all sorts of interdependencies involved.
I'm going to need a file from you.
Please copy the file C:\Windows\System32\config\COMPONENTS to your desktop, then compress it, and upload the compressed file to a fileshare site (It'll be too big for here, probably) such as SkyDrive or DropBox - post a link, and I'll see what I can see.
COMPONENTS is 1 KB, components is 38.4 MB.. I'll get them both here.
The small file is actually the COMPONENTS.LOG file :)
I've uploaded the COMPONENTS file (zipped as d50aa.zip) to my SkyDrive at
Noel's SkyDrive
Please download and save it.
Now go to the C:\Windows\System32\config folder, and rename the COMPONENTS file (the 40MB one) to COMPLONENTS.OLD
Extract the COMPONENTS file from the downloaded zipfile and put that in the C:\Windows\System32\config folder
now reboot
Then run CheckSUR again, and then SFC /SCANNOW and post the new log files.
I cant rename it because its running in System.