CheckSUR error, expected file name doesn't match actual


  1. Posts : 4
    Windows 7 Professional x64
       #1

    CheckSUR error, expected file name doesn't match actual


    Hi,
    New here, but have been solving my Windows 7 problems by landing here from google for some time. Anyway, having a problem using windows update. I've been troubleshooting for awhile so I may be fuzzy on the chain of events... got a code 643 in windows update, ran a .Net Framework Windows Help Utility, got a 0x80070490 error and problem with BITS, reset Windows Update Components, ran SUR, got an 0x80240009, retried the install after a reboot, got a prompt that SUR wasn't able to install KB947821, looked at CheckSUR.log and saw the 2 expected file name errors. Also another 16 errors in the persist log. My CBS log file is 35mb and the website is prompting me about an incorrect security token when I try and upload the 5 split zip files at 5mb each. So I uploaded it to my dropbox. Advice? Thanks for reading.
    https://www.dropbox.com/s/nkflm9aix0oqhhm/CBS.zip
    Last edited by mattross; 25 Apr 2013 at 13:42.
      My Computer


  2. Posts : 2,663
    Windows 8.1 Pro x64
       #2

    Hello mattross and welcome to the forums

    Your CheckSUR log is incorrectly reporting two files as having the wrong name which I can assure you is nothing to worry about, it is a bug in the SURT that is known to Microsoft.

    You do have a few missing deployments keys though, which I will have to add.

    Code:
    =================================
    Checking System Update Readiness.
    Binary Version 6.1.7601.21645
    Package Version 18.0
    2013-04-25 12:55
    
    Checking Windows Servicing Packages
    
    Checking Package Manifests and Catalogs
    (f)    CBS MUM Corrupt    0x00000000    servicing\Packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum        Expected file name Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~neutral~~10.2.9200.16437.mum does not match the actual file name
    (f)    CBS MUM Corrupt    0x00000000    servicing\Packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum        Expected file name Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~neutral~~10.2.9200.16437.mum does not match the actual file name
    
    Checking Package Watchlist
    
    Checking Component Watchlist
    
    Checking Packages
    
    Checking Component Store
    (f)    CSI Missing Deployment Key    0x00000000    microsoft.vc90.openmp_1fc8b3b9a1e18e3b_9.0.30729.4148_390a91d20a21a864    HKLM\Components\CanonicalData\Deployments    
    (f)    CSI Missing Deployment Key    0x00000000    microsoft.vc80.openmp_1fc8b3b9a1e18e3b_8.0.50727.4053_3b0e32bdc9afe437    HKLM\Components\CanonicalData\Deployments    
    (f)    CSI Missing Deployment Key    0x00000000    policy.8.0...vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.4053_0605300f695657e9    HKLM\Components\CanonicalData\Deployments    
    (f)    CSI Missing Deployment Key    0x00000000    policy.8.0...vc80.openmp_1fc8b3b9a1e18e3b_8.0.50727.4053_6b86c0e9b0196766    HKLM\Components\CanonicalData\Deployments    
    (f)    CSI Missing Deployment Key    0x00000000    policy.8.0...ft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.4053_024211bfff9b1183    HKLM\Components\CanonicalData\Deployments    
    (f)    CSI Missing Deployment Key    0x00000000    policy.8.0...vc80.openmp_1fc8b3b9a1e18e3b_8.0.50727.762_abac38a907ee8801    HKLM\Components\CanonicalData\Deployments    
    (f)    CSI Missing Deployment Key    0x00000000    policy.8.0...vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.4053_4db266e67dd280ef    HKLM\Components\CanonicalData\Deployments    
    (f)    CSI Missing Deployment Key    0x00000000    microsoft.vc80.openmp_1fc8b3b9a1e18e3b_8.0.50727.762_7b33aa7d218504d2    HKLM\Components\CanonicalData\Deployments    
    (f)    CSI Missing Deployment Key    0x00000000    policy.8.0...vc80.openmp_1fc8b3b9a1e18e3b_8.0.50727.4053_23d98a129b9d3e60    HKLM\Components\CanonicalData\Deployments    
    (f)    CSI Missing Deployment Key    0x00000000    microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.4053_8444db7d32915e4c    HKLM\Components\CanonicalData\Deployments    
    (f)    CSI Missing Deployment Key    0x00000000    policy.9.0...vc90.openmp_1fc8b3b9a1e18e3b_9.0.30729.4148_c6e3d20ca2b1ebce    HKLM\Components\CanonicalData\Deployments    
    (f)    CSI Missing Deployment Key    0x00000000    microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.4053_bc1d1e5b0be08790    HKLM\Components\CanonicalData\Deployments    
    (f)    CSI Missing Deployment Key    0x00000000    4e7ebb2d196..01d3f732515_31bf3856ad364e35_6.1.7601.17855_df002818becd0c01    HKLM\Components\CanonicalData\Deployments    
    (f)    CSI Missing Deployment Key    0x00000000    a5cf95a6bfd..712de143fe3_31bf3856ad364e35_6.1.7601.22009_e4cfc5bc0025f68c    HKLM\Components\CanonicalData\Deployments    
    (f)    CSI Missing Deployment Key    0x00000000    microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.4053_03ca5532205cb096    HKLM\Components\CanonicalData\Deployments    
    (f)    CSI Missing Deployment Key    0x00000000    microsoft.vc80.openmp_1fc8b3b9a1e18e3b_8.0.50727.4053_f360fbe6b533bb31    HKLM\Components\CanonicalData\Deployments    
    
    Summary:
    Seconds executed: 4429
     Found 18 errors
      CSI Missing Deployment Key Total count: 16
      CBS MUM Corrupt Total count: 2
    
    Unavailable repair files:
        servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum
        servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum
        servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.cat
        servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.cat
    Can you zip up the following file and upload it to your Dropbox please:

    C:\Windows\system32\config\COMPONENTS (it has no file extension)

    Your CBS log is overflowing with manifest errors which I will investigate and get back to you as soon as possible.

    Code:
    2013-04-25 14:18:58, Info                  CBS    Appl: Partial install Status testing, package: Package_for_KB976933~31bf3856ad364e35~amd64~~6.1.7601.17514, partially installed (true/false), 0
    2013-04-25 14:18:58, Info                  CBS    Failed to find package from aggreated XML string, package: Package_for_KB976933~31bf3856ad364e35~amd64~fr-FR~6.1.7601.17514 [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
    2013-04-25 14:18:58, Info                  CBS    Failed to find package from deployment update [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
    2013-04-25 14:18:58, Error                 CBS    Failed to check whether package is partially installed, package: Windows7SP1-KB976933~31bf3856ad364e35~amd64~~6.1.1.17514 [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
    2013-04-25 14:18:58, Info                  CBS    Failed to evaluate external applicability for package update: 976933-0_neutral_PACKAGE [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
    2013-04-25 14:18:58, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB976932~31bf3856ad364e35~amd64~~6.1.1.17514, Update: 976933-0_neutral_PACKAGE [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
    Tom
      My Computer


  3. Posts : 4
    Windows 7 Professional x64
    Thread Starter
       #3

    Here you go: https://www.dropbox.com/s/yjqne6cqdurnsae/components
    Thanks for the speedy response!
      My Computer


  4. Posts : 2,663
    Windows 8.1 Pro x64
       #4

    Hi mattross,

    Sorry for the delay, it's been a busy few days. I have prepared a fix for you:

    Command Prompt

    Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.


    1. Click on the Start button and in the search box, type Command Prompt
    2. When you see Command Prompt on the list, right-click on it and select Run as administrator
    3. When command prompt opens, copy and paste the following commands into it, press enter after each

      reg load HKLM\COMPONENTS %windir%\system32\config\components




    Then download the attached file, Fix.reg, and double click on this to merge it with your registry. Reboot then run the System Update Readiness Tool again and post the CheckSUR log please:

    C:\Windows\Logs\CBS\CBS.log

    Tom
      My Computer


  5. Posts : 4
    Windows 7 Professional x64
    Thread Starter
       #5

    Hi Tom,
    Click here for the log or here for the entire folder. The SUR installation was successful.
    Thanks, Matt.
      My Computer


  6. Posts : 2,663
    Windows 8.1 Pro x64
       #6

    Hi Matt,

    The CheckSUR log is showing that all of the problems have been fixed which is great! Can you try updating and let me know how it goes?

    Tom
      My Computer


  7. Posts : 4
    Windows 7 Professional x64
    Thread Starter
       #7

    I installed some Windows updates that did not require a computer restart and that went fine. Thanks for your help.
      My Computer


  8. Posts : 2,663
    Windows 8.1 Pro x64
       #8

    Hi Matt,

    That's great news! Thanks for posting back the results.

    You're most welcome for the help!

    Tom
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 17:21.
Find Us