Missing 8 CSI Payload Files, Cant update windows

Here's the list...

Code:

Checking Component Store
(f) CSI Payload File Missing 0x00000000 packager.dll amd64_microsoft-windows-packager_31bf3856ad364e35_6.1.7601.17727_none_4c2e48b0e7630a9d 
(f) CSI Payload File Missing 0x00000000 packager.dll x86_microsoft-windows-packager_31bf3856ad364e35_6.1.7601.21863_none_f06a092048474399 
(f) CSI Payload File Missing 0x00000000 packager.dll x86_microsoft-windows-packager_31bf3856ad364e35_6.1.7601.17727_none_f00fad2d2f059967 
(f) CSI Payload File Missing 0x00000000 packager.dll amd64_microsoft-windows-packager_31bf3856ad364e35_6.1.7600.16917_none_4a52bb96ea3482c0 
(f) CSI Payload File Missing 0x00000000 packager.dll amd64_microsoft-windows-packager_31bf3856ad364e35_6.1.7600.21094_none_4a82ae600395ec28 
(f) CSI Payload File Missing 0x00000000 packager.dll x86_microsoft-windows-packager_31bf3856ad364e35_6.1.7600.16917_none_ee34201331d7118a 
(f) CSI Payload File Missing 0x00000000 packager.dll x86_microsoft-windows-packager_31bf3856ad364e35_6.1.7600.21094_none_ee6412dc4b387af2 
(f) CSI Payload File Missing 0x00000000 packager.dll amd64_microsoft-windows-packager_31bf3856ad364e35_6.1.7601.21863_none_4c88a4a400a4b4cf

These are all variants of the same file.

I'll post a fix protocol later.

I've uploaded a file - elbaa.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:\elbaa
hit the enter key - if you get a 'Not Found' error try
DIR D:\elbaa
or
DIR E:\elbaa



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



XCOPY <drive>:\elbaa <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

Here's the remaining error...

Code:

 Line 27683: 2015-04-14 14:32:32, Info                  CSI    000002f8 [SR] Repairing 1 components
 Line 27684: 2015-04-14 14:32:32, Info                  CSI    000002f9 [SR] Beginning Verify and Repair transaction
 Line 27687: 2015-04-14 14:32:32, Info                  CSI    000002fb [SR] Cannot repair member file [l:28{14}]"iassdo.dll.mui" of Microsoft-Windows-Networking-Internet_Authentication_Service_Iassdo.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

Unfortunately, this particular one is one that has me stumped - it's not an uncommon one, but it's a very difficult one to fix without a repair install, as it appears to involve hardlinks.

Please run CheckSUR again and post the new CheckSUR.log file just to check that it can't do anything, and we'll see what I can come up with.

CheckSUR can take a few hours to run - just leave it to do its thing. It has a LOT of files to extract and search before it even really starts to function.

Good - CheckSUR is happy, at least!

I'll see what I can dream up by way of a fix for the other file later - in the meantime, you could try WIndows Update again, first doing a new Check for Updates.