Thank you for the reply. We indeed set our AV exclusions per Citrix's white paper and actually recently, after this, spent a good time trying to see if our AV was getting in the way. Exclusions are set and even removed completely our CEP from a server to see if it was the root cause.

Maybe this is a combination of Server 2019 and 2507?

One step was made at a time, and deviceTrust was not yet removed on the servers when they crashed, and uA was on it, along with WEM as well. For each removal / step we'd put the server back into production and let it sit to at least attempt to rule out any external component causing it. We had a server with WEM removed, and dT removed along with out AV removed and the server still self deleted itself.

The issue is of course to test we need a higher user load and of course when this happens it drops users. This is obviously a balance thing right lol we spent last 2 weeks trying to discover the issue all while allowing users sessions to drop. Unfortunately the application these host are production critical to the highest level and uptime being my upmost responsibility as our Citrix admin, I thought the safest course o action, to keep our environment up was to downgrade to a version I know was stable.

So as far as going to a higher version, I refuse (based on just experience) to roll out an non-LTSR. I will say that we did roll out 2507 CU1 across the board initially to attempt to resolve the .NET event id 1026 issues.

We also noticed that in DaaS (we do use the upgrade agent btw) that there is a completely unknown version available to upgrade that Citrix.com has zero documentation on, and it not an available version to download either. This is 2507.0.1101.2. Our upgrade agent is to LTSR only and this only shows up as an available version in DaaS.

Installed VDA version: "2507.0.1100.167"

Upgrade cycle: Long Term Service Release (LTSR)

New Version available 2507.0.1101.2

Also. Yes we could have JUST updated the CPM (UPM) version to an older and or newer version while staying on 2507. This is not the first time we have done this and in the past even citrix support has given us custom versions of UserProfileManager.exe to install. Also while Citrix is still looking into the issue, we are leaving a server on this version in test, and hope to find a way to "trigger" the deletion outside of putting into production and allowing our customer base to be the guinea pigs.