Problème de démarrage de Teams

Source : Resolve issues when starting the new Teams app - Microsoft Teams | Microsoft Learn

Solution testé, on peut utiliser les autres commandes pour faire les vérifications, mais essentiellement l’application rencontre des problèmes de permissions et cette étape résout la majorité des situations.

Créer 2 clé chaine(String) nommé AllowAllTrustedApps avec une valeur de 1 dans ces 2 endroits :

• Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\AppModelUnlock\

• Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Appx\

1. Check the AllowAllTrustedApps policy setting:

   1. Open a Command Prompt window, and then run the winver command.

   2. Compare your Windows version and build number in the results to the following versions of Windows 11 and Windows 10:

      • Windows 11 version 21H2 OS build 22000.2777

      • Windows 11 version 22H2 OS build 22621.2506

      • Windows 11 version 23H2 OS build 22631.2428

      • Windows 10 version 21H2 OS build 19044.4046

      • Windows 10 version 22H2 OS build 19045.3636

   3. If your Windows version and build number are earlier than those in the list, open Registry Editor, and then locate the AllowAllTrustedApps registry entry under one of the following subkeys:

      • Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\AppModelUnlock

      • Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Appx

   4. Check the value of AllowAllTrustedApps. If the value is 0, the policy is disabled. Change it to 1 to enable the policy, and then start new Teams again.

      Note: To start new Teams without enabling the AllowAllTrustedApps policy, you must be running one of the versions of Windows that are listed in step 5b.

Utiliser une script ou faire la vérification manuelle

Open

Perform the checks manually

Important

This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs.

1. Check whether the Cookies and Cache shell folders point to a location that is a reparse point:

   1. Run the following PowerShell commands:

      PowerShellCopy

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

   2. If both commands return False, go to step 2. Otherwise, open the Registry Editor and locate the following subkey:

      Computer\HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders

   3. For the shell folder that's returned as True in the PowerShell command, update the value of its associated registry entry to a location that isn't a reparse point. For example, you can set the value to the default path:

   Expand table

   Registry entryValueCookies%USERPROFILE%\AppData\Local\Microsoft\Windows\INetCookiesCache%USERPROFILE%\AppData\Local\Microsoft\Windows\INetCache

2. Check whether the values of the TEMP or TMP environment variables are set to a reparse point:

   1. Run the following PowerShell command:

      PowerShellCopy

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

   2. If the command returns False, go to step 3. Otherwise, set the value of the environment variables to a location that isn't a reparse point.

3. Check whether any of the following directories in the AppData folder are changed to function as reparse points:

   • %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

   • %USERPROFILE%\AppData\Roaming\Microsoft\SystemCertificates

   • %USERPROFILE%\AppData\Roaming\Microsoft\Windows

   • %USERPROFILE%\AppData\Roaming\Microsoft\Windows\Libraries

   • %USERPROFILE%\AppData\Roaming\Microsoft\Windows\Recent

   If any of the folders are reparse points, contact Microsoft Support.

4. Check for files that have the same name as a required system folder in the AppData folder. For example, a file that's named Libraries in the path, %AppData%\Microsoft\Windows\Libraries, has the same name as a folder that has the same path. For each folder that's listed in step 3, run the following PowerShell command:

   PowerShellCopy

   Test-Path -Path <directory name, such as $env:USERPROFILE\AppData\Local\Temp> -PathType Leaf

   If the command returns True, remove the file, and then create a folder by using the same name as the complete path for the system folder.

5. Check the AllowAllTrustedApps policy setting:

   1. Open a Command Prompt window, and then run the winver command.

   2. Compare your Windows version and build number in the results to the following versions of Windows 11 and Windows 10:

      • Windows 11 version 21H2 OS build 22000.2777

      • Windows 11 version 22H2 OS build 22621.2506

      • Windows 11 version 23H2 OS build 22631.2428

      • Windows 10 version 21H2 OS build 19044.4046

      • Windows 10 version 22H2 OS build 19045.3636

   3. If your Windows version and build number are earlier than those in the list, open Registry Editor, and then locate the AllowAllTrustedApps registry entry under one of the following subkeys:

      • Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\AppModelUnlock

      • Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Appx

   4. Check the value of AllowAllTrustedApps. If the value is 0, the policy is disabled. Change it to 1 to enable the policy, and then start new Teams again.

      Note: To start new Teams without enabling the AllowAllTrustedApps policy, you must be running one of the versions of Windows that are listed in step 5b.

6. If the issue persists, update the system to Windows 11, version 22H2, OS build 22621.2506 or a later version.