Share via

Outlook 2021 LTSC on Windows 11 – Emails delayed ~30 minutes, OWA instant, Windows 10 unaffected (Exchange 2016)

Hu Haowen 0 Reputation points
2026-02-08T11:02:06.8033333+00:00

Body

Hello,

We are experiencing a client-side mail delivery delay issue affecting Outlook 2021 LTSC on Windows 11 in an on-premises Exchange Server 2016 environment.

Environment

Exchange Server 2016 (on-premises)

Outlook 2021 LTSC

Windows 11 (affected)

Windows 10 (not affected)

Cached Exchange Mode enabled

Issue observed across multiple users and mailboxes

Issue Description

some users have reported that new emails take more than 30 minutes to appear in Outlook.

However:

Emails are delivered instantly in Outlook Web App (OWA)

The same mailboxes on Windows 10 Outlook clients work normally

No Exchange transport, database, or DAG issues are observed

This strongly suggests the issue is client-side and specific to Windows 11 + Outlook 2021 LTSC.

Observed Behavior

  • Outlook does not display new emails immediately
  • The issue does not occur in OWA
  • The issue started recently without any Exchange-side changes

Troubleshooting Performed

Verified Exchange transport and mailbox databases are healthy

Confirmed issue is reproducible only on Windows 11 clients

Compared behavior with Windows 10 (working as expected)

Exchange | Exchange Server | Management
Exchange | Exchange Server | Management

The administration and maintenance of Microsoft Exchange Server to ensure secure, reliable, and efficient email and collaboration services across an organization.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. FIRAT BOYAN 380 Reputation points Microsoft External Staff
    2026-02-25T23:05:50.89+00:00

    The behaviour you describe clearly indicates that Exchange transport and mailbox delivery are functioning correctly.

    OWA receives messages instantly, which confirms that the mailbox database, transport service, and DAG replication are healthy. The issue is therefore confined to the MAPI client layer on Windows 11 running Outlook 2021 LTSC.

    In this scenario the delay is almost always related to the client side MAPI notification mechanism, OST synchronisation, Windows Search indexing, or a recent Windows 11 networking stack update.

    Below is a structured diagnostic and remediation approach suitable for Exchange 2016 environments.

    1. Validate the connection mode in Outlook

    Open Outlook and hold Ctrl while right clicking the Outlook icon in the system tray. Select Connection Status.

    Confirm the following:

    • Protocol shows MAPI HTTP
    • Status is Established
    • Avg Response is low and stable
    • No repeated reconnect cycles

    If you see frequent reconnect attempts or RPC HTTP instead of MAPI HTTP, investigate Autodiscover configuration.

    Verify on Exchange:

    Get-OrganizationConfig | fl MapiHttpEnabled

    It must be True.

    2. Confirm this is Cached Mode synchronisation latency

    Since Cached Exchange Mode is enabled, Outlook relies on OST background synchronisation and push notifications.

    Temporarily disable Cached Mode on an affected machine:

    File → Account Settings → Account Settings → Change → Untick Use Cached Exchange Mode.

    Restart Outlook.

    If mail appears instantly in Online Mode, the issue is OST or sync related.

    If delay still occurs in Online Mode, the issue is notification or network related.

    3. Check Windows 11 TCP notification behaviour

    Windows 11 has introduced networking stack adjustments that affect long lived HTTP sessions.

    Exchange 2016 relies on MAPI HTTP persistent connections for push notifications.

    On affected Windows 11 clients, verify the following registry values:

    HKCU\Software\Microsoft\Office\16.0\Outlook\Cached Mode

    Create or confirm:

    DWORD: SyncWindowSetting

    For testing, reduce the cached window to 3 months or lower.

    Large OST files combined with Windows 11 Search indexing can delay UI refresh.

    4. Disable Windows Search integration test

    Windows 11 Search integration has been observed to delay UI refresh in Outlook 2021 LTSC.

    Test by disabling indexing for Outlook:

    Control Panel → Indexing Options → Modify Untick Microsoft Outlook.

    Restart Outlook and test mail arrival time.

    If issue resolves, rebuild the index or recreate OST.

    5. Recreate OST profile cleanly

    Do not reuse the existing profile.

    1. Close Outlook

    Control Panel → Mail → Show Profiles

    Create a new profile

    Do not copy existing settings

    Let Autodiscover configure the mailbox

    This eliminates corrupted OST and MAPI subscription states.

    6. Validate client push notifications

    Exchange 2016 push relies on notification subscriptions maintained over MAPI HTTP.

    Check if the client maintains active subscriptions.

    On the client:

    Press Ctrl and right click Outlook tray icon → Connection Status.

    Observe if connections remain stable or frequently drop.

    Frequent drops indicate:

    • TLS inspection by endpoint security
    • Windows 11 firewall update
    • Network device closing idle HTTPS sessions

    Test temporarily with endpoint protection disabled.

    7. Verify TLS and Schannel configuration

    Recent Windows 11 updates may alter TLS negotiation.

    Exchange 2016 should support TLS 1.2.

    Confirm TLS 1.2 is enabled on the Exchange server and client.

    On Exchange:

    Get-TlsCipherSuite

    On Windows 11 verify Schannel registry settings allow TLS 1.2 client mode.

    Mismatch can cause delayed reconnection cycles without full failure.

    8. Check Outlook build level

    Outlook 2021 LTSC receives different update cadence compared to Microsoft 365 Apps.

    Confirm the build number:

    File → Office Account → About Outlook.

    Ensure latest cumulative update for LTSC is installed.

    There have been fixes related to delayed folder sync in recent builds.

    9. Test MAPI over HTTP keep alive behaviour

    Windows 11 may close idle HTTP sessions earlier than Windows 10.

    As a diagnostic step, temporarily increase KeepAliveTime:

    Registry on Windows 11 client:

    HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

    Restart the machine.

    This prevents premature session termination which can delay push notifications.

    Most Probable Root Causes

    Based on your description and field experience in Exchange 2016 deployments, the most common causes are:

    • Corrupted OST combined with Windows 11 indexing
    • Windows 11 network stack update affecting MAPI HTTP push
    • Endpoint security performing HTTPS inspection
    • Outlook 2021 LTSC build regression
    • Idle session timeout on firewall

    Since Windows 10 clients function normally and OWA is instant, Exchange itself is not the source of the delay.

    Test Online Mode on one affected client

    Create new Outlook profile

    Rebuild OST

    Temporarily disable Windows Search integration

    Validate stable MAPI HTTP connection

    Confirm latest Outlook 2021 LTSC build

    Inspect firewall idle timeout settings

    If you can confirm whether Online Mode removes the delay, we can narrow this further to either sync engine or notification layer with precision.The behaviour you describe clearly indicates that Exchange transport and mailbox delivery are functioning correctly.

    OWA receives messages instantly, which confirms that the mailbox database, transport service, and DAG replication are healthy. The issue is therefore confined to the MAPI client layer on Windows 11 running Outlook 2021 LTSC.

    In this scenario the delay is almost always related to the client side MAPI notification mechanism, OST synchronisation, Windows Search indexing, or a recent Windows 11 networking stack update.

    Below is a structured diagnostic and remediation approach suitable for Exchange 2016 environments.

    1. Validate the connection mode in Outlook

    Open Outlook and hold Ctrl while right clicking the Outlook icon in the system tray.
    Select Connection Status.

    Confirm the following:

    • Protocol shows MAPI HTTP
    • Status is Established
    • Avg Response is low and stable
    • No repeated reconnect cycles

    If you see frequent reconnect attempts or RPC HTTP instead of MAPI HTTP, investigate Autodiscover configuration.

    Verify on Exchange:

    Get-OrganizationConfig | fl MapiHttpEnabled

    It must be True.

    2. Confirm this is Cached Mode synchronisation latency

    Since Cached Exchange Mode is enabled, Outlook relies on OST background synchronisation and push notifications.

    Temporarily disable Cached Mode on an affected machine:

    File → Account Settings → Account Settings → Change → Untick Use Cached Exchange Mode.

    Restart Outlook.

    If mail appears instantly in Online Mode, the issue is OST or sync related.

    If delay still occurs in Online Mode, the issue is notification or network related.

    3. Check Windows 11 TCP notification behaviour

    Windows 11 has introduced networking stack adjustments that affect long lived HTTP sessions.

    Exchange 2016 relies on MAPI HTTP persistent connections for push notifications.

    On affected Windows 11 clients, verify the following registry values:

    HKCU\Software\Microsoft\Office\16.0\Outlook\Cached Mode

    Create or confirm:

    DWORD: SyncWindowSetting

    For testing, reduce the cached window to 3 months or lower.

    Large OST files combined with Windows 11 Search indexing can delay UI refresh.

    4. Disable Windows Search integration test

    Windows 11 Search integration has been observed to delay UI refresh in Outlook 2021 LTSC.

    Test by disabling indexing for Outlook:

    Control Panel → Indexing Options → Modify
    Untick Microsoft Outlook.

    Restart Outlook and test mail arrival time.

    If issue resolves, rebuild the index or recreate OST.

    5. Recreate OST profile cleanly

    Do not reuse the existing profile.

    Close Outlook

    Control Panel → Mail → Show Profiles

    Create a new profile

    Do not copy existing settings

    Let Autodiscover configure the mailbox

    This eliminates corrupted OST and MAPI subscription states.

    6. Validate client push notifications

    Exchange 2016 push relies on notification subscriptions maintained over MAPI HTTP.

    Check if the client maintains active subscriptions.

    On the client:

    Press Ctrl and right click Outlook tray icon → Connection Status.

    Observe if connections remain stable or frequently drop.

    Frequent drops indicate:

    • TLS inspection by endpoint security
    • Windows 11 firewall update
    • Network device closing idle HTTPS sessions

    Test temporarily with endpoint protection disabled.

    7. Verify TLS and Schannel configuration

    Recent Windows 11 updates may alter TLS negotiation.

    Exchange 2016 should support TLS 1.2.

    Confirm TLS 1.2 is enabled on the Exchange server and client.

    On Exchange:

    Get-TlsCipherSuite

    On Windows 11 verify Schannel registry settings allow TLS 1.2 client mode.

    Mismatch can cause delayed reconnection cycles without full failure.

    8. Check Outlook build level

    Outlook 2021 LTSC receives different update cadence compared to Microsoft 365 Apps.

    Confirm the build number:

    File → Office Account → About Outlook.

    Ensure latest cumulative update for LTSC is installed.

    There have been fixes related to delayed folder sync in recent builds.

    9. Test MAPI over HTTP keep alive behaviour

    Windows 11 may close idle HTTP sessions earlier than Windows 10.

    As a diagnostic step, temporarily increase KeepAliveTime:

    Registry on Windows 11 client:

    HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

    Restart the machine.

    This prevents premature session termination which can delay push notifications.

    Most Probable Root Causes

    Based on your description and field experience in Exchange 2016 deployments, the most common causes are:

    • Corrupted OST combined with Windows 11 indexing
    • Windows 11 network stack update affecting MAPI HTTP push
    • Endpoint security performing HTTPS inspection
    • Outlook 2021 LTSC build regression
    • Idle session timeout on firewall

    Since Windows 10 clients function normally and OWA is instant, Exchange itself is not the source of the delay.

    Test Online Mode on one affected client

    Create new Outlook profile

    Rebuild OST

    Temporarily disable Windows Search integration

    Validate stable MAPI HTTP connection

    Confirm latest Outlook 2021 LTSC build

    Inspect firewall idle timeout settings

    If you can confirm whether Online Mode removes the delay, we can narrow this further to either sync engine or notification layer with precision.

    If this resolution has been helpful, I kindly request that you take a moment to click on

    ACCEPTED-ANSWER and select “Yes” to indicate that the response was helpful. Should you have any further questions or require additional assistance, please do not hesitate to let me know.

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.