KB5132061: Sage 50 crashes after November Windows updates

Call: Known issue. Sage says Sage 50 Accounting “starts crashing after installing Windows updates,” and it blames the November 10 Windows security updates. Sage’s only fix right now is to uninstall the update on the affected PCs. It also recommends “pausing Windows updates until Microsoft releases an update patch.” Microsoft hasn’t listed this as a known issue. Our take is narrower than Sage’s: hold November only on the PCs that run Sage 50, and keep patching everything else.

What breaks: Sage 50 opens and you can log in, then it closes as soon as you open a task or transaction window. One IT shop traced a crash in Vendors > Pay Bills on Sage 50 2026.2 to Peachw.exe 2026.2.0.234, faulting module Pchctls.dll, exception 0xc000041d, and says removing the hotpatch KB5132043 fixed it. In Sage’s community forum, several users say uninstalling KB5132061 brought Sage back, and two commenters on BleepingComputer report the same crash with on-prem Sage 50.

Who’s hit: Sage 50 (US) users on Windows 10 or 11 with the November updates. Sage’s knowledge base article (opens in a new tab) names KB5132061 (Windows 11 24H2/25H2/26H2), KB5132059 (26H1) and KB5131096 (Windows 10) first, and then gives a longer table that includes KB5132043, KB5131087, KB5131085, KB5131080, KB5131090 and others. That table also includes things that aren’t November security updates, such as KB5127936, October’s optional preview. So read it as “anything from this month,” not as an exact list. A few forum users still crash with none of the listed updates installed, and one still crashed after uninstalling. Whatever the cause is, it may not be the update alone.

Workaround:

On affected Sage machines only: Settings > Windows Update > Update history > Uninstall updates, remove the November update, restart, and test Sage.
Then pause or block that update on those machines so Windows Update doesn’t put it straight back. One forum user found it trying to reinstall within hours. Give the exception an owner and a review date. It’s a security update you’re leaving off.
Sage warns that “uninstalling these Windows updates can sometimes cause printing issues”. If that happens, remove the printer and add it again.
Back up the Sage company data before you start.

We’ll update this when Microsoft or Sage ships a real fix.

Sources: Sage KB: Crashing after installing Windows updates (opens in a new tab), Sage Community Hub announcement (opens in a new tab), Sage Community Hub thread (opens in a new tab), BMIT on KB5132043 (opens in a new tab), BleepingComputer comments (opens in a new tab).

KB5132061: Sage 50 crashes after November Windows updates

Sources

More from November 2026 patch cycle