Strange entries in CBS.log


  1. Posts : 6,285
    Windows 10 Pro X64
       #1

    Strange entries in CBS.log


    If I look at the CBS.log file (notepad %windir%\Logs\CBS\CBS.log), I see lots of entries like the following:

    2010-08-08 14:29:24, Info CBS Session: 30095143_2687862877 initialized by client WindowsUpdateAgent.
    2010-08-08 14:29:24, Info CBS Read out cached package applicability for package: Package_for_KB982381~31bf3856ad364e35~amd64~~6.1.1.3, ApplicableState: 112, CurrentState:112
    2010-08-08 14:29:24, Info CBS Session: 30095143_2688174877 initialized by client WindowsUpdateAgent.
    2010-08-08 14:29:24, Info CBS Read out cached package applicability for package: Package_for_KB976662~31bf3856ad364e35~amd64~~6.1.1.0, ApplicableState: 112, CurrentState:112
    2010-08-08 14:29:24, Info CBS Session: 30095143_2688174878 initialized by client WindowsUpdateAgent.
    2010-08-08 14:29:24, Info CBS Mismatch between open element and close element [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
    2010-08-08 14:29:24, Info CBS Failed to get next element [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
    2010-08-08 14:29:24, Info CBS Invalid enum string [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
    2010-08-08 14:29:24, Info CBS unexpected string [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
    2010-08-08 14:29:24, Info CBS Failed to get next package root element [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
    2010-08-08 14:29:24, Info CBS failed to process package [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
    2010-08-08 14:29:24, Info CBS Wrong package format [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
    2010-08-08 14:29:24, Info CBS Invalid xml format [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
    2010-08-08 14:29:24, Info CBS Manifest parsing error at line: 1, context:
    </assembly><assembly xmlns="urn:schemas-microsoft-com:asm.v3" co [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
    2010-08-08 14:29:24, Info CBS Failed to parse the manifest from the buffer. [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
    2010-08-08 14:29:24, Error CBS Failed to parse package manifest from given buffer [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
    2010-08-08 14:29:24, Info CBS Failed to initialize internal package [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
    2010-08-08 14:29:24, Error CBS Failed to create internal package [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
    Does this indicate a problem or is it normal Update stuff?

    Edit: There are 2109 "error" entries in CBS.log. First one on 7/19, continuing periodically to today.
      My Computer


  2. Posts : 17,796
    Windows 10, Home Clean Install
       #2

    This may or may not correct the potential problems, but it will tell you if there is a problem

    SFC /SCANNOW Command - System File Checker
      My Computer


  3. Posts : 6,285
    Windows 10 Pro X64
    Thread Starter
       #3

    I've been putting off running SFC, guess it time. Thanks.
      My Computer


  4. Posts : 17,796
    Windows 10, Home Clean Install
       #4

    It may fix corrupted files, but it will tell you if there are problems.
      My Computer


  5. Posts : 6,285
    Windows 10 Pro X64
    Thread Starter
       #5

    No, no problems:
    Beginning verification phase of system scan.
    Verification 100% complete.

    Windows Resource Protection did not find any integrity violations.
      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 21:21.
Find Us