Baz

hahaha all good. I would be too if i was on the other end.

CBS.log for me.

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

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?

that doesnt sound right. I have just logged a call. I'll keep you in the loop

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 ?