Windows 7 Updates Failing - CSI payload files missing

[mattysyr]

I am working on a computer for over a week now. Each time I run Windows updates it appears to complete successfully but upon reboot all changes are reverted. Ultimately I am trying to upgrade to IE 10 or 11 from 8 but would like to fix the Windows update mechanism as well.

I have run CheckSur and SFC.

CheckSur did fix many issues but I am stuck now with three missing files:
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 25.0
2014-08-13 11:31

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f) CSI Payload File Missing 0x00000000 KBDINHIN.DLL wow64_microsoft-windows-i..l-keyboard-00010439_31bf3856ad364e35_6.1.7601.17514_none_f6670d2d9f81941a
(f) CSI Payload File Missing 0x00000000 disrvci.dll amd64_divacx64.inf_31bf3856ad364e35_6.1.7600.16385_none_cf37cc4c5bc25dc7
(f) CSI Payload File Missing 0x00000000 HashCleanup.exe amd64_microsoft-windows-t..ched-hashcleanup-gc_31bf3856ad364e35_6.1.7600.20830_none_b0104b499be3fa14

Summary:
Seconds executed: 1062
Found 3 errors
CSI Payload File Missing Total count: 3

Thanks in advance for your help!

 

[NoelDP]

Here's the SFC can final summary...

 Line 5845: 2014-08-13 12:12:45, Info                  CSI    0000031c [SR] Repairing 5 components
 Line 5846: 2014-08-13 12:12:45, Info                  CSI    0000031d [SR] Beginning Verify and Repair transaction
 Line 5847: 2014-08-13 12:12:46, Info                  CSI    0000031e [SR] Cannot repair member file [l:22{11}]"disrvci.dll" of divacx64.inf, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, file is missing
 Line 5850: 2014-08-13 12:12:46, Info                  CSI    00000320 [SR] Cannot repair member file [l:16{8}]"msjh.ttf" of Microsoft-Windows-Font-TrueType-MicrosoftJhengHei, 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 in the store, hash mismatch
 Line 5853: 2014-08-13 12:12:46, Info                  CSI    00000322 [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, 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 in the store, hash mismatch
 Line 5854: 2014-08-13 12:12:46, Info                  CSI    00000323 [SR] Cannot repair member file [l:24{12}]"KBDINHIN.DLL" of Microsoft-Windows-International-Keyboard-00010439, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
 Line 5857: 2014-08-13 12:12:46, Info                  CSI    00000325 [SR] Cannot repair member file [l:14{7}]"msi.dll" of Microsoft-Windows-Installer-Engine, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

Interesting that CheckSUR appears to have found another file as well...

(f) CSI Payload File Missing 0x00000000 HashCleanup.exe amd64_microsoft-windows-t..ched-hashcleanup-gc_31bf3856ad364e35_6.1.7600.20830_none_b0104b499be3fa14

we would usually expect SFC to find everything that CheckSUR does in this type of problem.

I'll post a fix protocol later.

 

[NoelDP]

I've uploaded a file - myraa.zip - to my OneDrive at Noel's OneDrive
Please download and save it.

Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract
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:\myraa
hit the enter key - if you get a 'Not Found' error try
DIR D:\myraa
or
DIR E:\myraa



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



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



(e.g. XCOPY P:\wfire P:\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 reply

 

[mattysyr]

Thank you for the speedy response! I am working on this computer remotely. Is there anyway to copy these files from a windows environment rather then the pre boot environment?
Thanks!

 

[NoelDP]

You'd need to take ownership of the folders and files concerned and give yourself permission, then then restore the original permissions after copying the files across.

 

[mattysyr]

I have followed instructions and windows updates still failing. Please see attached logs.
Thanks!

 

[NoelDP]

Looks like that worked

How's Windows Update behaving now?

 

[mattysyr]

Still no good unfortunately. The windows part of the update appears to go through successfully, during reboot it gets to just about 100%, then it fails and reverts changes. It tries about 3 times to reinstall the updates then goes back to windows login.

This is the same behavior as before we resolved the CheckSur issues.

Thanks!

 

[NoelDP]

OK - run through the SFC and CheckSUR again, and post the new logs - also post the C:\Windows\windowsupdate.log file and I'll se what I can find.