This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(272, 83%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDB%3C/text%3E%3C/svg%3E)
I have hybrid AD/Azure AD joined Windows 10 machine that has been working fine. With no changes other than installing the feature update from 1909 to 20H2. The primary user of the device nor any other AD domain user can logon to the device. Only the local Administrator can logon.
The machine is still visible in the Endpoint Management Admin Center an shows that it is still checking in. Not sure what to do, any help would be appreciated.
anonymous userBarker-0944 Thanks for posting in our Q&A.
To clarify this issue, could you please tell us that is this device an Autopilot enrollment device?
Based on my experience, this screen shot is ESP(Enrollment Status Page). I find that this error occurs on Azure AD Connect to sync the device. We can read the following article as a reference.
https://learn.microsoft.com/en-us/troubleshoot/mem/intune/understand-troubleshoot-esp#account-setup
If there is anything unclear, feel free to let us know.
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
It is not an and Autopilot device. This is a Windows 10 Enterprise machine that has been joined to an Active Directory domain and Co-Managed via Configuration Manger and Intune for several years. The machine received the 20H2 feature update as a Windows Update and on the first boot after the feature update this is what occurred.
Thanks
Dave
anonymous userBarker-0944 Thanks for your reply.
For this issue, we need to do log analysis to confirm. With Q&A limitation, Q&A is not the best channel for such log analysis case. So we suggest to open a case to check on this. The following link describes how to open a case, we can refer to it:
https://learn.microsoft.com/en-us/mem/intune/fundamentals/get-support
Thanks for understanding and have a nice day.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(9.6, 34%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKF%3C/text%3E%3C/svg%3E)
For anyone else that has this issue, the Intune registration creates a bunch of tasks in
Task Scheduler Library - Microsoft - Windows - Enterprise Management - "GUID"
Once you logged in as a local admin, delete all of the tasks in the GUID that has a task that is set to run "at each user login".
Log out as the local admin and login as the domain user and it should log in fine.
I have had one where it still showed the failed screen but Ctrl + Alt + Del - sign out, sign in resolved it.