Screen Sharing Causes System Shutdown on Surface Pro
Dear Microsoft Teams Support, We are encountering a persistent issue with one of our users involving Microsoft Teams on a Microsoft Surface Pro 2 device. Each time she attempts to initiate screen sharing, the computer abruptly shuts down. We have already performed extensive troubleshooting, including: Verified that all drivers are up to date. Closed all background applications before attempting screen sharing. Updated Microsoft Teams to the latest version. Cleared the Teams cache. Attempted both repair and reset of Teams via Windows Settings. Ran System File Checker (SFC) and DISM scans, both of which reported no issues. Uninstalled Teams and downloaded the latest installer, but reinstallation fails. Despite these efforts, the issue remains unresolved. We would appreciate your guidance on further steps or escalation to resolve this problem. Thank you for your support.
"The paramter is incorrent" error in new Teams client (VDI)
Hello We have a serious issue with the new Teams client in our VDI (Horizon) environment. After running fine for a while (can be multiple hours up to days) Teams crashes / vanishes with the following error. We suspect it might happen during an automatic update. The same error is displayed when trying to launch ms-teams.exe from that path manually. This never happened with classic Teams. We have no idea what causes this and how to fix it, any help is appreciated.
Teams app crash when user use phone
Hello, We have an issue with a user who is using calling phone by number on Teams, Each call, Teams crashes and we are forced to cut the process We are direct routed We use Fslogix profil on on-prem rds2016 We have completely redone the user profile, We have updated the teams to the latest version, and tested the preliminary version : the problem is still there we have tested version 1.4.00.26376 and the calls work We have checked the configuration of the voice and license teams calls works on Teams web and Teams for mobile Thank you for your help Best RegardsTeams crashes overnight SBOX_FATAL_MEMORY_EXCEEDED
I use Teams in a Chrome tab exclusively Every morning that I come to work, the tab has crashed with the SBOX_FATAL_MEMORY_EXCEEDED message, Chrome is left using 8GB + of memory IMO it's a memory leak in the application code. Are there certain steps that I could do to give more information? Logs? A Chrome performance trace? Thanks, Philippe
Teams runs for an hour after install, and then dies
This is a weird one, and my work IT department can't seem to come up with any ideas other than "reinstall teams after various 'tweaks'" (Which has now been done a dozen times) or "Reimage your PC." The latter really means "lose your PC for a day, and lose productivity for the following week while you put the tools you actually use to do your job," so it's not really an option. And since we have no root cause, who's to say it won't start happening. Immediately after restarting teams, I get in and can interact with people, and then, without warning, the teams window vanishes. The teams system tray icon is still there, but gives me: When I right click the system tray icon, I get the following options: 1. Get Logs – opens notepad to give me the above log file 2. Collect Support files – cranks for a while and then shows me my “downloads” directory 3. Settings –gives me the ability to set whether Teams starts on login. 4. Open – this does NOTHING 5. Quit – exits teams. Rebooting or Restarting Teams after it has gotten into this mess will result in one of the following behaviors: 1. Teams icon sits with the above options. 2. white blank window appears, disappears, and reappears multiple times. 3. Teams system tray icon appears and disappears. 2 & 3 may eventually stabilize back on #1. And 2 & 3 are not mutually exclusive. Among the tweaks that have been recommended are: 1. apply all windows updates. 2. apply the Windows 21H1 feature update. Since this is essentially a reinstall of the OS, I didn't want to do it, but did. 3. Registry hacks including removing app compatibility information. 4. Switch from Websense Forcepoint DLP to Digital Guardian. I'm sure there are more than a couple of "darts" they chucked that I have forgotten, but you get the point. Since Teams was nice enough to collect the "support logs" in one place, here is the log set from the most recent time it croaked an hour or so after the reinstall. This has happened through literally a dozen reinstalls. If this was something like a DLL conflict, or other classic application interaction, I would expect the application to fail immediately after install, not anywhere from 30 minutes to 3 hours later. Miraculously the mobile client still works, and the web client works after a fashion (notifications are iffy @ best using EDGE). But the whole point of the desktop client is to have it come up as soon as I log in, and not when I remember to open the browser.Microsoft teams crashes during video calls.
Hi, I have this problem since many weeks now, Microsoft Teams crashes and restart itself 5-10 min after starting a call. The screen share is very slow, meaning that if one of my colleagues shares his screen to me, it takes a very long time for me to see his screen (black screen). When my colleagues activate their camera, the frames per second of the retransmission is very very low, it is very jerky, it is not smooth at all. When I use my desktop computer, it works perfectly fine, but when I use my laptop (Dell XPS 9300 2020), it is a mess... My laptop has a pretty decent configuration, so it is not a problem of performance. I can also assume that it is not a problem of internet, because my internet is pretty fast. I tried to uninstall and reinstall Microsoft Teams, nothing was fixed. Thank you.Teams Desktop App crashes in a restart loop (renderer process crashed)
Version: 1.3.00.28779 (64-Bit) - Windows 10 (20H2) If I start Teams Desktop App it crashes after a few seconds, restarts and then the same thing on and on... In the past it worked perfect on this system, but someday this error occured - maybe after driver or windows updates, don't really know. What I still tried: uninstall Teams install newest graphic drivers install all Windows updates deleting all cache data in appdata directory starting Teams by teams.exe directly, not by shortcut changing audio devices change window size directly minimize window to task bar and wait These are all "errors" in the logfile - i think the render process is the crash moment. Mon Dec 21 2020 14:28:31 GMT+0100 (Mitteleuropäische Normalzeit) <18028> -- error -- getInstallOrUpdateTime failed Mon Dec 21 2020 14:28:31 GMT+0100 (Mitteleuropäische Normalzeit) <18028> -- error -- Error occurred while saving env_config.json Mon Dec 21 2020 14:28:33 GMT+0100 (Mitteleuropäische Normalzeit) <18028> -- error -- Error saving cookie Mon Dec 21 2020 14:28:34 GMT+0100 (Mitteleuropäische Normalzeit) <18028> -- error -- RegistryService: failed to register Sfb App with error: No Path Mon Dec 21 2020 14:28:42 GMT+0100 (Mitteleuropäische Normalzeit) <18028> -- error -- Renderer process crashed; rendererName=pluginHost; crashType=crashed; url=about:blank; restarting app=YES
