Fix Classic Teams Is Still Launching on a Managed Device

If your organization uses Windows 10 or Windows 11 devices managed by Microsoft Intune or Group Policy, you may see the classic Teams app launch even after you have deployed the new Teams. This happens because the new Teams installer does not always remove the classic Teams app, and existing shortcuts and startup entries can still point to the old executable. In this article, you will learn why classic Teams persists and how to block it using policy settings, registry keys, and cleanup scripts.

Why Classic Teams Still Starts on Managed Devices

The classic Teams app, also known as Teams for Work or School, is a separate installation from the new Teams. When you deploy the new Teams via Intune or Group Policy, the installer does not uninstall the classic Teams app automatically. The new Teams installer only removes the classic Teams app if the user manually uninstalls it or if you run a specific uninstall command.

Additionally, the classic Teams app creates several startup entries. These include a registry key under HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run and a shortcut in the Startup folder. Even if you block the app from the Teams admin center, these entries still execute the classic Teams executable when the user signs in.

Another reason is that the new Teams does not automatically replace the classic Teams app on all devices. Microsoft provides a policy to enable the new Teams as the default, but this policy only affects the Teams app that appears in the Microsoft 365 Apps. If you have not configured that policy, the classic Teams app remains active.

How the New Teams Installer Behaves

The new Teams installer, when run per-machine, does not uninstall the classic Teams app. It only installs the new Teams and creates a new shortcut. The classic Teams app remains in the system and can still be launched from its own shortcut or from the Start menu. To fully remove classic Teams, you must run the uninstall string or use the Remove-AppxPackage cmdlet for the MSIX version.

Steps to Block Classic Teams on Managed Devices

Use the following steps to prevent classic Teams from launching on your managed devices. You can apply these settings via Intune or Group Policy, depending on your management tool.

Step 1: Set the Classic Teams App to Blocked in the Teams Admin Center

1. Open the Teams admin center
   Go to https://admin.teams.microsoft.com and sign in with an account that has the Teams Administrator role.
2. Navigate to Manage apps
   In the left navigation, select Teams apps, then select Manage apps.
3. Find the classic Teams app
   Search for “Microsoft Teams” in the list. The classic Teams app has the app ID 1f93c3a1-4b4a-4f3a-8f3a-2f3a4b5c6d7e. Select the app to open its details.
4. Block the app
   In the app details page, select the Status dropdown and choose Blocked. Then select Save.

Blocking the app in the Teams admin center prevents users from launching it from the Teams app store, but it does not remove the local installation. You still need to disable the startup entries.

Step 2: Disable the Classic Teams Startup Entry via Group Policy

1. Open the Group Policy Management Console
   On a domain controller or a management workstation, run gpmc.msc.
2. Create or edit a Group Policy Object
   Right-click your organizational unit and select Create a GPO in this domain, and Link it here. Give it a name like “Block Classic Teams.”
3. Edit the policy
   Right-click the new GPO and select Edit.
4. Navigate to the Teams policy
   Go to Computer Configuration > Policies > Administrative Templates > Microsoft Teams.
5. Enable the “Do not launch Teams” policy
   Double-click “Do not launch Teams” and select Enabled. This policy prevents the classic Teams executable from starting.

Step 3: Remove the Classic Teams Startup Registry Key

1. Create a PowerShell script
   Open Notepad and paste the following script:
   Remove-ItemProperty -Path "HKCU:\Software\Microsoft\Windows\CurrentVersion\Run" -Name "Teams" -ErrorAction SilentlyContinue
2. Save the script
   Save the file as Remove-ClassicTeamsStartup.ps1.
3. Deploy the script via Intune
   In the Microsoft Intune admin center, go to Devices > Scripts and add a new script. Upload the PowerShell script and assign it to the target devices.

Step 4: Uninstall Classic Teams Completely

1. Identify the classic Teams installation type
   Classic Teams can be installed as a per-machine MSI or a per-user MSIX. Run the following command to list installed apps:
   Get-Package -Name "Teams"
2. Uninstall the MSI version
   If the package is an MSI, run:
   Uninstall-Package -Name "Teams"
3. Uninstall the MSIX version
   If the package is an MSIX, run:
   Get-AppxPackage -Name "Microsoft.Teams" | Remove-AppxPackage

If Classic Teams Still Launches After the Main Fix

Classic Teams Appears in the Startup Folder

The classic Teams installer may place a shortcut in the user’s Startup folder. Delete this shortcut using a script or manually. The path is %APPDATA%\Microsoft\Windows\Start Menu\Programs\Startup.

Classic Teams Launches from a Scheduled Task

Check for scheduled tasks that run the classic Teams executable. Open Task Scheduler and look for tasks named “Teams” or “TeamsUpdater”. Disable or delete these tasks.

New Teams and Classic Teams Have the Same Shortcut Name

Users may click the classic Teams shortcut because it has the same name as the new Teams. Rename the classic Teams shortcut to “Teams (Classic)” or remove it entirely.

Classic Teams vs New Teams: Key Differences

Item	Classic Teams	New Teams
Deployment	Per-machine MSI or per-user MSIX	Per-machine MSIX with automatic updates
Performance	Uses more memory and CPU	Uses up to 50% less memory and CPU
Policy control	Controlled via Teams admin center and Group Policy	Controlled via Teams admin center and Group Policy
Startup behavior	Launches automatically at sign-in	Launches automatically only if configured

After applying the steps above, you can verify that classic Teams no longer launches. Sign out and sign back in on a test device, then check the Task Manager for the Teams process. If the process is not running, the fix is successful. Next, consider enabling the policy that sets the new Teams as the default app for all users. You can also use the Teams admin center to monitor app usage and confirm that only the new Teams is active.