This message was deleted.

Ouch, that’s disappointing to hear.

Interesting, I've only got 2203 CU1 at one customer, they did report some app launch issues, but I had figured it was down vSphere DRS being active. I asked them to disable DRS for the impacted VDAs. In your case, what errors are logged on the VDAs or 2203 infra?

@Owen Reynolds this thread basically. No errors, just hundreds of zombie sessions on any VDA we have attempted to move to past 1912_CU3 (not tried CU5) or the patched 2112

Ok! I'll review for the same symptoms

Actually i take that back.. There was an error with VDA 2203 and Office apps, Excel seeming to the main one. Redacted example attached. Rolling back the VDA resolved it, and the weirdness in Director (profiles not showing as running, latency calcs broken, "datasource not responding errors etc") Examples attached. It seems Any VDA past 1912CU3 has been a train-wreck one way or another for highly active farms, 2203 CU1 the worst so far.

Odd ! Never a dull moment 😃 Which OS, btw ? All server 2016? My client is 2019 w 2203.1

Mostly 2016. Handful of 2019 but those are machines we broker user to rather than own / manage, and are persistent VMs.