Scribd Logo
Upload

Welcome to Scribd!

  • 12 views

    Log

    Uploaded by

    Sukran Nirankari
    The document contains log messages from a servicing stack shim. It records the shim checking for and finding the wcp.dll file in two different locations, initializing the wcp.dll component, verifying and repairing 1 component without issues, and reporting the number of files opened by different providers. It also logs two errors where the shim was unable to mark handles for deletion on close due to the directory not being empty or the file not able to be deleted.

    Copyright:

    © All Rights Reserved
    Download as TXT, PDF, TXT or read online from Scribd
    Flag for inappropriate content

    You might also like

    Log

    Uploaded by

    Sukran Nirankari
    12 views1 page
    The document contains log messages from a servicing stack shim. It records the shim checking for and finding the wcp.dll file in two different locations, initializing the wcp.dll component, verifying and repairing 1 component without issues, and reporting the number of files opened by different providers. It also logs two errors where the shim was unable to mark handles for deletion on close due to the directory not being empty or the file not able to be deleted.

    Original Description:

    Original Title

    log

    Copyright

    © © All Rights Reserved

    Available Formats

    TXT, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    The document contains log messages from a servicing stack shim. It records the shim checking for and finding the wcp.dll file in two different locations, initializing the wcp.dll component, verifying and repairing 1 component without issues, and reporting the number of files opened by different providers. It also logs two errors where the shim was unable to mark handles for deletion on close due to the directory not being empty or the file not able to be deleted.

    Copyright:

    © All Rights Reserved
    Download as TXT, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as txt, pdf, or txt
    12 views1 page

    Log

    Uploaded by

    Sukran Nirankari
    The document contains log messages from a servicing stack shim. It records the shim checking for and finding the wcp.dll file in two different locations, initializing the wcp.dll component, verifying and repairing 1 component without issues, and reporting the number of files opened by different providers. It also logs two errors where the shim was unable to mark handles for deletion on close due to the directory not being empty or the file not able to be deleted.

    Copyright:

    © All Rights Reserved
    Download as TXT, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as txt, pdf, or txt
    of 1

    00000001 Shim considered [l:125]'\??

    \d:\windows\Servicing\amd64_microsoft-windows-
    servicingstack_31bf3856ad364e35_10.0.22621.898_none_6b467c06908d3d29\wcp.dll' : got
    STATUS_OBJECT_PATH_NOT_FOUND
    00000002 Shim considered [l:122]'\??\d:\windows\WinSxS\amd64_microsoft-windows-
    servicingstack_31bf3856ad364e35_10.0.22621.898_none_6b467c06908d3d29\wcp.dll' : got
    STATUS_SUCCESS
    00000001@2023/1/20:03:54:50.371 WcpInitialize: wcp.dll version 10.0.22621.898
    (WinBuild.160101.0800)
    00000002 CSI Store 2137017354944 initialized
    00000003 [SR] Verifying 1 components
    00000004 [SR] Beginning Verify and Repair transaction
    00000005 [SR] Verify complete
    00000006 Direct SIL provider: Number of files opened: 22.
    00000007 Direct SIL provider: Number of files opened: 4.
    00000003 Servicing stack shim unable to mark handle 198 ('\Device\Ramdisk{d9b257fc-
    684e-4dcb-ab79-03cfa2f6b750}\Windows\temp\SSS_a8abf0f1822cd90101000000e802d404\
    msdelta.dll') for delete-on-close, error STATUS_CANNOT_DELETE
    00000004 Servicing stack shim unable to mark handle 1e0 ('\Device\Ramdisk{d9b257fc-
    684e-4dcb-ab79-03cfa2f6b750}\Windows\temp\SSS_a8abf0f1822cd90101000000e802d404')
    for delete-on-close, error STATUS_DIRECTORY_NOT_EMPTY

    You might also like