Teams app collapsed

Question

I seriously need some help from Microsoft on this one because the Teams desktop client has become completely unusable. The app refuses to launch at all double-clicking the icon does nothing, no splash screen, no UI, nothing displayed on screen. What’s frustrating is that the Teams process is clearly running in the background since I can still see it active in Task Manager, but the client never renders. Teams Web works fine, so the issue seems isolated to the desktop app itself.

I’ve already tried a full uninstall/reinstall, cleared cache, and even went as far as performing a clean Windows reinstall, yet the problem still persists exactly the same way.

Event Viewer keeps logging Event ID 1001 whenever this happens. What makes this even more confusing is that I’m still able to successfully authenticate and connect to Teams services through PowerShell using "Connect-MicrosoftTeams", which suggests the backend connectivity and account access are functioning normally.

At this point I’m trying to understand whether this is a known issue with the new Teams client architecture, rendering pipeline, or some corrupted local dependency that survives even a clean OS reinstall.

Answer 1

Hi @Tomlin Izie

Based on the information you provided, I understand that your Teams desktop client has become completely unusable. While the process appears active in Task Manager and Teams Web works perfectly, the desktop UI refuses to launch or render at all. Even after trying a full reinstall, clearing the cache, and performing a clean Windows reinstall, the issue persists with Event ID 1001 being logged in Event Viewer, despite successful authentication via PowerShell.

After looking into this, it appears that other users have reported a similar issue tied to the April-A build of the new Teams client architecture. A fix for this rendering behavior has been integrated into the May-A build, which is currently rolling out gradually to the General Availability channel.

To resolve this issue, please try the following steps:

If the Teams desktop app manages to open even temporarily, check if the May-A update is already available on your device by going to: Settings > About > Check for updates. Since the client is currently failing to launch, please download and install the latest available version directly from the official Microsoft Teams download page: https://www.microsoft.com/en-us/microsoft-teams/download-app

Once installed, please check the version again under Settings > About to ensure you are on the latest build, and confirm if the launching issue has been resolved.

If the May-A update has not yet reached the affected machine, it should be available shortly as the rollout is actively progressing. In the meantime, the user can continue using Teams Web as a workaround.

Please let me know how it goes or if you have any further updates!

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have 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.

Answer 2

The behavior matches a Teams desktop launch failure where the process starts but no window appears. The documented guidance focuses on checking client health, local paths, and environment configuration rather than backend connectivity (which is already confirmed working via Connect-MicrosoftTeams and Teams Web).

Apply the following checks and fixes that specifically target new Teams launch issues and white/blank screen behavior:

1. Verify Teams can reach required endpoints

• Ensure no firewall or proxy is blocking Teams from reaching the documented Teams endpoints.
• If the Teams client cannot navigate to or times out waiting for Teams endpoints, it can start a background process without rendering a usable window.
• Review network configuration and confirm all Teams-related network requests are allowed.

2. Check for unsupported OS or environment

• Confirm the OS version is supported for the new Teams desktop client. If the OS is unsupported, update to a supported version of Windows.

3. Run the Teams launch diagnostics (or equivalent manual checks) If available in the environment, use the TeamsLaunchCheck.ps1 script described for resolving new Teams launch issues. It automates checks for:

• Reparse points on Cookies and Cache shell folders.
• TEMP/TMP environment variables pointing to reparse points.
• Permissions on key AppData paths.

If running the script is not an option, perform the documented manual checks:

3.1. Check Cookies and InternetCache shell folders for reparse points

• Run in PowerShell:

(gp ([environment]::getfolderpath("Cookies"))).Attributes -match 'ReparsePoint'
(gp ([environment]::getfolderpath("InternetCache"))).Attributes -match 'ReparsePoint'

• If either returns True, update the corresponding registry entries under: Computer\HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders so that:
  • Cookies → %USERPROFILE%\AppData\Local\Microsoft\Windows\INetCookies
  • Cache → %USERPROFILE%\AppData\Local\Microsoft\Windows\INetCache
• Ensure these locations are not symlinked or mapped to another path.

3.2. Check TEMP and TMP environment variables

• Run in PowerShell:

gci env:* | ?{@("TEMP", "TMP").Contains($_.Name)} | %{$_.Value+" - "+((gp $_.Value).Attributes -match 'ReparsePoint')}

• If either TEMP or TMP points to a reparse point (returns True), change them to a normal local folder path that is not a reparse point.

3.3. Verify permissions on AppData paths

• Confirm the account has Read access to all of the following directories:
  • %USERPROFILE%\AppData\Local
  • %USERPROFILE%\AppData\Local\Microsoft
  • %USERPROFILE%\AppData\Local\Microsoft\Windows
  • %USERPROFILE%\AppData\Local\Microsoft\Windows\Explorer
  • %USERPROFILE%\AppData\Local\Microsoft\Windows\History and its Low/History.IE5 subpaths
  • %USERPROFILE%\AppData\Local\Microsoft\Windows\IECompatCache and Low
  • %USERPROFILE%\AppData\Local\Microsoft\Windows\IECompatUaCache and Low
  • %USERPROFILE%\AppData\Local\Microsoft\Windows\INetCache
  • %USERPROFILE%\AppData\Local\Microsoft\Windows\INetCookies and all listed subfolders (including Low, DNTException, PrivacIE and their Low subfolders)
• Any missing permission can prevent Teams from initializing its local storage and cause a non-rendering client.

4. Avoid nonstandard installation paths or symlinked profiles

• If any Unix symlink or mapped drive is used for C:\Users or the profile, or if Teams was installed via a custom script into Program Files instead of the default user AppData location, Teams may fail to update and can exhibit white/blank screen behavior.
• Ensure Teams is installed in the default %USERPROFILE%\AppData-based path. If profile mapping must exist, use the web version as a workaround.

5. Check antivirus/DLP and VDI/profile tools

• Ensure non-Microsoft antivirus and DLP tools are not blocking the Teams desktop client, its auto-start executable, or Microsoft Edge WebView2. Blocking these can cause the client to start and then fail before rendering.
• In VDI or profile-virtualization scenarios:
  • Follow the documented profile and cache location guidance for Teams.
  • If using FSLogix on Windows Server 2019 and seeing storage-folder instantiation errors for MSTeams_8wekyb3d8bbwe\LocalCache, install the latest FSLogix version.
  • For Omnissa DEM with Windows OS Optimization Tool, ensure the “Clean Default User Profile” setting is not causing Teams app launch failures.

6. Use Teams client health insights

• In the Teams client health dashboard, review the Issues tab and the Insight column for this device/user. Insights such as:
  • “Unable to navigate to Teams endpoint”
  • “Timed out waiting for Teams endpoint”
  • “Teams application contains a script error”
  • “Unsupported OS version” map directly to the resolutions above.

7. If the issue persists

• After confirming endpoints, OS support, environment variables, shell folders, permissions, antivirus/DLP exclusions, and profile tools, and the client still launches only as a background process with Event ID 1001, escalate to Microsoft Support with:
  • Event Viewer logs for the Teams process.
  • Output of the TeamsLaunchCheck.ps1 script or the manual checks.
  • Details of any profile virtualization, FSLogix, or optimization tools in use.

---

References:

• Resolve Teams client launch failures
• Resolve issues when starting the new Teams app
• Teams starts with a white screen
• Install Teams for Virtualized Desktop Infrastructure (VDI)
• Known Issues