[SOLVED] Problem patching Windows Server 2016 w/ KB5022289 - 0x8000700d

[bahavel]

Hello. I've been trying to patch one of my Windows Server 2016 boxes with the 01-2023 cumulative patch, KB5022289, and keep getting a 0x8000700d error. Same if I tried the 12-2022 cumulative patch too. I've tried doing a dism restorehealth with the source installation DVD but am unable to get the problem areas to clean up (indicates no source is available). Unfortunately this host is in a very remote and inaccessible location so a rebuild is pretty much out of the question. I'm pretty much at my wits end in trying to get this host patches and into a clean state moving forward. Any assistance would be greatly appreciated. Thank you.

Components scanner output and CBS logs from the sfc/dism runs are attached.

 

[Maxstar]

Hi and welcome to Sysnative,

Step 1. Download

SFCFix and save it to your desktop.

Warning: This fix was written specifically for this system. Do not run this fix on another system.

• Save any work you have open, and close all programs.
• Download the attachment SFCFix.zip and save it to your desktop.
• Drag the SFCFix.zip file over the SFCFix.exe executable and release it.

• SFCFix will launch, let it complete.
• Once done, a file will appear on your desktop, called SFCFix.txt.
• Post the logfile (SFCFix.txt) as attachment in your next reply.

Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.

DISM /online /cleanup-image /RestoreHealth

 

[bahavel]

Applied the SFCFix script (output attached showed successful) and ran a dism restorehealth, which returned without an error on run this time. After I tried to apply the KB5022289 again and still receive the 0x8000700d error when attempting to apply the patch. (Tried both a previously downloaded version and one straight from the MS update site itself in case there was an issue with how it was being applied.)

A regular SFCFix run, ComponentsScanner, and dism restorehealth return no issues identified. I've attached an updated CBS log from the last dism restorehealth run and patch application attempt I tried.

Thanks for the assistance. Making progress slowly but surely.

- Brad

 

[Maxstar]

2023-01-30 14:14:10, Info                  CBS    Registry value for GPOLink is not a dword type. [HRESULT = 0x8007000d - ERROR_INVALID_DATA]

Hi,

Please attempt to update again with Process Monitor running.

Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try updating the system just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the square (CTRL +E) on the toolbar as shown below.



4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up the LogFile.PML and upload it to WeTransfer - Send Large Files & Share Photos Online - Up to 2GB Free and provide the link.
6. Please post a new copy of the CBS log as well.

 

[bahavel]

Thank you. I reran the KB5022289 patch with the process monitor running. Unfortunately due to organizational policy I am unable to use the recommended WeTransfer for the drop.

CBS log and the LogFile.PML can be downloaded from: Alaska ZendTo
(Link will be valid until ~2/9/2023)

 

[Maxstar]

Hi,

Please export the following registry key as *.hive file in an elevated command prompt.

reg save "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies" "%userprofile%\Desktop\policies.hiv"

ZIP this file and attach it tou your next post.

 

[bahavel]

Attached is the requested registry hive from the host.

 

[Maxstar]

Hi,

Export CBS (Component Based Servicing) hive

• Click on the Start button and 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 > Compressed (zipped) Folder.
• Attach the .ZIP file to your next post.
• If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.

 

[bahavel]

Attached is the CBS hive export.

 

[Maxstar]

2023-02-02 10:02:42, Info                  CBS    Registry value for GPOLink is not a dword type. [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
2023-02-02 10:02:42, Info                  CBS    Failed to enumerate all catalogs to uninstall. [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
2023-02-02 10:02:42, Error                 CBS    Failed to process single phase execution. [HRESULT = 0x8007000d - ERROR_INVALID_DATA]

Hi,

The following temporary key in the Components Based Servicing hive contains some non-default values. I would suggest to remove those values and then attempt to update again.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\CatalogsToUninstall]
"GPOLink"=dword:00000003
"GPOName"="{783D74B1-F62A-4AA9-9AE8-E8DB43EFB2C9}"
"FileSysPath"="\\\\xxx.xxxxxx.xxx\\sysvol\\xxx.xxxxxxx.xxx\\Policies\\{ADAA2FBE-6834-4B9D-A5F2-5290BD154B47}\\Machine"
"Options"=dword:00000000
"Version"=dword:00020002

 

[bahavel]

Removal of those temporary registry entries from the registry allowed a successful installation of the KB5022289 patch. Thank you very much for the assistance in getting this server cleaned up and back into a sane state.

 

[Maxstar]

Hi,
You're welcome. Glad to hear the latest LCU installed without any issues after removing the mentioned values.
I'll mark this thread as solved.