Sheridan Posted October 16, 2025 Posted October 16, 2025 All of our servers are 2022 - same patch level and all bar one have patched (so far) the Oct 2025 CU One stubbornly refuses to install it with the following error: {B38FAB3D-BA8D-4F6E-A0D5-4839E704108C} 2025-10-16 12:17:11:632+0100 1 182 [AGENT_INSTALLING_FAILED] 101 {5026AE86-A668-4D90-9CEE-72AA8EBD09F6} 501 8024200b wusa Failure Content Install Installation Failure: Windows failed to install the following update with error 0x8024200b: Security Update for Windows (KB5066782). q7C6eQdgGkmj4Nhd.2.1.0.3.0 I've done all of the usual: - delete SoftwareDistribution etc - sfc /scannow - dism /restore health - manual install of the cu downloaded from the catalog When I export the update logs I see entries like this: 2025/10/16 12:17:11.4293726 5404 4292 Deployment *FAILED* [80073701] Deployment job Id 4736DA9F-AC28-4B4A-A71C-1610466EE7A9 : Installing for Top level update id 5026ae86-a668-4d90-9cee-72aa8ebd09f6.501, bundled update id c3b372b6-6bd5-465a-bef9-84df2bd9b7a0.501 [CUpdateDeploymentJob::DeploySingleUpdateInternal:3103] 2025/10/16 12:17:11.4293853 5404 4292 Deployment *FAILED* [8024200B] Deployment job Id 4736DA9F-AC28-4B4A-A71C-1610466EE7A9 : Installing for Top level update id 5026ae86-a668-4d90-9cee-72aa8ebd09f6.501, bundled update id c3b372b6-6bd5-465a-bef9-84df2bd9b7a0.501 [CUpdateDeploymentJob::DeploySingleUpdateInternal:3122] 2025/10/16 12:17:11.4293983 5404 4292 Deployment *FAILED* [8024200B] file = onecore\enduser\windowsupdate\client\updatedeployment\lib\updatedeploymentjob.cpp, line = 3124 Not sure what these are, I've never seem this error before and its only on the one server Short of rebuilding a new server (massive pain due to the apps running on it!) is there another way around this?
Baz Posted October 19, 2025 Posted October 19, 2025 omg i am having the same issue. I have 16 x 2022 files servers. They are all the same. Not one bit difference between them all. 15 of them are fine. 1 of them the October 2025 monthly update will not install. Fails with SCCM/MECM and also downloading the patch manually from Windows update catalog. I am trying to avoid logging a call with MS, but i might have to. Have you ?
Sheridan Posted October 19, 2025 Author Posted October 19, 2025 I’m only having the issue on one server so far, but I did log with MS who seem to have decided it’s not in their scope of support Going to try a repair install with the latest 2022 iso this week…..
Baz Posted October 19, 2025 Posted October 19, 2025 that doesnt sound right. I have just logged a call. I'll keep you in the loop
Sheridan Posted October 20, 2025 Author Posted October 20, 2025 (edited) I've tried all the usual windows update fixes but so far this one has me stumped - MS basically sent me the usual fixes and also advised me to try a third party tool (SFCFix) which I thought was a bit odd Edited October 20, 2025 by Sheridan
Baz Posted October 20, 2025 Posted October 20, 2025 Ok I'm getting different response with MS. They got me to run a tool which produces tons of logs and to upload to there support site. Waiting to hear back from them. Question is ur server on esx, in Azure or physical?
Sheridan Posted October 20, 2025 Author Posted October 20, 2025 Its on esx - along with all the other ones that worked fine this patch run!
altecsole Posted October 20, 2025 Posted October 20, 2025 I had a similar issue. Spent ages trying to resolve and ended up doing a repair install from the ISO, which fixed the problem. 1
Sheridan Posted October 20, 2025 Author Posted October 20, 2025 22 minutes ago, altecsole said: I had a similar issue. Spent ages trying to resolve and ended up doing a repair install from the ISO, which fixed the problem. That's my plan - waiting until the next holiday as its used every day
Baz Posted October 22, 2025 Posted October 22, 2025 (edited) omg Microsoft fixed my issue. basically my logs showed that I had some sort of registry or file corruption: 2025-10-20 13:59:36, Error CSI 00000a55 (F) Hydration failed for component Microsoft-Windows-Printing-Workflow, version 10.0.20348.4294, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} on file Windows.Graphics.Printing.Workflow.Native.dll with NTSTATUS -1073283059. Matching Component = Microsoft-Windows-Printing-Workflow, version 10.0.20348.3692, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}. FileHasForwardReverseDeltas = false, GenerateReverseDelta = true[gle=0x80004005] But: System detected a possible corruption with component Microsoft-Windows-Printing-Workflow, version 10.0.20348.3692, stating that one of its file Windows.Graphics.Printing.Workflow.Native.dll is not a ForwardORReverseDeltas. However upon checking the device WinSxS folder, I can see that the file is a F&R, hence there is a possible corruption rooted in the registry of this file, which ultimately lead to update installation failure. So she gave me a script to run to go thru my registry and look for corruptions and fix them. Ran it, then patched it. It worked. Have attached the script. GOOD LUCK!!!! InvalidDatascript.zip Edited October 22, 2025 by Baz
jezi55 Posted October 22, 2025 Posted October 22, 2025 I ended up having the same issue but did an inplace upgrade to 2025 and this resolved my issue.
Sheridan Posted October 22, 2025 Author Posted October 22, 2025 1 hour ago, Baz said: omg Microsoft fixed my issue. basically my logs showed that I had some sort of registry or file corruption: 2025-10-20 13:59:36, Error CSI 00000a55 (F) Hydration failed for component Microsoft-Windows-Printing-Workflow, version 10.0.20348.4294, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} on file Windows.Graphics.Printing.Workflow.Native.dll with NTSTATUS -1073283059. Matching Component = Microsoft-Windows-Printing-Workflow, version 10.0.20348.3692, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}. FileHasForwardReverseDeltas = false, GenerateReverseDelta = true[gle=0x80004005] But: System detected a possible corruption with component Microsoft-Windows-Printing-Workflow, version 10.0.20348.3692, stating that one of its file Windows.Graphics.Printing.Workflow.Native.dll is not a ForwardORReverseDeltas. However upon checking the device WinSxS folder, I can see that the file is a F&R, hence there is a possible corruption rooted in the registry of this file, which ultimately lead to update installation failure. So she gave me a script to run to go thru my registry and look for corruptions and fix them. Ran it, then patched it. It worked. Have attached the script. GOOD LUCK!!!! InvalidDatascript.zip 4.02 kB · 1 download Which log file did that appear in? Seems to be a different error to mine but the log file is enormous!
HC_Netman Posted October 22, 2025 Posted October 22, 2025 Don't want to be the suspicious type but be careful. This guy joined Sunday and has only posted 4 times (all in this thread). Sorry Baz if you are real! 1
Baz Posted October 22, 2025 Posted October 22, 2025 10 hours ago, Sheridan said: Which log file did that appear in? Seems to be a different error to mine but the log file is enormous! CBS.log for me.
Baz Posted October 22, 2025 Posted October 22, 2025 10 hours ago, HC_Netman said: Don't want to be the suspicious type but be careful. This guy joined Sunday and has only posted 4 times (all in this thread). Sorry Baz if you are real! hahaha all good. I would be too if i was on the other end. 1
Sheridan Posted October 24, 2025 Author Posted October 24, 2025 Repair install using Sept 25 ISO and then add Oct Cu worked for me too. MS seemed more concerned about our licensing so I gave up with that route. 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now