Windows logon timeout : MDM ConfigurationManager: Caller did not specify user to impersonate to. Targetted user sid: (NULL) Result: (Unknown Win32 Error code: 0x86000022).

LECIGNE Benjamin (exterieur)
1
Reputation point
Hello, we have an issue in our environment. When a new user try to log on a new computer (never logged before) the computer stuck on "Welcome" during an hour.
During this time, there is plenty of log :
MDM ConfigurationManager: Caller did not specify user to impersonate to. Targetted user sid: (NULL) Result: (Unknown Win32 Error code: 0x86000022).
Event ID : 455
It happen without any modifications on Intune
Regards,
Ben
{count} votes
Hello Crystal,
i can confirm
Regards,
@LECIGNE Benjamin (exterieur) , Thanks for your reply. For the picture you provided, I find it is non-English. I can't read it.
If the Join Type in Azure AD shows "Hybrid Azure AD joined", then we use domain account to login the device. If the Join Type shows "Azure AD registered", it means we use local account to login the device.
For the event you provided, it seems it is related with win32 app. But your issue is with windows login. Based on my research, I didn't find the event may cause the windows login issue. For your issue, please contact windows support to analyze related logs to help on it: Here is a link containing the Phone number to contact. for your reference
https://support.microsoft.com/en-us/topic/global-customer-service-phone-numbers-c0389ade-5640-e588-8b0e-28de8afeb3f2
Thanks for your understanding.