Teams install with MS 365 apps fails and causes removal loop

Question

Teams install with MS 365 apps fails and causes removal loop

Doug Cote 6

We are migrating users from MS 365 apps 32-bit to 64-bit. With every deployment group, some percentage of users report that Teams is missing from their device after install. I've compared the C2R logs between a user who successfully migrated without issue to a user that lost Teams. In both cases it appears that the ODT invokes a Teams install despite the fact that the Teams client is already fully installed (Teams user-based install and Teams machine-wide installer are both present). For most users, the process runs normally, as shown in these lines I found in the C2R log...

For a user with Teams missing, the log shows this...

It seems like this failure is resulting in a repeated re-install attempt that's stripping Teams from the device and then failing to recover it, but I can't seem to find root cause. The 1638 error code indicates "another version is already installed". I don't understand why most don't have a problem but some do. I am guessing I could potentially prevent this by always removing an existing Teams install before installing MS 365 apps, but that's going to add more time to the migration I'd like to avoid and would likely downgrade the version of Teams, which is even worse. Is there some way to suppress this behavior if Teams is already on the machine? Anyone run into this and can offer other options? Thanks for your assistance.

Yuki Sun-MSFT 41,376 Reputation points Moderator

2022-01-17T08:12:09.673+00:00

Hi @Doug Cote ,

I don't understand why most don't have a problem but some do.

Have you had a chance to compare the version information of the Teams application via Control Panel to see if there are any difference between the problematic ones' and the others' who have no issue?

From the information you shared above, I am thinking that there might be some differences on certain Teams related registry keys local files between the normal users' machines and the others' which finally led to the 1638 error code. But after searching around, I didn't find any relevant information for digging deeper. So given this situation it could be time consuming to troubleshoot the issue, personally agree with you on that removing the existing Teams install before installing MS 365 apps might be the best option currently.
Yuki Sun-MSFT 41,376 Reputation points Moderator

2022-01-20T02:55:23.15+00:00

Hi @Doug Cote ,

I am writing to see how everything is going on with this thread. Should there is any update or you need further assistance on this, feel free to post back.
Doug Cote 6 Reputation points

2022-01-20T14:19:51.017+00:00

Hi. Thanks for getting back to me. I was hoping for something a little better to prevent this condition from developing, but I'm resigned to the fact that the process of migrating from 32 to 64-bit is too complex for the existing tools to handle gracefully 100% of the time. I'm going to try to update my install logic to detect when the 1638 error appears and only proceed with a remove/re-install at that point. We'll see if that's possible.
Yuki Sun-MSFT 41,376 Reputation points Moderator

2022-01-25T09:03:29.367+00:00

Thanks @Doug Cote for sharing the current status of this issue. By the way, if you figured out a better way to deploy Teams with Microsoft 365 for your case, would be much appreciated that you can briefly share your solution here. That must be super helpful for others who encounter a similar situation.

Your answer

Yuki Sun-MSFT 41,376 Reputation points Moderator

2022-01-17T08:12:09.673+00:00

Hi @Doug Cote ,

I don't understand why most don't have a problem but some do.

Have you had a chance to compare the version information of the Teams application via Control Panel to see if there are any difference between the problematic ones' and the others' who have no issue?

From the information you shared above, I am thinking that there might be some differences on certain Teams related registry keys local files between the normal users' machines and the others' which finally led to the 1638 error code. But after searching around, I didn't find any relevant information for digging deeper. So given this situation it could be time consuming to troubleshoot the issue, personally agree with you on that removing the existing Teams install before installing MS 365 apps might be the best option currently.
Yuki Sun-MSFT 41,376 Reputation points Moderator

2022-01-20T02:55:23.15+00:00

Hi @Doug Cote ,

I am writing to see how everything is going on with this thread. Should there is any update or you need further assistance on this, feel free to post back.
Doug Cote 6 Reputation points

2022-01-20T14:19:51.017+00:00

Hi. Thanks for getting back to me. I was hoping for something a little better to prevent this condition from developing, but I'm resigned to the fact that the process of migrating from 32 to 64-bit is too complex for the existing tools to handle gracefully 100% of the time. I'm going to try to update my install logic to detect when the 1638 error appears and only proceed with a remove/re-install at that point. We'll see if that's possible.
Yuki Sun-MSFT 41,376 Reputation points Moderator

2022-01-25T09:03:29.367+00:00

Thanks @Doug Cote for sharing the current status of this issue. By the way, if you figured out a better way to deploy Teams with Microsoft 365 for your case, would be much appreciated that you can briefly share your solution here. That must be super helpful for others who encounter a similar situation.

Share via

Teams install with MS 365 apps fails and causes removal loop

Your answer