I did a Vdisk update over the weekend on a old windows 2016 vdisk that hasn't been updated in a while (I patched it using latest MS security rollup and installed Fslogix 2210 HF1 with all the new features turned off Install appx packages/Disk compaction/roam recycle bin ect. the image is booted to our Pre prod servers and been having a few issues where servers will randomly hang on a black screen on user logon (console/rdp/citrix) it takes 10 mins and eventually lets you on but windows explorer spins out and it also gets stuck on the sign out. The Fslogix log has multiple failed to acquired session lock for user xxx the wait operation timed out errors. I was going to roll back fslogix to a known working version 2201 HF2 as i know 2210 has been buggy as hell but i came across these articles with same symptoms and it mentions a Microsoft KIR to rollback to a working state. Is that KIR still required or fixed in new MS cumulative updates https://www.reddit.com/r/fslogix/comments/w8ies1/fslogix_failed_to_acquired_logon_lock_on_server/ and https://worldofeuc.slack.com/archives/CKBVDG48H/p1660120033932589