Share via

FSLogix - Login loop fix?

Yuki Pham 20 Reputation points
2025-11-07T15:30:32.95+00:00

Hello,

Last week, without anyone updating or touching anything, our VDI desktops of instant clones started to throw a parameter error related to Teams and Snipping Tool. Upon finding out it was FSLogix related, we of course decided to upgrade our FSLogix on the main virtual machine that all the instant clones are based off of. While it did fix the problem, we are currently facing another annoying issue of Teams, Outlook, and even Onedrive, are all prompting users to sign back in multiple times a day, every day.

We tried looking at some registry but not really sure where to start. We did go back to our previous version to test some things out, but we just end up getting the same parameter error that led us to this point. Is anyone else experiencing the same issue on this version we are on, or is this possibly a different issue?

We are currently on FSLogix_25.09 - Product Version - 3.25.822.19044

Our previous version was Product Version - 2.9.8111.53415

Moved from: Community Center | Not monitored

Windows for business | Windows Client for IT Pros | User experience | FSLogix
0 comments
Answer accepted by question author
  1. Finn Dang 955 Reputation points Independent Advisor
    2025-11-07T19:29:04.38+00:00

    Hi Yuki

    What you’re seeing after moving to FSLogix 25.09 (3.25.822.19044) is classic tokens not roaming behavior. Teams/Outlook/OneDrive keep asking to sign in because the WAM/AAD tokens live in LocalAppData and aren’t persisting across sessions with your current settings.

    Try this, in order of impact:

    Roam identity tokens with FSLogix Profiles -> turn on RoamIdentity ODFC (Office Container)
    -> also turn on RoamIdentity and Office activation

    HKLM\SOFTWARE\FSLogix\Profiles\Enabled = 1 HKLM\SOFTWARE\FSLogix\Profiles\RoamIdentity = 1 HKLM\SOFTWARE\FSLogix\ODFC\Enabled = 1
    HKLM\SOFTWARE\FSLogix\ODFC\RoamIdentity = 1
    HKLM\SOFTWARE\FSLogix\ODFC\IncludeOfficeActivation = 1

    Make sure your redirections.xml (if you use one) is not excluding these paths. They need to live inside the container:

    %LocalAppData%\Packages\Microsoft.AAD.BrokerPlugin_* %LocalAppData%\Microsoft\TokenBroker %LocalAppData%\Microsoft\IdentityCache For new Teams, also keep the MSIX package data inside the container: %LocalAppData%\Packages\MSTeams_8wekyb3d8bbwe

    Clear stale tokens once for an affected test user (one time action) -> sign out everywhere, then remove the user’s cached tokens and let them sign in once so FSLogix captures the fresh state:

    delete %LocalAppData%\Packages\Microsoft.AAD.BrokerPlugin_\AC\TokenBroker
    delete %LocalAppData%\Microsoft\TokenBroker*
    delete %LocalAppData%\Microsoft\IdentityCache* for Teams: sign out in Teams, exit, remove its LocalCache, start again

    If you rely only on the Profile Container, enable it for all users that run M365 apps.
    If you split Profile + ODFC, keep ODFC enabled so Outlook/OneDrive/Teams + activation roam reliably. Check the basics that cause token churn -> AV exclusions for the VHD/VHDX and the profile share, no sporadic file locks, correct NTFS/SMB permissions, and stable storage (Cloud Cache: healthy providers). Flaky I/O often surfaces as repeated sign-in prompts.

    Workarounds:
    if you need immediate relief: temporarily disable WAM sign-in for M365 to fall back to ADAL tokens, or keep only one Teams version (new Teams preferred), but permanent fix is roaming identity as above.

    This usually stops the daily sign-in prompts within one logon cycle. If you still hit a loop after enabling RoamIdentity, share whether you use redirections.xml, Cloud Cache, and which Teams build (classic vs new). I could try adjusting the exact keys/paths for that mix.
    Best regards,
    Finn

    1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Q&A Assist
    2025-11-07T15:31:02.12+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    It sounds like you're experiencing issues with FSLogix that are causing repeated sign-in prompts for applications like Teams, Outlook, and OneDrive. This can be related to several factors, including configuration issues or potential bugs in the version you are using.

    Here are a few steps you can take to troubleshoot the issue:

    1. Check for Updates: Ensure that you are using the latest version of FSLogix. Sometimes, newer versions contain fixes for known issues that could resolve your sign-in problems.
    2. Review Configuration: Make sure that your FSLogix configuration is set up correctly, particularly regarding the handling of user profiles and any related settings that might affect sign-in behavior.
    3. Network and DNS Issues: Verify that there are no network or DNS issues affecting the ability of the virtual machines to communicate with the storage providers or authentication services. You can use Test-NetConnection in PowerShell to check connectivity.
    4. Storage Provider Capacity: Ensure that your storage provider has enough capacity and is performing well. If the storage provider is full or slow, it can lead to issues with profile loading and sign-ins.
    5. Anti-virus Configuration: If you have anti-virus software running, ensure that it is properly configured to exclude FSLogix-related files and folders to prevent any interference.
    6. Check Logs: Look into the FSLogix logs for any errors or warnings that could provide more insight into the issue. These logs can help identify if there are specific problems during the sign-in process.

    If the problem persists after trying these steps, it may be beneficial to reach out to Microsoft support for further assistance, especially if this issue is widespread among other users.

    References:

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.