0x139 in wcifs!WcRemoveInMemoryTombstoneAfterRenameLink on Server 2019 RDS hosts with new Teams

Your repeated stack is useful escalation evidence, but 0x139 parameter 1=3 establishes LIST_ENTRY corruption, not necessarily where that corruption originated. Microsoft notes that detection can occur after the damaging operation. I could not find a published Microsoft notice matching this wcifs/cldflt signature or a Server 2019 fix date, so I cannot confirm it as a known defect or promise a patch. Open a Windows Server support case and provide the kernel dumps privately, exact OS/Teams versions, crash times and your cross-host comparison. Ask support to correlate the affected list entries and filter state rather than treating the process name as proof of cause. There is also a support boundary: Teams’ current VDI guidance lists Server 2019 support ending October 2025 and Server 2022 ending October 2026, recommending migration to Server 2025. Pilot a supported configuration with controlled variables; the existing Server 2022/FSLogix comparison changes two variables and cannot isolate either.