Surface Pro 9 Inaccessible boot device

Question

Surface Pro 9 Inaccessible boot device

Anonymous

I have a SP9 that is unable to boot after a windows updated. Here is the output of my current troubleshooting. Any help is greatly appreciated.

sfc /scannow: found and repair errors, issue persists

bcdedit

Windows Boot Manager

identifier {bootmgr}

device partition=\Device\HarddiskVolume1

path \EFI\Microsoft\Boot\bootmgfw.efi

description Windows Boot Manager

locale en-us

inherit {globalsettings}

default {default}

resumeobject {5ccdcba4-945d-11ee-9401-96e64303ba36}

displayorder {default}

toolsdisplayorder {memdiag}

timeout 30

Windows Boot Loader

identifier {default}

device partition=C:

path \Windows\system32\winload.efi

description Windows 11

locale en-us

inherit {bootloadersettings}

isolatedcontext Yes

allowedinmemorysettings 0x15000075

osdevice partition=C:

systemroot \Windows

resumeobject {5ccdcba4-945d-11ee-9401-96e64303ba36}

nx OptIn

bootmenupolicy Standard

diskpart > list vol

Volume ### Ltr Label Fs Type Size Status Info

Volume 0 C Local Disk NTFS Partition 949 GB Healthy

Volume 1 SYSTEM FAT32 Partition 260 MB Healthy Hidden

Volume 2 NTFS Partition 643 MB Healthy Hidden

"DISM /Image:C: /Cleanup-Image /RestoreHealth /Source:D:" (D: is a Win11 image created using the image creation tool)

2023-12-06 10:33:15, Info DISM PID=1116 TID=1992 Scratch directory set to 'X:\windows\TEMP'. - CDISMManager::put_ScratchDir

2023-12-06 10:33:15, Info DISM PID=1116 TID=1992 DismCore.dll version: 10.0.22621.1 - CDISMManager::FinalConstruct

2023-12-06 10:33:15, Info DISM Initialized Panther logging at X:\windows\Logs\DISM\dism.log

2023-12-06 10:33:15, Info DISM PID=1116 TID=1992 Successfully loaded the ImageSession at "X:\windows\system32\Dism" - CDISMManager::LoadLocalImageSession

2023-12-06 10:33:15, Info DISM Initialized Panther logging at X:\windows\Logs\DISM\dism.log

2023-12-06 10:33:15, Info DISM DISM Provider Store: PID=1116 TID=1992 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger

2023-12-06 10:33:15, Info DISM Initialized Panther logging at X:\windows\Logs\DISM\dism.log

2023-12-06 10:33:15, Info DISM DISM Manager: PID=1116 TID=1992 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession

2023-12-06 10:33:15, Info DISM DISM.EXE:

2023-12-06 10:33:15, Info DISM DISM.EXE: <----- Starting Dism.exe session ----->

2023-12-06 10:33:15, Info DISM DISM.EXE:

2023-12-06 10:33:15, Info DISM DISM.EXE: Host machine information: OS Version=10.0.22621, Running architecture=amd64, Number of processors=12

2023-12-06 10:33:15, Info DISM DISM.EXE: Dism.exe version: 10.0.22621.1

2023-12-06 10:33:15, Info DISM DISM.EXE: Executing command line: DISM /Image:C: /Cleanup-Image /RestoreHealth /Source:D:

2023-12-06 10:33:15, Info DISM DISM FFU Provider: PID=1116 TID=1992 [C:] is not recognized by the DISM FFU provider. - CFfuImage::Initialize

2023-12-06 10:33:15, Info DISM DISM Imaging Provider: PID=1116 TID=1992 The provider FfuManager does not support CreateDismImage on C:\ - CGenericImagingManager::CreateDismImage

2023-12-06 10:33:15, Info DISM DISM VHD Provider: PID=1116 TID=1992 [C:] is not recognized by the DISM VHD provider. - CVhdImage::Initialize

2023-12-06 10:33:15, Info DISM DISM Imaging Provider: PID=1116 TID=1992 The provider VHDManager does not support CreateDismImage on C:\ - CGenericImagingManager::CreateDismImage

[1116.1992] [0x80070002] FIOReadFileIntoBuffer:(1456): The system cannot find the file specified.

[1116.1992] [0xc142011c] UnmarshallImageHandleFromDirectory:(641)

[1116.1992] [0xc142011c] WIMGetMountedImageHandle:(2910)

2023-12-06 10:33:15, Info DISM DISM WIM Provider: PID=1116 TID=1992 [C:] is not a WIM mount point. - CWimMountedImageInfo::Initialize

2023-12-06 10:33:15, Info DISM DISM Imaging Provider: PID=1116 TID=1992 The provider WimManager does not support CreateDismImage on C:\ - CGenericImagingManager::CreateDismImage

2023-12-06 10:33:15, Info DISM DISM Imaging Provider: PID=1116 TID=1992 No imaging provider supported CreateDismImage for this path - CGenericImagingManager::CreateDismImage

[1116.1992] [0x80070002] FIOReadFileIntoBuffer:(1456): The system cannot find the file specified.

[1116.1992] [0xc142011c] UnmarshallImageHandleFromDirectory:(641)

[1116.1992] [0xc142011c] WIMGetMountedImageHandle:(2910)

2023-12-06 10:33:15, Info DISM DISM WIM Provider: PID=1116 TID=1992 [C:] is not a WIM mount point. - CWimMountedImageInfo::Initialize

2023-12-06 10:33:15, Info DISM DISM FFU Provider: PID=1116 TID=1992 [C:] is not recognized by the DISM FFU provider. - CFfuImage::Initialize

2023-12-06 10:33:15, Info DISM DISM VHD Provider: PID=1116 TID=1992 [C:] is not recognized by the DISM VHD provider. - CVhdImage::Initialize

2023-12-06 10:33:15, Info DISM DISM Manager: PID=1116 TID=1992 physical location path: C:\ - CDISMManager::CreateImageSession

2023-12-06 10:33:15, Info DISM DISM Manager: PID=1116 TID=1992 Event name for current DISM session is Global\__?_Volume{177e5e21-d8e3-4f6c-a320-facf81a86743}__404995486_65536_83456 - CDISMManager::CheckSessionAndLock

2023-12-06 10:33:15, Info DISM DISM Manager: PID=1116 TID=1992 Create session event 0x258 for current DISM session and event name is Global\__?_Volume{177e5e21-d8e3-4f6c-a320-facf81a86743}__404995486_65536_83456 - CDISMManager::CheckSessionAndLock

2023-12-06 10:33:15, Info DISM DISM Manager: PID=1116 TID=1992 Copying DISM from "C:\Windows\System32\Dism" - CDISMManager::CreateImageSessionFromLocation

2023-12-06 10:33:15, Info DISM DISM Manager: PID=1116 TID=1992 Successfully loaded the ImageSession at "X:\windows\TEMP\C8E7F117-ED01-4B92-BBF2-283C87A8D1CD" - CDISMManager::LoadRemoteImageSession

2023-12-06 10:33:15, Info DISM DISM Image Session: PID=2004 TID=1976 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore

2023-12-06 10:33:15, Info DISM DISM OS Provider: PID=2004 TID=1976 Defaulting SystemPath to C:\ - CDISMOSServiceManager::Final_OnConnect

2023-12-06 10:33:15, Info DISM DISM OS Provider: PID=2004 TID=1976 Defaulting Windows folder to C:\Windows - CDISMOSServiceManager::Final_OnConnect

2023-12-06 10:33:15, Info DISM DISM Provider Store: PID=2004 TID=1976 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect

2023-12-06 10:33:15, Info DISM Initialized Panther logging at X:\windows\Logs\DISM\dism.log

2023-12-06 10:33:15, Info DISM DISM Provider Store: PID=2004 TID=1976 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger

2023-12-06 10:33:15, Info DISM Initialized Panther logging at X:\windows\Logs\DISM\dism.log

2023-12-06 10:33:15, Info DISM DISM Manager: PID=1116 TID=1992 Image session successfully loaded from location: X:\windows\TEMP\C8E7F117-ED01-4B92-BBF2-283C87A8D1CD - CDISMManager::CreateImageSession

2023-12-06 10:33:15, Info DISM DISM OS Provider: PID=2004 TID=1976 Setting SystemPath to C:\ - CDISMOSServiceManager::SetSystemPath

2023-12-06 10:33:15, Info DISM DISM.EXE: Target image information: OS Version=10.0.22631.2715, Image architecture=amd64

2023-12-06 10:33:15, Info DISM DISM.EXE: Image session version: 10.0.22621.1

2023-12-06 10:33:15, Info DISM DISM Transmog Provider: PID=2004 TID=1976 Current image session is [OFFLINE] - CTransmogManager::GetMode

2023-12-06 10:33:15, Info DISM DISM OS Provider: PID=2004 TID=1976 Determined System directory to be C:\Windows\System32 - CDISMOSServiceManager::get_SystemDirectory

2023-12-06 10:33:15, Info DISM DISM Transmog Provider: PID=2004 TID=1976 Determined WinDir path = [C:\Windows] - CTransmogManager::GetWinDirPath

2023-12-06 10:33:15, Info DISM DISM Transmog Provider: PID=2004 TID=1976 GetProductType: ProductType = [WinNT] - CTransmogManager::GetProductType

2023-12-06 10:33:15, Info DISM DISM Transmog Provider: PID=2004 TID=1976 Product Type: [WinNT] - CTransmogManager::Initialize

2023-12-06 10:33:15, Info DISM DISM Transmog Provider: PID=2004 TID=1976 Product Type ServerNT : [No] - CTransmogManager::Initialize

2023-12-06 10:33:15, Info CSI 00000001 Shim considered [l:126]'??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.22621.2567_none_e93fb1d442e4b410\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND

2023-12-06 10:33:15, Info CSI 00000002 Shim considered [l:123]'??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.22621.2567_none_e93fb1d442e4b410\wcp.dll' : got STATUS_SUCCESS

2023-12-06 10:33:16, Info DISM DISM Driver Manager: PID=2004 TID=1976 Further logs for driver related operations can be found in the target operating system at %WINDIR%\inf\setupapi.offline.log - CDriverManager::Initialize

2023-12-06 10:33:16, Info DISM DISM Package Manager: PID=2004 TID=1976 Finished initializing the CbsConUI Handler. - CCbsConUIHandler::Initialize

2023-12-06 10:33:16, Info CSI 00000001 Shim considered [l:126]'??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.22621.2567_none_e93fb1d442e4b410\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND

2023-12-06 10:33:16, Info CSI 00000002 Shim considered [l:123]'??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.22621.2567_none_e93fb1d442e4b410\wcp.dll' : got STATUS_SUCCESS

2023-12-06 10:33:16, Info CBS Universal Time is: 2023-12-06 18:33:16.654

2023-12-06 10:33:16, Info CBS Failed to find a matching version for servicing stack: C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.22621.2567_none_e93fb1d442e4b410\ [HRESULT = 0x80070490 - ERROR_NOT_FOUND]

2023-12-06 10:33:16, Info CBS Failed to find servicing stack directory in online store. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]

2023-12-06 10:33:16, Info CBS Offline servicing, using stack version from: C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.22621.2567_none_e93fb1d442e4b410\cbscore.dll

2023-12-06 10:33:16, Info CBS Loaded Servicing Stack v10.0.22621.2567 with Core: C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.22621.2567_none_e93fb1d442e4b410\cbscore.dll

2023-12-06 10:33:16, Info CBS Setting core mode: CbsCoreModeOffline

2023-12-06 10:33:16, Info CSI 00000001@2023/12/6:18:33:16.654 WcpInitialize: wcp.dll version 10.0.22621.2567 (WinBuild.160101.0800)

2023-12-06 10:33:16, Info CBS TurboContainer load Successful

2023-12-06 10:33:16, Info CBS Lock: New lock added: CCbsSessionManager, level: 11, total lock:9

2023-12-06 10:33:16, Info CBS Lock: New lock added: CSIInventoryCriticalSection, level: 64, total lock:10

2023-12-06 10:33:16, Info DISM DISM Package Manager: PID=2004 TID=1976 Loaded servicing stack for offline use only. - CDISMPackageManager::CreateCbsSession

2023-12-06 10:33:16, Info CBS Lazy store initialization mode

2023-12-06 10:33:16, Info CSI 00000001 Shim considered [l:126]'??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.22621.2567_none_e93fb1d442e4b410\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND

2023-12-06 10:33:16, Info CSI 00000002 Shim considered [l:123]'??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.22621.2567_none_e93fb1d442e4b410\wcp.dll' : got STATUS_SUCCESS

2023-12-06 10:33:16, Info DISM DISM Package Manager: PID=2004 TID=1976 Processing the top level command token(cleanup-image). - CPackageManagerCLIHandler::Private_ValidateCmdLine

2023-12-06 10:33:16, Warning DISM DISM Package Manager: PID=2004 TID=1976 The scratch directory size might be insufficient to perform this operation. This can cause unexpected behavior. Use the /ScratchDir option to point to a folder with sufficient scratch space. The recommended size is at least 1024 MB - CPackageManagerCLIHandler::ExecuteCmdLine

2023-12-06 10:33:16, Info DISM DISM Package Manager: PID=2004 TID=1976 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine

2023-12-06 10:33:16, Info DISM DISM Package Manager: PID=2004 TID=1976 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine

2023-12-06 10:33:17, Info CBS Lazy store initialization mode, fully initialize.

2023-12-06 10:33:17, Info CBS Offline image is writable

2023-12-06 10:33:17, Info CBS Loading offline registry hive: SOFTWARE, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Windows/System32/config/SOFTWARE' from path '\?\C:\Windows\System32\config\SOFTWARE'.

2023-12-06 10:33:17, Info CBS Loading offline registry hive: SYSTEM, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Windows/System32/config/SYSTEM' from path '\?\C:\Windows\System32\config\SYSTEM'.

2023-12-06 10:33:17, Info CBS Loading offline registry hive: SECURITY, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Windows/System32/config/SECURITY' from path '\?\C:\Windows\System32\config\SECURITY'.

2023-12-06 10:33:17, Info CBS Loading offline registry hive: SAM, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Windows/System32/config/SAM' from path '\?\C:\Windows\System32\config\SAM'.

2023-12-06 10:33:17, Info CBS Loading offline registry hive: COMPONENTS, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Windows/System32/config/COMPONENTS' from path '\?\C:\Windows\System32\config\COMPONENTS'.

2023-12-06 10:33:17, Info CBS Loading offline registry hive: DRIVERS, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Windows/System32/config/DRIVERS' from path '\?\C:\Windows\System32\config\DRIVERS'.

2023-12-06 10:33:17, Info CBS Loading offline registry hive: DEFAULT, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Windows/System32/config/DEFAULT' from path '\?\C:\Windows\System32\config\DEFAULT'.

2023-12-06 10:33:17, Info CBS Loading offline registry hive: ntuser.dat, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Users/Default/ntuser.dat' from path '\?\C:\Users\Default\ntuser.dat'.

2023-12-06 10:33:17, Info CBS Loading offline registry hive: schema.dat, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Windows/system32/smi/store/Machine/schema.dat' from path '\?\C:\Windows\system32\smi\store\Machine\schema.dat'.

2023-12-06 10:33:17, Info CSI 00000002 CSI Store 2888884070272 initialized

2023-12-06 10:33:17, Info CBS Build: 22621.1.amd64fre.ni_release.220506-1250

2023-12-06 10:33:17, Info CBS Session: 2004_2199109 initialized by client DISM Package Manager Provider, external staging directory: (null)

2023-12-06 10:33:17, Info CBS Exec: Addsource called, Session: 2004_2199109, Client: DISM Package Manager Provider, from GPO: No, Path: D:\sources

2023-12-06 10:33:17, Info DISM DISM Package Manager: PID=2004 TID=1976 CBS session options=0x40000! - CDISMPackageManager::Internal_Finalize

2023-12-06 10:33:17, Info CBS Client specifies manual store corruption detect or repair.

2023-12-06 10:33:17, Info CBS Exec: Session processing started. Client: Manual, Session(DISM Package Manager Provider Store Corruption Detect/Repair): 2004_2199109

2023-12-06 10:33:17, Info CBS FLOW: Entering stage: CheckCbs

2023-12-06 10:33:17, Info CBS Failed to open package file: \?\C:\Windows\Servicing\Packages\Microsoft-Windows-Kernel-LA57-FoD-Package~31bf3856ad364e35~amd64~~10.0.22621.1.mum [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

2023-12-06 10:33:17, Info CBS Failed to read in xml content [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

2023-12-06 10:33:17, Info CBS Repr: CBS Store check completes

2023-12-06 10:33:17, Info CSI 00000003 StoreCorruptionRepair transaction begun. WcpVersion: [l:38]'10.0.22621.2567 (WinBuild.160101.0800)'.

2023-12-06 10:33:17, Info CSI 00000004@2023/12/6:18:33:17.935 Starting corruption detection (InnerFlags=2)

2023-12-06 10:33:17, Info CBS FLOW: Entering stage: CheckCsi

2023-12-06 10:34:08, Info CSI 00000005 Direct SIL provider: Number of files opened: 113719.

2023-12-06 10:34:08, Info CSI 00000006@2023/12/6:18:34:08.810 Corruption detection complete. numCorruptions = 0, Disp = 1.

2023-12-06 10:34:08, Info CBS Repr: CSI meta data corruption found, will commit repair transaction if repair is asked.

2023-12-06 10:34:08, Info CBS Repr: CSI Store check completes

2023-12-06 10:34:08, Info CBS FLOW: Entering stage: CheckStagedPackages

2023-12-06 10:34:09, Info CBS Missing Current State value for package: Microsoft-Windows-Kernel-LA57-FoD-Package~31bf3856ad364e35~amd64~~10.0.22621.1, force absent so at least it can be re-installed

2023-12-06 10:34:09, Info CBS Failed to get visibility for package: Microsoft-Windows-Kernel-LA57-FoD-Package~31bf3856ad364e35~amd64~~10.0.22621.1 [HRESULT = 0x80070490 - ERROR_NOT_FOUND]

2023-12-06 10:34:09, Info CBS Package Format: PSFX

2023-12-06 10:34:09, Info CBS Delta Format: ForwardOnly

2023-12-06 10:34:09, Info CBS Package Format: PSFX

2023-12-06 10:34:09, Info CBS Delta Format: ForwardOnly

2023-12-06 10:34:09, Info CBS Package Format: PSFX

2023-12-06 10:34:09, Info CBS Delta Format: ForwardOnly

2023-12-06 10:34:09, Info CBS Appl:LCU package and revision compare set to explicit

2023-12-06 10:34:09, Info CBS Package Format: PSFX

2023-12-06 10:34:09, Info CBS Delta Format: ForwardOnly

2023-12-06 10:34:09, Info CBS Repr: Staged package check completes

2023-12-06 10:34:09, Info CBS Exec: Not able to find Microsoft-Windows-Kernel-LA57-FoD-Package~31bf3856ad364e35~amd64~~10.0.22621.1.mum from directory local source

2023-12-06 10:34:09, Info CBS Exec: Not able to find Servicing\Packages\Microsoft-Windows-Kernel-LA57-FoD-Package~31bf3856ad364e35~amd64~~10.0.22621.1.mum from directory local source

2023-12-06 10:34:09, Info CBS Exec: Not able to find update.mum from directory local source

2023-12-06 10:34:09, Info CBS Exec: Not able to find Servicing\Packages\update.mum from directory local source

2023-12-06 10:34:09, Info CBS Repr: Not able to find replacement manifests for package Microsoft-Windows-Kernel-LA57-FoD-Package~31bf3856ad364e35~amd64~~10.0.22621.1 from any local source

2023-12-06 10:34:09, Info CBS Repr: The system configuration is not qualified for Windows Update download, skip WU.

2023-12-06 10:34:09, Info CBS Failed to collect payload and there is nothing to repair. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]

2023-12-06 10:34:09, Info CBS FLOW: Entering stage: RemoveStagedPackages

2023-12-06 10:34:09, Info CBS Failed to repair store. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]

2023-12-06 10:34:09, Info CBS

2023-12-06 10:34:09, Info CBS =================================

2023-12-06 10:34:09, Info CBS Checking System Update Readiness.

2023-12-06 10:34:09, Info CBS

2023-12-06 10:34:09, Info CBS (p) CBS MUM Corrupt (n) Microsoft-Windows-Kernel-LA57-FoD-Package~31bf3856ad364e35~amd64~~10.0.22621.1

2023-12-06 10:34:09, Info CBS Repair failed: Missing replacement mum/cat pair.

2023-12-06 10:34:09, Info CBS (w) CBS Package CurrentState Missing Microsoft-Windows-Kernel-LA57-FoD-Package~31bf3856ad364e35~amd64~~10.0.22621.1

2023-12-06 10:34:09, Info CBS (w) CBS Package Visibility Missing Microsoft-Windows-Kernel-LA57-FoD-Package~31bf3856ad364e35~amd64~~10.0.22621.1

2023-12-06 10:34:09, Info CBS (w) CBS Package Owner Missing Microsoft-Windows-Kernel-LA57-FoD-Package~31bf3856ad364e35~amd64~~10.0.22621.1

2023-12-06 10:34:09, Info CBS

2023-12-06 10:34:09, Info CBS Summary:

2023-12-06 10:34:09, Info CBS Operation: Detect and Repair

2023-12-06 10:34:09, Info CBS Operation result: 0x800f081f

2023-12-06 10:34:09, Info CBS Last Successful Step: Remove staged packages completes.

2023-12-06 10:34:09, Info CBS Total Detected Corruption: 4

2023-12-06 10:34:09, Info CBS CBS Manifest Corruption: 1

2023-12-06 10:34:09, Info CBS CBS Metadata Corruption: 3

2023-12-06 10:34:09, Info CBS CSI Manifest Corruption: 0

2023-12-06 10:34:09, Info CBS CSI Metadata Corruption: 0

2023-12-06 10:34:09, Info CBS CSI Payload Corruption: 0

2023-12-06 10:34:09, Info CBS Total Repaired Corruption: 0

2023-12-06 10:34:09, Info CBS CBS Manifest Repaired: 0

2023-12-06 10:34:09, Info CBS CSI Manifest Repaired: 0

2023-12-06 10:34:09, Info CBS CSI Payload Repaired: 0

2023-12-06 10:34:09, Info CBS CSI Store Metadata refreshed: True

2023-12-06 10:34:09, Info CBS Staged Packages:

2023-12-06 10:34:09, Info CBS CBS Staged packages: 0

2023-12-06 10:34:09, Info CBS CBS Staged packages removed: 0

2023-12-06 10:34:09, Info CBS

2023-12-06 10:34:09, Info CBS Total Operation Time: 52 seconds.

2023-12-06 10:34:09, Info CBS Ensure WCP corruption flag is clear

2023-12-06 10:34:09, Info CBS CheckSur: hrStatus: 0x800f081f [CBS_E_SOURCE_MISSING], download results: <none>

2023-12-06 10:34:09, Info CBS Count of times corruption detected: 1

2023-12-06 10:34:09, Info CBS Seconds between initial corruption detections: -1

2023-12-06 10:34:09, Info CBS Seconds between corruption and repair: -1

2023-12-06 10:34:09, Info CBS Failed to run Detect and repair. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]

2023-12-06 10:34:09, Info CBS Exec: Processing complete, session(Corruption Repairing): 2004_2199109 [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]

2023-12-06 10:34:09, Info DISM DISM Package Manager: PID=2004 TID=1976 Error in operation: source for package or file not found, ResolveSource() unsuccessful. (CBS HRESULT=0x800f081f) - CCbsConUIHandler::Error

2023-12-06 10:34:09, Error CBS Session: 2004_2199109 failed to perform store corruption detect and repair operation. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]

2023-12-06 10:34:09, Info CBS Session: 2004_2199109 finalized. Reboot required: no [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]

2023-12-06 10:34:09, Error DISM DISM Package Manager: PID=2004 TID=1976 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800f081f)

2023-12-06 10:34:09, Error DISM DISM Package Manager: PID=2004 TID=1976 The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg

2023-12-06 10:34:09, Error DISM DISM Package Manager: PID=2004 TID=1976 Failed processing package changes with session options - CDISMPackageManager::Internal_ProcessChangesWithOptions(hr:0x800f081f)

2023-12-06 10:34:09, Error DISM DISM Package Manager: PID=2004 TID=1976 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x800f081f)

2023-12-06 10:34:09, Error DISM DISM Package Manager: PID=2004 TID=1976 The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg

2023-12-06 10:34:09, Info CBS Deleting directory: \?\C:\Windows\CbsTemp\2004_2199109\

2023-12-06 10:34:09, Info CBS Moving directory from \?\C:\Windows\CbsTemp\2004_2199109\ to \?\C:\Windows\CbsTemp{57BE335C-61BB-485E-8813-FB9D61E362FE}

2023-12-06 10:34:09, Info CBS Deletion of: \?\C:\Windows\CbsTemp{57BE335C-61BB-485E-8813-FB9D61E362FE} successful

2023-12-06 10:34:09, Info CBS Force unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Windows/System32/config/SOFTWARE

2023-12-06 10:34:09, Info CBS Force unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Windows/System32/config/SYSTEM

2023-12-06 10:34:09, Info CBS Force unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Windows/System32/config/SECURITY

2023-12-06 10:34:09, Info CBS Force unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Windows/System32/config/SAM

2023-12-06 10:34:09, Info CBS Force unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Windows/System32/config/COMPONENTS

2023-12-06 10:34:09, Info CBS Force unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Windows/System32/config/DRIVERS

2023-12-06 10:34:09, Info CBS Force unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Windows/System32/config/DEFAULT

2023-12-06 10:34:09, Info CBS Force unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Users/Default/ntuser.dat

2023-12-06 10:34:09, Info CBS Force unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Windows/system32/smi/store/Machine/schema.dat

2023-12-06 10:34:09, Info CSI 00000007 Direct SIL provider: Number of files opened: 63208.

2023-12-06 10:34:09, Error DISM DISM Package Manager: PID=2004 TID=1976 Failed to restore the image health. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x800f081f)

2023-12-06 10:34:09, Error DISM DISM Package Manager: PID=2004 TID=1976 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f081f)

2023-12-06 10:34:09, Info DISM DISM Package Manager: PID=2004 TID=1976 Finalizing CBS core. - CDISMPackageManager::Finalize

2023-12-06 10:34:09, Info CBS CbsCoreFinalize: ExecutionEngineFinalize

2023-12-06 10:34:09, Info CBS Execution Engine Finalize

2023-12-06 10:34:09, Info CBS CbsCoreFinalize: ComponentAnalyzerFinalize

2023-12-06 10:34:09, Info CBS CbsCoreFinalize: PackageTrackerFinalize

2023-12-06 10:34:09, Info CBS CbsCoreFinalize: CoreResourcesUnload

2023-12-06 10:34:09, Info CBS CbsCoreFinalize: SessionManagerFinalize

2023-12-06 10:34:09, Info CBS Lock: Lock removed: CSIInventoryCriticalSection, level: 64, total lock:10

2023-12-06 10:34:09, Info CBS Lock: Lock removed: CCbsSessionManager, level: 11, total lock:9

2023-12-06 10:34:09, Info CBS CbsCoreFinalize: CapabilityManagerFinalize

2023-12-06 10:34:09, Info CBS CbsCoreFinalize: GetPublicObjectMonitor::Audit

2023-12-06 10:34:09, Info CBS CbsCoreFinalize: PublicObjectMonitorFinalize

2023-12-06 10:34:09, Info CBS CbsCoreFinalize: Enter vCoreInitializeLock

2023-12-06 10:34:09, Info CBS CbsCoreFinalize: WcpUnload

2023-12-06 10:34:09, Info CBS CbsCoreFinalize: DrupUnload

2023-12-06 10:34:09, Info CBS CbsCoreFinalize: CfgMgr32Unload

2023-12-06 10:34:09, Info CBS CbsCoreFinalize: DpxUnload

2023-12-06 10:34:09, Info CBS CbsCoreFinalize: SrUnload

2023-12-06 10:34:09, Info CBS CbsCoreFinalize: TurboStackUnload

2023-12-06 10:34:09, Info CBS CbsCoreFinalize: TurboContainerUnload

2023-12-06 10:34:09, Info CBS TurboContainer unload Successful

2023-12-06 10:34:09, Info CBS CbsCoreFinalize: CbsEsdUnload

2023-12-06 10:34:09, Info CBS CbsCoreFinalize: CbsOneSettingsFinalize

2023-12-06 10:34:09, Info CBS CbsCoreFinalize: CbsTraceInfoUninitialize

2023-12-06 10:34:09, Info CBS CbsCoreFinalize: CbsEventUnregister

2023-12-06 10:34:09, Info CBS CbsCoreFinalize: AppContainerUnload

2023-12-06 10:34:09, Info CBS CbsCoreFinalize: WdsUnload, logging from cbscore will end.

2023-12-06 10:34:09, Info DISM DISM Manager: PID=1116 TID=1992 Closing session event handle 0x258 - CDISMManager::CleanupImageSessionEntry

2023-12-06 10:34:09, Info DISM DISM.EXE: Image session has been closed. Reboot required=no.

2023-12-06 10:34:09, Info DISM DISM.EXE:

2023-12-06 10:34:09, Info DISM DISM.EXE: <----- Ending Dism.e

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

7 answers

Answer 1

Hello Angelo,

Thank you for posting in Microsoft Community.

I'm sorry to hear that you're experiencing issues with your Surface Pro 9. The "inaccessible boot device" error message usually indicates that there is an issue with the hard drive or the storage device. I value the time you have spent in trying to fix this issue. Let us work on this together.

Can you confirm that you executed this command by booting your Surface into the Windows Recovery Environment (WinRe)?
May I know which Surface pro 9 configuration do you have, the Intel or 5G(SQ3)?

If running all the system files didn't work, you may need to recover your Surface using a USB recovery drive. A recovery drive image allows you to reset your Surface to factory settings. This will reimage the entire device as well as reinstall Windows, including the drivers and firmware. This will remove everything from the device. You will also need a 16GB/32GB flash driver that has been formatted as FAT32 before downloading the Recovery image. Don't use anything larger than a 32GB USB drive. See steps below for guidance.

To download the Recovery Image: You'll another working device running on Windows.

Visit the page to Download the recovery image for your Surface
Sign in with your Microsoft Account
From the list of Surface devices available, select the device that you need a recovery image for
Please note that while you will only be presented with devices that are currently registered on your account, you will also be presented with the option to get an image for a different type of device. If you try to use this option, you will be prompted to enter the serial number for that device.
Download the recovery image using the button on the page
When the download bar pops up at the bottom of your screen, save the file in a location you will be able to find it.

Note: Formatting a recovery drive will erase anything that is already stored on your USB drive. Make sure to transfer any important data from your USB drive to another storage device before using it to create a Surface USB recovery drive.

Format USB Drive:

Insert your USB drive into the USB port of your PC.
From the desktop, open File Explorer
Tap and hold or right-click on the USB drive and choose Format.
Select FAT32 as the file system and enter a Volume label to name the USB drive, such as RECOVERY, and then tap or click Start
Tap or click OK to erase the contents of the USB drive
Tap or click OK when the format is complete

Create a recovery drive:

On your Surface or PC, open recovery image that you downloaded by double-clicking it or right click then select Extract and then Extract all.
Select the USB drive you formatted earlier for the location and click Extract.

Use a USB recovery drive to reset your Surface:

Shutdown the Surface
Insert the USB recovery drive into the USB port
Press and hold the volume-down (-) rocker
Press and release the power button
When the Surface logo appears, release the volume-down (-) rocker
Surface will start the recovery software on the USB recovery drive
When prompted, choose your language options and keyboard layout.
Select Troubleshoot
Select Recover from a Drive. Choose Remove Everything and Fully Clean the Drive. Recovering this PC.
If prompted, select Repartition the drives
If prompted for BitLocker Key, tap Skip this Drive.

Let me know how it goes.

Kind regards,

Lavenia

Answer 2

Anonymous

Yes I executed these commands in the recovery environment. It's an Intel system. I ended up reinstalling windows. The kernel file was gone.

Answer 3

I'm glad to know that you're able to reinstall Windows successfully. Thank you for giving us the opportunity to work with you regarding this concern.

To help other customers searching for help on related issues, feel free to mark the response you found most helpful by clicking***“Yes”***on the bottom of that post. This will ensure the helpful responses are most visible when searching (and you can vote more than once if the solution was spread over multiple posts).

Answer 4

Anonymous

I would have liked more troubleshooting help trying to get the system back without reinstalling windows.

Answer 5

Anonymous

Do you mean you still haven't reinstalled your Windows system?

Your only choice if your Surface won't boot up is to use a USB recovery drive to restore the device.

Share via

Surface Pro 9 Inaccessible boot device

7 answers