Forum Discussion
Machine-Wide Teams - White screen and crashing often
Azure Virtual Desktop version of Teams crashes often for staff displaying a white screen. When this occurs, often Edge and sometimes Explorer will also freeze and crash.
Teams Machine Wide version 1.6.00.1381
Windows 10 Enterprise Multi-Session
FSlogix 2201 hotfix 2
To resolve the issue, user must quit teams from the tray, then close it from the task bar and attempt to re-launch (Sometimes instantly crashing upon relaunch too). This occurs multiple times a week (or day) for multiple users across multiple session hosts.
When edge freezes at the same time, it doesn't have any obvious issues - just stops responding and does not seem to matter what websites you're on at the time.
This has been occurring for many months, sometimes going away for a while - then returning frequently. We've been hoping updates will fix it, but as we are intending to roll out teams telephony business-wide soon, we really need this to be rock solid without random crashes happening.
I definitely believe teams crashing and edge freezing are related and the same issue at hand.
We have created a support ticket but waiting for response. Posting here hoping someone has resolved this issue.
our Teams issue got fixed after re-deploying all Win10 AVD hosts in the Host pool from the gold template (we use Nerdio). Our FSlogix was a bit behind and I also installed the latest version 2.9.8440.42104. I doubt FSlogix was the root cause.
13 Replies
Hi PaulStirling , We are having the exact same issue. Did you figure it out?
We are running the latest version of Teams (1.6.00.7354), Windows 10 Updates, latest AVD client, etc.
- Funny you should ask. I have been doing a lot of work on this tonight.
We have been through many Teams, Agent, FSLogix, OS updates since an no joy.
We find it happens mostly in the afternoon with full load. but that may be a coincidence.
Just this week I completely rebuild our image, Window 10 2H22 from MS library, every app installed fresh etc etc. Same issue!
After a ton of googling I have just now refined our FSlogix GPO to ensure no teams or MS edge cache is included in the profile to keep it fresh. Also, disabled GPU acceleration on Teams (GPO to edit the JSON setting file for each user) and Disabled 'User hardware acceleration if available' on edge (we don't use a GPU on our VMs).
According to some articles this may help. So I'll update you next week!
So incredibly frustrating when we are trying to go production with Teams Telephony. We simply can't until this is resolved.
What is your experience and what have you tried?- Further to this. New users into our organization also get this issue, so clearly not the FSLogix profile itself. Really am pinning my hopes on turning off GPU acceleration, or some built up of cache issue.
We have worked on a Microsoft support ticket for this and essentially went nowhere so any help you or anyone can provide would be much appreciated. Troubleshooting info etc
