Regarding the Microsoft Teams Installation Folder After Patching

Question

Regarding the Microsoft Teams Installation Folder After Patching

원성 박 0

Our company uses an internal system recovery application. This application restores the computer to a predefined state whenever the computer is restarted.

Recently, we encountered an issue with Microsoft Teams. After a Teams update is released, an unupdated version of Teams can no longer be used. Therefore, we would like to exclude the Microsoft Teams installation files from our system recovery process so that Teams updates can be retained after a reboot.

However, we found that the installation folder for Microsoft Teams changes with every update. The folder name contains the specific Teams version number, and therefore the folder path changes every time Teams is patched.

Because of this, it is not possible for us to specify the Teams installation folder as an exclusion in our system recovery application.

We would like to know if there is an officially supported way to configure the Microsoft Teams installation path or specify a fixed folder/path that does not change when Teams is updated.

There are also some important limitations in our environment:

It is not possible to disable the system recovery application, perform the Teams update, and then re-enable the recovery application every time an update is released. We have a large number of company computers, and updating each computer individually in this way would require significant time and effort. Additionally, some users cannot or do not want to perform this procedure themselves.
We cannot exclude the higher-level Microsoft application folder from the recovery process because that folder contains many other Microsoft applications and system files that must remain protected.
Therefore, we need a way to exclude only Microsoft Teams from the system recovery process while allowing Teams to update normally.

Could you please advise us on the recommended or officially supported solution for this situation?

In particular, we would like to know whether Microsoft Teams provides a fixed installation path, an environment variable, a wildcard-compatible path, or another supported configuration that would allow us to exclude Teams from a system recovery application even though the Teams version-specific folder name changes after each update.

댓글 0개

답변 1개

답변

Answer 1

Since you posted your question in English , I’ll reply in this language as well. If you’re more comfortable using another language, please let me know, I’ll be happy to tailor my response to your preferred language.

Hi @원성 박,

Thank you for your question.

Based on the information available, Microsoft Teams (new Teams) is deployed as an MSIX application and uses a version-specific installation folder that changes when the application is updated. At this time, there does not appear to be a documented option to configure a fixed installation path or prevent the folder name from changing across updates.

Because your scenario involves a third-party system recovery solution and requires guidance on supported deployment and exclusion methods for your specific environment, I recommend opening a support case with Microsoft Support. The support team can review your environment in detail and provide guidance on any available deployment, update management, or recovery-related options that may apply to your organization.

Find your Microsoft 365 admin: If you don't know who the global admin is in your organization, you can find guidance here: How can I find my Microsoft 365 admin? - Microsoft Support
Submit a service request: The Global Administrator should create a support request with Microsoft to receive advanced technical assistance. For detailed instructions, see: Get support - Microsoft 365 admin | Microsoft Learn
If your subscription is from a partner or reseller, contact the reseller's support provider to help open a service request on behalf of you instead.
If you have access to Premier/Unified Support, you may also open a ticket through your organization's support agreement.

If you discover any solutions or have additional insights, please consider replying to this thread to help others in the community.

I sincerely apologize for redirecting you to the Microsoft Technical Support Team. While I strive to assist as much as possible here in the forum, my resources are limited when it comes to backend-level diagnostics and advanced troubleshooting. Some issues require deeper technical analysis and access to internal tools that only the official support team can provide.

If you need further assistance, feel free to reply. I'm here and happy to help!

Note: Please follow the steps in the forum documentation to enable e-mail notifications if you want to receive the related email notification for this thread.