Anyone ever see this before with Teams 2.0? This is the second launch of the desktop with my profile saved in CPM, with all required Teams settings per MS's docs. I was expecting Teams to auto-launch, which never happened, and when I manually launch this, I get this error. Server 2025, 2507 LTSR, App Layering.

Are the AV exclusions configured? We once had this issue when the S1 agent was not up to date.

The CrowdStrike team refuses to exclude anything, so that's a no go there.

FSLogix is not installed, right? I found the following in the Microsoft documentation: • msteams_autostart.exe "The parameter is incorrect": In non-persistent environments that use FSLogix (any version before 2210 HotFix 4) or Citrix Profile Manager profile containers, when Teams attempts to autostart or a user tries to launch Teams from the Start menu, it throws the error: "The parameter is incorrect." The frequency and reproducibility of the error varies depending on the environment and especially the antivirus software being used (SentinelOne, Palo Alto, Trend Micro, Bitdefender, CrowdStrike, and so on.) and exclusions in place. This issue is now fixed on FSLogix 2210 HotFix 4. Customers facing this issue with Citrix Profile Manager are must upgrade to CPM 2402 or 2203 CU5. ◦ "The parameter is incorrect" error can be caused by other file system drivers. Running fltmc from an elevated command window lists the drivers. Two Citrix drivers (UPMAction and upmjit) can cause the error, even if you're only using FSLogix HotFix 4 and don't have Citrix Profile Manager. This error happens because Citrix VDA installers typically install profilemgt_x64.msi by default for Citrix Director monitoring of logon time counters. Removing that MSI can fix "the parameter is incorrect" error.

Nope, just using CPM for this.

@richminichiello something like we were working through with this whole packages folder situation

The behavior is absolutely wild. I didn't exclude AppData\Local in my first test and was seeing 8-15 minute sync times. I exclude AppData\Local\Packages and first logon is up to 50 minutes on the sync time.

did you work through this @Nick Panaccio?

Yes, my issue is our storage. When I use a VDA in the same datacenter, I see normal logoff times around 1 minute.

If you reset Teams data, does it work? It's most likely the mirrored vhdx roaming ...

@Nick Panaccio Are you using S1 ?

Haven't tried resetting Teams data yet, but will do that the next time around. And yes, we suspect the vhdx. Hopefully my buddy kept a copy of the bad one so that we can compare the two. If resetting the data works, I'll try and create a self-service PS script to perform that action for the users.

Sorry, SentinelOne

Ah, no, we're a CrowdStrike shop.

Nope, for prod W22, it's only file-based. For new, W25, I've tested accelerated mirroring, I saw the Ctx statement .. without any exclusions, it's 2.5GB LOL ... So I was testing with the exclusions but I'm not comfortable to have this running in prod. Especially that now you have issues with it!

That's where I am with this. Not sure I trust excluding anything if Citrix says not to.

I am tempted to raise a case to confirm, it doesn't make sense! For now I'll prob stick to file-based for W25, still the best option so far IMO

@richminichiello didn't we fix this by deleting something from hkcu with a login script

There was something that we were triggering with WEM to delete some data at disconnect/reconnect I believe. We'd have to look in your tenant and see.