Microsoft Teams Desktop App - Chat History Intermittently Missing and Unable to Send Messages (Web Version Works Fine)

Question

Microsoft Teams Desktop App - Chat History Intermittently Missing and Unable to Send Messages (Web Version Works Fine)

Alfin CP 0

Hi Team,

We are experiencing an intermittent issue with the Microsoft Teams desktop application in our organization, and we would appreciate any guidance or recommendations.

Issue Summary:

Only some users are affected (not organization-wide).
The issue occurs only in the Microsoft Teams desktop application.
Users accessing Teams through the web browser do not experience this issue.

Symptoms:

Chat history intermittently disappears or does not load in the desktop app.
Occasionally, users are unable to send messages from the desktop application.
The issue is intermittent and reoccurs after a few days, even after applying a temporary fix.

Temporary Workarounds:

When chat history is missing, resetting the Teams app via: Settings > Apps > Installed Apps > Microsoft Teams > Advanced Options > Reset restores normal functionality.
When users cannot send messages, quitting and relaunching the Teams application usually resolves the issue temporarily.

However, both workarounds are only temporary, and the problem returns after some time.

Additional Information:

The issue affects only a subset of users.
The Teams web client works without any issues for the affected users.
Since the issue is limited to the desktop client, we suspect it may be related to the local Teams application, cache, profile, or device configuration.

Has anyone encountered a similar issue? Are there any known causes, Microsoft advisories, or recommended troubleshooting steps beyond resetting the application?

Any suggestions would be greatly appreciated.

Thank you.

John Aquilino Napoleon Contreras 5 Reputation points

2026-07-08T05:24:17+00:00
Thank you for providing the details.

Based on the information shared, the issue appears to be isolated to the Microsoft Teams desktop application, as the web version continues to function normally. To help narrow down the root cause, could you please provide the following information?

What version of the Microsoft Teams desktop application is installed on the affected devices?

Are all affected users using the new Teams client, or are some still using the classic client (if applicable)?

Is the issue occurring on specific devices only, or does it follow the user's account when they sign in to another computer?

Are the affected devices managed by your organization's endpoint management solution (such as Microsoft Intune), and have any recent policy or security changes been implemented?

Does the issue occur on a specific network (corporate LAN, VPN, Wi-Fi), or does it persist regardless of the network connection?

Have you noticed any common factors among the affected users, such as the same operating system version, device model, or department?

Are there any error messages or error codes displayed when chat history fails to load or when users are unable to send messages?

Have you checked the Teams client logs and Windows Event Viewer for any related errors at the time the issue occurs?

Does signing out of Teams and signing back in resolve the issue without resetting the application?

Have you tried completely clearing the Teams cache or reinstalling the Teams desktop client to determine whether the behavior persists?

Is Microsoft 365 Service Health reporting any advisories or incidents related to Microsoft Teams that coincide with the affected timeframe?

Are third-party security software, proxy configurations, VPN clients, or firewall rules installed on the affected devices that could be interfering with the Teams desktop application?

The answers to these questions will help determine whether the issue is related to the local Teams client, user profile, device configuration, network environment, or a broader Microsoft service issue. If available, please also share Teams client logs, timestamps when the issue occurred, and screenshots of any error messages to assist with further investigation.
Alfin CP 0 Reputation points

2026-07-08T06:49:50.7233333+00:00

Dear @John Aquilino Napoleon Contreras ,
Thank you for your response and for the detailed troubleshooting questions.

Please find my findings below:

Microsoft Teams desktop application version: 26163.405.4842.717

Teams client: All affected users are using the new Teams client.

Affected devices: Yes, the issue appears to be device-specific rather than affecting all users.

Device management: The affected devices are not managed by Microsoft Intune or any other endpoint management solution.

Network: The issue occurs both on our office LAN and on users' personal ISP/home networks, so it does not appear to be network-specific.

Operating System: The affected users are running Windows 11 Home, version 25H2.

Error messages: No error messages or error codes are displayed when the issue occurs.

Windows Event Viewer: I have checked the Event Viewer but did not find any relevant errors corresponding to the issue.

Teams logs: I have not yet reviewed the Teams client logs. Could you please advise which specific log files or log locations I should collect and analyze the next time the issue occurs?

Sign out/Sign in: I have not yet tested signing out of Teams and signing back in. I will try this the next time the issue occurs.

Reinstallation: I have completely uninstalled and reinstalled Microsoft Teams on the affected devices. Unfortunately, the issue still reappears after some time.

Security software / Proxy / VPN / Firewall: There are no third-party security products, proxy configurations, VPN clients, or firewall rules that appear to be interfering with Teams.

One additional observation I have made is that the affected users are signed into Windows using a Microsoft account (the same account that is also signed into Outlook and Microsoft Teams). In contrast, users who are using a local Windows account have not reported this issue so far.

At this point, I cannot confirm whether this is related or simply a coincidence, but I wanted to mention it in case it helps identify a pattern.

If there are any specific Teams diagnostic logs, Windows logs, or Microsoft troubleshooting tools that you recommend collecting when the issue reoccurs, I would appreciate your guidance.

1 answer

Your answer

Answer 1

Sophie N 18,175 Microsoft External Staff Moderator

Dear @Alfin CP,

Thank you for providing such a detailed breakdown of the issue.

Since the problem is strictly isolated to the Teams desktop client, is intermittent, and is temporarily resolved by clearing the app's local state (resetting/restarting), the core issue likely stems from persistent local caching conflicts or background sync failures unique to those specific devices.

Because standard end-user troubleshooting only provides temporary relief, I recommend moving beyond client-side resets and utilizing tenant-level diagnostics to find a permanent fix. Here are the official Microsoft steps and resources to help you investigate further:

Step 1: Monitor Client Health via Teams Admin Center

You can review the health and performance metrics of the affected devices directly from your admin portal. The Teams client health dashboard allows administrators to investigate end-user-impacting issues, such as application crashes, launch delays, and sync sync-related failures. Documentation: Teams client health - Microsoft Teams | Microsoft Learn

Step 2: Collect Remote Client Diagnostic Logs

Since the issue occurs intermittently and is difficult to catch in real-time, you can trigger log collection remotely. Microsoft Teams allows admins to request and download diagnostic logs for Windows and Mac clients directly from the Teams admin center without interrupting the user. Documentation: Diagnostic logs for Teams Client - Microsoft Teams | Microsoft Learn

If these logs do not highlight a specific local conflict (such as a third-party security software or profile sync issue blocking the Teams backend connection), I highly recommend opening a formal support ticket via the Microsoft 365 Admin Center. Recurring, desktop-only synchronization issues that defy local resets often require Microsoft's backend support teams to look at the telemetry data for those specific user sessions.

Please let me know if you need help navigating these diagnostic tools!

Alfin CP 0 Reputation points

2026-07-08T06:48:49.0466667+00:00

Dear @Sophie N ,

Thank you for the recommendations and for pointing me to the Teams Admin Center diagnostics.

I will review the Teams client health dashboard and use the remote client diagnostic log collection feature the next time the issue occurs. Since the problem is intermittent, collecting logs during the occurrence should provide more useful information.

I have one follow-up question regarding the diagnostic logs. Are there any specific log entries, error patterns, or components that I should focus on when analyzing the collected logs? For example, should I look for authentication/token refresh failures, chat synchronization errors, cache/database corruption, network connectivity issues, or WebView2-related errors?

Additionally, if Microsoft support becomes necessary, are there any particular log files or diagnostic data that you recommend collecting in advance to help expedite the investigation?

I'll update this thread once I have collected the client logs and reviewed the Teams client health information.

Thank you again for your guidance.
Sophie N 18,175 Reputation points Microsoft External Staff Moderator

2026-07-08T23:32:23.0933333+00:00

Dear @Alfin CP,

Thank you for the update. Your approach of collecting logs while the issue is actively occurring is exactly the right strategy for an intermittent client-side problem.

Since you've observed that the issue appears to be device-specific and persists across reinstalls, those timestamps and client logs will be particularly valuable for Microsoft Support to correlate client activity with backend telemetry. The fact that the Teams web client continues to work normally also makes it useful to note whether the desktop client recovers immediately after a restart or reset, as this can help identify whether the issue is related to local client state or communication with the service.

Please keep us updated after you collect the logs and review the Teams client health information. The findings should help narrow down whether this is a client cache issue, an authentication problem, or a synchronization-related issue within the desktop application.