Forum Discussion
Horizon instantclone stuck logging out with message, "Please wait for the FSLogix Apps Services"
I know this is a really old post, but were you ever able to determine what was causing your issue? We are experiencing a very similar issue after using FSLogix for years without problem, this just started and is throwing our VMWare Horizon View VDI environment into disarray because of slow logins and hung logoffs. Any details you could share regarding a resolution would be VERY APPRECIATED!
YakimaRandy really wish I could help, but we're still having the problem after all this time. I have updated to a newer version of FSLogix apps but we then started seeing our VHD files start getting completely corrupt. We didn't know if it was the new version causing it or not, so we reverted back to the old version that we had prior. If you have FSLogix support, I'd suggest contacting them for a fix. I don't have a support contract so I can't get their assistance. If you get it fixed, I'd love to hear what it was?
scythe944 we are working currently with FSLogix (Microsoft) Support to address our FSLogix issue. So far, however, we have not been able to determine what is causing this and everything we have tried (created two brand new SMB file servers, updated to the latest FSLogix client, changed several registry settings on the file server side) has had no positive effect.
They now want us to upgrade our Windows 10 OS on the virtual desktops to the latest version as we are running an "out of scope" version of Win10 right now. Even though that "out of scope" version was working prior to a month ago without any problem. I'll let you know if we come up with a fix.
- Thanks so much! I believe that all of our Gold images are Windows 10 Version 22H2, really hope you get some sort of fix from Microsoft soon, I would love to get this problem fixed for good.
If it helps at all, I have seen several users VHD files start getting corrupt and we have to log them off their session, then attach their profile VHD file to our machines, give it a drive letter and then run a chkdks /f on the drive. It seems to find errors most of the time but fixes them. I feel like these errors are happening due to the CloudCache / FSLogix getting stuck at log out, then the user tries to login again and their machine is still stuck and can't get into a machine. So of course they call our Helpdesk and helpdesk usually just resets the computer in order to get the user working again. I believe that the resetting of the computer is causing the errors on the drive. I've even had a few VHD's go completely corrupt and can't be opened or mounted at all, and I have to use a third-party utility to convert the damaged VHD to a VHDX, then convert it back to VHD to get it operable again. Takes a long time to do.