If Sage opens normally but freezes when you try to pay a vendor, check the computer’s recent Windows updates. A reported issue after the November security updates is interrupting transaction screens in Sage 50.
In the reported case, Sage 50 2026.2 froze and closed when opening Vendors > Pay Bills. Other parts of Sage still worked, and computers without the update continued working normally. Removing KB5132043 was reported to resolve the problem.
The update and crash details
Microsoft identifies KB5132043 as its November 10 hotpatch security update. On Windows 11 26H2, it corresponds to OS build 26300.9911.
The reported crash contained these details:
- Application:
Peachw.exe, version2026.2.0.234 - Faulting module:
Pchctls.dll - Exception code:
0xc000041d
A verified answer in Sage Community Hub also links transaction-window crashes to November updates and recommends temporarily removing the affected update. That answer lists KB5132061, KB5132059 and KB5131096. KB5132043 comes from the separate incident described above, so the installed update needs to be checked on each affected computer.
The temporary workaround
For a computer with KB5132043 installed and the same Pay Bills crash, have your IT team coordinate the rollback:
- Confirm the update number and crash details, check that a current Sage company-data backup is available, and close Sage and other open applications.
- Open Settings > Windows Update > Update history > Uninstall updates. Remove KB5132043 if Windows offers it, then restart. If removal is unavailable or fails, have IT review the machine before trying other changes. Microsoft’s uninstall guidance describes the Windows workflow.
- Reopen Sage and verify that Vendors > Pay Bills works.
- Have IT temporarily block KB5132043 from reinstalling on affected computers while awaiting a correction from Microsoft or Sage. Review the hold regularly and test the correction before resuming deployment.
This rollback removes a security update, so the hold needs an owner and a review date. Keep the exception limited to affected computers and return them to supported patching as soon as a working resolution is available.
If Sage still crashes after the rollback, send your IT team the new error details. Removing additional updates without checking the results can make troubleshooting harder.
Help for Boston businesses using Sage
If your accounting team is stuck at Pay Bills, contact BMIT with the computer name, installed KB number and crash message. We can help review the affected workstation and plan the next step.
Boston Managed IT
