I am having the same problem as you!
Window 11 24H2 / Can't Join Domain
![](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(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
We have about 500 PCs on our domain. Functional level is Server 2016. We received our first laptop from Dell which shipped with Windows 11 Pro 24H2 and it will not join. Since it's failure, I've tested various versions of Win10 and Win11 not running 24H2 and they all join just fine.
netsetup.log shows:
08/28/2024 08:09:17:784 -----------------------------------------------------------------
08/28/2024 08:09:17:784 NetpValidateName: checking to see if 'XPS' is valid as type 1 name
08/28/2024 08:09:17:784 NetpCheckNetBiosNameNotInUse for 'XPS' [MACHINE] returned 0x0
08/28/2024 08:09:17:784 NetpValidateName: name 'XPS' is valid for type 1
08/28/2024 08:09:17:810 -----------------------------------------------------------------
08/28/2024 08:09:17:810 NetpValidateName: checking to see if 'xps' is valid as type 5 name
08/28/2024 08:09:17:810 NetpValidateName: name 'xps' is valid for type 5
08/28/2024 08:09:17:816 -----------------------------------------------------------------
08/28/2024 08:09:17:816 NetpValidateName: checking to see if 'domainname' is valid as type 3 name
08/28/2024 08:09:17:816 NetpValidateName: 'domainname' is not a valid NetBIOS domain name: 0x7b
08/28/2024 08:09:28:877 NetpCheckDomainNameIsValid for domainname returned 0x54b, last error is 0x0
08/28/2024 08:09:28:877 NetpCheckDomainNameIsValid [ Exists ] for 'domainname' returned 0x54b
The PC attempting to join sits on the same subnet as our DCs and there are no security appliances/firewalls filtering traffic.
From the 24H2 PC that won't join, I have tried or am able to:
- perform name resolution to various hostnames via nslookup
- verified inbound/outbound AD ports are open on our DCs
- DCs are replicating and are healthy (other PCs join w/o issue)
- Access any other resource on our LAN
- Tried statically assigning DNS servers (which are our DCs) on the PCs NIC
- Disabled Windows firewall on the PC
- Factory reset the laptop (Dell XPS 13 9345) and attempted again with no success
Another post suggest searching for a registry key relating to NT4Emulator on the DCs in the event the domain ever had an NT4 DC. This key doesn't exist on our DCs and if we had a DC running NT4 here, it was way before my arrival.
I can't think of any reason why this laptop is different other than it's the first running 24H2. I can't seem to find anyone having this issue.
Any help or suggestions is appreciated.
Windows for business | Windows Server | Directory services | Active Directory
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
72 answers
Sort by: Newest
-
Anonymous
2024-10-24T02:53:52+00:00 -
Anonymous
2024-10-23T23:50:50+00:00 I don't know if this will continue to work long term, but I was able to get a new computer with Windows 11 24H2 to join our domain after entering the domain name + ".local". So far, everything appears to be working. I hope I'm not causing problems I'm not aware of.
-
Anonymous
2024-10-16T16:55:19+00:00 this needs to be patched quickly. I am currently disconnected from our domain and can only make connection over VPN. this works but is ultra slow. I have been looking for downloading the older windows 11 23H2 (that worked) but can no longer be downloaded to "roll back". this is inflicting serious malfunction for our company, so I would say this is urgent. asking for us to mess around in domain zones and whatever, or registries is something MS cant afford. we are not all geeks and depend on the system to work. please fix SOON
-
Anonymous
2024-09-20T21:52:03+00:00 I am having the same issue, but I think they removed the ability to connect to a single label domain in 24H2. I used to be able to put in a registry key to allow it, but it is not working for me anymore. I am hoping that this is resolved quickly.
-
Anonymous
2024-09-10T16:20:20+00:00 Check your netsetup.log. Does it have similar entries like ours did?
I was confused by it saying the domain name we were providing wasn't a valid Netbios name since every other version of Windows was joining without issue using the same exact name.
Our log entries were actually accurate in telling us where to look. There was an issue with the records in our _msdcs zone; either missing or not in the right place. We just recreated the _msdcs.domain zone, restarted netlogon service and it automatically recreated that zone with the proper records. We verified the recreated zone was replicated across all DNS servers. After we verified it was there, we were then able to join 24H2 to our domain.