FSLogix error code 0x0000052E

This is a quick short blog about these error codes: FSLogix error code 0x0000052E

The user profile failed to attach. Please contact support
Status: 0x0000001B, Message: cannot find the virtual disk at the provided location
Reason: 0x00000005, Message: Reason initialized to empty state
Error code: 0x0000052E, Message: The user name or password is incorrect.

You will see this message when a user logs on:

Note: This is a fix for Entra Joined AVD hosts with FS Logix profiles on an Azure Files Share that uses Microsoft Entra Kerberos.

If you want to know how to set this up, please check out this blog.

Now, the fix for FSLogix error code 0x0000052E:

The Microsoft Documentation states this:

The first option, Policy CSP, does not work on multisession VMs. Which you are probably running.

You can’t use the second option because you have Entra Joined AVD hosts. If you have Active Directory joined AVD hosts, you can easily use this group policy:

(Computer > Administrative Templates > System > Kerberos)

Unfortunately, this setting is not yet available in the Setting Catalog in Microsoft Intune. That would everything a whole lot easier.

Lastly, you can set the registry key. (I use this one). I tried to put it into my image but after the sysprep it was gone. So, I now use a Win32App in Microsoft Intune with this script to set the registry key on the machine:

$registryPath = "HKLM:\SYSTEM\CurrentControlSet\Control\Lsa\Kerberos\Parameters"
$Name = "CloudKerberosTicketRetrievalEnabled"
$value = "1"

New-ItemProperty -Path $registryPath -Name $name -Value $value -PropertyType DWORD -Force | Out-Null

4 thoughts on “FSLogix error code 0x0000052E”

  1. Hi Niels, I don’t know why the registry key disappears after you use Sysprep, but when I do that, it is still there afterwards.

    • Hi Gertjan,

      Hmmm, that’s weird. I must take a look at my image pipeline. Tried it multiple times with multiple methods.

      Thanks, will update the blog!



Leave a Comment