Window 11 24H2 / Can't Join Domain

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.

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.

0 comments

72 answers

Anonymous

2024-09-10T15:57:55+00:00

I am running into the same issue with the 24h2, all other computers on older versions join fine.

The response from NeuviJ is exzactly why nobody uses this forum for help as they just paste useless junk that does nothing to address the issue.
Was this answer helpful?

50+ people found this answer helpful.

0 comments No comments
Anonymous

2024-11-29T14:59:56+00:00

Hi

We also encountered this problem of connecting to a single-label DNS domains with Windows 11 24H2. Spent hours trying to figure out a dns issue. However, unlike you, adding a key in the registry allowed us to resolve the problem. I post the procedure below:

To resolve this issue, a registry modification is required. Follow the steps below:

Open the Registry Editor:

Press Win + R, type regedit, and press Enter.

Navigate to the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters

In the right pane, right-click and select New > DWORD (32-bit) Value.

Name the new DWORD as AllowSingleLabelDnsDomain

Double-click AllowSingleLabelDnsDomain and set its value to 1.

Close the Registry Editor.

Restart the computer to apply the changes.

This modification allows support for single-label DNS domains on Windows 11 version 24H2, resolving the connection issue.

After deleting the registry key the issue is back so it confirms that this modification should bypass this issue nethertheless others issues with netlogon and group policy still there.
Was this answer helpful?

20+ people found this answer helpful.

0 comments No comments
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.
Was this answer helpful?

10+ people found this answer helpful.

0 comments No comments
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.
Was this answer helpful?

9 people found this answer helpful.

0 comments No comments
Anonymous

2024-12-13T17:56:38+00:00
I HAVE BEEN PULLING MY HAIR OUT FOR THE LAST TWO DAYS.

With the knowledge from this thread of comments:

Yes the win 11 24H2 updates does not let you join a single label domain.

I adopted a single label domain when joining the company and adding devices to the domain has NEVER been a huge issue until two days ago when imaging a brand new laptop from dell for office staff.

The thing that let me to success was seeing the registry edit suggestions. I didn't think that was necessary at first so i kept troubleshooting and troubleshooting, going crazy in the end so then finally I added a registry key and i finally got the prompt for credentials.

I almost threw the laptop across the room. Special thanks to AI/GPT and the users in this thread. Anyway here is the special sauce:

To join a Windows 11 computer to a single-label domain, you need to access the system settings, navigate to "Computer name, domain, and workgroup settings", select "Domain" as the membership type, and enter the full single-label domain name, but be aware that this configuration is not recommended due to potential compatibility issues and may require additional registry adjustments to enable single-label domain resolution on the computer; you might need to create a DWORD value called "AllowSingleLabelDnsDomain" in the registry with a value of "1" to allow joining a single-label domain.

Key points to remember:
- Not recommended:
Single-label domains (SLDs) are generally not recommended due to potential issues with DNS resolution and compatibility with certain applications.
- Registry modification:
To join an SLD, you might need to manually edit the registry on the computer to enable single-label DNS resolution by creating the "AllowSingleLabelDnsDomain" DWORD value.

How to join a single-label domain:1. Open System Settings: Go to Start menu, then select "Settings" > "System" > "About". 2. Access Computer Name: Click on "Change" under "Computer name, domain, and workgroup settings". 3. Select Domain: Choose "Domain" as the membership type. 4. Enter Domain Name: Enter the full single-label domain name (e.g., "example"). 5. Registry Modification (if necessary):
```
- **Open the Registry Editor.**
- **Navigate to HKEY\_LOCAL\_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters.**
- **Create a new DWORD value called "AllowSingleLabelDnsDomain" and set its value to "1".**
```
Was this answer helpful?

7 people found this answer helpful.

0 comments No comments