Windows Server 2019: Install errors with out-of-band update KB5039705 from May 23, 2024

Windows[German]A short follow-up to the May 2024 security update for Windows Server 2019. The cumulative update KB5037765 from May 14, 2024 was withdrawn due to installation errors with a missing en-us language pack. Microsoft has since released the out-of-band update KB5039705 with corrections on May 23, 2024. However, I have received user reports that this update runs on errors if the cumulative update KB5037765 from May 14, 2024 is installed. Here is some information on what to do if you are affected.


Advertising

Update KB5037765 fails with install error

Cumulative update KB5037765 published on May 14, 2024, fails during installation on non-English-speaking Windows Server 2019 instances with an installation error 0x800f0982. The reason for this was that the language pack en-us, which was required for installation, was missing. Systems that contained the language pack then generally allowed the KB5037765 update to be installed. Microsoft then withdrew the security update from May 14, 2024. I addressed this issue promptly in the posts linked at the end of the article (see Windows Server 2019: Update KB5037765 fails with error 0x800f0982).

Out-of-band update KB5039705

As of May 23, 2024, Microsoft has provided the out-of-band update KB5039705 for Windows Server 2019 (as well as Windows 10 2019 Enterprise LTSC and IoT Enterprise LTSC ). The following is explicitly noted as a fixes:

This update addresses a known issue that is related to the English (United States) language pack. If your device does not have it, installing KB5037765 might fail. The error code is 0x800f0982.

Microsoft also notes: "But this issue might affect devices that do have that language pack. In that case, the error code is 0x80004005.", which I interpret as, that you should install the out-of-band update KB5039705 for Windows Server 2019 in any case, even if the update KB5037765 from May 14, 2024 was installed – just to avoid problems with subsequent updates.

Update KB5039705 fails with errors

Unfortunately, it appears that the revised update KB5039705 fails on individual Windows Server 2019 installations with errors during or after installation.

Install error 0x800f0985

German reader dr-tiger posted this German comment on the German blog and reported that installation error 0x800f0985 had occurred on a Windows Server 2019. The installation error 0x800f0985 is also mentioned in this French comment by reader aa.


Advertising

Install error 0x800F0986

In my German blog post Windows Server 2019: Out-of-Band-Update KB5039705 veröffentlicht (23. Mai 2024) Andreas has posted this comment and writes that he gets the installation error 0x800F0986 when updating KB5039705 on systems that already have KB5037765 installed. On systems that have not yet had KB5037765, installation runs  through without errors, according to the blog reader.

The installation error 0x800F0986 is also mentioned in this comment, in the comment by Fritz, as well as in this French comment by reader aa and in this French comment by reader tuxbox64.

The error 0x800F0986 stands for "Corrupted or missing system files", something has been broken by the installed May 2024 update, which then leads to the error during the out-of-band update.

Install error 0x8007371b

German blog reader Horst reports in this German comment that update KB5039705 to Windows Server 2019 RDS with Citrix VDA 1912 fails with the installation error 0x8007371b. This applies to both Windows Update and the download from the Microsoft Update Catalog.

Hyper-V guests with problems

User ZEN-Master has reported in this comment that KB5039705 caused a VM to hang. After a hard shutdown, the VM started up again.

What can be done?

The installation error 0x800f0982 can be found in several comments. A workaround is to uninstall the problem update KB5037765 from May 14, 2024 and then install update KB5039705. This worked.

Some readers have tried to repair the system with sfc and dism (see), which did not help. Here I refer to this comment, where someone instructed the dism command to repair the system from a working server..

Dism /online /Cleanup-Image /RestoreHealth /Source:\\goodserver.domain\C$\Windows

The advantage is that all files can be downloaded from the "good" dism servers in the event of problems.

Similar articles:
Microsoft Security Update Summary (May 14, 2024)
Patchday: Windows 10-Updates (May 14, 2024)
Patchday: Windows 11/Server 2022-Updates (May 14, 2024)
Windows Server 2012 / R2 and Windows 7 (May 14, 2024)

Windows Server 2019: Update KB5037765 fails with error 0x800f0982
Windows Server 2019 Update KB5037765: Install error 0x800f0982 confirmed
Windows Server 2019: Revised update KB5037765 with WSUS detection bug?
Windows Server 2019: Out-of-Band-Update KB5039705 released (May 23, 2024)


Advertising

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

5 Responses to Windows Server 2019: Install errors with out-of-band update KB5039705 from May 23, 2024

  1. Robert Gijsen says:

    0x8007371b here too, on RD Session hosts. No Citrix though. So far no luck, as the initial may update wasn't installed at all. Bit of an issue this…

  2. Robert Gijsen says:

    Update: currently I'm updating all our servers, it's our maintenance day. It failed on ALL 2019 servers with RDS role installed, but it installed fine on those without. Now on those machines there are additional languagepacks installed, which is not the case on non-RD machines (only US-English there). So there's two differences there, but as the initial May update seemed to have issues with language packs, so I figured there would be the issue. I still started with removing the RDS role and try that, because installing / removing LP is so extremely slow…(why??) and presto! It installs just fine.

    !!!BUT!!! After installing this update, I can't re-enable RDS anymore:

    PS C:\Windows\system32> Install-WindowsFeature -Name RDS-RD-Server -IncludeAllSubFeature
    Install-WindowsFeature : The request to add or remove features on the specified server failed.
    Installation of one or more roles, role services, or features failed.
    One or more required members of the transaction are not present. Error: 0x8007371b
    At line:1 char:1
    + Install-WindowsFeature -Name RDS-RD-Server -IncludeAllSubFeature
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : InvalidOperation: (@{Vhd=; Credent…Name=localhost}:PSObject) [Ins
    tall-WindowsFeature], Exception
    + FullyQualifiedErrorId : DISMAPI_Error__Failed_To_Enable_Updates,Microsoft.Windows.ServerMan
    ager.Commands.AddWindowsFeatureCommand

    Success Restart Needed Exit Code Feature Result
    ——- ————– ——— ————–
    False No Failed {}

    PS C:\Windows\system32>

    So I still tried removing the NL-nl language pack we have on our RD machines, and re-enable the RDS role, but we got the same error.

    So I guess there's something wrong with the RDS bits in this update, considering people with Citrix report this issue as well. Way to go MS. Another 5 hours wasted on borked updates.
    ————-
    2nd comment:
    Posted a large reply twice, which either has to be approved (?) or something else went wrong. Bottom line:

    In our environment, it has nothing to do with languagepacks but with the RDS role. When RDS is removed the update installs fine, but RDS can't be enabled after that anymore.
    ————-
    GB answer: Found it twice in the trash – maybe some filtering was responsible.

  3. DR says:

    I'm still getting "2024-05 Cumulative Update for Windows Server 2019 (1809) for x64-based Systems (KB5039705) – Error 0x800f0986" after trying everything on a 2019 1809 Server DC. Can't seem to sort it out, no other language packs besides English installed. I even installed a different English version and removed the original and then came back, still bombs as of this AM.

Leave a Reply

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

Note: Please note the rules for commenting on the blog (first comments and linked posts end up in moderation, I release them every few hours, I rigorously delete SEO posts/SPAM).