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

2025-01-09T21:16:57+00:00

We are having the same issue, and the work-around we've been using is just doing an offline domain join using the djoin command.
Was this answer helpful?

0 comments No comments
Anonymous

2025-01-08T10:19:26+00:00
It is clear that version 24H2 has a serious problem with certain network/domain combinations.

In our case, a Windows Server 2016 Domain server, a Single Label domain, which works without problems with versions 23H2 of W11 and W10.

We have tried all the recommendations found:
- Activate the key AllowSingleLabelDnsDomain in the registry
- Disable IP6
- Manually configure the DNS
- use the .local suffix of our domain
The only solution that worked for us, but partially, was to activate the Credential Guard by editing the Windows registry In the path HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa including the key "LsaCfgFlags" with value 1 or 2 (to use or not the UEFI lock, 1 uses it, 2 does not...)

This option already allows logging in with the domain user, but all connections to shared resources or logon scripts or access to shared directories of sysvol or netlogon are lost, so our users do not have full functionality when connecting to our network.

The only thing that works is going back to version 23H2 from the Windows Update options, as long as it hasn't been more than 10 days since the PC was updated.

To prevent this DISASTER VERSION of Windows 11 from being installed, we have created a script with registry modifications to block the version to 23H2

In the path: HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate

Create the keys:
- "TargetReleaseversion" type DWORD32, with value: 1
- "TargetReleaseversionInfo" type STRING, with value: 23H2
Currently we cannot get the 23H2 ISO since Microsoft only offers 24H2 to the public, but if you are a Microsoft Insider, you can get the 23H2 ISO by downloading the iso: Windows 11 Insider Preview (Beta Channel) - Build 22621

I'm afraid we have to wait for Microsoft to create a new build that fixes all these problems. In the meantime, formatting, reinstalling or returning to Windows 10 are the options we will have to use.
Was this answer helpful?

0 comments No comments
Anonymous

2025-01-02T17:26:59+00:00

Hi,

My issue is not quite similar (we had company.local domain so not single label).

I always disable IPV6 first, because so far it has brought nothing but trouble, no upsides.

I enabled smb1 (on the client side), yeah I know, will get rid of the one old 2003 AD server soon.

I managed to join domain with fresh 24H2 W11 installation, BUT...

I could not access sysvol or netlogon shares (no logon scripts etc.). "Ordinary" shares I could access.

DNS etc. are working nicely.

What helped (at least for now) is disabling Netbios over TCP/IP

(TCP/IPv4 settings / advanced / WINS tab in the advanced settings)

Hope this helps somebody out there :-)
Was this answer helpful?

0 comments No comments
Anonymous

2024-12-23T17:19:22+00:00

I had a similar issue today, after disabling IP6 it worked.

Best Regards

Christian Lützeler

Furtok Media
Was this answer helpful?

0 comments No comments
Anonymous

2024-12-20T16:54:03+00:00

Thank you my savior
Was this answer helpful?

0 comments No comments