Windows Server 2022: Update KB5032198 fails with error 0x8007000d / 0x800f081f

Windows[German]A quick question for administrators who have installed the November 2023 security updates on Windows Server 2022. I have come across reports – mainly from English-speaking administrators – where the installation of the update KB5032198 fails with the error 0x8007000d (or 0x800f081f). The error does not seem to be that widespread, but I have found several people affected.


Update KB5032198 f0r Windows Server 2022

Cumulative Update KB5032198 was released for Windows Server 2022 on November 14, 2023 (see Patchday: Windows 11/Server 2022-Updates (November 14, 2023)). The support article lists a number of fixes – for example, a bug in VMware ESXi environments that prevents Windows Server 2022 VMs from starting is fixed (see Windows Server 2022: Nov. 2023 update KB5032198 fixes VMware ESXi bug caused by KB5031364).

Install fails with error 0x8007000d

I had already pointed out in the blog post above that an administrator had reported issues with this update. The administrator, according to his e-mail address from Switzerland, reports here that the installation under Windows Server 2022 fails with the following message:

Windows failed to install the following update with error 0x8007000d: 2023-11 Cumulative Update for Microsoft server operating system version 21H2 for x64-based Systems (KB5032198).

He asked if others had had the same experience. Later another administrator has responded to this comment and reported the same installation error.

Another administrator writes in this comment that he also gets the error 0x8007000d during installation. He then tried to download the update from the Microsoft Update Catalog and install it manually, but this failed with the same error. A search also revealed this entry, where the installation error occurred under VMware ESXi.

Install fails with error 0x800f081f

It is interesting to note that two other administrators, Sören and another person, have reported that the installation of update KB5032198 fails in Windows Server 2022 with the error code 0x800f081f. A search for this installation error then resulted in this hit at Microsoft, where a user describes the problem.


Repair attempts do not seem to help

The error code 0x8007000d stands for ERROR_INVALID_DATA (see), a rather generic error indicating that invalid data has been downloaded or corruption has occurred. The advice is to download the update again and start the installation. However, this does not seem to help.

The error code 0x800f081f stands for CBS_E_SOURCE_MISSING (see), a source or a package that is required in the update could not be found. This case means that the component store is damaged. Repair attempts via Dism and SFC using the following command sequence have probably been fruitless in cases with the two error codes above:

sfc /scannow
Dism /online /cleanup-image /StartComponentCleanup
Dism /online /cleanup-image /RestoreHealth

The approach of resetting the update store, as described here for error code 0x800f081f, does not seem to have worked for those affected either. So far, I am also not aware that Microsoft has reported anything about a known error in the update package.

An analysis of the generated CBS.log file could possibly provide clarification. However, this often does not help. In this comment, CheongKing describes that he was only able to solve the installation problem by performing an inplace upgrade under Windows Server 2022. He was able to keep the user files and settings during this process. The update could then be installed – so the damage was repaired. But this approach cannot be applied to multiple affected Windows Server 2022 instances – and I have seen several cases where multiple machines were affected rather than individual servers.

Similar articles:
Microsoft Security Update Summary (November 14, 2023)
Patchday: Windows 10-Updates (November 14, 2023)
Patchday: Windows 11/Server 2022-Updates (November 14, 2023)

Cookies helps to fund this blog: Cookie settings

This entry was posted in issue, Update, Windows and tagged , , , . Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *