Forum Discussion
Solved
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 versio...
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.
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?
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
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
- I'm having the same issue, only it's Windows 11 Enterprise Multisession.
I'm using FSLogix 2.9.8440.42104 with Teams 64-bit machine-wide install version 1.6.0.6754. (I also used an earlier version of FSLogix and Teams prior, same issue).
I also disable GPU acceleration and excluded Teams cache using the redirections.xml, following the guide here: https://techcommunity.microsoft.com/t5/azure-virtual-desktop/wvd-fslogix-reduce-profile-container-size-exclude-teams-cache/m-p/1503683 (The GPU and Teams cache exclusions did not help).
The weird thing I've noticed is if I log into a Win11 AVD host, Teams will launch fine. As soon as I login to that same host as the 2nd test user and Teams opens, it will display the teams app info normally for about 5 seconds, then white screen. If I quit and re-open Teams, that does not fix it either. If I do the reverse and login with my test user 1st, Teams opens just fine and as soon as I login with the 2nd user is when Teams white screens.
Luckily I'm just testing and we have no users in this environment. I feel your pain though, I probably spent 10+ hours troubleshooting this, spinning up new VMs, re-installing Teams, FSLogix, Recreating FSLogix user profiles, no dice.- Wow interesting experience, thank you for sharing. Certainly is an annoying and tricky issue to pin down.
So to confirm from my recent testing. Excluding cache, disabling GPU acceleration did not help for us either. Monday morning went by fine for our 150 users, then in the afternoon around 2-3pm we started having the random white screen for some users, but not others.
Here is a log we captured on our MS ticket in Feb (which ended up being closed with no resolution). I can confirm we still get the exact same error in our logs now.
Thu Feb 23 2023 13:54:05 GMT+1300 (New Zealand Daylight Time) <106516> -- warning -- ExperienceRenderer: unable to find experience renderer for metadata
Thu Feb 23 2023 13:54:05 GMT+1300 (New Zealand Daylight Time) <106516> -- info -- Middleware:: Action:
{"type":"RENDERER_CRASHED","rendererId":"main-renderer","time":2420977.4839999974}
Thu Feb 23 2023 13:54:05 GMT+1300 (New Zealand Daylight Time) <106516> -- info -- Middleware:: Action:
{"type":"WEBCONTENTS_CRASHED","webContentsId":"1","time":2420977.6998999976}
I am currently spinning up an AMD version of our SH - Standard NV16as v4 (with a GPU and enable GPU acceleration again) to see if that helps by changing the architecture
Previously we have been using - Intel - Standard D16s v5 (no GPU)
Clutching at straws now...
Another note is we have exclusively Surface pro 7/7+/8's as our client devices, not sure if this is a factor, although it really shouldn't be.
Any other suggestions of what I can try would be greatly appreciated.- This is the post I made, about my experience with much more details - if there's any similarities, might be good to follow:
https://learn.microsoft.com/en-us/answers/questions/1274356/teams-white-screen-and-crashing-on-win11-avd-multi?page=1&orderby=Helpful&comment=answer-1244359#newest-answer-comment
