The KB5035849 cumulative update released during today's Patch Tuesday fails to install on Windows 10 and Windows Server systems with 0xd0000034 errors.
According to a wave of reports from administrators and users, KB5035849 will not install when checking online for updates via Windows and Microsoft update servers.
Affected systems include those running Windows Server 2019 or Windows 10 Enterprise LTSC 2019, which have reached their mainstream end-of-support date on January 9 and are under extended support for five more years until January 2029.
Source: BleepingComputer
"Had the same issue (0xd0000034) with 'Check online for updates', but WSUS versions of these seem to install w/o issue," one admin said.
"Yep - entirely fails to install on every single Server 2019 instance we've got - which is an *awful* lot of instances," another confirmed.
While many customers have already reported that KB5035849 doesn't install on their devices, Microsoft says that it's "not currently aware of any issues with this update."
In today's support document, the company also tagged it as available for installation via Windows Update and Microsoft Update.
Those experiencing these issues can still deploy KB5035849 manually by downloading and installing it from Microsoft's Update Catalog.
"The MSU has not been released for WUD on this KB yet. You can download it from the update catalog," one user said.
However, as Redmond explains, you must first install the KB5005112 August 2021 servicing stack update (SSU) for your operating system before manually deploying the KB5035849 cumulative update.
Comments
GT500 - 3 months ago
Another update failing to install? Is Microsoft still doing QA?
doncoyote - 3 months ago
"Update successfully failed to install."
dthomsonit - 3 months ago
I had spybot running on Windows 2019 Server. If you can disable this or any type of malware software. It will install. Ending the spybot tasks and running the update again i.e "retry" worked for me.However be patient it can take a bit of time to jnstall. Pausing a bit on 25%, the 45%, then 75% roughly. It also wants a reboot, which I have not actioned yet. Disclaimer: I would be very cautious about disabling.antivirus products, with inbuilt malware and ransomware. I have ESET Endpoint Security and I DIDN'T disable this at all. If unsure wait for more articles and a update from Microsoft in Windows Update. Hope this assists you all.If you don't have a reliable disaster recovery method I would be cautious.
NoneRain - 3 months ago
TIL some ppl use Spybot to this day. And in damn servers
tverweij - 3 months ago
Yesterday I got the error on any server - this morning it installed without problems.
DyingCrow - 3 months ago
Bonus XP for those who rush to install windows updates right when they come out. -INT temporary debuff for those who go the extra mile doing all the silly troubleshooting, download and install from the catalogue. Waste of time.
On a side note, if it wasn't for those brave logic-defiant efforts, we might not have have articles like these informing about what has become routine - windows updates *$%&^ fail to install. M$ has the telemetry and can issue advisories about known issues, but we can't really trust in that as a honorable action, can we?