Sage 50 US Version 2026 closes the moment you open a transaction window after installing the November 2026 Windows security update. Sage staff confirmed the cause on their community forum on November 11–12, 2026, and users report the same fix working: remove the update, restart, and Sage 50 opens transactions again. No reinstall of Sage 50 is needed.
Quick Fix Summary
- Problem: Sage 50 Version 2026 closes when opening any transaction window after installing Windows update KB5132061 (Windows 11) or KB5132059 / KB5131096 (Windows 10).
- Fix: Uninstall KB5132061 from Settings → Windows Update → Update history → Uninstall updates, then restart your PC.
- After the fix: Pause Windows updates so the same update does not install itself again overnight.
Technical Root Cause
| Error Code | Affected Version | Root Cause | Current Status |
|---|---|---|---|
| KB5132061 | Sage 50 US Version 2026 on Windows 11 | November 2026 security update breaks Sage 50 transaction windows — Task screens close on open, Maintain screens still work | No patch from Sage or Microsoft yet; uninstall is the verified fix |
| KB5132059 / KB5131096 | Sage 50 US Version 2026 on Windows 10 | Same November 2026 security update set, Windows 10 builds | Same — uninstall is the verified fix |
How to Confirm KB5132061 Is Installed
Open PowerShell and run:
Get-HotFix -Id KB5132061If it returns a row with an install date, the update is on the machine. On Windows 10, check for KB5132059 or KB5131096 the same way.
Step-by-Step: Fix the Sage 50 Crash
Step 1 — Back Up Your Sage 50 Company Data
In Sage 50, go to File → Backup and save a fresh copy of your company file before you change anything in Windows Update.
Before you touch Windows Update — back up your company file
Uninstalling a security update is low risk, but your Sage 50 company data is the one thing you cannot rebuild from scratch. A fresh File → Backup in Sage 50 covers the company file. For a full safety net, Acronis Cyber Protect images the whole drive, so a bad update — or a bad uninstall — costs you minutes, not a business day. (Affiliate link — DebugRadar earns a commission if you buy through it.)
Step 2 — Uninstall KB5132061 from Settings
- Open Settings → Windows Update → Update history → Uninstall updates.
- Find KB5132061 (Windows 11) or KB5132059 / KB5131096 (Windows 10).
- Select it, click Uninstall, and confirm.
- Restart when Windows asks.
This is the path Sage staff pointed users to, and the path users confirmed working.
Step 3 — Command-Line Alternative
If Settings will not list the update, run this from an elevated PowerShell window:
wusa /uninstall /kb:5132061 /quiet /norestartThen restart manually:
shutdown /r /t 0Note: on some Windows 11 builds, wusa reports that the update cannot be removed. If that happens, use the Settings path in Step 2 — that is the path users confirmed working.
Step 4 — Verify Sage 50 Opens Again
- Open Sage 50 and open any transaction window — a sales invoice, a purchase order, a receipt.
- If the window opens and stays open, the fix worked.
- Re-run
Get-HotFix -Id KB5132061— it should now return nothing.
Step 5 — Stop the Update Coming Back
Users reported the update reinstalling itself overnight and having to uninstall it a second time. Right after the fix, go to Settings → Windows Update → Pause updates and pause for the longest period offered. Check with Sage support before unpausing, and reinstall the update — or its replacement — once Sage or Microsoft ships a fix.
FAQ
Will uninstalling KB5132061 leave my PC unprotected?
It removes one month of security fixes, so treat it as a short-term trade-off. Keep your firewall and antivirus on, pause updates, and reinstall the update or its replacement once Sage or Microsoft ships a fix. Do not leave it uninstalled for months.
Do I need to reinstall Sage 50?
No. The problem is the Windows update, not Sage 50. Users who uninstalled the update had Sage 50 working again with no reinstall.
Why does Sage 50 still crash after I uninstalled the update?
Check the update actually left — run Get-HotFix -Id KB5132061. If it is still listed, it reinstalled itself: uninstall it again and pause updates immediately. Also confirm the crash is in transaction windows (Task screens). A crash somewhere else is a different problem.
Sources: Sage Community Hub thread on Sage 50 Version 2026 crashing after the November 2026 security update (communityhub.sage.com).