Share via

Use same FSLogix profile moving to 24H2 from 23H2?

Zuuber 10 Reputation points
2025-04-16T15:48:23.7166667+00:00

We want to make use of the new Dadsv6 series session hosts for AVD over our current Dadsv5 series.

We currently use 23H2 but looks like the 6 series only supports 24H2 due to the disk controller.

Are we able to use the same profiles for ours users, or would new profiles be required?

We use FSLogix profile containers stored in a premium Azure file storage account.

Will the profiles be ok logging into 24H2 from 23H2?

Anyone already tried this?

Windows for business | Windows Client for IT Pros | User experience | FSLogix
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Finn Dang 460 Reputation points Independent Advisor
    2025-07-23T17:04:03.6366667+00:00

    Hello Zuuber,
    You can keep your existing FSLogix profile containers when you move from 23H2 to 24H2. FSLogix VHD(X) files are essentially just user profiles and don’t bake in OS version specifics, so they’ll mount and roam just fine - as long as you:

    • Upgrade the FSLogix agent on your new 24H2 hosts to a build that officially supports Windows 24H2.
    • Point your host‑pool group policy or cloud‑config at the same Azure Files share and path.
    • Test with a pilot user to confirm login, group‑policy application and Office/OneDrive behavior.

    No need to create new containers, just join your Dadsv6 session hosts, install/configure the updated agent, and let users pick up exactly where they left off.
    I hope this helps.
    Finn

    0 comments

Your answer

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