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

[mikewse]

Experiencing the 80070490 error on Windows 7 Professional, I have followed the instructions on http://support.microsoft.com/kb/947821 and run the System Update Readiness Tool.

CheckSUR.log contains the following:

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2015-02-18 18:35
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 rasctrs.ini amd64_microsoft-windows-rasctrs.resources_31bf3856ad364e35_6.1.7600.16385_sv-se_013f700a3fef0220 
(f) CSI Payload File Missing 0x00000000 _ServiceModelEndpointPerfCounters.ini amd64_wcf-m_svc_mod_end_perf_ini_31bf3856ad364e35_6.1.7600.16385_none_26b27bcaa70f123f 
(f) CSI Payload File Missing 0x00000000 _ServiceModelEndpointPerfCounters.h amd64_wcf-m_svc_mod_end_perf_h_31bf3856ad364e35_6.1.7600.16385_none_819e8545cdbf46af 
(f) CSI Payload File Corrupt 0x00000000 CbsCore.dll amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17514_none_678566b7ddea04a5 
Summary:
Seconds executed: 1103
 Found 4 errors
  CSI Payload File Missing Total count: 3
  CSI Payload File Corrupt Total count: 1

The missing/corrupted files are not part of any KB downloads. How can I (re)install the correct packages?
Thanks
Mike

 

[NoelDP]

Please follow the Windows Update Posting Instructions and post the requested data

If the file is too large (8MB compressed), remove the older CBSPersist cab files until the final file is below the limit - you can always post them separately after zipping them. (the forum doesn't allow the upload of bare CAB files, for a number of reasons)

Please also post the C:\Windows\windowsudpate.log file

 

[mikewse]

Thanks, and sorry about the omission! I'm now back at the problematic computer after travelling last two days. I have attached CBS.zip (had to remove a few CABs) and the log file.

 

[NoelDP]

Here's the error-list from SFC...

 Line 19571: 2015-02-21 09:46:53, Info                  CSI    00000368 [SR] Repairing 8 components
 Line 19572: 2015-02-21 09:46:53, Info                  CSI    00000369 [SR] Beginning Verify and Repair transaction
 Line 19575: 2015-02-21 09:46:54, Info                  CSI    0000036b [SR] Cannot repair member file [l:24{12}]"atiumd64.dll" of atiilhag.inf, Version = 6.1.7601.17514, 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, hash mismatch
 Line 19578: 2015-02-21 09:46:54, Info                  CSI    0000036d [SR] Cannot repair member file [l:20{10}]"dfrgui.exe" of Microsoft-Windows-Defrag-AdminUI, Version = 6.1.7601.17514, 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 19581: 2015-02-21 09:46:54, Info                  CSI    0000036f [SR] Cannot repair member file [l:14{7}]"wet.dll" of Microsoft-Windows-MigrationWizardApplication, Version = 6.1.7601.17514, 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 19584: 2015-02-21 09:46:55, Info                  CSI    00000371 [SR] Cannot repair member file [l:26{13}]"netcenter.dll" of Microsoft-Windows-NetworkCenter, Version = 6.1.7601.17514, 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 19585: 2015-02-21 09:46:55, Info                  CSI    00000372 [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, file is missing
 Line 19586: 2015-02-21 09:46:55, Info                  CSI    00000373 [SR] Cannot repair member file [l:70{35}]"_ServiceModelEndpointPerfCounters.h" of WCF-M_SVC_MOD_END_PERF_H, 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, file is missing
 Line 19587: 2015-02-21 09:46:55, Info                  CSI    00000374 [SR] Cannot repair member file [l:74{37}]"_ServiceModelEndpointPerfCounters.ini" of WCF-M_SVC_MOD_END_PERF_INI, 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, file is missing
 Line 19590: 2015-02-21 09:46:55, Info                  CSI    00000376 [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

As you can see, it's a little different to the one produced by CheckSUR!

I'll post a fix protocol later.

 

[NoelDP]

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



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



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

 

[mikewse]

Very interesting, thanks!
All is fine up to the repair login in your guide. This is a domain-joined laptop and I am local admin only when logged in to my domain account, but this account is not available on the repair login screen. Is there any other way I can get into the right kind of command prompt? (safe mode etc)
Best regards
Mike

 

[NoelDP]

Not really - the only other way to do it would be to give yourself permissions to the folders concerned, copy the files in, then remove the new permissions.

 

[mikewse]

So if adding the necessary permissions, will it work to perform this copying from a normal or safe mode startup, or is it imperative that the computer is booted in repair mode?
(The repair login shows a dropdown with only account which I think was set up by the person doing the install but who has now left the company)

 

[NoelDP]

You can do it all in normal mode... plesse mske sutre that you get the permissions right at the end.

 

[mikewse]

I've been struggling with adding enough permissions to the winsxs folder while trying not to do too much harm. It seems many guides recommend taking ownership of the winsxs folder and subfolders. Do you know if this is needed or is there a leaner way through this? Ideally I would just like to assign some permissions to c:\, c:\windows, c:\windows\winsxs and appropriate subfolders from an elevated command prompt...

 

[NoelDP]

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

 

[mikewse]

All done now. One thing I noticed was that one of the package dirs differed in locale:
amd64_microsoft-windows-rasctrs.resources_31bf3856ad364e35_6.1.7600.16385_en-us_1c236de0f7c0fc1e
instead of as on my system:
amd64_microsoft-windows-rasctrs.resources_31bf3856ad364e35_6.1.7600.16385_sv-se_013f700a3fef0220
I put the incoming files in my sv-se package.

BTW, I used the free NTFS Permissions Tool to copy/paste ownership and permissions between files.

Supplying new CBS.log.
Thanks for all your help so far

 

[NoelDP]

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...

 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.

 

[mikewse]

Oh, sorry, I guessed that the intention was not to create a brand new package directory in winsxs, my bad.
Generating CheckSUR.log again reported no errors, so I retried Windows Update which gave success on a couple of updates but failed others.
I attach a newly generated CBS.log in case this changed things (it did get smaller).
Best regards
Mike

 

[NoelDP]

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.

 

[mikewse]

Thanks for doing that extra work . It didn't occur to me that locale specific stuff would show up so forgot to mention the non-US installation language.

 

[NoelDP]

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

 

[mikewse]

Sorry about the delay, the computer was out of town
The new log file is attached!

 

[NoelDP]

Here's the new error-list...

 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.

 

[mikewse]

Ah yes, the scan did mention some repairing in its console output.
Thanks for your endurance. Just let me know if you want more information from the system