Windows 8 and 8.1 Forums


System File Problem - Possibly MSI - CBS log Included

  1. #1


    Posts : 12
    Windows 8

    System File Problem - Possibly MSI - CBS log Included


    Hi all,

    My laptop is running ok but I have noticed that certain programs have been taking a lot longer than usual to install/update (e.g. iTunes) but they always do. Then the last few days AVG Antivirus has been wanting to auto-update the software (not just the virus definitions) but each time it would freeze during the ''configuring'' step and subsequently cause every other program running to freeze and stop the opening of any other program - although I could still move the cursor so not a complete freeze if that makes sense.

    So today I removed AVG with the removal tool and tried to do a fresh install but now I get a failure message immediately telling me ''MSI Engine: failed to initialize the package''.

    I have no idea how to go about fixing this and ran system file check which said corrupt files were found but it was unable to repair some of them. Here is the log:

    Quote Originally Posted by CBS.log
    2014-08-20 14:24:13, Info CBS TI: --- Initializing Trusted Installer ---
    2014-08-20 14:24:13, Info CBS TI: Last boot time: 2014-08-20 13:56:23.498
    2014-08-20 14:24:13, Info CBS Starting TrustedInstaller initialization.
    2014-08-20 14:24:13, Info CBS Ending TrustedInstaller initialization.
    2014-08-20 14:24:13, Info CBS Starting the TrustedInstaller main loop.
    2014-08-20 14:24:13, Info CBS TrustedInstaller service starts successfully.
    2014-08-20 14:24:13, Info CBS No startup processing required, TrustedInstaller service was not set as autostart
    2014-08-20 14:24:13, Info CBS Startup processing thread terminated normally
    2014-08-20 14:24:13, Info CBS Starting TiWorker initialization.
    2014-08-20 14:24:13, Info CBS Ending TiWorker initialization.
    2014-08-20 14:24:13, Info CBS Starting the TiWorker main loop.
    2014-08-20 14:24:13, Info CBS TiWorker starts successfully.
    2014-08-20 14:24:13, Info CBS Universal Time is: 2014-08-20 13:24:13.676
    2014-08-20 14:24:13, Info CBS Loaded Servicing Stack v6.2.9200.16683 with Core: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.2.9200.16683_none_62280e15510f8e79\cbscore.dll
    2014-08-20 14:24:13, Info CSI 00000001@2014/8/20:13:24:13.688 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7ff8a1e6229 @0x7ff8a4c9806 @0x7ff8a484da4 @0x7f67a01d1df @0x7f67a01d95c @0x7ffac8d2185)
    2014-08-20 14:24:13, Info CSI 00000002@2014/8/20:13:24:13.696 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7ff8a1e6229 @0x7ff8a525f64 @0x7ff8a4e76e1 @0x7ff8a484f17 @0x7f67a01d1df @0x7f67a01d95c)
    2014-08-20 14:24:13, Info CBS SQM: Initializing online with Windows opt-in: False
    2014-08-20 14:24:13, Info CBS SQM: Cleaning up report files older than 10 days.
    2014-08-20 14:24:13, Info CBS SQM: Requesting upload of all unsent reports.
    2014-08-20 14:24:13, Info CBS SQM: Failed to start upload with file pattern: C:\Windows\servicing\sqm\*_std.sqm, flags: 0x2 [HRESULT = 0x80004005 - E_FAIL]
    2014-08-20 14:24:13, Info CBS SQM: Failed to start standard sample upload. [HRESULT = 0x80004005 - E_FAIL]
    2014-08-20 14:24:13, Info CBS SQM: Queued 0 file(s) for upload with pattern: C:\Windows\servicing\sqm\*_all.sqm, flags: 0x6
    2014-08-20 14:24:13, Info CBS SQM: Warning: Failed to upload all unsent reports. [HRESULT = 0x80004005 - E_FAIL]
    2014-08-20 14:24:13, Info CBS NonStart: Set pending store consistency check.
    2014-08-20 14:24:13, Info CBS Session: 30391418_148605113 initialized by client WindowsUpdateAgent.
    2014-08-20 14:24:27, Info CBS Session: 30391418_287364006 initialized by client WindowsUpdateAgent.
    I have no idea how to read one of these or even if it effectively evaluates the status of the installer so any help with this would be much appreciated.

    PS Apologies if this is in the wrong sub-forum.

      My System SpecsSystem Spec

  2. #2


    Posts : 12
    Windows 8


    Ok so since then I restored windows to yesterday evening to see how things would be, AVG was a bit wonky so first tried to repair the install (using the regular install file downloaded from the website) - this led to a BSOD citing ''BAD_POOL-HEADER''. I don't know what that is but anyway I continued by then removing AVG and trying a fresh install and this time it worked fine, no problems.

    I just ran and sfc scan again however and got the same message as before but this time the log file is alarmingly much much longer and has a lot more information in it so I've attached the file instead of copying the text in here.

    Again I'd really appreciate it if someone more knowledgeable could help me diagnose the issue
    System File Problem - Possibly MSI - CBS log Included Attached Files
      My System SpecsSystem Spec

  3. #3


    Posts : 1,121
    Windows 8.1 x64


    The way you check for SFC problems is to use the command below in an Administrative command prompt window. Remember, the log is written in sequence, so it may show several SFC runs, check the date and time. Then look near the end for something related to "Unable to Repair".

    findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"
      My System SpecsSystem Spec

  4. #4


    Posts : 12
    Windows 8


    Quote Originally Posted by Saltgrass View Post
    The way you check for SFC problems is to use the command below in an Administrative command prompt window. Remember, the log is written in sequence, so it may show several SFC runs, check the date and time. Then look near the end for something related to "Unable to Repair".

    findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"
    Thanks for your reply.

    I've quoted below the files that could not be repaired and attached the log.

    Quote Originally Posted by Cbs.log
    ...........
    2014-08-20 19:11:42, Info CSI 000003fe [SR] Verifying 100 (0x0000000000000064) components
    2014-08-20 19:11:42, Info CSI 000003ff [SR] Beginning Verify and Repair transaction
    2014-08-20 19:11:45, Info CSI 00000401 [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.2.9200.16430, 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
    2014-08-20 19:12:00, Info CSI 00000403 [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.2.9200.16430, 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
    2014-08-20 19:12:00, Info CSI 00000404 [SR] This component was referenced by [l:164{82}]"Package_86_for_KB2769165~31bf3856ad364e35~amd64~~6.2.1.0.2769165-12166_neutral_GDR"
    2014-08-20 19:12:00, Info CSI 00000405 [SR] Verify complete
    .............
    .............
    2014-08-20 19:21:57, Info CSI 000006c5 [SR] Verifying 57 (0x0000000000000039) components
    2014-08-20 19:21:57, Info CSI 000006c6 [SR] Beginning Verify and Repair transaction
    2014-08-20 19:22:04, Info CSI 000006c7 [SR] Verify complete
    2014-08-20 19:22:04, Info CSI 000006c8 [SR] Repairing 1 components
    2014-08-20 19:22:04, Info CSI 000006c9 [SR] Beginning Verify and Repair transaction
    2014-08-20 19:22:04, Info CSI 000006cb [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.2.9200.16430, 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
    2014-08-20 19:22:04, Info CSI 000006cd [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.2.9200.16430, 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
    2014-08-20 19:22:04, Info CSI 000006ce [SR] This component was referenced by [l:164{82}]"Package_86_for_KB2769165~31bf3856ad364e35~amd64~~6.2.1.0.2769165-12166_neutral_GDR"
    2014-08-20 19:22:04, Info CSI 000006cf [SR] Repair complete
    2014-08-20 19:22:04, Info CSI 000006d0 [SR] Committing transaction
    2014-08-20 19:22:05, Info CSI 000006d5 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired
    ............
    ............
    2014-08-20 21:06:03, Info CSI 000003fe [SR] Verifying 100 (0x0000000000000064) components
    2014-08-20 21:06:03, Info CSI 000003ff [SR] Beginning Verify and Repair transaction
    2014-08-20 21:06:04, Info CSI 00000401 [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.2.9200.16430, 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
    2014-08-20 21:06:16, Info CSI 00000403 [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.2.9200.16430, 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
    2014-08-20 21:06:16, Info CSI 00000404 [SR] This component was referenced by [l:164{82}]"Package_86_for_KB2769165~31bf3856ad364e35~amd64~~6.2.1.0.2769165-12166_neutral_GDR"
    2014-08-20 21:06:16, Info CSI 00000405 [SR] Verify complete
    ...........
    ...........
    2014-08-20 21:06:03, Info CSI 000003fe [SR] Verifying 100 (0x0000000000000064) components
    2014-08-20 21:06:03, Info CSI 000003ff [SR] Beginning Verify and Repair transaction
    2014-08-20 21:06:04, Info CSI 00000401 [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.2.9200.16430, 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
    2014-08-20 21:06:16, Info CSI 00000403 [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.2.9200.16430, 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
    2014-08-20 21:06:16, Info CSI 00000404 [SR] This component was referenced by [l:164{82}]"Package_86_for_KB2769165~31bf3856ad364e35~amd64~~6.2.1.0.2769165-12166_neutral_GDR"
    2014-08-20 21:06:16, Info CSI 00000405 [SR] Verify complete
    How do I go about fixing these problems and is the damage major?
    System File Problem - Possibly MSI - CBS log Included Attached Files
      My System SpecsSystem Spec

  5. #5


    San Jose - California
    Posts : 2,847
    8.1x64PWMC Ubuntu14.04x64 MintMate17x64


    Try:
    1. Uninstall AVG completely
    2. delete %windir%\Logs\CBS\CBS.log
    3. Admin command prompt then type: dism /Online /Cleanup-Image /RestoreHealth
    4. Next, run: sfc /scannow =====> might need to run multiple times until you get the message: no integrity ....
      My System SpecsSystem Spec

  6. #6

    folder removal


    As with most uninstallers the programme in its own right is removed

    HOWEVER

    The folders still remain in "C" and until these are deleted, manually, MS will treat them as still installed.

    Thats how i got MSE in W7 to run , same for 8, after installing/deleting a 3rd party AV.

    Roy
      My System SpecsSystem Spec

  7. #7


    Posts : 1,121
    Windows 8.1 x64


    The only file showing a problem in SFC is that stupid printer file which causes that error for 80% to 90% of Windows 8 users. Not a problem, but the DSIM command recommended should replace it.
      My System SpecsSystem Spec

System File Problem - Possibly MSI - CBS log Included
Related Threads
I've looked through the forums and found different answer but none so far has worked. I ran the SFC /Scannow many times and got this message "Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log....
So i'm trying to delete this file i have in my downloads folder, which is a normal .avi file. however, this file is really broken, it wont delete. I suspect this file makes my folder not showing thumbnails and acting slow and sometimes wont show anything at all, just a loading bar thing. i...
humongous system file in Performance & Maintenance
I have a 34 gb hidden system file on my C drive. what's up with this? 35614
(Or how to remove Write Protection from Pendrive). Pendrive doesn't have any write protection lock key on it.
Solved Encrypting File System Problem in General Support
I have an external drive which was used with a Vista PC, and which contains some folders encrypted using the Encrypting File System feature. My Vista PC crashed, so I bought a Win 8 PC. This PC doesn't have the Encrypting File System feature, and so will not let me access these files. Is there...
Sorry I can't find the BSOD error.. I tried googling on how to find out what it is yourself but it's not that easy for some reason. I couldn't see what error it was when it happened but what I was doing was watching a show on a program called VLC Media Player in fullscreen. :huh: I got a new...
My CPU cooler, an Antec Khuler H2O 920, is powered by internal USB 2.0. This allows the radiator and fans to be controlled from a program inside Windows (ChillControl). The fans and radiator pump work, but I am unable to get the fans to run any faster than idle (this is important for doing anything...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook