Windows Update Issues

I hate to say this - but I think we've hit the end of the road.
Unless what we try now has some fairly dramatic results, I don't think we're going to be able to repair this manually....


Please download SFCFix from here... http://www.sysnative.com/niemiro/apps/SFCFix.exe and save it to your desktop (we'll need it later anyhow, I think)

Once saved, double-click on it and accept the warnings. It'll run, and create a file SFCFix.log on the desktop - please upload it to your reply.

I can see the problem that SFC found, at least :)

Code:

2014-06-12 21:26:24, Info                  CSI    00000304 [SR] Repairing 1 components
2014-06-12 21:26:24, Info                  CSI    00000305 [SR] Beginning Verify and Repair transaction
2014-06-12 21:26:24, Info                  CSI    00000306 Manifest hash for component [ml:280{140},l:182{91}]"amd64_microsoft-windows-wmi-consumers_31bf3856ad364e35_6.1.7600.16385_none_a6c7190f7292676c" does not match expected value. 
 Expected:{l:32 b:994e67800c3d65f02e8dded6363542763523a84450e2097bbf0a54b509637af8}
 Found:{l:32 b:994e67800c3d65f02e8dded6363542363523a84450e2097bbf0a54b509637ab8}.
2014-06-12 21:26:24, Info                  CSI    00000307 Unable to load manifest for component [ml:280{140},l:182{91}]"amd64_microsoft-windows-wmi-consumers_31bf3856ad364e35_6.1.7600.16385_none_a6c7190f7292676c"
2014-06-12 21:26:24, Info                  CSI    00000308 [SR] Cannot verify component files for Microsoft-Windows-WMI-Consumers, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
2014-06-12 21:26:24, Info                  CSI    00000309 Repair results created:
POQ 128 starts:

This is a bitflip - I'll post a fix protocol for it later.
In the meantime, please run CheckSUR again, and post the new CheckSUR.log file - it may even fix the problem.
Also, run the SFCFix, and see what it has to say - post its log file as well.

To repair the error... (BEFORE running CheckSUR!)

Open an Elevated Command Prompt, and run the following commands

Code:

REG LOAD HKLM\COMPONENTS C:\Windows\System32\config\Components
REG ADD HKLM\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-wmi-consumers_31bf3856ad364e35_6.1.7600.16385_none_a6c7190f7292676c /v S256H /t REG_BINARY /d 994e67800c3d65f02e8dded6363542 363523a84450e2097bbf0a54b509637ab8 /f
 
.

Close the window, and reboot
then try Windows Update again.
If WU fails again, run CheckSUR, and post the log

Here are some instructions to make life easier :)
1) To open an Elevated Command Prompt Window (the ECP window), click on Start, All Programs, Accessories – then right-click on Command Prompt, and select Run as Administrator. Accept the UAC prompt.
2) To run the commands easier, highlight the block of commands, and right-click on the highlight – select Copy. In the CP Window, click on the black/white icon at top left – select Paste. The commands will run but may not complete the last command, so hit the Enter Key once.
3) To copy the results... click on the Black/White icon in the top left, and select Edit... 'Select All', and hit the Enter key - then use Ctrl+V or r-click+Paste to paste it into your response.

That looks as if the entry is not missing, as such - but corrupted...


I need to have a look at your COMPONENTS registry hive

Please copy the C:\Windows\System32\config\COMPONENTS file (no extension) to your desktop and then compress it - upload the compressed file to your favoured fileshare site (preferably Dropbox or OneDrive) and post a link.

Hah! - I just realised what the problem with the command was....
something split the data variable in two when I posted it - which is why the command was complaining about bad syntax...

try this set instead

Code:

REG LOAD HKLM\COMPONENTS C:\Windows\System32\config\Components
REG ADD HKLM\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-wmi-consumers_31bf3856ad364e35_6.1.7600.16385_none_a6c7190f7292676c /v S256H /t REG_BINARY /d 994e67800c3d65f02e8dded6363542363523a84450e2097bbf0a54b509637ab8 /f
 
.

Oh dear...

Here's the summary from your CheckSUR log

Code:

Summary:
Seconds executed: 1660
 Found 98 errors
  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 Corrupt Registry Value Total count: 2
  CBS Registry Error Total count: 1
  CBS Watchlist Package Missing Total count: 1

It really is not practical to attempt to fix that number of deployment keys manually - your best hope is a repair install.




Download the SP1 Refresh for your language and edition from the links on these pages...

Heidoc - Microsoft DR Download links

The links are for downloads from the Digital River servers run for MS, so are about as safe as you can get :)

Once you have it downloaded, you then need to burn the DVD from it - use either the Windows Disk Image Burner, or (better still) your favourite burning application at the slowest speed possible.

Note that you do NOT 'drag and drop' the file to the disk, you must use the 'burn an image' option from your app - or you'll end up with a useless coaster :)

Once you have the disk burnt, check that it boots the (or any other) system OK - but do NOT start the repair from there - you must start the repair from within a normal Windows boot.

Follow the instructions in this tutorial - https://www.sevenforums.com/tutorials/3413-repair-install.html
- and they should help you get through it (it's not as difficult as it looks!)

Always ask questions first if you're unsure.

Good luck with it!