I've got a Windows Server 2016 server that had issues installing the 2023-09 Cumulative Update for Windows Server 2016 (KB5030213). The OS Build should have been incremented to 14393.6252 but the build still shows 14393.6167 (which is the build post-Aug CU). I don't have any event logs for what went wrong and I didnt even notice it until this past week. When I run SFC & DISM with all the usual switches, I see these messages in the CBS.Log
2023-12-02 20:21:00, Info CBS Failed to run Detect and repair. [HRESULT = 0x800f0821 - CBS_E_ABORT]
2023-12-02 20:21:00, Info CBS Exec: Processing complete, session(Corruption Detecting): 31073666_3088936771 [HRESULT = 0x800f0821 - CBS_E_ABORT]
2023-12-02 20:21:00, Error CBS Session: 31073666_3088936771 failed to perform store corruption detect and repair operation. [HRESULT = 0x800f0821 - CBS_E_ABORT]
2023-12-02 20:21:00, Info CBS Session: 31073666_3088936771 finalized. Reboot required: no [HRESULT = 0x800f0821 - CBS_E_ABORT]
2023-12-02 20:21:00, Info CBS Failed to FinalizeEx using worker session [HRESULT = 0x800f0821]
2023-12-02 20:22:00, Info CBS Session: 31073671_490757144 initialized by client DISM Package Manager Provider, external staging directory: (null), external registry directory: (null
2023-12-02 20:22:00, Info CBS Client specifies manual store corruption detect or repair.
2023-12-02 20:22:00, Info CBS Exec: Session processing started. Client: Manual, Session(DISM Package Manager Provider Store Corruption Detect/Repair): 31073671_490757144
2023-12-02 20:22:00, Info CBS Reboot mark set
2023-12-02 20:22:00, Info CBS Winlogon: Registering for CreateSession notifications
2023-12-02 20:22:00, Info CBS FLOW: Entering stage: CheckCbs
2023-12-02 20:22:01, Info CBS Repr: CBS Store check completes
2023-12-02 20:22:01, Info CSI 00000008 StoreCorruptionRepair transaction begun. WcpVersion: [l:41]'10.0.14393.5771 (rs1_release.230213-1720)'.
2023-12-02 20:22:01, Info CSI 00000009@2023/12/3:01:22:01.958 Starting corruption detection (InnerFlags=5)
2023-12-02 20:22:01, Info CBS FLOW: Entering stage: CheckCsi
2023-12-02 20:27:42, Info CSI 0000000a@2023/12/3:01:27:42.954 Corruption detection complete. numCorruptions = 0, Disp = 1.
2023-12-02 20:27:42, Info CBS Repr: CSI meta data corruption found, will commit repair transaction if repair is asked.
2023-12-02 20:27:42, Info CBS Repr: CSI Store check completes
2023-12-02 20:34:00, Info CBS Session: 31073672_3401745232 initialized by client WinMgmt, external staging directory: (null), external registry directory: (null
2023-12-02 20:34:00, Info CBS Not able to find an installed package package from moniker: @Foundation [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2023-12-02 20:34:00, Info CBS Failed to resolve package from moniker [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2023-12-02 20:34:00, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
I see these messages in the DISM.log file.
2023-12-02 14:05:12, Info DISM DISM Provider Store: PID=7020 TID=6952 Getting Provider DISM Package Manager - CDISMProviderStore::GetProvider
2023-12-02 14:05:12, Info DISM DISM Provider Store: PID=7020 TID=6952 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2023-12-02 14:05:12, Info DISM DISM Provider Store: PID=7020 TID=6952 Loading Provider from location C:\Windows\TEMP\1AC5D405-DA5A-4C6D-B35A-101ED66B1CD8\CbsProvider.dll - CDISMProviderStore::Internal_GetProvider
2023-12-02 14:05:12, Info DISM DISM Provider Store: PID=7020 TID=6952 Connecting to the provider located at C:\Windows\TEMP\1AC5D405-DA5A-4C6D-B35A-101ED66B1CD8\CbsProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2023-12-02 14:05:12, Info DISM DISM Provider Store: PID=7020 TID=6952 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2023-12-02 14:05:12, Info DISM DISM Package Manager: PID=7020 TID=6952 Finished initializing the CbsConUI Handler. - CCbsConUIHandler::Initialize
2023-12-02 14:05:12, Info DISM DISM Package Manager: PID=7020 TID=6952 CBS is being initialized for online use. More information about CBS actions can be located at: %windir%\logs\cbs\cbs.log - CDISMPackageManager::Initialize
2023-12-02 14:05:12, Info DISM DISM Package Manager: PID=7020 TID=6952 Loaded servicing stack for online use only. - CDISMPackageManager::RefreshInstanceAndLock
2023-12-02 14:05:12, Error DISM DISM Package Manager: PID=7020 TID=6952 Failed opening package @Foundation. - CDISMPackageManager::Internal_CreatePackageByName(hr:0x800f0805)
2023-12-02 14:05:12, Error DISM DISM Package Manager: PID=7020 TID=6952 Failed to get the underlying cbs package. - CDISMPackageManager::OpenPackageByName(hr:0x800f0805)
2023-12-02 14:05:12, Error DISM DISM Package Manager: PID=7020 TID=6952 The specified package is not valid Windows package. - GetCbsErrorMsg
2023-12-02 14:05:12, Error DISM API: PID=6916 TID=6608 Failed to open package - CGetFeaturesCommandObject::InternalExecute(hr:0x800f0805)
2023-12-02 14:05:12, Error DISM API: PID=6916 TID=6608 InternalExecute failed - CBaseCommandObject::Execute(hr:0x800f0805)
2023-12-02 14:05:12, Error DISM API: PID=6916 TID=6968 CGetFeaturesCommandObject internal execution failed - DismGetFeaturesExInternal(hr:0x800f0805)
When I look at the registry key for HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\, serveral of the subkeys are missing data including: ComponentDetect, PackageDetect, PackageIndex, and Packages. When I run "DISM /online /get-packages", i get "(No packages found)".
What can I do to resolve this? I've run SFC /ScanNow and DISM /Online /Cleanup-Image /ScanHealth many times (followed by /RestoreHealth). it's not saying there is anymore corruption but I can't get the Sept update to install (nor the Oct or Nov). Thank you!
2023-12-02 20:21:00, Info CBS Failed to run Detect and repair. [HRESULT = 0x800f0821 - CBS_E_ABORT]
2023-12-02 20:21:00, Info CBS Exec: Processing complete, session(Corruption Detecting): 31073666_3088936771 [HRESULT = 0x800f0821 - CBS_E_ABORT]
2023-12-02 20:21:00, Error CBS Session: 31073666_3088936771 failed to perform store corruption detect and repair operation. [HRESULT = 0x800f0821 - CBS_E_ABORT]
2023-12-02 20:21:00, Info CBS Session: 31073666_3088936771 finalized. Reboot required: no [HRESULT = 0x800f0821 - CBS_E_ABORT]
2023-12-02 20:21:00, Info CBS Failed to FinalizeEx using worker session [HRESULT = 0x800f0821]
2023-12-02 20:22:00, Info CBS Session: 31073671_490757144 initialized by client DISM Package Manager Provider, external staging directory: (null), external registry directory: (null
2023-12-02 20:22:00, Info CBS Client specifies manual store corruption detect or repair.
2023-12-02 20:22:00, Info CBS Exec: Session processing started. Client: Manual, Session(DISM Package Manager Provider Store Corruption Detect/Repair): 31073671_490757144
2023-12-02 20:22:00, Info CBS Reboot mark set
2023-12-02 20:22:00, Info CBS Winlogon: Registering for CreateSession notifications
2023-12-02 20:22:00, Info CBS FLOW: Entering stage: CheckCbs
2023-12-02 20:22:01, Info CBS Repr: CBS Store check completes
2023-12-02 20:22:01, Info CSI 00000008 StoreCorruptionRepair transaction begun. WcpVersion: [l:41]'10.0.14393.5771 (rs1_release.230213-1720)'.
2023-12-02 20:22:01, Info CSI 00000009@2023/12/3:01:22:01.958 Starting corruption detection (InnerFlags=5)
2023-12-02 20:22:01, Info CBS FLOW: Entering stage: CheckCsi
2023-12-02 20:27:42, Info CSI 0000000a@2023/12/3:01:27:42.954 Corruption detection complete. numCorruptions = 0, Disp = 1.
2023-12-02 20:27:42, Info CBS Repr: CSI meta data corruption found, will commit repair transaction if repair is asked.
2023-12-02 20:27:42, Info CBS Repr: CSI Store check completes
2023-12-02 20:34:00, Info CBS Session: 31073672_3401745232 initialized by client WinMgmt, external staging directory: (null), external registry directory: (null
2023-12-02 20:34:00, Info CBS Not able to find an installed package package from moniker: @Foundation [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2023-12-02 20:34:00, Info CBS Failed to resolve package from moniker [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2023-12-02 20:34:00, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
I see these messages in the DISM.log file.
2023-12-02 14:05:12, Info DISM DISM Provider Store: PID=7020 TID=6952 Getting Provider DISM Package Manager - CDISMProviderStore::GetProvider
2023-12-02 14:05:12, Info DISM DISM Provider Store: PID=7020 TID=6952 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2023-12-02 14:05:12, Info DISM DISM Provider Store: PID=7020 TID=6952 Loading Provider from location C:\Windows\TEMP\1AC5D405-DA5A-4C6D-B35A-101ED66B1CD8\CbsProvider.dll - CDISMProviderStore::Internal_GetProvider
2023-12-02 14:05:12, Info DISM DISM Provider Store: PID=7020 TID=6952 Connecting to the provider located at C:\Windows\TEMP\1AC5D405-DA5A-4C6D-B35A-101ED66B1CD8\CbsProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2023-12-02 14:05:12, Info DISM DISM Provider Store: PID=7020 TID=6952 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2023-12-02 14:05:12, Info DISM DISM Package Manager: PID=7020 TID=6952 Finished initializing the CbsConUI Handler. - CCbsConUIHandler::Initialize
2023-12-02 14:05:12, Info DISM DISM Package Manager: PID=7020 TID=6952 CBS is being initialized for online use. More information about CBS actions can be located at: %windir%\logs\cbs\cbs.log - CDISMPackageManager::Initialize
2023-12-02 14:05:12, Info DISM DISM Package Manager: PID=7020 TID=6952 Loaded servicing stack for online use only. - CDISMPackageManager::RefreshInstanceAndLock
2023-12-02 14:05:12, Error DISM DISM Package Manager: PID=7020 TID=6952 Failed opening package @Foundation. - CDISMPackageManager::Internal_CreatePackageByName(hr:0x800f0805)
2023-12-02 14:05:12, Error DISM DISM Package Manager: PID=7020 TID=6952 Failed to get the underlying cbs package. - CDISMPackageManager::OpenPackageByName(hr:0x800f0805)
2023-12-02 14:05:12, Error DISM DISM Package Manager: PID=7020 TID=6952 The specified package is not valid Windows package. - GetCbsErrorMsg
2023-12-02 14:05:12, Error DISM API: PID=6916 TID=6608 Failed to open package - CGetFeaturesCommandObject::InternalExecute(hr:0x800f0805)
2023-12-02 14:05:12, Error DISM API: PID=6916 TID=6608 InternalExecute failed - CBaseCommandObject::Execute(hr:0x800f0805)
2023-12-02 14:05:12, Error DISM API: PID=6916 TID=6968 CGetFeaturesCommandObject internal execution failed - DismGetFeaturesExInternal(hr:0x800f0805)
When I look at the registry key for HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\, serveral of the subkeys are missing data including: ComponentDetect, PackageDetect, PackageIndex, and Packages. When I run "DISM /online /get-packages", i get "(No packages found)".
What can I do to resolve this? I've run SFC /ScanNow and DISM /Online /Cleanup-Image /ScanHealth many times (followed by /RestoreHealth). it's not saying there is anymore corruption but I can't get the Sept update to install (nor the Oct or Nov). Thank you!