Sage 50 QUANTUM U.S EDITION WIN 11 24H2 problem!!?

Suggested

after updating my windows to the latest one, sage started to be too slow, when i returned the windows to 10, problem resolved, but after updating again to the windows 11 the problem comes back, is this normall is the sage is not supported by the latest windows 11 update, if someone faced this problem and resolved please tell us the solution

  • 0

    Hi Bashar,

    Sage 50 US is supported on Windows 11 operating systems, and there are no specific outstanding issues between Sage 50 US and Windows 11.   

    However as updates are released things in the environment are changed that may impact how Sage 50, other applications, and the OS overall performs.  For example Win 11 24H2 introduces several network security updates/changes that while improving security, have the potential to slow down network processing.  Its also worth noting that each update to your operating system consumes more virtual and physical resources which, if are already stretched thin, can slow things down even in the local environment.

    What type of slowness specifically are you experiencing?  Opening a company? Processing a transaction? Running a report?

    Thank you.

  • 0 in reply to DonaldC

    Hi, Thanks for your response, the slowness i'm facing it's in everything, from opening the company, to all stuff inside, inventory, invoice, all of it, even when i make refresh it takes more than 1 min every time i make refresh . Also the problem isn't with the server its with my pc that is connected via local network, all of my switches are gigabyte no problem with them, i tried sending files via network also its working fine, the problem is just with sage application, its too slow and i've used to work on it without any problems, on the other desktops with win 10 there's no problem.

  • 0 in reply to Bashar Kaeen
    SUGGESTED

    Hi Bashar,

    The article below contains a few things that may help:

    Performance issues on a standalone or network

    Thank you.

  • 0 in reply to DonaldC

    Hi, Again, I've tried all of them, same problem

  • 0 in reply to DonaldC

    any other solution if possible?

  • 0 in reply to Bashar Kaeen
    SUGGESTED

    Unfortunately I don't have any further advice with regard to the Sage 50 US program specifically, I was able to locate some other material online where network impacts have been mitigated by making changes (i.e. disabling) to things like SMB signing (which is enabled by default in 24H2), but this can make your system less secure and you'll want to discuss with your administrators before making changes such as this.

    Thank you.

  • 0 in reply to DonaldC

    i tried that, also same problem, maybe there is somthing conflicting sage, if we know all the services that refers to speed of the network to check them if they're working fine or not

  • 0

    One of my clients runs Sage 50 and after the Win 11 24H2 Update, Sage 50 either slowed to a crawl, or would not load at all (Peachw.exe at 0% CPU...Startup / Login screen would never appear). After researching and not finding any answers, I finally did a Repair install. In my case, I used the latest Sage 50 Upgrade package (Sage50_2024.0.0.Upgrade.exe...used Repair Option) then PTXA2024.0.1.exe, then Tax2025Feb_Release2024.exe. Rebooted after the installations, and performance returned to normal (normal as it can be with Sage 50...). During the process I saw there was later release. I will have to install that in near term. 

    So for those of you experiencing this, you may want to try reinstalling. 

    Lonnie

  • 0 in reply to LThibx
    1. I did reinstallation for sage , also i reinstalled the full system i install the latest 24h2 image from windows site and again same problem, this wwas 3months ago but now im using the 23h2 win 11 and didn't tried again idk if now they fixed the problem
  • 0 in reply to LThibx
    1. I did reinstallation for sage , also i reinstalled the full system i install the latest 24h2 image from windows site and again same problem, this wwas 3months ago but now im using the 23h2 win 11 and didn't tried again idk if now they fixed the problem