we somewhat recently moved many of our customers from FSLogix to UPM. we might have not realized it at first, but I think we are having a lot of problems with users' registry - their NTUSER.DAT files essentially get reset, so their sessions' AppData is ok but registry isn't right. and so you often hear complaints of "temp profile" although I don't think that's really accurate. the VHDX attaches with their existing AppData, but with new NTUSER.DAT. and so we roll back the VHDX and it's good. but I see how FSLogix and UPM handle this differently. we use CrowdStrike, and I see Citrix has a long list of files and paths to do CrowdStrike SVE (Sensor Visibility Exception) on... our standard has been to not use SVE's as it is higher risk - but I'm curious if others have done that

You definitely need the exclusions, unless you want to end up with a painful user experience

have you experienced both sides of it?

I wrote an article last year: balintoberrauch.com/2025/06/30/demystifying-av-in-a-vdi-environment

thanks for that - yeah we've gone off that article with with machine learning exclusions and not SVEs. but it makes sense why you need an SVE. well we'll see how it goes...