Troubleshooting one user VHDx in FSLogix

Gregg Hughes 291 Reputation points

Good afternoon!

We're running FSLogix in a customer's small Server 2019 farm. Some of the users are nearing or hitting the 30 GB default VHDx size limit. I've successfully migrated all but one subject VHDx; that one has two results, depending on the session server.

The migration completes successfully, according to the result from the command line. However, when we log in to RDS1, the doesn't mount and FSLogix creates a new, local profile. On RDS2, the profile fails to attach with an unknown error. The original VHDx mounts fine in either server.

I'd like to fix the VHDx so we don't have to go through saving files and recreating the profile from scratch. Does anyone have guidance on inspecting and perhaps fixing these VHDs in an FSLogix environment?



A set of solutions that enhance, enable, and simplify non-persistent Windows computing environments and may also be used to create more portable computing sessions when using physical devices.
465 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Eleven Yu (Shanghai Wicresoft Co,.Ltd.) 10,696 Reputation points Microsoft Vendor


    Could you please clarify more about how you migrate the VHDx file? Are you using the way mentioned in below two links or any other way to expand the FSlogix VHDx size.

    How to resize the current VHD(x) in FSLogix
    Expanding an FSLogix profile disk

    I've successfully migrated all but one subject VHDx

    What do you mean by "subject VHDx"?

    Does the issue occur on one user or all users whose profiles have been migrated?

    What if we move back the VHDx files?


    If the Answer is helpful, please click "Accept Answer" and upvote it. Thanks.