[ltsb, 1809] 2024-05 Cumulative Update (KB5037765) - Error 0x80004005

[Koldov]

2024-05 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5037765) - Error 0x80004005

 

Not sure if I just haven't had enough coffee this morning or what?

 

Wednesday I set my 2 'in the wild' machines to do their Windows Updates... Server 2019 went OK, but it killed my very old Windows 10 client 'Phenom Machine' (I just thought that maybe it was finally time to let it go anyway, so wasn't too concerned). Yesterday I approved this in WSUS for my 'proper' test machines, Server 2019 went OK, but it would just not install on the Windows 10 client (failed 5 times), so I did some digging...

 

Apparently there are threads appearing all over from non-native English speaking countries that are saying it is failing on Server 2019/2016 because the English - United States (EN-US) language pack isn't installed. This probably hasn't been noticed here because I guess there is only one 'English' version of Server...

 

Anyway, it was getting late and that's when I realised all my Windows 10 clients are EN-GB ('International' ) clients and also don't have the EN-US language pack installed....

 

I thought I could prove this but had a real hard time installing the EN-US language pack for some reason (probably because my WSUS isn't configured for language packs), so I went to the trouble of downloading the 5GB language pack .iso from MVLSC (or MAC as it's called now).

 

Ready to get stuck in this morning and install the EN-US language and give it another go, but my client is refusing to even acknowledge the update exists... it's still in WSUS, but the client tells me it's 'Up To Date' (even thought it's showing the CU failed to install 5 times)...

 

If it's still in my WSUS, has it been pulled somehow? How does that work? Nothing new has appeared in my WSUS to replace it and the client can't 'see' the old one so I can't test it...

[Michael]

I can't answer your query, but have you considered WUfB?

 

You can still stage groups of workstations to install updates at different times/days, all via GPO, on or off site.

[jthompson]

I'm not seeing the 2024-05 CU for my 2019 servers. I think Microsoft have held it back for the language pack issue. Interestingly, a couple of off-domain 2019 servers here installed the update right after patch Tuesday (before it was pulled?), but on my domain-joined servers which are configured to defer quality updates for a few days, there's no sign of the update yet.

[chris11256]

Same here, none of my 2019 servers are finding it via WSUS.

[Steve21]

Microsoft blocked it temporarily due to other issues - Supposed to be a re release coming soon

 

Steve

[Koldov]

**UPDATE NOW REPLACED WITH KB5039705**

 

The May 2024 security update might fail to install

[TerryLambert]

Ugh, update issues are the worst! That 0x80004005 error is a headache. Sounds like the missing EN-US language pack might be the culprit. If WSUS isn’t configured for language packs, that could be why your clients aren’t picking it up.

 

Since you already downloaded the language pack ISO, try manually installing it on one of the test machines. After that, restart and see if the update shows up.

 

If the update still doesn’t appear, it’s possible Microsoft pulled it, but that’s rare without some notification. Sometimes WSUS can be a bit glitchy with recognizing updates after several failures. You might need to reset the Windows Update components on the client.

[jthompson]

**UPDATE NOW REPLACED WITH KB5039705**

 

The May 2024 security update might fail to install

 

Yep, now seeing the patch installed successfully.