[SOLVED] Server 2012 R2, Can't Update Can't Repair

[mangoman264]

I've got a Windows Server 2012 R2 instance giving me fits trying to patch and install WMF 5.1, and after a few days of banging my head against my desk I've found the Jedi here doing the impossible. After pouring over the registry, CBS, and DISM logs I've found the following:

CBS:
2024-12-16 15:48:45, Info CSI 0000000b@2024/12/16:20:48:45.384 Corruption detection complete. numCorruptions = 4, Disp = 1.
....
2024-12-16 15:48:45, Info CBS Failed to collect payload and there is nothing to repair. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2024-12-16 15:48:45, Info CBS Failed to repair store. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2024-12-16 15:49:32, Info CBS Session: 31150076_38661187 initialized by client DISM Package Manager Provider.
2024-12-16 15:49:32, Info CBS Not able to find an installed package package from moniker: @Foundation [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2024-12-16 15:49:32, Info CBS Failed to resolve package from moniker [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2024-12-16 15:49:32, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
...
bunch of CBS watchlist package missing entries...

DISM:
2024-12-16 17:00:03, Info DISM DISM Package Manager: PID=8716 TID=10952 Loaded servicing stack for online use only. - CDISMPackageManager::RefreshInstanceAndLock
2024-12-16 17:00:03, Error DISM DISM Package Manager: PID=8716 TID=10952 Failed opening package @Foundation. - CDISMPackageManager::Internal_CreatePackageByName(hr:0x800f0805)
2024-12-16 17:00:03, Error DISM DISM Package Manager: PID=8716 TID=10952 Failed to get the underlying cbs package. - CDISMPackageManager::OpenPackageByName(hr:0x800f0805)
2024-12-16 17:00:03, Error DISM DISM Package Manager: PID=8716 TID=10952 The specified package is not valid Windows package. - GetCbsErrorMsg
2024-12-16 17:00:03, Error DISM API: PID=6684 TID=11572 Failed to open package - CGetFeaturesCommandObject::InternalExecute(hr:0x800f0805)
2024-12-16 17:00:03, Error DISM API: PID=6684 TID=11572 InternalExecute failed - CBaseCommandObject::Execute(hr:0x800f0805)
2024-12-16 17:00:03, Error DISM API: PID=6684 TID=10272 CGetFeaturesCommandObject internal execution failed - DismGetFeaturesExInternal(hr:0x800f0805)

Registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex (NO ENTRIES)
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages (NO ENTRIES)

 

[Windows Update Bot]

Hi @mangoman264,

Welcome to Sysnative Forums!

If you haven't already, please review the posting instructions here, and attach the requested log files. Without log files, our helpers will not be able to assist, and this will slow down fixing your machine.

If logs have been already been provided, our team of volunteers will analyse the provided log files to build a fix for your system. Please be aware that this may take several days from your initial post, due to the high volume of threads that we receive.


- Sysnative Windows Update Team

 

[mangoman264]

Other items per posting instructions.

 

[PeterJ]

Hello and welcome,

Export registry as hive

• Click on the Start button and in the search box, type regedit
• When you see regedit on the list, right-click on it and select Run as administrator.
• When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.
  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing
  
  
• Once selected, click File > Export....
• Change the Save as type: to Registry Hive Files (*.*).
• Name this file ComponentBasedServicing (with no file extension) and save it to your Desktop.
• Right-click on the saved file and choose Send To -> Compressed (zipped) Folder.
• Attach the .ZIP file to your next post.
• If the file is too large to upload here, please upload to Gofile or WeTransfer and just provide the downloadlink here.

 

[mangoman264]

Attached - Thank you.

 

[PeterJ]

Some registry keys are empty which is not good. Do you have a recent registry backup ?

 

[mangoman264]

I do not. I think this server's been borked for awhile, but we've only recently started caring about it.

 

[PeterJ]

Sorry but I don't think this corruption is repairable.

 

[mangoman264]

Thanks for your time!

 

[PeterJ]

Your welcome.