Has anyone else seen odd behavior with New Teams SlimCore optimization where it’s totally reliable on a pooled random W11 desktops DH but inconsistent (more common failure to optimizt than not) on dedicated 1:1 persistent W11 desktop? The desktop where we see SlimCore fail is persistent, so it’s not like UEM (ProU) is landing a reg setting too late (registry is read from persistent disk). Via Monitor, I see Teams virtual channels open but “plugin not detected” some days on that persistent desktop, yet the same user on the same endpoint gets a 100% success SlimCore‑optimized on a pooled random desktop, and other users on the same persistent pool are fine. Annnnd now the crazy part, if we don't auto-start Teams on the peristent desktop, and had the user launch Teams manually after logon, SlimCore started working consistently. Curious if anyone has run into a similar Teams/SlimCore timing or race condition tied to auto‑start on persistent single‑session desktops, and if you found any clean way to address it beyond just turning off auto‑start. (2603 VDAs/latest CR CWA and CWA/GACS managed Teams plugin)

We personally have not seen this with VDA 2402 CU2/2507 CU1/2607. I have been running the latest CR build of CWA on my endpoint, including the newer x64 build, and haven't had issues. This would be for W11 23H2.

It's odd that it seems to manifest for one user as a race condition... for settings that are not user specific.