Fixing "Error code: 0x00000020" when logging into developer cloud desktop

Kai 0 Reputation points
2024-03-20T17:12:01.8633333+00:00

Hi everyone, I'm receiving this error whenever I login from my developer cloud desktop.. I have tried stopping and restarting the virtual machine but I am still getting this error. Any idea how to fix this? Thanks so much.

The user profile failed to attach. Please contact support.

 

Profiles

Status: 0x0000000B, Message: Cannot open virtual disk

Reason: 0x00000005, Message: Reason initialized to empty state

Error code: 0x00000020, Message: The process cannot access the file because it is being used by another process.

 

Computer name: ******

Azure Virtual Machines
Azure Virtual Machines
An Azure service that is used to provision Windows and Linux virtual machines.
7,900 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. deherman-MSFT 37,241 Reputation points Microsoft Employee
    2024-03-20T17:26:45.89+00:00

    @Kai
    Can you confirm which Azure service you are using. Is this Azure Virtual Desktop or Microsoft Dev Box?
    If Dev Box you can post on their dedicated forum here. The below answer was generated by Microsoft Copilot:

    It seems you’re encountering an issue with FSLogix where the user profile fails to attach. Let’s troubleshoot this:

    Corrupt Profiles: First, try deleting any corrupt profiles from the registry location: Local_Machine\Software\FsLogix\Profiles. Then navigate to the path of VHDLocations and delete the profiles. Signing back in should create a new profile(https://learn.microsoft.com/en-us/answers/questions/200605/fslogix-error-the-user-profile-failed-to-attach).

    Storage Allocation: Ensure that the storage container for FSLogix in Azure has sufficient allocated space. If it exceeds the allocated limit, it can cause issues(https://learn.microsoft.com/en-us/answers/questions/200605/fslogix-error-the-user-profile-failed-to-attach).

    Recent Updates: If you’ve recently installed Windows updates, particularly KB5005568 or KB5005625, they might have affected FSLogix. Consider uninstalling these updates or checking for compatibility issues2.

    Temporary Profiles: Check for temporary profiles and delete them:

    Go to Control Panel → System → Advanced System Properties → Advanced → User Profiles → Settings.

    Delete any profiles with Type set as TEMP(https://learn.microsoft.com/en-us/answers/questions/491256/fslogix-error-cannot-get-user-profile-to-attach).

    Virtual Disk Access: Reboot the machine during off-hours, log in with an admin account, and delete the user’s VHDX. Then ask the user to log in again to see if the new VHDX attaches successfully(https://learn.microsoft.com/en-us/answers/questions/349366/fslogix-profile-failed-to-open-virtual-disk). Remember to back up critical data before making any changes. If the issue persists, consider reaching out to support for further assistance.

    0 comments No 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.