Sage 100

 View Only

  • 1.  Windows 11 Release 24H2 Slow Loading Sage 2024 Standard

    Posted 11-19-2025 13:32

    Client recently replaced their WIN 10 workstations with Windows 11 24H2 - 16 GB RAM

    Programs open very slowly now.  Once the program is open, speed is acceptable.  Migrated to 64-bit, no change.  

    Verified path in ICON properties was mapped, not URL.

    Similar problem in Windows 10 a few years back, Sage said it was an MSFT issue.

    IT said they were excluding the Sage extensions per the AV KB.

    Thoughts?



    ------------------------------
    Jeff Schwenk
    Owner
    Bottomline Software, Inc.
    Waynesboro VA
    (540) 221-4444

    Improving bottom lines for over 25 years!
    ------------------------------


  • 2.  RE: Windows 11 Release 24H2 Slow Loading Sage 2024 Standard

    Posted 11-19-2025 21:32

    Are the shortcut properties for the Target and Start in a UNC path or a mapped drive?  if it's a UNC path change it to a mapped drive to reduce DNS resolution latency.



    ------------------------------
    Doug Higgs
    Midwest Commerce Solutions, Inc
    (312) 315-0960
    Chauffeur, Chef, and Personal Assistant to Sprinkles
    ------------------------------



  • 3.  RE: Windows 11 Release 24H2 Slow Loading Sage 2024 Standard

    Posted 11-20-2025 04:31

    If the issue is DNS, use the server IP address instead of the server name.



    ------------------------------
    Phil McIntosh
    Friendly Systems
    ------------------------------

    Original Message


  • 4.  RE: Windows 11 Release 24H2 Slow Loading Sage 2024 Standard

    Posted 11-20-2025 09:15

    Gemini 3 did some hallucinating but came up with a couple good suggestions 

    Because Sage 100 Standard relies heavily on direct SMB file locking (unlike the SQL version), the Windows 11 24H2 SMB Signing requirement is almost certainly the cause of your "slow load, fast run" symptom. The workstation is pausing to negotiate a signed SMB packet for the initial MAS90\Home directory access, timing out, and then falling back.

    Here are the troubleshooting steps specifically for Sage 100 Standard on Windows 11 24H2.

    1. The Primary Fix: Disable SMB Client Signing (Critical for Sage 100)

    I can't vouch for this one .. 

    This is the most common fix for 24H2. Since Sage 100 Standard creates thousands of file locks (?) across the network, the new 24H2 requirement for signed packets creates a massive bottleneck during the initial handshake.

    Run this on the Windows 11 Workstation:

    1. Right-click Start > Terminal (Admin) or PowerShell (Admin).

    2. Run:

      <response-element class="" ng-version="0.0.0-PLACEHOLDER"></response-element>
      PowerShell 
      Set-SmbClientConfiguration -RequireSecuritySignature $false
      <response-element class="" ng-version="0.0.0-PLACEHOLDER"></response-element>

    3. Restart the workstation.

    2. The "Default Printer" Timeout (Classic MAS 90 Issue)

    Sage 100 checks the Windows Default Printer immediately upon launch to load form settings. If 24H2 has "offline" printer security enabled or if the default printer is a network printer causing a handshake delay, Sage will hang at the splash screen.

    3. Validating the "Standard" Path (UNC vs. Mapped)

    Use mapped drive

    4. Disable "Sage Product Enhancement Program" (PEP)

    5. Antivirus Exclusions (ProvideX Specifics)



    ------------------------------
    Wayne Schulz
    wayne@s-consult.com
    Schulz Consulting
    (860) 516-8990
    Connecticut
    ------------------------------



  • 5.  RE: Windows 11 Release 24H2 Slow Loading Sage 2024 Standard

    Posted 11-20-2025 10:40

    Thanks @Wayne Schulz.

    @Doug Higgs - Shortcut is mapped drive.

    @Phil McIntosh - Good thought.  The shortcut is a mapped drive.  I will try if Wayne's suggestion comes up short



    ------------------------------
    Jeff Schwenk
    Owner
    Bottomline Software, Inc.
    Waynesboro VA
    (540) 221-4444

    Improving bottom lines for over 25 years!
    ------------------------------

    Original Message


Related Content