Forum Widgets
Latest Discussions
FRXTray functionality replacement
Our company has used FsLogix going back well before Microsoft stepped in and we have always relied on the FRXTray stoplight for Profile troubleshooting. This tool makes it easy for my field staff to know when the users profile has loaded or not. Now that the tool has been removed in 25.02 (3.25) I am left wondering how my field staff can easily determine if the profile isn't loading. Is there another tool or command line item that can be run, or is it a matter of slogging though the logs to find the answer?FSLogix 2210 (2.9.8361.52326) bugs: black screen and log off issues
Hi all, there seem to be a couple of bugs in FSLogix 2210 (2.9.8361.52326): some users experience a black screen when logging on (loading their profile may take up to 10-15 minutes), session logoffs don’t work (child processes have to be killed) and user profile roaming between different session hosts is problematic. Workaround: I had to fall back to the FSLogix 2201 hotfix 2 (2.9.8228.50276). There were no more issues since then. For now I keep all my customers on this build.
Recurring Outlook issue - stuck on "Loading Profile" on Windows RDS servers.
Our first support request about this issue was in September 2023, but it has been more frequent over the past few months and weeks. Randomly we will have users report that Outlook will be stuck on loading profile. It's usually more than one user with the issue but it doesn't usually happen for everyone on that RDS host. Out support techs will always reboot that RDS host to resolve the issue. It seems like the same exact issue reported in the community post linked below - but that was in the context of an Azure VDI environment. https://techcommunity.microsoft.com/discussions/fslogix/azure-vdi---outlook-stuck-on-loading-profile/4267498 Some additional info: - There are two RDS hosts, both running Windows Server 2019 Standard - There will be around 20-25 users on each RDS host during peak hours, but this issue can occur at any time of day - FSLogix is on latest version 2210 hotfix 4 - Physical server infrastructure is Dell PowerEdge hosts running ESXi (with vCenter), connected to Dell SCv3020 SAN for storage. Any input is appreciated! We are also pursuing Microsoft support for this issue but from our experience it can take awhile to make progress with them on anything related to on-prem servers anymore.
Local Profiles not unloading on latest version of FSLogix
Good Afternoon, I've recently been troubleshooting an issue we have experienced running FSLogix 2210 hotfix 4 (2.9.8884.27471) with new teams on a Server 2019 image. The behaviour observed was that after launching Teams, users local_username profiles would not detach from the server, and when that same user logs back into that server, there is a new temporary profile created with the format local_username1. These local profiles could not be deleted due to containing a file in use by SYSTEM. After reading of the improvements with unloading local profiles with msix packages, I updated fslogix to the latest version FSLogix 25.02 (3.25.202.4223) After this upgrade, we are still experiencing the same issues, where local profiles do not detach and write back to the primary profile VHD. We then tested the latest version of FSLogix on an older image, that still had classic teams installed. The same behaviour was seen where the local profile stays attached and does not write back to the main profile. Are there any new configuration changes that I need to make in order to get this to work, or is anyone else experiencing this same issue?
Fslogix and outlook 58tm1 problems
Hello, I am in dire need of some help because i'm at my wit's end here. We have a few on prem windows 2022 RDS farms using fslogix and outlook. We are bashing our heads against the wall because of the dreaded 58tm1 problem. Every once in a while (5 times a day) a user will get a 58tm1 error while trying to open outlook, we usually fix the problem by deleting the Microsoft.AAD.BrokerPlugin which would fix things for a short while, because we've tried everything else out there, nothing works. Every possible settings combination, registry fixes etc... Newest fslogix versions (hello 25.09) do not fix anything but break everything (this entire branch has a nasty bug which would create temporary profiles and fill every storage space available). The users are growing tired, the support guy is considering goat herding as an alternative and the higher ups are veeeeeeeery displeased. Problem, we can't fix this, not in a timely fashion, not cleanly or easily. This seems to be an ongoing issue which has been present for years but got exacerbated lately with modern auth and subscription model shift for office. Is there some hope or do i have to start explaining to people how to type in their passwords? Because my next step would be to nuke everyone's aadbrokerplugin folder at the end of the day. Thank you for reading my rant :)
FSlogix Profile Disconnects
Hi, Just wondering has seen this issue with their AVD instances and FSlogix in regards to profile container disconnects. We have version 3.25.822.19044 and my theory is that computers that go into sleep mode (due to power timeouts) are not cleanly triggering the disconnect procedure for the container to be cleanly disconnected. We have noticed this by the users .VHDX.metadata file not deleting on their log off. It's also not releasing the Handles and Leases for their containers, making them sign in with a temp profile if they try again. We are just running a standard regedit profile setup based on this page, https://learn.microsoft.com/en-us/fslogix/concepts-configuration-examples Just seeing if anyone else has any fixes in place? Or is this a known issue. Thanks Josh.
Error removing Rule at logoff
Hello folks. during user logoff Fslogix is trying to remove some rules but get an exception [ERROR:80070490] Error removing Rule: C:\Users\username\AppData\Local\CrashDumps (Element not found.) As a result it removes "users profile" and "local_username" folder correctly with no issues, but sends Error to the logs. It's spamming the logs because it will put error one every excluded folder from redirection. We don't use any FSLogixAppsRuleEditor or something else, checked by ."\frx.exe list-rules -verbose" it returns - "No rules" The redections.xml looks like [...] <Exclude Copy="0">AppData\Local\CrashDumps</Exclude> [...] Is this an known issue ? Thinking it came around with 3.25.202.4223. Thx Jens
FSLogix v3 25.02 profiles not unloading
Hi all! Like mentioned in the comments in the FSLogix Blog: FSLogix v3 Release 25.02 is now generally available! | Microsoft Community Hub Disks are not unloaded on logoff and the excluded conten (local_%username%) remains on the Worker. Eventlog shows: Event source: Apps (Microsoft-FSLogix-Apps) Event id: 26 invalid map<K, T> key (An exception occurred in the service when handling the control request.) Event source: Apps (Microsoft-FSLogix-Apps) Event id: 42 SessionId: 3, ErrorCode: 1064, Detail: Logoff failed, Please check logs and tracelogging and verify that the users disk was detached. Event source: Apps (Microsoft-FSLogix-Apps) Event id: 26 UnloadProfile failed. Version: 3.25.202.4223. User: <user>. SID: <SID>. SessionId: 3. FrxStatus: 1064 (An exception occurred in the service when handling the control request.) Best regards, JanAzure VDI - Outlook Stuck on 'Loading Profile'
Issue occurs every morning and we have been chasing this up with the Microsoft support team as well. We've tried a lot of things but switching to and from VDI's seems to eventually get people logged in. We've rebuilt mail profiles, safe mode, resetnavpane, disabled add-ins, updating Office, restarted VDIs, deleted duplicate user profiles on the VDI, deleted OSTs and temp files within AppData, cleared credential manager. One thing which seemed to help was running Microsoft SaRA. It said we had modern authentication setup on our tenant and the VDIs were using legacy. It performed the fix and sorted the issue right away. It looked to calm the problem for some time but more people started getting this again. Something to note is this usually happens in the mornings or just when someone starts work. I know a lot of people experience the same issue but not come across a reliable fix so far.
Old file server still present in registry on user profiles
We are running FSLogix 2.9.8884.27471 on Server 2022. Our domain controllers are all Server 2022. We just migrated to a new file server. The Citrix profiles are stored on a completely different server; we have not changed the Citrix profile file server. We only changed/migrated the general file server used for general file storage. After we powered off the old file server, Citrix users complained of "slowness" when using File Explorer. We discovered that there are a bunch of references to the old file server in each user's FSLogix profile registry. If we mount the FSLogix profile, when a user is logged out, and delete the references from a user's profile registry, the "slowness" issues with File Explorer, are resolved. The registry entries that seem to be present in each user's profile are located in the following: HKU\FSL.VHD.****\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints 2 (there are a couple mount points still present for the old file server) HKU\FSL.VHD.****\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders (we use GPO to redirect a users "Favorites" folder - the old file server is still listed in the "Favorites" registry entry, even though the GPO is setup to point to the new file server) HKU\FSL.VHD.****\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders (we use GPO to redirect a users "Favorites" folder - the old file server is still listed in the "Favorites" registry entry, even though the GPO is setup to point to the new file server) When we delete the "Favorites" entries, we find that after a user logs in/out, the "Favorites" entry updates properly to the new file server path. We can also remedy the File Explorer "slowness" by simply powering on the old file server. Again, all of the sharing on the old file server has been disabled. So it seems like as long as a user can "ping" the old file server, then that's all FSLogix needs to ensure that File Explorer works. This issue does not occur on physical Windows computers/servers- only with with FSLogix profiles. Instead of either leaving on the old file server powered on, or manually editing the registry in each user's profile, is there a way to remove (or update) these registry entries that point to the old file server?
