Due to org policy, you can't install the new Teams.

Question

Due to org policy, you can't install the new Teams.

AmazingPhone6248 20

As per the title and screenshot below.
This issue has occurred for 2 people in our department, whereas everyone else has installed it just fine.

We enabled new Teams via the global update policy, with the setting of "classic teams as default".

To fix it for the one person I'm troubleshooting with so far, I created a new update policy with the setting of "New Teams as default", to force the new teams. This policy took ONE WHOLE WEEK to apply to his laptop.

Microsoft's website states the following...
"You can edit the global policy or create and assign a custom policy. After you edit the global policy or assign a policy, it may take 24 hours for changes to take effect."

I've now took them out of the custom update policy, which should revert him back to having the toggle switch to turn new Teams on or off. Am I going to be waiting another week for the policy change to apply??

So questions...

Has anyone else seen this message in the title/screenshot?

What did they do to fix it?

Is one week to apply an update policy normal?

Sandro D'Incà 231 Reputation points

2023-10-25T12:07:15.0266667+00:00

hey there

it seems that we have exact the same problem:

https://learn.microsoft.com/en-us/answers/questions/1402823/switch-to-new-teams-client-failed

our next step is to reinstall the teams-client on the affected machines, other tests with reapply the policy, deleting the cache etc. did not work for us.
Newhouse, Michael 0 Reputation points

2023-10-25T14:07:18.2133333+00:00

We are having the same issue with users this morning!
Roland Schmid 0 Reputation points

2023-10-25T23:12:02.11+00:00

yeah we're experiencing the same for a few users as well, super frustrating

Edit: solution - found that manually running the installer (MSTeams-x86.msix) on those problem machines fixed the issue.
Sandro D'Incà 231 Reputation points

2023-10-26T06:53:56.05+00:00

yeah, same here. uninstallation and reinstall the teams client is a workaround. but we will open a MS-case to troubleshoot the root-cause.

because if we start to deploy the new client in our organization, the uninstall / install-workaround is not a solution for us...
Jeff Kong 0 Reputation points

2023-11-02T14:01:30.1+00:00

I cleared the cache of the Teams folder and that solved the issue for us.

https://learn.microsoft.com/en-us/microsoftteams/troubleshoot/teams-administration/clear-teams-cache
Sandro D'Incà 231 Reputation points

2023-11-22T12:52:21.2233333+00:00

final status-update:

we had opened a microsoft case and based on the following article we could sucessfully solve the problem:

https://learn.microsoft.com/en-us/microsoftteams/troubleshoot/teams-administration/clear-teams-cache

clearing the complete teams-appdata-folder solved the problem.

based on other microsoft-sources, we only cleared several specific folders in the appdata-folder, but not all folders because deleting all of it will reset many specific custom teams-settings of the user (for example custom backgrounds etc.).

and another interesting statement from the microsoft support: "New Teams must be fully developed, there is no other workaround available at the moment".
Ernesto Garcia 0 Reputation points

2024-06-06T23:32:38.7433333+00:00
I have the same issue at my company most of the users transitioning to the new teams but some of them received the same error you are getting , after doing multiples things the one that works is the following but keep in mind you need admin rights to perform a few task:

1.Open Registry Editor as Administrator and search for the following values:

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

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

Delete the following values:

o   BlockNonAdminUserInstall

o   AllowAllTrustedApps

o   AllowDevelopmentWithoutDevLicense

You will only have Default value :

3.Then open CMD as administrator and run a GPUPDATE command .

This will allow the Policy to be update then the End User needs to restart the computer.

4.Nex step is to Log off from teams by going to the picture of the user and select Sign out then

The user will be prompted to log in back.

5.Last step is to click on the Try New teams and will start downloading and it will change to the new Version on team

If you do not get the new version please go back to step 1 and delete the value of the Registry Editor and go back to step 2 and should be working ..

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

5 answers

Your answer

Sandro D'Incà 231 Reputation points

2023-10-25T12:07:15.0266667+00:00

hey there

it seems that we have exact the same problem:

https://learn.microsoft.com/en-us/answers/questions/1402823/switch-to-new-teams-client-failed

our next step is to reinstall the teams-client on the affected machines, other tests with reapply the policy, deleting the cache etc. did not work for us.
Newhouse, Michael 0 Reputation points

2023-10-25T14:07:18.2133333+00:00

We are having the same issue with users this morning!
Roland Schmid 0 Reputation points

2023-10-25T23:12:02.11+00:00

yeah we're experiencing the same for a few users as well, super frustrating

Edit: solution - found that manually running the installer (MSTeams-x86.msix) on those problem machines fixed the issue.
Sandro D'Incà 231 Reputation points

2023-10-26T06:53:56.05+00:00

yeah, same here. uninstallation and reinstall the teams client is a workaround. but we will open a MS-case to troubleshoot the root-cause.

because if we start to deploy the new client in our organization, the uninstall / install-workaround is not a solution for us...
Jeff Kong 0 Reputation points

2023-11-02T14:01:30.1+00:00

I cleared the cache of the Teams folder and that solved the issue for us.

https://learn.microsoft.com/en-us/microsoftteams/troubleshoot/teams-administration/clear-teams-cache
Sandro D'Incà 231 Reputation points

2023-11-22T12:52:21.2233333+00:00

final status-update:

we had opened a microsoft case and based on the following article we could sucessfully solve the problem:

https://learn.microsoft.com/en-us/microsoftteams/troubleshoot/teams-administration/clear-teams-cache

clearing the complete teams-appdata-folder solved the problem.

based on other microsoft-sources, we only cleared several specific folders in the appdata-folder, but not all folders because deleting all of it will reset many specific custom teams-settings of the user (for example custom backgrounds etc.).

and another interesting statement from the microsoft support: "New Teams must be fully developed, there is no other workaround available at the moment".
Ernesto Garcia 0 Reputation points

2024-06-06T23:32:38.7433333+00:00

I have the same issue at my company most of the users transitioning to the new teams but some of them received the same error you are getting , after doing multiples things the one that works is the following but keep in mind you need admin rights to perform a few task:

1.Open Registry Editor as Administrator and search for the following values:

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

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

Delete the following values:

o BlockNonAdminUserInstall

o AllowAllTrustedApps

o AllowDevelopmentWithoutDevLicense

You will only have Default value :

3.Then open CMD as administrator and run a GPUPDATE command .

This will allow the Policy to be update then the End User needs to restart the computer.

4.Nex step is to Log off from teams by going to the picture of the user and select Sign out then

The user will be prompted to log in back.

5.Last step is to click on the Try New teams and will start downloading and it will change to the new Version on team

If you do not get the new version please go back to step 1 and delete the value of the Registry Editor and go back to step 2 and should be working ..

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

Answer 1

Anonymous

Hi @AmazingPhone6248

You can try to let users clear Teams cache after updating the policy.

User's image

If clearing the cache has no effect, please try downloading New Teams directly from the Teams official website.
According to the documentation: It's possible that the MSIX package installation could be blocked by registry keys set by GPO policy/third party tool. For a complete list of registry keys: How Group Policy works with packaged apps - MSIX

The registry keys that could block new Teams MSIX package installation are:

BlockNonAdminUserInstall
AllowAllTrustedApps
AllowDevelopmentWithoutDevLicense

These registry keys can be found at one of these locations:

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\AppModelUnlock
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Appx

Please check this setting for your computer:

User's image

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.

Anonymous

2023-10-30T06:39:58.5666667+00:00

Hi @AmazingPhone6248

I am checking the status of this case. Please let us know if you would like further assistance.
Meanwhile, if the reply is helpful to you, please try to mark it as an answer to help others who encounter the same issue and read this thread.
Thank you for your understanding and patience.
Anonymous

2023-11-01T02:49:32.0833333+00:00

Hi @AmazingPhone6248

I am checking the status of this case. Please let us know if you would like further assistance.
Meanwhile, if the reply is helpful to you, please try to mark it as an answer to help others who encounter the same issue and read this thread.
Thank you for your understanding and patience.
Kwak, Dohee 0 Reputation points

2024-06-03T21:08:53.6533333+00:00
We had same issue. I tried on one of pc that had issues. Run regedit as administartor delete the keys..

BlockNonAdminUserInstall

AllowAllTrustedApps

AllowDevelopmentWithoutDevLicense Restart Teams and PC got updated with New Teams. Thank you.

Answer 2

Followed the steps above to ensure that no GPO settings are preventing the new Teams from installing.

https://learn.microsoft.com/en-us/microsoftteams/new-teams-troubleshooting-installation#how-do-i-know-which-one-of-the-above-policies-is-blocking-me

For me, I found that affected machines have this key/value set.

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\AppModelUnlock
AllowAllTrustedApps = 0

Deleting the "AllowAllTrustedApps" and performing a restart allowed the the new Teams app to install.

Answer 3

final status-update from my side:

we had opened a microsoft case and based on the following article we could sucessfully solve the problem:

https://learn.microsoft.com/en-us/microsoftteams/troubleshoot/teams-administration/clear-teams-cache

clearing the complete teams-appdata-folder solved the problem.

based on other microsoft-sources, we only cleared several specific folders in the appdata-folder, but not all folders because deleting all of it will reset many specific custom teams-settings of the user (for example custom backgrounds etc.).

and another interesting statement from the microsoft support: "New Teams must be fully developed, there is no other workaround available at the moment".

Answer 4

Kindly do these steps on your machine, then quit the teams and restart.

How to check for restrictive policies for your computer

In Windows, search for Edit Group Policy. Or, right-click the Windows logo button, select Run, and then enter gpedit.msc. This action opens the Local Group Policy Editor.

Navigate to Computer Configuration > Administrative Templates > Windows Components > App package Deployment, and check the following policy settings:

Prevent non-admin users from installing packaged Windows apps
- Allow all trusted apps to install
Make sure that these settings are set to Not configured.

Answer 5

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more

Share via

Due to org policy, you can't install the new Teams.

5 answers

Your answer