This message was deleted.

I would expect it to be released in May, based on the timeframe between CUs. It contains a fix for crashing that we have seen in our environments, so we're also waiting for it.

I had to go to 2203 CU2 VDA due to the recent high sev security vulnerability affecting prior VDA versions

I have nothing to base this on, but since 1912 CU7 (CU6 in November) was just released, I expect 2203 CU3 (CU2 in December) in April, based solely one prior release cycle. @Nick Panaccio What crashing are you seeing? We have our entire 2016/2019 server environment on CU2 and not seeing anything crash related. UPM issues, for sure.

For us, in 2203 CU2, after booting up a VDA and waiting (no specific timeframe, all random), I'd see picadd entries in the event list stating that virtual channels were being blocked (Webex/ControlUp was attempting to open them). If we launched a Webex meeting after this happened, Webex would launch unoptimized and the VDA would blue screen. I was able to reproduce this every single day, at least once per day. Citrix provided a private hotfix (picadd.sys and PicaSvc2.exe) for CU2 that completely resolved the issue for us, and told us it should be included in CU3. That made sense given that the file version of both was .3000.

Ah, I don't block virtual channels yet.

We don't, either... I have a policy explicitly allowing all VCs. That's what made this weird.

Ok. Yeah, that's really weird.

ya for us we have no idea what it is but definitely can say both 2203 cu1 and cu2 will sporatically (few times a day) blue screen us (mcs persistent) and if we uninstall/reinstall w/ 1912 all is good. loooooong running ticket w/ both microsoft and citrix in which Microsoft pointed out picadd.sys as the culprit and citrix is being difficult now asking me to start totally over and get more crash files (examples exactly like what i opened the ticket w/ months ago so i'm pushing back)

Had lots of crashing issues with CU1 as well, but mainly on 2016 servers and didn't deploy very widely because of it. Whatever they found for our specific issue they provided a private fix for and included in CU2. There's always something with picadd.sys it seems.

I get random issues when I try to reconnect to an existing session, and end up with the error "Unknown client error 0".

I'd wait for CU3, personally, if you're able to. It should be right around the corner, and will have a slew of other fixes in it.