CheckSUR file - CBS MUM Corrupt 0x800F0900

I think we're getting there - this set of errors appears to be a common one....

Code:

 Line 49995: 2013-01-24 22:11:22, Info                  CSI    00000359 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:32{16}]"WUDFPlatform.dll"; source file in store is also corrupted
 Line 50000: 2013-01-24 22:11:22, Info                  CSI    0000035c [SR] Could not reproject corrupted file [ml:520{260},l:62{31}]"\??\C:\Windows\System32\drivers"\[l:20{10}]"WUDFRd.sys"; source file in store is also corrupted
 Line 50005: 2013-01-24 22:11:22, Info                  CSI    0000035f [SR] Could not reproject corrupted file [ml:520{260},l:62{31}]"\??\C:\Windows\System32\drivers"\[l:20{10}]"WUDFPf.sys"; source file in store is also corrupted
 Line 50010: 2013-01-24 22:11:22, Info                  CSI    00000362 [SR] Could not reproject corrupted file [ml:520{260},l:62{31}]"\??\C:\Windows\System32\drivers"\[l:80{40}]"MsftWdf_User_01_11_00_Inbox_Critical.Wdf"; source file in store is also corrupted
 Line 50015: 2013-01-24 22:11:22, Info                  CSI    00000365 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:22{11}]"WUDFSvc.dll"; source file in store is also corrupted
 Line 50020: 2013-01-24 22:11:22, Info                  CSI    00000368 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:24{12}]"WUDFHost.exe"; source file in store is also corrupted
 Line 50025: 2013-01-24 22:11:22, Info                  CSI    0000036b [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:38{19}]"WUDFCoinstaller.dll"; source file in store is also corrupted
 Line 50030: 2013-01-24 22:11:22, Info                  CSI    0000036e [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:18{9}]"WUDFx.dll"; source file in store is also corrupted
 Line 50041: 2013-01-24 22:11:22, Info                  CSI    00000370 [SR] Repair complete
 Line 50042: 2013-01-24 22:11:22, Info                  CSI    00000371 [SR] Committing transaction

I think I know how to fix it now - it'll have to wait until tomorrow, though.

In the meantime, to confirm the problem, please upload the following files.
C:\Windows\System32\WUDFPlatform.dll
C:\Windows\winsxs\amd64_microsoft-windows-d..frameworks-usermode_31bf3856ad364e35_6.1.7601.17803_none_fb416b4f0bdbe260\WUDFPlatform.dll
C:\Windows\winsxs\Backup\amd64_microsoft-windows-d..frameworks-usermode_31bf3856ad364e35_6.1.7601.17803_none_fb416b4f0bdbe260\WUDFPlatform.dll

(the last one may not exist)

The files are definitely damaged - they should be signed, and aren't, and appear to be full of nothing but null characters.
We'll replace all the affected files but I suspect the SFC will still fail, in which case a little more surgery will be required.

Back in a bit with the fix protocol - caffeine required!

I've uploaded a file - claaa.zip - to my SkyDrive at Noel's SkyDrive
Please download and save it.
Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract
This should create a folder C:\claaa
Close all windows (it would be a good idea to print these instructions!)
Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.
Pick the option to use a Command Prompt
At the prompt type
DIR C:\claaa
hit the enter key - if you get a 'Not Found' error try
DIR D:\claaa
or
DIR E:\claaa

The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...

XCOPY <drive>:\claaa <drive>:\windows\winsxs /y /i /s /v /h

run the command (it should take almost no time)and when the prompt returns, type
EXIT
and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.
Now run SFC /SCANNOW in an Elevated Command Prompt
then reboot and upload the new CBS.log file to your SkyDrive Public folder, and post a new link
Also run a new MGADiag report, and post the result.

Ooops! - I seem to have done everything but upload it

It should be there now.

OK - to my surprise, the files came back OK, but the manifest fails....

Code:

 Line 56751: 2013-01-25 23:39:45, Info                  CSI    000002eb [SR] Cannot verify component files for Microsoft-Windows-DriverFrameworks-UserMode.Resources, Version = 6.1.7601.17803, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
 Line 56756: 2013-01-25 23:39:45, Info                  CSI    000002ee [SR] Recovered manifest from backup for Microsoft-Windows-DriverFrameworks-UserMode.Resources, Version = 6.1.7601.17803, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
 Line 56763: 2013-01-25 23:39:45, Info                  CSI    000002f0 [SR] Repair complete

I'm not certain whether is was properly replaced or not - please run another SFC /SCANNOW and reboot, then post the new CBS log.
Your MGADiag is OK - once you've posted the new CBS log, please test Windows Update to see what happens.

(bed-time here now :))

See you tomorrow!