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.
https://www.elevenforum.com/t/specify-target-feature-update-version-in-windows-11.3811/https://www.elevenforum.com/attachments/specify_target_feature_update_version_to_windows11_23h2-reg.87851/?hash=60ea4a409030d60c3e89bda7ac0c1d12
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate]
"ProductVersion"="Windows 11"
"TargetReleaseVersion"=dword:00000001
"TargetReleaseVersionInfo"="23H2"
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.
What is domain controller? Active directory or openldap?
I am not the same person. But I have the same problem.
I use OpenLDAP.
Do you have a solution to the problem? Or any idea?
I am not the same person. But I have the same problem.
I use OpenLDAP.
Do you have a solution to the problem? Or any idea?
nltest /dsgetdc:<domainname>
nslookup -type=SRV _ldap._tcp.dc._msdcs.<domainname>
Run these commands from windows clients, and confirm SRV location for your domain is available on DNS server. If not good to update. Give a try.
I am not the same person. But I have the same problem.
I use OpenLDAP.
Do you have a solution to the problem? Or any idea?
Hi Filipe,
Can you tell what is your openldap version?
