This message was deleted.

Pretty close to cu1. Not sure whats in it.

Not sure I can survive that long...unless it comes out today. 🙂 Looks like the rollback process might not be as simple as I was hoping either.

yea they wont know when

We have a few 2203 for CUPM which seem okay. FSLogix and 2203 sucks so we rolled back to 2106 as all the other releases were bodged!

I have a few clients on 2203 CUPM that are running ok as well. Trying to find the commonality on the ones that are having issues, and it seems like its the more active/larger clients, but still could be something else entirely. Still digging.

@Dave Brown haven’t seen issues with 2203 and fslogix.

@Dennis Parker we have the Zoom VDI client installed on all the problematic servers too.

@Dave Brown That's very interesting to note. I rolled back to 1912 CU3 for my troubled clients but I may see if I can find a way to go about testing that doesn't affect clients now that I have something possibly to go on. I appreciate the feedback. Looking forward to your results.

@Dennis Parker hi Dennis, are you using 2203 with the UPM solution from Citrix, and if yes, with profile containers or originally roaming profile, or to you have FSLogix in place. thx and remain with best regards Thorsten

@Thorsten Sorry for the late response...was away on vacation for a bit. We are using UPM from Citrix with Citrix Profile Containers.

Hello All, Have you any news on this BSOD problem ? In my case, it's about 10 out of 800 VDAs per day. We are using CPM (not FSLogix) and OS is Win2016

For the 2016 BSODs, we have memory dumps submitted to Citrix which are "under review by the next level of support" for what that's worth. I was expecting 2203 CU1 to release and have a fix actually, but no word on that. It feel like it may not have been ready for public release after the early access users got a hold of it for testing maybe. That's pure conjecture on my part though. I haven't done more testing with Zoom, and have been wondering about @Dave Brown's experience with removing Zoom as a test.

In my case, Zoom plugin is not used. I will check if I see some users doing Zoom before the BSOD

To be clear, 2016 servers and BSOD is not related to Zoom here either. Zoom is on the 2019 servers with profile issues.

@Dennis Parker unfortunately when I removed Zoom it made no difference, 😞 is anyone rushing out to check 2206? Based on 2206 not announcing any fixes I can’t imagine its going to make any difference.

Thanks for the follow-up @Dave Brown. I'll have to go back and see what/if I can find....I'm not hopeful, there must be something because I have several 2019 client servers that aren't having the profile issues. And the few that were rolled back. Can't move forward 2203 until something is resolved. Need 2203 to get support for issues we are having. I am frustrated with the support situation we are in at the moment.

@Dennis Parker any news about the BSOD issue with 2016 Server and VDA 2203. We do open an incident, we think it could be something with users connecting with HTML 5 receiver --> testing the next two days. And next would be, go for CU1. thx Thorsten

@Thorsten We have a VDA with some additional logging enabled per Citrix support request. We had that VDA experience the BSOD on Friday and have provided Citrix with the logs. It is possible that it is the HTML5 receiver. I was suspecting the Mac clients as well, as there are many of them. Support says there is not a fix in CU1 as they don't know what the issue is yet.

@Dennis Parker do you happen to know what the private fix was listed as from Citrix? We’ve had quite a lot of success with 2203 CU1 with the registry fix for “EnforceUserPolicyEvaluationSuccess”. This morning I just noticed one of our VDA’s BSOD for the first time, it was updated to 2203 CU1 last night.

To be clear, the BSOD is only on the 2016 servers in our environment. I don't know what they have done to fix it by any stretch. I don't have a fix number to provide you, but our case number is: 81228955 if you can get support to look at the case and see what fix and history they can provide.

Much appreciated, I’ve only observed it on 2019 servers. There's been two so far. Appreciated for the case details, I'll put a ticket in.

we have also BSOD with Server 2016, Case is open, but takes weeks to give us the files to get it fixed. we hope 2209 version comes out this week.