Windows 10: "Public CBS Session Leak Detected" in CBS Logs- What Does it Mean?

Discus and support "Public CBS Session Leak Detected" in CBS Logs- What Does it Mean? in Windows 10 Software and Apps to solve the problem; combing through CBS logs to find another instance of some other event, there's 2 errors back to back at the same time, that say "Public CBS Session... Discussion in 'Windows 10 Software and Apps' started by JamesBacon620, Sep 9, 2023.

  1. JAMESBACON620
    JamesBacon620 Win User

    "Public CBS Session Leak Detected" in CBS Logs- What Does it Mean?


    combing through CBS logs to find another instance of some other event, there's 2 errors back to back at the same time, that say "Public CBS Session Leak Detected", then it lists the Session ID and lists clients FodHelper and SystemSettings attached belowa bit later, Trusted Installer started doing its usual shutdown process, and it said "Session Leaks appear to be benign, continuing shutdown process"; right below that however, the 2 errors appeared again, displaying the exact same things described, and also shown below. a few logs below that, it also said "Mark Session as Corrupt"this was

    :)
     
    JamesBacon620, Sep 9, 2023
    #1
  2. SALTGRASS
    Saltgrass Win User

    Anyone know what "Forcing GE" means in the CBS Log?

    I checked my CBS log today and it seems every day I am getting hundreds of the below type of entries. It seems to be for all versions of 17763.1 and for packages on that version. For all I know, this may have been going on since the 17763 public build
    release... and seems to cover my Win 10 Pro version and, as you can see, others. This is a very small sample of what I see in the logs.

    Thanks for reading.

    Info CBS Appl:Forcing GE on revision on parent:Microsoft-Windows-ServerSolutionEdition~31bf3856ad364e35~amd64~~10.0.17763.1

    Info CBS Appl:Forcing GE on revision on parent:Microsoft-Windows-ServerStandardACorEdition~31bf3856ad364e35~amd64~~10.0.17763.1

    Info CBS Appl:Forcing GE on revision on parent:Microsoft-Windows-ServerStandardCorEdition~31bf3856ad364e35~amd64~~10.0.17763.1

    Info CBS Appl:Forcing GE on revision on parent:Microsoft-Windows-ServerStandardEdition~31bf3856ad364e35~amd64~~10.0.17763.1

    Info CBS Appl:Forcing GE on revision on parent:Microsoft-Windows-ServerStandardEvalCorEdition~31bf3856ad364e35~amd64~~10.0.17763.1

    Info CBS Appl:Forcing GE on revision on parent:Microsoft-Windows-ServerStandardEvalEdition~31bf3856ad364e35~amd64~~10.0.17763.1

    Info CBS Appl:Forcing GE on revision on parent:Microsoft-Windows-ServerStandardNanoEdition~31bf3856ad364e35~amd64~~10.0.17763.1
     
    Saltgrass, Sep 9, 2023
    #2
  3. GREG CARMACK - WINDOWS MVP 2010-2020
    Greg Carmack - Windows MVP 2010-2020 Win User
    CBS Persist File

    Hi Esther. I'm Greg, 10 years awarded Windows MVP, here to help you.

    Here's how to deal with CBS persist files:

    CBS Persist: 5 Important Things and Huge Log file - Tools Pond

    https://amartakarya.co.id/news-windows-logs-cbs...

    https://community.spiceworks.com/topic/450305-c...

    Feel free to ask back any questions. Based on the results you post back I may have other suggestions if necessary.

    ______________________________________________

    Standard Disclaimer: There are links to non-Microsoft websites. The pages appear to be providing accurate, safe information. Watch out for ads on the sites that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the sites before you decide to download and install it.
     
    Greg Carmack - Windows MVP 2010-2020, Sep 9, 2023
    #3
  4. BRENSMITH9911
    brensmith9911 Win User

    "Public CBS Session Leak Detected" in CBS Logs- What Does it Mean?

    My CBS log.,

    I will just post the lot, some duplicate ownership stuff in it, my PC is working atm but has problems occasionally freexes at shut down then problems rebooting requiring a restore, the last restore report problem but the PC is running OK at the momenet,
    outwardly at least no probs for 2 -3 days.

    I had to cut bits out as it was too big to post :O)

    Any comments?

    2017-01-14 17:39:54, Info CBS TI: --- Initializing Trusted Installer ---

    2017-01-14 17:39:54, Info CBS TI: Last boot time: 2017-01-14 11:10:32.484

    2017-01-14 17:39:54, Info CBS Starting TrustedInstaller initialization.

    2017-01-14 17:39:54, Info CBS Ending TrustedInstaller initialization.

    2017-01-14 17:39:54, Info CBS Starting the TrustedInstaller main loop.

    2017-01-14 17:39:54, Info CBS TrustedInstaller service starts successfully.

    2017-01-14 17:39:54, Info CBS No startup processing required, TrustedInstaller service was not set as autostart

    2017-01-14 17:39:54, Info CBS Startup processing thread terminated normally

    2017-01-14 17:39:54, Info CBS TI: Startup Processing completes, release startup processing lock.

    2017-01-14 17:39:54, Info CBS Starting TiWorker initialization.

    2017-01-14 17:39:54, Info CBS Ending TiWorker initialization.

    2017-01-14 17:39:54, Info CBS Starting the TiWorker main loop.

    2017-01-14 17:39:54, Info CBS TiWorker starts successfully.

    2017-01-14 17:39:54, Info CBS Universal Time is: 2017-01-14 17:39:54.955

    2017-01-14 17:39:54, Info CBS Loaded Servicing Stack v10.0.14393.82 with Core: C:\WINDOWS\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.14393.82_none_5be7b69702339d1d\cbscore.dll

    2017-01-14 17:39:54, Info CSI 00000001@2017/1/14:17:39:54.958 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7ffa25096c49 @0x7ffa254655bb @0x7ffa25466372 @0x7ff64b612d9d @0x7ff64b6135e0 @0x7ffa6aff7de3)

    2017-01-14 17:39:54, Info CBS NonStart: Set pending store consistency check.

    2017-01-14 17:39:54, Info CBS Session: 30568077_933023451 initialized by client WindowsUpdateAgent, external staging directory: (null), external registry directory: (null

    2017-01-14 17:39:54, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]

    2017-01-14 17:39:54, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805]

    2017-01-14 17:39:54, Info CBS Session: 30568077_933054501 initialized by client WindowsUpdateAgent, external staging directory: (null), external registry directory: (null

    2017-01-14 17:39:54, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]

    2017-01-14 17:39:54, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805]

    2017-01-14 17:39:56, Info CBS WU creates the package, AppID"Public CBS Session Leak Detected" in CBS Logs- What Does it Mean? :Device Driver Retrieval Client, UpdateID:{92EC2FD0-E6D7-4983-9685-02789AFB5C86}, revision: 201

    2017-01-14 17:39:56, Info CBS Read out cached applicability from TiLight for package: Microsoft-Windows-LanguageFeatures-Basic-zh-cn-Package~31bf3856ad364e35~amd64~~10.0.14393.0, ApplicableState: 0, CurrentState:0

    2017-01-14 17:39:56, Info CBS WU creates the package, AppID"Public CBS Session Leak Detected" in CBS Logs- What Does it Mean? :Device Driver Retrieval Client, UpdateID:{6B1BDF42-539B-4C6F-AD6C-727D06B404E1}, revision: 201

    2017-01-14 17:39:56, Info CBS Read out cached applicability from TiLight for package: Microsoft-.0, arch Host= amd64 Guest= x86, culture [l:5]'sv-se', nonSxS, pkt {l:8 b:31bf3856ad364e35}

    2017-01-14 18:13:45, Info CSI 0000476b@2017/1/14:18:13:45.605 Primitive installers committed for repair

    2017-01-14 18:13:45, Info CSI 0000476c@2017/1/14:18:13:45.629 Primitive installers committed for repair

    2017-01-14 18:13:45, Info CSI 0000476d Error - Overlap: Duplicate ownership for directory \??\C:\WINDOWS\SysWOW64\de-DE in component Microsoft-Windows-LSA-MSPrivs.Resources, version 10.0.14393.0, arch Host= amd64 Guest= x86, culture [l:5]'de-de',
    nonSxS, pkt {l:8 b:31bf3856ad364e35}

    repair

    2017-01-14 18:18:50, Info CSI 00005a9e [SR] Verify complete

    2017-01-14 18:18:50, Info CSI 00005a9f [SR] Verifying 71 components

    2017-01-14 18:18:50, Info CSI 00005aa0 [SR] Beginning Verify and Repair transaction

    2017-01-14 18:18:52, Info CSI 00005aa1@2017/1/14:18:18:52.731 Primitive installers committed for repair

    2017-01-14 18:18:52, Info CSI 00005aa2@2017/1/14:18:18:52.754 Primitive installers committed for repair

    mmitted for repair

    2017-01-14 18:18:54, Info CSI 00005ae7@2017/1/14:18:18:54.438 Primitive installers committed for repair

    2017-01-14 18:18:54, Info CSI 00005ae8 [SR] Verify complete

    2017-01-14 18:18:54, Info CSI 00005ae9 [SR] Repairing 1 components

    2017-01-14 18:18:54, Info CSI 00005aea [SR] Beginning Verify and Repair transaction

    2017-01-14 18:18:54, Info CSI 00005aeb Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_10.0.14393.0_none_46c76e6076b59fe9\MSDTC.LOG do not match actual file [l:9]'MSDTC.LOG' :

    Found: {l:32 HIZCUIacyB5KV4jprVput1klCJsx2WL4E+VaGV3fJpo=} Expected: {l:32 Q4htnI+yK+Jo0DJugTfqjq40IHkXFkIWyyAaDjFGEvo=}

    2017-01-14 18:18:54, Info CSI 00005aec [SR] Cannot repair member file [l:9]'MSDTC.LOG' of Microsoft-Windows-COM-DTC-Runtime, version 10.0.14393.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2017-01-14 18:18:54, Info CSI 00005aed@2017/1/14:18:18:54.553 Primitive installers committed for repair

    2017-01-14 18:18:54, Info CSI 00005aee Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_10.0.14393.0_none_46c76e6076b59fe9\MSDTC.LOG do not match actual file [l:9]'MSDTC.LOG' :

    Found: {l:32 HIZCUIacyB5KV4jprVput1klCJsx2WL4E+VaGV3fJpo=} Expected: {l:32 Q4htnI+yK+Jo0DJugTfqjq40IHkXFkIWyyAaDjFGEvo=}

    2017-01-14 18:18:54, Info CSI 00005aef [SR] Cannot repair member file [l:9]'MSDTC.LOG' of Microsoft-Windows-COM-DTC-Runtime, version 10.0.14393.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2017-01-14 18:18:54, Info CSI 00005af0 [SR] This component was referenced by [l:161]'Microsoft-Windows-Client-Features-Package-AutoMerged-com~31bf3856ad364e35~amd64~~10.0.14393.0.Microsoft-Windows-Client-Features-Package-AutoMerged-com-Deployment'

    2017-01-14 18:18:54, Info CSI 00005af1 [SR] This component was referenced by [l:106]'Microsoft-Windows-ComDTC-com-Package~31bf3856ad364e35~amd64~~10.0.14393.0.f1ef22942af5b956516a3cd533741660'

    2017-01-14 18:18:54, Info CSI 00005af2 [DIRSD OWNER WARNING] Directory [l:29 ml:30]'\??\C:\WINDOWS\System32\Msdtc' is not owned but specifies SDDL in component Microsoft-Windows-COM-DTC-Runtime, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}

    2017-01-14 18:18:54, Info CSI 00005af3@2017/1/14:18:18:54.678 CSIPERF - FileMapsCreated 103ms

    2017-01-14 18:18:54, Info CSI 00005af4 CSIPERF - FilePI Commit 109ms

    2017-01-14 18:18:54, Info CSI 00005af5@2017/1/14:18:18:54.709 Primitive installers committed for repair

    2017-01-14 18:18:54, Info CSI 00005af6 [SR] Repair complete

    2017-01-14 18:18:54, Info CSI 00005af7 [SR] Committing transaction

    2017-01-14 18:18:54, Info CSI 00005af8 Creating NT transaction (seq 1), objectname '(null)'

    2017-01-14 18:18:54, Info CSI 00005af9 Created NT transaction (seq 1) result 0x00000000, handle @0x9e4

    2017-01-14 18:18:54, Info CSI 00005afa@2017/1/14:18:18:54.797 Beginning NT transaction commit...

    2017-01-14 18:18:54, Info CSI 00005afb@2017/1/14:18:18:54.911 CSI perf trace:

    CSIPERF:TXCOMMIT;154774

    2017-01-14 18:18:54, Info CSI 00005afc [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired

    2017-01-14 18:21:01, Info CBS Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP

    2017-01-14 18:21:01, Info CBS TiWorker signaled for shutdown, going to exit.

    2017-01-14 18:21:01, Info CBS CbsCoreFinalize: ExecutionEngineFinalize

    2017-01-14 18:21:01, Info CBS Ending the TiWorker main loop.

    2017-01-14 18:21:01, Info CBS Starting TiWorker finalization.

    2017-01-14 18:21:01, Info CBS CbsCoreFinalize: ManifestCacheFinalize

    201 Exec: Session processing started. Client: Manual, Session(DISM Package Manager Provider Store Corruption Detect/Repair): 30568088_70078704

    2017-01-14 18:57:13, Info CBS Reboot mark set

    2017-01-14 18:57:13, Info CBS Winlogon: Registering for CreateSession notifications

    2017-01-14 18:57:13, Info CBS Winlogon: Loading SysNotify DLL

    2017-01-14 18:57:13, Info CBS Winlogon: Starting notify server

    2017-01-14 18:57:13, Info CBS FLOW: Entering stage: CheckCbs

    2017-01-14 18:59:25, Info CBS Repr: CBS Store check completes

    2017-01-14 18:59:26, Info CSI 00000002 IAdvancedInstallerAwareStore_ResolvePendingTransactions (call 1) (flags = 00000004, progress = NULL, phase = 0, pdwDisposition = @0xa577f7f820

    2017-01-14 18:59:26, Info CSI 00000003 Poqexec successfully registered in [l:12 ml:13]'SetupExecute'

    2017-01-14 18:59:26, Info CSI 00000004 CSI Store 2522724894448 initialized

    2017-01-14 18:59:26, Info CSI 00000005 StoreCorruptionRepair transaction begun. WcpVersion: [l:39]'10.0.14393.82 (rs1_release.160805-1735)'.

    2017-01-14 18:59:26, Info CSI 00000006@2017/1/14:18:59:26.190 Starting corruption detection (InnerFlags=5)

    2017-01-14 18:59:26, Info CBS FLOW: Entering stage: CheckCsi

    2017-01-14 19:10:23, Info CSI 00000007 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_10.0.14393.0_none_46c76e6076b59fe9\MSDTC.LOG do not match actual file [l:9]'MSDTC.LOG' :

    Found: {l:32 HIZCUIacyB5KV4jprVput1klCJsx2WL4E+VaGV3fJpo=} Expected: {l:32 Q4htnI+yK+Jo0DJugTfqjq40IHkXFkIWyyAaDjFGEvo=}

    2017-01-14 19:20:13, Warning CBS Current tick count lower than last tick count. [HRESULT = 0x8007000d - ERROR_INVALID_DATA]

    2017-01-14 19:20:13, Info CSI 00000008@2017/1/14:19:20:13.966 Corruption detection complete. numCorruptions = 1, Disp = 1.

    2017-01-14 19:20:14, Info CBS Repr: CSI meta data corruption found, will commit repair transaction if repair is asked.

    2017-01-14 19:20:14, Info CSI 00000009@2017/1/14:19:20:14.079 CSI Transaction @0x24b60ee6fd0 initialized for deployment engine {d16d444c-56d8-11d5-882d-0080c847b195} with flags 00000000 and client id 'TI5.30568088_70078704:1/'

    2017-01-14 19:20:14, Info CSI 0000000a@2017/1/14:19:20:14.128 CSI Transaction @0x24b60ee6fd0 destroyed

    2017-01-14 19:20:14, Info CBS Repr: CSI Store check completes

    2017-01-14 19:20:14, Info CBS ASSERT: Assertion failed in onecore\base\cbs\util\inc\CbsArray.h(535)

    Index out of bound.

    2017-01-14 19:20:16, Info CBS Failed to FinalizeEx using worker session [HRESULT = 0x800706be]
     
    brensmith9911, Sep 9, 2023
    #4
Thema:

"Public CBS Session Leak Detected" in CBS Logs- What Does it Mean?

Loading...

  1. "Public CBS Session Leak Detected" in CBS Logs- What Does it Mean? - Similar Threads - Public CBS Session

  2. CBS LOG

    in Windows 10 Gaming
    CBS LOG: windows resource protection found corrupt files but was unable to fix some of them. how to fix this? https://answers.microsoft.com/en-us/windows/forum/all/cbs-log/f84b7065-caf7-4c54-93f4-9badf1ae5e62

  3. CBS LOG

    in Windows 10 Software and Apps
    CBS LOG: windows resource protection found corrupt files but was unable to fix some of them. how to fix this? https://answers.microsoft.com/en-us/windows/forum/all/cbs-log/f84b7065-caf7-4c54-93f4-9badf1ae5e62

  4. "Package Does Not Have OobeApplicability" in CBS Log, What Does it Mean?

    in Windows 10 Gaming
    "Package Does Not Have OobeApplicability" in CBS Log, What Does it Mean?: I checked my CBS logs and saw something that has never happened before; it's normal behaviour for CBS to log a series of "detect package" messages, that's nothing newhowever, it would appear that since 10:57am on the 13th of December, a new message appears under every...

  5. "Package Does Not Have OobeApplicability" in CBS Log, What Does it Mean?

    in Windows 10 Software and Apps
    "Package Does Not Have OobeApplicability" in CBS Log, What Does it Mean?: I checked my CBS logs and saw something that has never happened before; it's normal behaviour for CBS to log a series of "detect package" messages, that's nothing newhowever, it would appear that since 10:57am on the 13th of December, a new message appears under every...

  6. "Package Does Not Have OobeApplicability" in CBS Log, What Does it Mean?

    in Windows 10 Network and Sharing
    "Package Does Not Have OobeApplicability" in CBS Log, What Does it Mean?: I checked my CBS logs and saw something that has never happened before; it's normal behaviour for CBS to log a series of "detect package" messages, that's nothing newhowever, it would appear that since 10:57am on the 13th of December, a new message appears under every...

  7. "Public CBS Session Leak Detected" in CBS Logs- What Does it Mean?

    in Windows 10 Gaming
    "Public CBS Session Leak Detected" in CBS Logs- What Does it Mean?: combing through CBS logs to find another instance of some other event, there's 2 errors back to back at the same time, that say "Public CBS Session Leak Detected", then it lists the Session ID and lists clients FodHelper and SystemSettings attached belowa bit later, Trusted...

  8. "Public CBS Session Leak Detected" in CBS Logs- What Does it Mean?

    in Windows 10 Network and Sharing
    "Public CBS Session Leak Detected" in CBS Logs- What Does it Mean?: combing through CBS logs to find another instance of some other event, there's 2 errors back to back at the same time, that say "Public CBS Session Leak Detected", then it lists the Session ID and says this:this was on the 4th of September; since then, even though I wasn't...

  9. CBS log error

    in Windows 10 Gaming
    CBS log error: HiWhere do i find and how do i read itThank youTIMMY 2 TOES https://answers.microsoft.com/en-us/windows/forum/all/cbs-log-error/dbff8182-75b3-452a-814d-89de21bbcb05

  10. Anyone know what "Forcing GE" means in the CBS Log?

    in Windows 10 BSOD Crashes and Debugging
    Anyone know what "Forcing GE" means in the CBS Log?: I checked my CBS log today and it seems every day I am getting hundreds of the below type of entries. It seems to be for all versions of 17763.1 and for packages on that version. For all I know, this may have been going on since the 17763 public build release... and seems...