[22h2] Teams / Other Store apps

[Bugzi]

Hello,

 

Hopefully someone may be able to shed some light on this or help me please.

 

I've been looking into an issue for several weeks now but without much success.

 

For example, I've tried to reinstall MS Teams app via the Microsoft's bootstrapper.exe but to do this I tried to uninstall teams first.

I know the new Teams app is a MSIX/Store app so I've tried to run the usual Appx commands in PowerShell but if more than one user had logged into the device it is failing to remove the app.

 

When I try the command "Get-AppxPackage -Name MSTeams -Allusers | Remove-AppxPackage", this generally fails with an error about remote procedure call.

I get the same if I run Powershell as system user, using psexec.

 

As a test I manually removed all the profiles via Control Panel, but when you run Get-AppxPackage -Name MSTeams -AllUsers, it is still listing the app installed under the old profiles.

 

Apart from a complete reimage of the device, I've not had any luck with trying to find a working solution.

 

Does anyone have any tips please?

 

Thanks

[DavR]

How was Teams previously deployed in your environment? I'm not sure it needs to be removed from every profile before you deploy the new version, just go ahead and deploy it via the bootstrapper.

 

Teams lives entirely in the individual user profile; all the deployment packages for Teams do is put install / update files into a central location on the PC, to then install /update into user profiles.

 

When Teams users try to use their current version, I think it should then just update to the new version.

[Bugzi]

I used the bootstrapper previously but it seems the MSTeams.msix from February 2024 seems to be to old by now as the bootstrapper was throwing non stop error codes at me when I tried to manually install it after SCCM was reporting errors.

 

The behaviour with store apps I described I see with other store apps too on our devices.

[DavR]

OK, there's two separate issues there I think.

 

If the Feb 2024 version isn't working, then go ahead and download the latest Oct/Nov 2024 version from here - https://learn.microsoft.com/en-us/microsoftteams/new-teams-bulk-install-client#option-1b-download-and-install-new-teams-using-an-offline-installer. That link also contains useful info on deployment, I'd read the whole page just to check.

 

The second point re the behaviour with "Store" apps, do you mean apps you bought via Microsoft Store, or, just UWP/msix apps in general? If the latter, yes, they are problematic to install and uninstall. Again, because they install into users profiles rather than the machine a lot of the time. When I've needed to remove UWP apps in the past, I've used uninstall scripts either at user login or logout - because the apps are installed per user profile.

[Bugzi]

I tried to use the latest msix for teams but that still didn't work until the device was reimaged. I can't remember the exact error code I got atm.

 

Yes I mean the UWP/msix apps in general.

There are sometimes actual store apps but I try to solve that with WinGET.

 

The issue is, i cant use logon/logoff scripts when users don't log into the same device frequently and then you are stuck trying to solve a broken uwp/msix app on a device, like I had today.

[2097]

Heres everything I use , I install VIA SCCM and the Teambootstrapper.exe

 

Make sure you grab the latest bootstrapper with the MSIX

 

Install.bat

 

 @echo off
taskkill /IM ms-teams.exe /F
taskkill /IM Teams.exe /F
powershell.exe -NoProfile -ExecutionPolicy Bypass -command .\RemoveOldTeams.ps1 -Basic
powershell.exe -NoProfile -ExecutionPolicy Bypass -command .\Install-MSTeams.ps1 -ForceInstall -Offline

 

See attached files and the code above for the batch

 

Install-MSTeams.ps1

 

RemoveOldTeams.ps1

[Bugzi]

Thank you for sharing this.

 

I've actually just stumbled across the installer you use too, on this url:

CodeDump/Install-MSTeams.ps1 at main · suazione/CodeDump · GitHub

 

One of the issues I am tackling is that when I call the bootstrapper.exe with the "-p" command, I get this error code "0x80070490". I've not found a solution to that yet.

 

When people suggest on other websites to use "Get-AppXPackage -Name MSTeams -AllUsers | Remove-AppxPackage -AllUsers", like the install script you have, I then get this error message "Remove-AppxPackage : The remote procedure call failed." That too I've failed at finding a solution for too

[2097]

Thank you for sharing this.

 

I've actually just stumbled across the installer you use too, on this url:

CodeDump/Install-MSTeams.ps1 at main · suazione/CodeDump · GitHub

 

One of the issues I am tackling is that when I call the bootstrapper.exe with the "-p" command, I get this error code "0x80070490". I've not found a solution to that yet.

 

When people suggest on other websites to use "Get-AppXPackage -Name MSTeams -AllUsers | Remove-AppxPackage -AllUsers", like the install script you have, I then get this error message "Remove-AppxPackage : The remote procedure call failed." That too I've failed at finding a solution for too

 

On the .exe file , make sure you its "Unblocked" .

 

On the MSIX i had to also make sure it was correct as i was also experiencing issues when installing originaly.

 

providing the MSI and Exe are in the folder with the script , it shouldnt reach out from the internet.

Edited November 6, 2024 by 2097

[Bugzi]

Thanks.

 

I've checked and both the .exe and .msix are unblocked.

 

for newly imaged devices, using the bootstrapper.exe this works fine now.

 

For existing devices which has users on already, this is still problematic.

 

Another error code I got when trying to run teamsbootstrapper.exe -p either as admin or as system (using psexec) is "0x80073CF9".

This I managed to resolve with the following:

 

b) Type "net stop wuauserv" and press Enter.c) Type "rename c:\windows\SoftwareDistribution softwaredistribution.old" and pressenter.d) Type "net start wuauserv"and press enter.

 

When I run the Install-MSTeams.ps1 either as admin or system user, that also errors out with "The remote procedure call failed.".