Windows Update 80070490 and non-KB items in CheckSUR.log

I would prefer to do the changes ONLY on the affected folders, and not the whole of winsxs. Some files don't just take their permissions from the parent, and require slightly different ones (they don't concern us here).

The best way to do it to take ownership, then ADD full permissions for the Administrators group
you can the copy to your hearts content.
Once complete, remove the added permissions, and transfer ownership back to TrustedInstaller

PLEASE only follow the given instructions - they have been carefully developed over hundreds of threads to avoid problems with later updates.
two of the affected files still require work...

Code:

 Line 47263: 2015-02-24 23:01:25, Info                  CSI    0000034e [SR] Repairing 5 components
 Line 47264: 2015-02-24 23:01:25, Info                  CSI    0000034f [SR] Beginning Verify and Repair transaction
 Line 47267: 2015-02-24 23:01:27, Info                  CSI    00000351 [SR] Cannot repair member file [l:22{11}]"rasctrs.ini" of Microsoft-Windows-Rasctrs.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"sv-SE", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 47270: 2015-02-24 23:01:27, Info                  CSI    00000353 [SR] Cannot repair member file [l:48{24}]"FirewallControlPanel.dll" of Networking-MPSSVC, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

I'll post a new fix protocol tomorrow.

My fault - it was the end of a very long day! (out at 07:30, back at 23:00)
I did in fact post the wrong file there, so you can delete the folder amd64_microsoft-windows-rasctrs.resources_31bf3856ad364e35_6.1.7600.16385_en-us_1c236de0f7c0fc1e unless you also have English installed.
I've managed to get the proper Swedish files now - so I'll post the new fix when I can find the time.

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



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



XCOPY <drive>:\mwsab <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 new error-list...

Code:

 Line 66787: 2015-03-08 18:07:32, Info                  CSI    0000033c [SR] Repairing 2 components
 Line 66788: 2015-03-08 18:07:32, Info                  CSI    0000033d [SR] Beginning Verify and Repair transaction
 Line 66789: 2015-03-08 18:07:32, Info                  CSI    0000033e [SR] Repairing corrupted file [ml:520{260},l:72{36}]"\??\C:\Windows\Inf\RemoteAccess\041D"\[l:22{11}]"rasctrs.ini" from store
 Line 66792: 2015-03-08 18:07:32, Info                  CSI    00000340 [SR] Repairing corrupted file [ml:48{24},l:46{23}]"\??\C:\Windows\SysWOW64"\[l:48{24}]"FirewallControlPanel.dll" from store
 Line 66805: 2015-03-08 18:07:32, Info                  CSI    00000342 [SR] Repair complete

...This would seem to mean that one of us made a mistake

It's likely to be my problem - I can't see for now where I went wrong, but I'll have a look and get back when I can.