Sage 50 Crashing After the November 2026 Windows Update (KB5132061): What to Do

If Sage 50 Accounting started crashing this week, the Windows security updates released on 10 November 2026 are the likely cause. Sage has linked the crashes to those updates, including KB5132061 and KB5132059. Its current workaround is to remove the update from affected PCs and pause Windows Update. No fix from Microsoft or Sage had been announced when this was written on 13 November 2026.

Removing a security update is a trade-off, not a free fix. The steps below follow Sage's guidance and add the checks we would make before doing it on a business PC.

What are people seeing?

Sage published a knowledgebase article on 11 November, updated on 13 November, describing Sage 50 Accounting crashing or closing during normal tasks after Windows updates. In Sage's community forum, users describe the program opening normally and then closing when they open a transaction window such as an invoice, purchase order or check. One report on Microsoft's Tech Community lists the faulting module as Pchctls.dll with exception code 0xc000041d, which may help your IT team match the symptom in Event Viewer.

These reports concern Sage 50 Accounting in the US. As of 13 November we had not seen an equivalent notice for Sage 50 Accounts in the UK. If you use the UK product and see similar crashes, check Sage UK's support pages before changing anything.

Which Windows updates are involved?

Sage's article lists about twenty November updates across Windows 10, Windows 11 and Windows Server. The ones most business desktops will have are:

Sage's article also names KB5121096 in one place and KB5131096 in another, so check the update history on the affected PC rather than relying on a single number. Servers that run Sage, including those hosting the company data for other users, are on the same list.

Microsoft's own pages for KB5132061 and KB5132059 did not mention Sage or other application crashes on 13 November. Microsoft separately confirmed that some devices could not install KB5132061, which is a different problem.

Sage's workaround

Sage notes that removing the update can sometimes affect printing, in which case reinstalling the printer may help. Some users have been told the update cannot be uninstalled; Sage's fallback is System Restore. Forum reports also suggest that fixing one machine is not always enough on a network: every PC and server that runs Sage may need the same check.

Before you uninstall a security update

Security updates close vulnerabilities, so taking one off leaves that PC more exposed until a fixed update is installed. Limit the risk:

• Back up the Sage company data and confirm the backup opens before changing anything.
• Remove the update only from machines that run Sage and actually crash. Leave it installed everywhere else.
• Pause updates with an end date, not indefinitely, and put a reminder in the diary to review it.
• Keep antivirus or endpoint protection running and avoid using affected PCs for general web browsing or opening unexpected attachments.
• Record which PCs had the update removed, so they are not forgotten when a fix arrives.
• Check Sage's article and Microsoft's release notes regularly, and reinstall updates once a fix is confirmed.

How to stop the next update causing the same problem

This is not the first time a Windows update has broken accounting or line-of-business software, and it will not be the last. The practical defence is to stage updates: install them first on one or two test or low-risk machines, check that the applications your business depends on still work, then release them to everyone else a few days later.

In Microsoft 365 businesses this is usually done with Windows Update rings in Intune, which let you hold updates for a group of devices and pause them centrally rather than PC by PC. Our Intune setup checklist covers update rings, and Microsoft 365 and Intune support explains how we manage them for clients.

If Windows updates are currently installed by each user without a test group, that is worth changing whatever happens with this Sage issue. BPro's managed IT services include patch management with an agreed approval process, so a problem update can be held back for the affected systems without leaving the rest of your devices unpatched.