Windows Update Issues

OK - things are going to be fun, then.

Please boot to Safe Mode, and copy the file C:\Windows\System32\config\COMPONENTS (no extension) to your desktop.
Compress the copied file, and upload it to your favourite fileshare site (preferably DropBox or OneDrive)- post a link in your reply. (The compressed file will almost certainly be too big for the forum to allow)

OK - I've fixed the ones I can find (for the moment, at least!)....


I've uploaded a file - gdwaa.zip - to my OneDrive at Noel's OneDrive
Please download and save it to your desktop.
Right-click on the file and select Extract All, and save to the default destination (which should be a folder on the desktop)

Create a new System Restore point

Open an Elevated Command Prompt, and run the following commands.

REN C:\Windows\System32\config\COMPONENTS COMPONENTS.OLD1
COPY %userprofile%\desktop\gdwaa\COMPONENTS C:\Windows\System32\config

If you get an error with either command, STOP THERE - do not reboot! - post for instructions.

Assuming both commands go OK, reboot, and run another CheckSUR scan - post the new CheckSUR.log file.

SFC still failing at this point is not too surprising -

Here's the latest summary from the CheckSUR log

Code:

Summary:
Seconds executed: 945
 Found 99 errors
  CSI Manifest and S256H Do Not Match Total count: 1
  CSI Missing Deployment Key Total count: 91
  CSI Corrupt Deployment Keyform Total count: 1
  CSI Mismatched Identity Total count: 1
  CSI Corrupt I/P Mark Total count: 1
  CSI Located Replacement: Invalid (S256H) Total count: 16
  CSI Corrupt Registry Value Total count: 2
  CBS Registry Error Total count: 1
  CBS Watchlist Package Missing Total count: 1
Unavailable repair files:
 winsxs\manifests\amd64_microsoft-windows-wmi-consumers_31bf3856ad364e35_6.1.7600.16385_none_a6c7190f7292676c.manifest

- no change from the earlier one.


The CBS log shows a few more bitflips - e.g.

Code:

2014-06-08 13:30:45, Error                 CSI    0000000d (F) STATUS_OBJECT_NAME_NOT_FOUND #177503# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = 0, key = {provider=NULL, handle=0}, da = (KEY_READ|DELETE|KEY_WOW64_64KEY), oa = @0xd7d450->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[217]"\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.17592 (win7sp1_gdr.110408-1631)\ComponentFamilies\amd64_microsoft-windows-d..gement-winproviders_31bf3856ad364e35_none_f21e73acf5c7442d\v!6n1.7600.16385"; a:(OBJ_CASE_INSENSITIVE)}, disp = Unmapped disposition: 14145560 (0x00d7d818))[gle=0xd0000034]

I'll fix that from my copy of the file and upload it again when done.

Back soon - I hope!

I've uploaded a file - gdwab.zip - to my OneDrive at Noel's OneDrive
Please download and save it to your desktop.
Right-click on the file and select Extract All, and save to the default destination (which should be a folder on the desktop)

Create a new System Restore point

Open an Elevated Command Prompt, and run the following commands.

REN C:\Windows\System32\config\COMPONENTS COMPONENTS.OLD1
COPY %userprofile%\desktop\gdwab\COMPONENTS C:\Windows\System32\config

If you get an error with either command, STOP THERE - do not reboot! - post for instructions.

Assuming both commands go OK, reboot, and run another CheckSUR scan - post the new CheckSUR.log file.

Change the 'components.old1' to 'components.old2' and try again.