Prevent antivirus and DLP tools from blocking or crashing Microsoft Teams

Third-party applications for antivirus, reliability monitoring, and data loss prevention (DLP) can interfere with the Microsoft Teams app and Edge WebView2. These tools can degrade Teams client performance and also cause the app to exit unexpectedly. To improve application stability and efficency when you use non-Microsoft antivirus or DLP applications on desktops, you can include or approve the use of the Teams app, the executable that automatically updates the Teams app, and Edge Webview2.

New Teams

To prevent issues from occurring when you start or use the new Teams app, add all the following processes to the exclusion list in the antivirus software that you use:

• msedgewebview2.exe
• ms-teams.exe
• ms-teamsupdate.exe
• ms-teams_autostarter.exe

Alternatively, you can add the processes to the allowlist for programs in your DLP application. The method to accomplish this addition varies. For specific instructions, contact your DLP application manufacturer.

The MSIX installer installs the new Teams app in the WindowsApps folder instead of the user profile folder in which the classic Teams app is installed. Because users can't write to the WindowsApps folder, this location adds better protection against attacks that are intended to alter the installation of the Teams app.

Note: The MSIX installer and all files in the same directory are signed by using a Microsoft certificate.

The name of the folder in which the new Teams app is installed is dynamic and it changes when the app version is updated. The folder name begins in MSTeams_, ends in _8wekyb3d8bbwe, and includes the app's version number in between. For example, MSTeams_23247.1112.2396.409_x64_8wekyb3d8bbwe.

Location of the Teams installation folder

To add the Teams processes to either the exclusion list or the allow list, you can find their location by using the following steps:

1. Open Windows PowerShell and run the following cmdlet to determine the location of the installation files:

   Get-AppPackage -name "msteams"
   

   The results include the value of the InstallLocation parameter, such as C:\Program Files\WindowsApps\MSTeams_23247.1112.2396.409_x64_8wekyb3d8bbwe.

2. To view the individual files, open Task Manager, and select Details.

3. On the Details tab, locate and right-click ms-teams.exe, and then select Open file location.

Classic Teams

To prevent issues from starting the classic Teams app, add the following processes to the exclusion list in the antivirus software that you're using:

• C:\Users\*\AppData\Local\Microsoft\Teams\current\teams.exe
• C:\Users\*\AppData\Local\Microsoft\Teams\update.exe
• C:\Users\*\AppData\Local\Microsoft\Teams\current\squirrel.exe
• C:\Users\*\AppData\Local\Microsoft\TeamsMeetingAddin

Alternatively, you can add the processes to the allowlist for programs in your DLP application. The method to accomplish this addition varies. For specific instructions, contact your DLP application's manufacturer.

Applications that might block Teams or cause it to fail

The following table lists applications and their associated DLLs that are known to potentially block or cause Teams to stop responding.

Other DLLs that might affect Teams desktop client and Edge WebView2

The following DLLs are known to affect the Teams desktop client and Edge WebView2. You should verify the presence of the DLLs, and also verify the ownership and integrity of the DLLs.

• bsijt64.dll
• core64.dll
• cptlwa64.dll
• cryptacl.dll
• csprnthk.dll
• cssguard64.dll
• ctiuser.dll
• dgapia64.dll
• dsefilesystemext64.dll
• dsloaderinj.x64.dll
• emcnt64.dll
• encappctrl64.dll
• estoutgo64.dll
• f_lph.dll
• guard64.dll
• hkapi.x64.dll
• hookcreateprocessinternal64.dll
• imfph64.dll
• ldgetprintcontent64.dll
• ldprintmonitor64.dll
• ldsmartenc64.dll
• ldwatermarkhook64.dll
• ldxghijt64.dll
• libwire_api_monitor_4.4.0.9.1662362401.dll
• lpghijt64.dll
• monfileop64.dll
• mozartbreathprotect.dll
• oeareader64.dll
• printhk64.dll
• sbieoutside.dll
• sdckern.dll
• sdwhf2130.dll
• tmailhook64.dll
• tsafedoc64.dll
• uhk64.dll
• vozokopot.dll
• winahframe64.dll
• wincept64.dll
• winncap364.dll
• xpspntdll64_6016.dll

Third-party information disclaimer

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

Third-party contact disclaimer

Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

Third-party information and solution disclaimer

The information and the solution in this document represents the current view of Microsoft Corporation on these issues as of the date of publication. This solution is available through Microsoft or through a third-party provider. Microsoft does not specifically recommend any third-party provider or third-party solution that this article might describe. There might also be other third-party providers or third-party solutions that this article does not describe. Because Microsoft must respond to changing market conditions, this information should not be interpreted to be a commitment by Microsoft. Microsoft cannot guarantee or endorse the accuracy of any information or of any solution that is presented by Microsoft or by any mentioned third-party provider.

Microsoft makes no warranties and excludes all representations, warranties, and conditions whether express, implied, or statutory. These conditions include but are not limited to representations, warranties, or conditions of title, non-infringement, satisfactory condition, merchantability, and fitness for a particular purpose, regarding any service, solution, product, or any other materials or information. In no event will Microsoft be liable for any third-party solution that this article mentions.

Still need help? Go to Microsoft Support Community.