Mum not found in the KB cab

Page 6 of 6 FirstFirst ... 456

  1. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #51

    You're running with Window Mail installed, right?
    Code:
     Line 7051: 2013-05-04 00:45:02, Info                  CSI    00000310 [SR] Repairing 1 components
     Line 7052: 2013-05-04 00:45:02, Info                  CSI    00000311 [SR] Beginning Verify and Repair transaction
     Line 7055: 2013-05-04 00:45:02, Info                  CSI    00000313 [SR] Cannot repair member file [l:16{8}]"msoe.dll" of Microsoft-Windows-Mail-Core-DLL, 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 7058: 2013-05-04 00:45:02, Info                  CSI    00000315 [SR] Cannot repair member file [l:16{8}]"msoe.dll" of Microsoft-Windows-Mail-Core-DLL, 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 7059: 2013-05-04 00:45:02, Info                  CSI    00000316 [SR] This component was referenced by [l:242{121}]"Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.Microsoft-Windows-Client-Features-Update"
     Line 7064: 2013-05-04 00:45:02, Info                  CSI    00000319 [SR] Could not reproject corrupted file [ml:520{260},l:66{33}]"\??\C:\Program Files\Windows Mail"\[l:16{8}]"msoe.dll"; source file in store is also corrupted
     Line 7069: 2013-05-04 00:45:02, Info                  CSI    0000031b [SR] Repair complete
    .... in which case that error would be expected :)

    However - outside the SFC report, these errors appear....
    Code:
    2013-05-04 00:05:23, Info                  CSI    00000008 CSI Store 4236720 (0x000000000040a5b0) initialized
    2013-05-04 00:05:23, Info                  CBS    Session: 30296088_77177967 initialized by client DISM Package Manager Provider.
    2013-05-04 00:05:24, Info                  CBS    Warning: Unrecognized packageExtended attribute.
    2013-05-04 00:05:24, Info                  CBS    Expecting attribute name [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
    2013-05-04 00:05:24, Info                  CBS    Failed to get next element [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
    2013-05-04 00:05:24, Info                  CBS    Warning: Unrecognized packageExtended attribute.
    2013-05-04 00:05:24, Info                  CBS    Expecting attribute name [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
    2013-05-04 00:05:24, Info                  CBS    Failed to get next element [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
    2013-05-04 00:05:24, Info                  CBS    Warning: Unrecognized packageExtended attribute.
    2013-05-04 00:05:24, Info                  CBS    Expecting attribute name [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
    2013-05-04 00:05:24, Info                  CBS    Failed to get next element [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
    2013-05-04 00:05:24, Info                  CBS    Warning: Unrecognized packageExtended attribute.
    2013-05-04 00:05:24, Info                  CBS    Expecting attribute name [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
    2013-05-04 00:05:24, Info                  CBS    Failed to get next element [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
    2013-05-04 00:05:24, Info                  CBS    Warning: Unrecognized packageExtended attribute.
    2013-05-04 00:05:24, Info                  CBS    Warning: Unrecognized packageExtended attribute.
    2013-05-04 00:05:24, Info                  CBS    Expecting attribute name [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
    2013-05-04 00:05:24, Info                  CBS    Failed to get next element [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
    2013-05-04 00:05:24, Info                  CBS    Warning: Unrecognized packageExtended attribute.
    2013-05-04 00:05:24, Info                  CBS    Expecting attribute name [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
    2013-05-04 00:05:24, Info                  CBS    Failed to get next element [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
    2013-05-04 00:05:24, Info                  CBS    Warning: Unrecognized packageExtended attribute.
    2013-05-04 00:05:24, Info                  CBS    Expecting attribute name [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
    2013-05-04 00:05:24, Info                  CBS    Failed to get next element [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
    2013-05-04 00:05:24, Info                  CBS    Warning: Unrecognized packageExtended attribute.
    2013-05-04 00:05:24, Info                  CBS    Expecting attribute name [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
    2013-05-04 00:05:24, Info                  CBS    Failed to get next element [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
    2013-05-04 00:05:24, Info                  CBS    Warning: Unrecognized packageExtended attribute.
    ...which I don't remember seeing before?

    Perhaps another CheckSUR run is called for - it may be able to point us in the right direction as to what the problem is.
    Please also post a copy of the C:\Windows\windowsupdate.log file - it may help.
      My Computer


  2. Posts : 25
    Windows 7 Enterprise x64
    Thread Starter
       #52

    Hi Noel,

    Yes, right, Windows Mail is running so I guess that's why it couldn't replace it.

    Executed CheckSUR, here is the CBS.log:

    =================================
    Checking System Update Readiness.
    Binary Version 6.1.7601.21645
    Package Version 18.0
    2013-05-06 18:25

    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

    Summary:
    Seconds executed: 482
    Found 2 errors
    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

    and also the windows update log..

    Thanks!
      My Computer


  3. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #53

    CheckSUR is normal for a system with IE10 installed - the 'errors' aren't 'fixable'. MS is said to be working on a solution to the flags.


    I can't find any entries in the Windowsudate log that correspond to the ones I posted above - maybe they are from something else.

    The entries in the log that I think are relevant are these....
    Code:
    2013-05-04 01:29:14:770 4440 17dc Handler CBS package identity: Package_for_KB2790113~31bf3856ad364e35~amd64~~6.1.1.1
    2013-05-04 01:29:14:770 4440 17dc Handler Installing express with source=C:\Windows\SoftwareDistribution\Download\20a0241289deea96b9f0b7d45706bc13, workingdir=C:\Windows\SoftwareDistribution\Download\20a0241289deea96b9f0b7d45706bc13
    2013-05-04 01:29:25:162 4440 eec Handler FATAL: CBS called Error with 0x8007371b, 
    2013-05-04 01:29:25:162 1564 c38 AU >>##  RESUMED  ## AU: Installing update [UpdateId = {F92C8766-DA08-4E0D-841D-1F36D3270CD3}]
    2013-05-04 01:29:25:162 4440 17dc Handler FATAL: Completed install of CBS update with type=0, requiresReboot=0, installerError=1, hr=0x8007371b
    2013-05-04 01:29:25:162 1564 c38 AU   # WARNING: Install failed, error = 0x8007371B / 0x8007371B
    Unfortunately, that's more recent than any data from the CBS.log you posted - can you please post a new CBS.log - and check that it contains the appropriate times?? (if not, post the persist.cab file for that period)
      My Computer


  4. Posts : 25
    Windows 7 Enterprise x64
    Thread Starter
       #54

    Would this persistent CBS.log help?
      My Computer


  5. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #55

    Nope - that's the CheckSUR history.
    Lets grab the whole folder....

    Copy the C:\Windows\Logs\CBS folder to your desktop
    Compress it
    attach the compressed file to your response - you can delete both it, and the desktop copy afterwards.
      My Computer


 
Page 6 of 6 FirstFirst ... 456

  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 01:35.
Find Us