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

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

Crystal-MSFT 48,591 Reputation points Microsoft Vendor

2022-09-07T02:57:35.483+00:00
@LECIGNE Benjamin (exterieur) , From your description, I know the user is unable to login the device.. Before going on, I would like to collect some information:

Was the device Hybrid Azure AD joined?

Is it enrolled into Intune? Was it a co-managed device?

Is this a device installed with configuration manager client?

Please collect the above information to let us know the issue better. Thanks!
LECIGNE Benjamin (exterieur) 1 Reputation point

2022-09-07T07:18:29.04+00:00
Hello Crystal,
i can confirm

The device is well registered in Azure AD (sorry for french screenshot)

It is enrolled into Intune

The computer are install with Kace SMA, and enrolled with group policy

Regards,
Crystal-MSFT 48,591 Reputation points Microsoft Vendor

2022-09-07T07:46:19.893+00:00

@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.

1 answer

Pavel yannara Mirochnitchenko 12,581 Reputation points MVP

2024-03-22T14:25:25.6966667+00:00

I have the same error after BIOS update which did something to TPM keys, after this I cannot access Teams or other user related M365 services, but device itself registers to Intune every day fine. Single problem, not mass. dmsreg status shows all good.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

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

1 answer

Your answer