Forum Discussion

mafb9401's avatar
mafb9401
Copper Contributor
Nov 12, 2026

Sage 50 Application Crashes after Security Update 10-Nov 2026

In case anyone else has recently encountered issues with functions in Sage 50 US crashing suddenly, it is related to compatibility issues in the latest Microsoft Security Update released this week. Having already worked over Sage to no avail, I thought to check for recent Windows Updates. Indeed, the affected user's PC had installed the latest security update the night before (KB5132061, KB5132059, KB5121096).

 

I removed the update and disabled windows updates on all Accounting Department computers as I suspect a 30-day pause won't be enough for a fix to come from Microsoft. After retrieving data from Event Viewer, I went to Sage's support page to send up a notice and discovered they are already aware of the issue.

In the meantime, Sage's official answer is to remove the latest security patch and restart. I can confirm that the application does work normally after removal. 

Note, the application will open normally, but when trying to open database items (Invoices, POs, etc.) it will crash at launch of those functions. 

 

Below is the Event Viewer record for the crash, it highlights the affected dll in the Sage application that fails to respond after the security update. 

 

Faulting application name: Peachw.exe, version: 2026.0.0.82, time stamp: 0x68ee9cae

Faulting module name: Pchctls.dll, version: 2026.0.0.82, time stamp: 0x68ee999a

Exception code: 0xc000041d

Fault offset: 0x000512ce

Faulting process id: 0xECC

Faulting application start time: 0x1DD72B6CB4581B8

Faulting application path: Program Files (x86)....Peachw.exe

Faulting module path: Program Files (x86)....Pchctls.dll

Report Id: 13719643-0442-4a6e-ad55-f15c42759163

4 Replies

  • mafb9401's avatar
    mafb9401
    Copper Contributor

    Update: 

    I've removed the KB5132061 update from our accounting team's workstations multiple times. The updater service is disabled in Windows and reenables after each restart, then subsequently reinstalls KB5132061. So, I've changed the login ID for the service and put the brakes on that.

    Note, I performed this task after setting updates to be paused for the next 30 days didn't work, and neither did creating a unique OU in Active Directory and attaching these endpoints to it with a group policy object disabling Automatic Updates.

    The update reinstalls after every system restart. 

    I've now uninstalled again....(each time has been elevated, so it's not a user issue) and this time completely cleaned out the Windows "SoftwareDistribution" folder on one of the endpoints to see if I can finally put the brakes on this. If that still fails to do the trick, I'll advise again. 

    • mafb9401's avatar
      mafb9401
      Copper Contributor

      Update: 20 November 2026, Preview Update KB5132057 (Build 26300.10075) appears to correct the glitch that's crashing Sage 50. There's no mention of it in the notes on the page, but I've just applied it to one to the test workstation, and Sage 50 is able to run its higher functions without crashing. Unfortunately, it's still in Preview; so, it won't see general rollout until the middle of December. 

  • PeterTech99's avatar
    PeterTech99
    Copper Contributor

    Use my screenshots as a reference for what to do:  A, A1 and then 1, 2, 3, 5 and 5a [the numbers and letters are in the top right-hand corner for each screenshot. Rather then trying to perform a "System Restore" [my attempts on 3 computers actually crashed those computers - not sure why] you should use the "powershell" command line within Windows-11, run as an administrator, to perform the Windows-11 update(s) that are affecting your system.  Make sure to "Pause" Windows-11 updates for at least 4 to 6 weeks before you re-start your PC after removing the updates   Hope this helps others. I spoke to Sage but they have not yet posted my findings.  Also, I am running a Windows-11 peer-to-peer network; I did not have to remove the Windows-11 update on the SAGE50 server - just on the workstations.  Good luck!

     

  • Vasjohsin's avatar
    Vasjohsin
    Copper Contributor

    In the Microsoft Q&A community, users reported the exact same situation: after installing the Windows update on the evening of November 10, 2026, the Sage Peachtree program crashed.