Team app can not login when computer restart

The behavior indicates a recurring Teams sign-in/startup issue tied to the local profile and system configuration rather than a one‑time cache problem. After cache cleanup, Teams works once, but fails again after reboot, so persistent environment or profile issues must be addressed.

Use the following sequence, prioritizing the documented checks and fixes.

1. Run the Teams launch diagnostic script (recommended)

• Use the documented TeamsLaunchCheck.ps1 PowerShell script to automate all required checks for the new Teams app startup issues.
• This script runs the same checks described below (reparse points, environment variables, permissions) and is the preferred option.

2. Manually verify shell folders and environment variables If the script is not used, perform the manual checks:

1. Check Cookies and Cache shell folders for reparse points

• Run in PowerShell:

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

• If both commands return False, continue to the next step.
• If either returns True, update the corresponding registry entry so it points to a non‑reparse path:
  • Open Registry Editor and go to: Computer\HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders
  • Set the value to the default path, for example:
    • Cookies → %USERPROFILE%\AppData\Local\Microsoft\Windows\INetCookies
    • Cache → %USERPROFILE%\AppData\Local\Microsoft\Windows\INetCache
• Back up the registry before editing and follow change procedures carefully, as incorrect edits can cause serious problems.

2. Check TEMP and TMP environment variables

• Run in PowerShell:

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

• If the output ends with False for both variables, continue.
• If any returns True, change the TEMP/TMP values to a folder that is not a reparse point (for example, a normal local path). Use the documented set command guidance to adjust environment variables.

3. Verify AppData permissions Ensure the user has at least Read permission to all required AppData paths. Lack of access can cause Teams to fail at startup after reboot.

Check that the user can read these 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
• %USERPROFILE%\AppData\Local\Microsoft\Windows\History\Low
• %USERPROFILE%\AppData\Local\Microsoft\Windows\History\Low\History.IE5
• %USERPROFILE%\AppData\Local\Microsoft\Windows\IECompatCache
• %USERPROFILE%\AppData\Local\Microsoft\Windows\IECompatCache\Low
• %USERPROFILE%\AppData\Local\Microsoft\Windows\IECompatUaCache
• %USERPROFILE%\AppData\Local\Microsoft\Windows\IECompatUaCache\Low
• %USERPROFILE%\AppData\Local\Microsoft\Windows\INetCache
• %USERPROFILE%\AppData\Local\Microsoft\Windows\INetCookies
• %USERPROFILE%\AppData\Local\Microsoft\Windows\INetCookies\DNTException
• %USERPROFILE%\AppData\Local\Microsoft\Windows\INetCookies\DNTException\Low
• %USERPROFILE%\AppData\Local\Microsoft\Windows\INetCookies\Low
• %USERPROFILE%\AppData\Local\Microsoft\Windows\INetCookies\PrivacIE
• %USERPROFILE%\AppData\Local\Microsoft\Windows\INetCookies\PrivacIE\Low
• %USERPROFILE%\AppData\Local\Microsoft\Windows\PPBCompatCache
• %USERPROFILE%\AppData\Local\Microsoft\Windows\PPBCompatCache\Low
• %USERPROFILE%\AppData\Local\Microsoft\Windows\PPBCompatUaCache
• %USERPROFILE%\AppData\Local\Microsoft\Windows\PPBCompatUaCache\Low
• %USERPROFILE%\AppData\Local\Microsoft\WindowsApps
• %USERPROFILE%\AppData\Local\Packages
• %USERPROFILE%\AppData\Local\Packages\VirtualizationTests.Main__8wekyb3d8bbwe\LocalCache
• %USERPROFILE%\AppData\Local\Publishers
• %USERPROFILE%\AppData\Local\Publishers\8wekyb3d8bbwe
• %USERPROFILE%\AppData\Local\Temp
• %USERPROFILE%\AppData\LocalLow
• %USERPROFILE%\AppData\LocalLow\Microsoft
• %USERPROFILE%\AppData\LocalLow\Microsoft\Internet Explorer
• %USERPROFILE%\AppData\LocalLow\Microsoft\Internet Explorer\DOMStore
• %USERPROFILE%\AppData\LocalLow\Microsoft\Internet Explorer\EdpDomStore
• %USERPROFILE%\AppData\LocalLow\Microsoft\Internet Explorer\EmieSiteList
• %USERPROFILE%\AppData\LocalLow\Microsoft\Internet Explorer\EmieUserList
• %USERPROFILE%\AppData\LocalLow\Microsoft\Internet Explorer\IEFlipAheadCache
• %USERPROFILE%\AppData\Roaming
• %USERPROFILE%\AppData\Roaming\Microsoft
• %USERPROFILE%\AppData\Roaming\Microsoft\Crypto
• %USERPROFILE%\AppData\Roaming\Microsoft\Internet Explorer
• %USERPROFILE%\AppData\Roaming\Microsoft\Internet Explorer\UserData
• %USERPROFILE%\AppData\Roaming\Microsoft\Internet Explorer\UserData\Low
• %USERPROFILE%\AppData\Roaming\Microsoft\Spelling

If any of these paths are redirected, locked down, or on unavailable storage at logon, adjust the configuration or permissions so they are accessible.

4. Reinstall Teams if sign-in still fails If the above checks do not resolve the issue and the problem persists after reboot:

1. Uninstall Teams from the device.
2. Go to %appdata%\Microsoft and delete the Teams folder.
3. Download and reinstall Teams, preferably by running the installer as administrator (right‑click → Run as administrator).

5. Escalate with logs if unresolved If none of these steps resolves the problem, collect Teams debug logs and the error code shown on the Teams sign-in screen, then open a support request so the issue can be investigated further.

References:

• Resolve issues when starting the new Teams app
• Resolve sign-in errors in Teams