No release date has been announced for a permanent fix to the Sage 50 problems caused by KB5132061; as of November 18, 2026, Sage’s current workaround is to uninstall the November update from affected computers.^1^
Remove KB5132061 temporarily
Uninstalling a security update removes its security protections, so use this only on computers where the Sage 50 failure prevents business operations.
- Close Sage 50 and create or confirm a current backup of the company data.
- Open Start → Settings → Windows Update.
- Select Update history.
- Under Related settings, select Uninstall updates.
- Locate KB5132061, select Uninstall, and restart Windows.
- Test Sage 50 and confirm that the affected company opens and operates normally.
These are Microsoft’s supported Windows 11 update-removal steps.^2^ Sage’s advisory identifies rollback as the currently known remedy for the Sage 50 crash.^3^
If KB5132061 is not listed, it might not be removable through Settings. Do not roll Windows back to an older feature version solely for this issue; contact Sage support for the next supported recovery option.
Current fix status
Microsoft’s KB5132061 release notes do not list the Sage 50 regression as a known issue or announce a correction date. The documented fixes in KB5132061 concern other issues, while its listed unresolved issue concerns SQL Server linked-server connections—not Sage 50.^4^
Sage has acknowledged that Sage 50 can close unexpectedly after a Windows update, but its announcement currently directs customers to the rollback guidance rather than announcing a Sage patch or Microsoft update date.^5^
Monitor these two pages before reinstalling the update:
- Sage’s Crashing after installing Windows updates advisory.
- Microsoft’s KB5132061 release notes.
Reinstall KB5132061—or a later cumulative update—only after Sage or Microsoft explicitly confirms that the Sage 50 compatibility problem is resolved. For business-managed devices, also report the impact through the organization’s Sage support channel and Microsoft Support so the affected Sage version, Windows version, and crash details are recorded.
References