Teams freezes on a specific chat across all win11 devices and apps

David Herr 0 Reputation points
2026-06-15T17:43:05.54+00:00

User has a chat with two other users. So 3 in total. It is a renamed chat "Susans patients" and each time it is accessed it freezes out whatever app it is on. It is an ongoing chat of about 1 year. They periodically send 2-3 page pdfs to each other. A few times a week.

I fix it by clearing the appropriate cache, but the moment the user accesses that chat it re-freezes. Teams becomes unusable and no actions work. This happens on the teams desktop app (our preferred app), chrome & edge. We moved user to a new computer and it happens again.

Two questions.
One, how would I go about solving this?

Two, what would cause this?

Microsoft Teams | Microsoft Teams for business | Chats | Share photos, files, and video
0 comments

2 answers

Sort by: Oldest
Most helpful Newest Oldest

  1. AI answer

    2026-06-15T17:43:25.0766667+00:00

    To resolve and understand a single-chat freeze that follows the user across devices and clients, focus on client-side corruption and cached content for that specific conversation.

    Because this affects:

    • Desktop app on multiple Windows 11 devices
    • Web clients (Chrome & Edge)
    • Only one specific chat

    the most effective approach is to fully reset the Teams client profile and then isolate problematic content in that chat.

    1. How to go about solving this

    Follow these steps in order and test the problematic chat after each major step.

    1. Fully sign out everywhere
      • In Teams desktop, select the profile picture → Sign out.
      • Close the app completely (ensure no Teams process is running in Task Manager).
      • Sign out of Teams in all browsers as well.
    2. Clear Teams cache on the affected Windows profile
      Since clearing “appropriate cache” helped temporarily, perform a more complete cleanup similar to the approaches used for other client issues:
      • Close Teams.
      • Under the user profile, remove Teams-related cached data in AppData (for example, as done in the Q&A where removing leftover Teams files under the entire AppData tree and reinstalling resolved persistent crashes).
      • Reopen Teams and let it fully re-sync, then test opening the “Susans patients” chat.
    3. Test in a clean browser profile
      • Open an InPrivate/Incognito window in Edge or Chrome.
      • Sign in to https://teams.microsoft.com and open the problematic chat.
      • If it still freezes in a clean browser session, the issue is likely tied to specific content in that chat, not just local cache.
    4. Check for client crash indicators and environment conflicts
      • If the Teams app exits unexpectedly when opening that chat, review the Teams client health / crash insights as described in the client crash guidance.
      • Ensure antivirus/DLP tools are not interfering with Teams or its media stack, as recommended in the crash article (include/approve Teams desktop client and Microsoft Edge WebView2).
      • If any third‑party VPN or network filter is in use (similar to the Astrill VPN case that caused repeated crashes), temporarily disable/uninstall it and test again.
    5. Repair or reset the Teams app in Windows
      • Go to Settings → Apps → Installed apps → Microsoft Teams → Advanced options.
      • Select Repair first. If the issue persists, select Reset (note: reset may delete local app data, as noted in the Q&A).
      • Launch Teams, sign in, and test the chat.
    6. If still reproducible, escalate with logs
      • At this point, the behavior is likely due to a specific message or file in that chat that the service or client cannot render.
      • Collect logs and open a support case so the problematic conversation content can be analyzed by Microsoft Support.

    2. What would cause this

    From the behavior and the patterns in similar Teams issues, likely causes include:

    1. Corrupted cached data tied to that conversation
      • Teams heavily caches chat and media content. A corrupted cache entry for that specific chat can repeatedly crash or freeze the client when that conversation is loaded.
      • This aligns with the fact that clearing cache temporarily helps until the chat is opened and the problematic content is re-fetched.
    2. Problematic media or file in the chat history
      • Large or malformed PDFs or other attachments in a long‑running chat could trigger a rendering or media stack failure when the chat is loaded.
      • The crash guidance mentions media stack technology failures and recommends checking drivers and using Windows Error Reporting to identify root causes; a similar underlying failure could be triggered only when that chat’s content is processed.
    3. Interaction with security or network software
      • As in the example where Astrill VPN caused Teams to repeatedly crash, a specific pattern of traffic or content (for example, repeated large PDFs in one chat) might interact badly with VPN, antivirus, or DLP tools and cause the client to hang when loading that conversation.
    4. Client bug triggered by specific chat state
      • A long‑running renamed group chat with a large history and frequent file sharing can expose edge‑case bugs in the client’s chat rendering or synchronization logic.
      • Because the issue follows the user across devices and clients, this points to a server‑side conversation state or content pattern that the clients all struggle with.

    Given the cross‑device, cross‑client nature and the fact that only one chat is affected, the most probable explanation is a specific message/file or conversation state in that chat that triggers a client bug, surfaced through cached data. After exhausting cache clearing, app repair/reset, and environment checks, the remaining step is to involve Microsoft Support with logs so that chat’s content can be inspected and the underlying defect addressed.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. Vy Nguyen 11,410 Reputation points Microsoft External Staff Moderator
    2026-06-15T18:43:45.3166667+00:00

    Hi David, 

    I hope you're doing well today.  

    Based on the information you shared that Microsoft Teams becomes unresponsive whenever the renamed group chat is opened, and this same behavior occurs on all Windows 11 devices that have been tested, including the Teams desktop app, Microsoft Edge, and Google Chrome. 

    Since clearing the Teams cache only provides temporary relief and the issue returns as soon as that specific chat is opened, The issue is most likely caused by data inside that specific group chat, most commonly a problematic file reference or conversation item that Teams cannot process correctly when the thread is opened. In addition, Microsoft documents that files shared in Teams chats are stored in OneDrive, so if a file reference or chat item in that thread is not loading correctly, Teams may stop responding each time the conversation is accessed.  

    To address this in a way that best suits your situation, please follow the steps below: 

    1/ Isolate the original chat by creating a new group conversation 

    • Create a new group chat with the same three participants. 
    • Keep the new chat unnamed at first. 
    • Send a short text message first, and then test with one small PDF file. 
    • If the new chat works normally, this will help confirm that the original thread contains the issue rather than the Teams client itself. 

    2/ Review whether a specific item in the original thread is triggering the freeze 

    • Check the timeline of when the issue first started. 
    • Ask one of the other participants to review the most recent messages or PDF files added before the freezing began. 
    • If one file appears suspicious, share a fresh copy in the new chat instead of continuing to use the original thread. 
    • Because files shared in Teams chats are stored in OneDrive, a broken file link or file related loading issue inside that thread can affect how the conversation opens in Teams.  
    • Reference: Error when uploading files to a Teams chat - Microsoft Teams | Microsoft Learn 

    3/ Transition the workflow to a private Teams channel (Long-Term Resolution) 

    The most effective and lasting approach for your situation is to move this ongoing collaboration into a dedicated private Teams channel rather than continuing within a group chat.  

    • Teams channels are specifically designed to support long-term, document-heavy workflows, files shared within a channel are stored and indexed through SharePoint, which handles large volumes of content far more efficiently than the OneDrive-based storage used by group chats. 
    • This architectural difference is precisely why the chat has become unstable over time, and why a channel environment will suit this workflow much better going forward. 

    4/ Reach out to IT admin to collect Teams logs and proceed with a Microsoft support investigation 

    Since your account is managed by your organization, please contact your IT administrator to review your permissions and policies. If the issue persists after these checks, ask your IT administrator to submit a support request directly to Microsoft Support team.           

    They can raise a support ticket by visiting: Get support - Microsoft 365 admin | Microsoft Learn 

    In case you do not know who is your IT admin, kindly refer to this article: How do I find my Microsoft 365 admin? - Microsoft Support 

    • Reproduce the issue and collect the Teams client diagnostic logs immediately afterward. 
    • Include the affected user’s UPN, the exact chat name, the names of the other two participants, and the date and local time when the freeze occurs. 
    • Note clearly that the same issue occurs across multiple devices and browsers, and that clearing cache helps only until the affected chat is opened again. 
    • Request a service side investigation for the specific chat thread and any linked file objects associated with it. 

    As community moderators, we appreciate your understanding that our access to internal development details is limited. Our primary role is to guide users toward the appropriate resources and support channels. While we may not have visibility into deeper backend analysis, we’ll continue doing our best to support you within the scope of our responsibilities.          

    At this stage, the most practical workaround is to continue communication in a newly created group chat while the original conversation is being investigated further. If needed, participants can also leave the affected group chat once the new thread has been validated for ongoing use. 

    I hope this information is helpful. Please follow these steps and let me know if it works for you. If you have any updates regarding the issue, please feel free to share them with me.           

    Thank you for your patience and your understanding. I look forward to continuing the conversation.  

    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have any extra questions about this answer, please click "Comment".              

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.  

    Was this answer helpful?

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.