Skip to content

TechDirectArchive

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

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

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

Posted on 28/07/202003/09/2026 Christian By Christian 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.

Screenshot of Ansible Server running on Windows Event Viewer displaying Administrative Events, including an error log for Event ID 307 related to User Device Registration.

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.

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

  • install virtualbox on linux mint ubuntu 1
    How to install Windows Server 2019 on Virtualbox Windows Server
  • Connect to FTP Server
    Secure FTP Login Issue: NAT Router Configuration for Passive Mode and Port Forwarding Windows Server
  • Screenshot 2021 10 07 at 00.00.32
    How to fix this computer is a domain controller: The snap-in cannot be used on a domain controller Windows Server
  • 2022 1
    Install Windows Server 2022 on VirtualBox Network | Monitoring
  • RDS Architecture
    The following servers in this deployment are not part of the deployment Pool: Create an RDS Session Host and Collection Windows Server
  • hero windowsadmincenter
    Failed to create a scheduled task: There is no disconnected command associated with the runspace Windows Server

More Related Articles

powershell01 How to add servers to the Trusted Hosts list Scripts
Windows Defender exclusion Mitigate Veeam Threat Hunter Service Scanning Interference Windows Server
Windows server 2025 set up Install Windows Server 2025 via iDRAC Virtual Media or PXE Windows Server
OOBEZDP OOBEZDP: Something went wrong during the Windows deployment Windows
fhgjk Replicating MDT Deployment Share: How to Create a Selection Profile and Link MDT Deployment Shares Windows Server
adfs Install and configure Active Directory Federation Service (ADFS) 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

vexpert-badge-stars-5

Virtual Background

VEEAMLEGEND

Categories

Top 30 Sysadmin blog

veeaam100

Veeam Vanguard

  • 2022 1
    Install Windows Server 2022 on VirtualBox Network | Monitoring
  • azure logo 1
    How to use the built-in Azure Active Directory Connect tool AWS/Azure/OpenShift
  • Remote desktop connection over udp and tcp
    Remote Desktop Connection behavior over UDP and TCP Windows Server
  • HyperV and vSwitch creation
    Install HyperV and Configure vSwitch on Windows Server with PowerShell Virtualization
  • apply and install Veeam NFR Licence
    How to apply and install Veeam NFR License Backup
  • Mendeley Error Code ACLx80sr
    Fix Mendeley Cite Error has occurred: ECITE40001 (ac1x80sr) JIRA|Confluence|Apps
  • windows update 03
    Fix Windows cannot check for updates in Windows 8, 7, and 10 Windows
  • ad lds 832x400 1
    Active Directory Lightweight Directory Services [AD LDS] Windows Server

Subscribe to Blog via Email

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

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

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.