Skip to content

TechDirectArchive

Hands-on IT, Cloud, Security, Veeam & DevOps

  • Home
  • About
  • Advertise With US
  • Reviews
  • Tech News
  • Contact
  • Toggle search form

Error 0x801c001d – Automatic registration failed: Failed to look up the registration service from AD

Posted on 28/07/202008/09/2024 IT Expert By IT Expert 2 Comments on Error 0x801c001d – Automatic registration failed: Failed to look up the registration service from AD
  1. Home
  2. Windows Server
  3. Error 0x801c001d – Automatic registration failed: Failed to look up the registration service from AD

Microsoft’s identity solutions span across on-premises and cloud-based capabilities. In this article, we shall discuss how to fix “Error 0x801c001d – Automatic registration failed: Failed to look up the registration service information from Active Directory with exit code unknown HResult”. These solutions create a common user identity for authentication and authorization of all resources, regardless of location. This is referred to as a “hybrid identity”. Please see How to fix DISM Error 87: The package is unknown, and How to fix Unknown Hard Error on Windows Server and Windows 10.

Therefore, Hybrid identity is having a common user identity for authentication and authorization both on-premises and in the cloud.

Kindly see the following guides on Pass-Through Authentication: AD Connect Tool status displays inactive, and “Pass-Through Authentication sign-in issue, non-routable domain, Invalid username and password for Single Sign-On.

To achieve a hybrid identity with Azure AD, one of three authentication methods can be used, depending on your scenarios. The three methods are:

  • Password hash synchronization (PHS)
  • Pass-through authentication (PTA)
  • Federation (AD FS)

Failed to look up the registration service information

When prompted with the following error as shown in the figure below “Automatic registration failed. Failed to look up the registration service information from Active Directory. Exit code: Unknown HResult Error code: 0x801c001d.

This error occurs when the infrastructure is not prepared for Hybrid join. When the device tries to do a Hybrid join, the registration fails, and the events are logged.

Therefore, the Automatic Device Join runs as a scheduled task whenever someone logs into a server. This can cause a lot of event errors as shown below.

Suggestion to Error 0x801c001d on Wndows Server

Basically, if the infrastructure is in a non-hybrid join environment, these event IDs are expected during Windows 10 deployment. They can be ignored! They are therefore ignored by me. 🙂

If you have a Hybrid environment and you wish to fix this issue, kindly visit this article “troubleshooting hybrid Azure Active Directory joined devices“.

You might also be interested in these: Azure Active Directory integration with on-Premise AD using PTA, and VM environment setup on Hyper-V for Windows Server Active Directory, Azure Active Directory Integration,

I hope you found this blog post helpful on how to fix “Error 0x801c001d – Automatic registration failed: Failed to look up the registration service information from Active Directory with exit code unknown HResult”. If you have any questions, please let me know in the comment session.

5/5 - (1 vote)

Thank you for reading this post. Kindly share it with others.

  • Share on X (Opens in new window) X
  • Share on Reddit (Opens in new window) Reddit
  • Share on LinkedIn (Opens in new window) LinkedIn
  • Share on Facebook (Opens in new window) Facebook
  • Share on Pinterest (Opens in new window) Pinterest
  • Share on Tumblr (Opens in new window) Tumblr
  • Share on Telegram (Opens in new window) Telegram
  • Share on WhatsApp (Opens in new window) WhatsApp
  • Share on Mastodon (Opens in new window) Mastodon
  • Share on Bluesky (Opens in new window) Bluesky
  • Share on Threads (Opens in new window) Threads
  • Share on Nextdoor (Opens in new window) Nextdoor
Windows Server Tags:errors, Event Viewer, eventlog, TaskScheduler, Windows 10, Windows Server 2016

Post navigation

Previous Post: Fix SSO sign-in and non-routable domain issues
Next Post: Nslookup unknown: Fix cannot find non-existent domain

Related Posts

  • Missing Windows defender
    Missing Windows Defender? Install and manage Microsoft Defender via Windows Security on Windows Server Windows Server
  • DC creation as recommended by Microsoft
    Setup a Domain Controller as Recommended by Microsoft Windows Server
  • telnet
    Could not open a connection to the host, on the port, connect failed Windows Server
  • screenshot 2020 02 08 at 20.02.50
    Windows 10 Administrative Shortcut command key Windows Server
  • ghm
    MDT Driver injection: How to import drivers in .exe format into Microsoft Deployment Toolkit Windows Server
  • dasfdg
    Unable to execute: The application GUID not found in the application list Windows Server

More Related Articles

Missing Windows defender Missing Windows Defender? Install and manage Microsoft Defender via Windows Security on Windows Server Windows Server
DC creation as recommended by Microsoft Setup a Domain Controller as Recommended by Microsoft Windows Server
telnet Could not open a connection to the host, on the port, connect failed Windows Server
screenshot 2020 02 08 at 20.02.50 Windows 10 Administrative Shortcut command key Windows Server
ghm MDT Driver injection: How to import drivers in .exe format into Microsoft Deployment Toolkit Windows Server
dasfdg Unable to execute: The application GUID not found in the application list Windows Server

Comments (2) on “Error 0x801c001d – Automatic registration failed: Failed to look up the registration service from AD”

  1. Avatar photo chkitout1 says:
    12/01/2024 at 3:21 PM

    This is not at all helpful. The log file is full of these errors and it makes it hard to find a valid error. How do I get rid of this error so it does not show up in the log?

    Log in to Reply
    1. chris Christian says:
      12/01/2024 at 3:34 PM

      I agree! Like Micrsoft recommends, if you do not have a hybrid environment, you can ignore these errors. But if you do have a Hybrid environment, then take a look at this article: https://learn.microsoft.com/en-us/entra/identity/devices/troubleshoot-hybrid-join-windows-current

      Log in to Reply

Leave a Reply Cancel reply

You must be logged in to post a comment.

Microsoft MVP

VEEAMLEGEND

vexpert-badge-stars-5

Virtual Background

GoogleNews

Categories

veeaam100

Veeam Vanguard

  • IIS8
    How to add an account to the local IIS_IUSRS group Windows Server
  • screenshot 2020 04 02 at 23.27.20
    Cloud Protection Manager: N2WS Veeam CPM Guide Backup
  • powershell commands lede 1024x276 1
    Enable WinRM on Windows Servers and Windows PCs Scripts
  • ETWindows
    An Overview of Event Tracing for Windows Windows
  • Screenshot 2024 02 09 at 7.34.18 PM
    How to create a Logic App for monitoring tweets AWS/Azure/OpenShift
  • Commvault Docker Images
    Pull and Push Commvault Images to Azure Container Registry AWS/Azure/OpenShift
  • Amazon
    Import Virtual Machines to AWS as AMI AWS/Azure/OpenShift
  • find my device banner
    Video on how to Enable Find My Device on Windows 11 Windows

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 1,762 other subscribers
  • RSS - Posts
  • RSS - Comments
  • About
  • Authors
  • Write for us
  • Advertise with us
  • General Terms and Conditions
  • Privacy policy
  • Feedly
  • Telegram
  • Youtube
  • Facebook
  • Instagram
  • LinkedIn
  • Tumblr
  • Pinterest
  • Twitter
  • mastodon

Tags

Active Directory Azure Bitlocker Microsoft Windows PowerShell WDS Windows 10 Windows 11 Windows Deployment Services Windows Server 2016

Copyright © 2026 TechDirectArchive

Loading Comments...

You must be logged in to post a comment.