This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](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)
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:
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.
I had the same problem with a "mydom." without tld .lan, .local .
The problem was present both on 23H2 and 24H2
Here is the fix I found and solved the problem :
On each DC :
KEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\AllowSingleLabelDnsDomain (dword 1)
On computer :
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DnsCache\Parameters\UpdateTopLevelDomainZones (dword 1)
Restart computer and join on "mydomain." (do not forget the "." to validate tld )
Thank you for the post Neuvi. This problem is specific to Win11 24H2. Every Win other win client can connect without a problem. MS needs to address this as more people are running into this problem.
thanks for your input. this has to do with OOBE and UEFI. Rather not the problem of; not be able to join a corporate domain.
Patch KB5044384 will solve the issue you mentioned. (OS Build 26100.2161)
our problem is still pending....
I found a work around that worked for my Win11 24H2 devices. This is by no means a fix.
I opened a cmd and ran "ipconfig /renew" and in all cases Domain log ins and DNS calls started working after about 10 seconds.
The whole TCP stack seems to drift randomly and the PCs eventually start behaving the same way, losing their Domain connections and ability to resolve DNS.
Because of this I created a task on the PCs to run the command every hour in perpetuity. I am not fond of the idea of having to run this in the background, but it does seem to resolve things from the end user pov.
Hopefully this might also be a red flag for developers.
tried that also before a few times but no fix. something else is causing this. so far no solutions to be found anywhere. i tried registry options and anything else i could find.... re-installing does not seem to fix it also. I can log into the domain but then i am forced into the guest network connection that wil limit functionality like network drives. only PVN connection over Citrix works and then i am logged into the .local network. only problem here is that it is extremly slow....