Document Routing Agent - broken after May 2026 Updates

(7) Share

Report

Posted on by JR-18051649-0

After applying the Security patches for May 2026, our DRA server broke and stopped working. We are running Windows server 2022, D365F&O .46, and the latest DRA agent and after the patch was applied, DRA stopped working. We were getting an error about the splwow64.exe and not being able to connect. (see below).

We tried uninstalling and re-installing the DRA service followed by reboots, but that did not work. We also uninstalled DRA and deleted the user profile that we set it up with, and then logged back in and installed\configured the DRA again, but the jobs all still failed.

Finally, we started removing Windows updates one at a time, rebooted, and tried jobs until the jobs started printing again. After we uninstalled KB5087424 and rebooted, the DRA service started working again. Not sure if anyone else has run into this but hopefully this helps anyone else running into this issue.

Categories:

Dynamics 365 Finance

All responses (8)

Sort by

RW-19050810-0 8 on at

Like (3)

Report
Copy link

Link copied!

We are seeing the exact same issue on our Server 2022 environment after applying KB5087424 and have also been forced to roll back.
Suggested answer

Deepak Agarwal 9,065 on at

Like (1)

Report
Copy link

Link copied!

I would prefer to raise with Microsoft so if this is the root cause , they can publish some information to other customers or share some plan fix the issue in patch itself.
PT-20051559-0 6 on at

Like (2)

Report
Copy link

Link copied!

Thanks for posting, we are also seeing the same issue, not related to Dynamics, but other applications caused by KB5087424.
DS-22051823-0 7 on at

Like (2)

Report
Copy link

Link copied!

Hi, same thing on one of my client's servers in Azure.

I was trying to do all found suggestions for the splwow64.exe error - no luck. After uninstalling the update - it was back running.
CU27050020-2 4 on at

Like (1)

Report
Copy link

Link copied!

We're having the same issue on our Azure server. No issues after uninstall and pausing updates, but I would sure love a more permanent solution.
NE-27050648-0 6 on at

Like (2)

Report
Copy link

Link copied!

This needs more visibility.

Server 2022 RDS host serving a business application. It suddenly started throwing: splwow64.exe - Application Error: The application was unable to start correctly (0xc0000142)

Any 32-bit app that touched printing would crash on launch (reproduced it with plain 32-bit Notepad too). 64-bit printing worked fine. Hit it on two RDS hosts at once, which is what tipped me off it was a patch and not my environment.

Wasted hours chasing the print driver, VC++ redists, SFC/DISM (all clean) — none of it was the cause.

Root cause: Process Monitor (filter splwow64.exe) showed the process die with exit status -1073741502 (0xc0000142) immediately after touching:
C:\Windows\WinSxS\amd64_microsoft-windows-hotpatches_..._10.0.20348.5074_..._splwow64_hotpatch.exe

Build 20348.5074 = KB5087424, the May 12 2026 Azure hotpatch. The hotpatched splwow64 image fails to map.

Fix: Uninstall KB5087424, reboot. Printing immediately restored.

To stop it reinstalling run PS:
Hide-WindowsUpdate -KBArticleID KB5087424 -Confirm:$false
JS-29051256-0 2 on at

Like (0)

Report
Copy link

Link copied!

Does Microsoft have a plan to remedy this issue? Either by fixing the problem in KB5087424 that's causing the issue, or by providing a "fix" in GP? Skipping Windows Updates is not a good practice.
LB-03060845-0 3 on at

Like (0)

Report
Copy link

Link copied!

Same issue here.

we use DRA for 100+ printers, for a business invoicing application, on several Windows Server 2022 boxes in Azure.

the DRA was working fine until mid-may, when this splwow64.exe started to crash consistently when sending a print job, or a single test page job.

server is a Windows Server 2022 in Azure, with the Datacenter Hotpatch distribution, using Azure Update Manager for patching.

the error description in DRA logs, and in Event Viewer, was not useful at all, but after "out of the box" thinking, the date when failures started evoked a possibility that the Windows Update, which correctly applied in May, may have an adverse impact.

removing the KB5087424 then rebooting the servers allowed the printing jobs to pass successfully.

Hope that MS had a corrective action in the short-term plans.

we create a couple SRs on MS Support, and also an Impact Report, a new feature, from Azure Portal.

Thx for sharing your pain previously here, this publicity helped us to go back to production, which was halted for 3 weeks...