Using Windows 11 24H2 causes "The specified domain either does not exist or could not be contacted."

[jcams]

I'm trying to build an image using the W11 24H2 iso downloaded directly from Microsoft. After installing Windows to the partition, and using unattended mode, Windows will spend about 15 minutes saying "Please wait..." before eventually getting to a login screen that shows the Administrator account, but says "the specified domain either does not exist or could not be contacted." Also, I can't do anything from here because when I try to click any of the buttons on the bottom of the screen, there's a popup about LogonUI.exe having an error or something like that (I don't have it in front of me anymore).

This has happened whether I'm trying to join a domain or not, but only with 24H2, I didn't have any issues with 23H2. I've tried changing multiple settings around in the Unattended page and Apply page, including using a local admin account, but I just can't get it to work. I've attached a picture of the error and hopefully the correct .XML file that is usually asked for.

Mod Note: Redacted user password in preset.

 

[garlin]

This specific preset doesn't have any customizations, other than Unattended mode. But your source image is 26100.3476 (March 2025).
Is the ISO a clean download, or was there a previous edit to it?

 

[jcams]

It's a clean download from here in the "Download Windows 11 Disk Image (ISO) for x64 devices" section. It's been downloaded multiple times just in case there was a corruption with the download, but same thing every time. A month or so ago I also tried using an iso from the "Create Windows 11 Installation Media" section (had to download from home instead of work, though), but same thing.

Also, there were some changes made to settings in the Configure section, Post-Setup, one Registry file in the Registry section, drivers, and Updates in the Integrate section. Last month, I think I changed something in Features, but nothing now.

 

[garlin]

You're using the %SERIAL% hostname feature in Unattended mode. What is your PC's S/N (don't list the specific letters or numbers, but does it have a series of dashes or special characters in the sequence?).

Something like my S/N looks like "XXXX-XXXX". It could be the derived hostname is causing Windows to be confused.

 

[jcams]

No, they're Dell computers which are generally all 7 characters long of numbers and letters, no dashes or other special characters. Using pretty much the same exact configuration (for serial name or other sections) with 23H2 doesn't cause an issue, it's just 24H2.

 

[garlin]

In NTlite under Settings, enable Boot.wim Legacy Setup option.

Manual method:
UPDATE: Corrected & error in the quoted reg file.

You're on the free edition, but you can try reverting WinPE to the old Setup client using a .reg file.

1. Load boot.wim (Windows Setup).

2. From the Registry screen, add this file:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\Setup]
"CmdLine"="cmd /c start /min wpeinit && \\sources\\setup"

3. Apply changes, and create a new ISO.

 

[jcams]

Sorry for the delay, it's been busy. I loaded boot.wim from the 24H2 iso, added the Registry file and created a new iso. Should I then be loading that new iso and selecting Windows 11 Pro to re-set up the software and stuff I was trying to add before? Or can I load the preset I had?

 

[garlin]

You can just modify the existing boot.wim from your current ISO project, without starting over. The point is to test a simple change.

 

[jcams]

I didn't do anything else after attempting your steps. I took the iso created from there, applied it to a flash drive via Rufus, and it's working perfectly! The iso contained all of the software and customizations I had applied previously. Thank you so much, garlin!

 

[asig]

Hi,
I already have the same issue since Winodws 11 24H2 was avalaible. I tried to apply your solution, but when I load Windows Setup and try to add the reg file from Registry , I have this message (sorry it's in french) :"
[4306] La bibliothèque, le lecteur ou le pool de média sont vides.' - Ajouter 'C:\NTLite\Registre\JoinDomain.reg'".
I'm working on a new image downloaded from Microsoft site. I didn't make any changes yet, only tried to add the file.

Any idea about this error message ?

Thanks

 

[garlin]

Which problem are you trying to solve? The shared reg file is intended to switch the Setup client on a clean install.

1. Load the boot.wim (Windows Setup) image.
2. Add the reg file.
3. Apply changes.

 

[tistou77]

Hi,
I already have the same issue since Winodws 11 24H2 was avalaible. I tried to apply your solution, but when I load Windows Setup and try to add the reg file from Registry , I have this message (sorry it's in french) :"
[4306] La bibliothèque, le lecteur ou le pool de média sont vides.' - Ajouter 'C:\NTLite\Registre\JoinDomain.reg'".

What version of NTLite are you using ?

 

[asig]

Hi all,
Thanks for your reply.
I'm trying like JCAMS to auto join domain (specialize options) as it's was possible before Windows 11 24H2 release. I arleady have this message in Microsoft events logs (Source: NetJoin, Event ID: 4097, "The computer xxxxxx attempted to join the domain xxxxxxxx but failed." The error code was 2202. I also see error code 2 with the same message).
My domain is FQDN as domain.local. I found some posts in Microsoft site talking about this problem, when domain is not FQDN.
After image installation, the computer is not joined to the domain (as it was previsously with Windows 11 23H2), but I can join it manually, with the same account and password which is set in ntlite settings.
DHCP correctly delivers an address during the process.
So I found this post talking about the registry value and I tried to do it, but I'm facing this issue when I try to add the file to the ntlite image.

My Ntlite version is 2025.6.10459 (64 bit) with licensing.

Thanks a lot.

 

[tistou77]

Ok, I was asking about the version because I couldn't find this entry in the language file "La bibliothèque, le lecteur ou le pool de média sont vides"
This translation jumped out at me

As for your reg file to add, you can share it so we can look at/test it

 

[asig]

I found the problem. I had to replace "&&" by "&&", because "&&" is the way encoding in XML and HTML.
So the error message was meaning that the value doesn't exists or be processed by ntlite.
I'm gonna quickly test it and pray that it works and solve my issue.

I'll keep you up-to-date.

Thanks again

 

[garlin]

I found the problem. I had to replace "&&" by "&&", because "&&" is the way encoding in XML and HTML.
So the error message was meaning that the value doesn't exists or be processed by ntlite.
I'm gonna quickly test it and pray that it works and solve my issue.

I'll keep you up-to-date.

Thanks again

Ah. The dreaded copy & paste problem when copying text from a web forum (in this case, my own post).
Thanks for noticing my error. I fixed the original post.

[HKEY_LOCAL_MACHINE\SYSTEM\Setup]
"CmdLine"="cmd /c start /min wpeinit && \\sources\\setup"

 

[asig]

Ah. The dreaded copy & paste problem when copying text from a web forum (in this case, my own post).
Thanks for noticing my error. I fixed the original post.

[HKEY_LOCAL_MACHINE\SYSTEM\Setup]
"CmdLine"="cmd /c start /min wpeinit && \\sources\\setup"

you're welcome

 

[asig]

Hi all,
Finally after 6 months, trying many solutions, this solution works. I tired many times to be sure that the autojoin works fine.
Thanks a lot for help.
Just for my understanding, I have a few questions :
- What happened between Windows 23H2 and 24H2, for autojoin not working any more ?
- I understand wpeinit.exe, initialize a lot of components before the installation, but why does this registry entry solves the issue ? (I have noticed the UI installation is back to the previous 23H2 UI installation, there was a new one with the 24H2)
- And last question, is ntlite will deploy a fix to solve this issue ?

Thx

 

[nuhi]

Hi all,
Finally after 6 months, trying many solutions, this solution works. I tired many times to be sure that the autojoin works fine.

Hi,

so can I somehow help with the tool auto-converting so that this does not happen to others?
Settings applying has Boot.wim Legacy setup option already, no need to integrate files.

Just for my understanding, I have a few questions :
- What happened between Windows 23H2 and 24H2, for autojoin not working any more ?
- I understand wpeinit.exe, initialize a lot of components before the installation, but why does this registry entry solves the issue ? (I have noticed the UI installation is back to the previous 23H2 UI installation, there was a new one with the 24H2)

That's a Windows question, NTLite does not control how the well known methods are interpreted by the various versions of setup.
To summarize what you found, the new 24H2 "Modern Setup" does not support unattended autojoin?
Someone should ask Microsoft if that is a bug or a deprecated feature.

- And last question, is ntlite will deploy a fix to solve this issue ?

Let me know if NTLite sets anything wrongly, what it could do is suggest Legacy Setup when someone uses Autojoin.
Warning will be on the Apply page.

Thanks for the feedback.

 

[asig]

Hi Dino,
Thank you for your detailed reply, much appreciated!
Regarding your response, I’d like to follow up on a few specific points:
- You mentioned that “Settings applying has Boot.wim Legacy setup option already, no need to integrate files.”
However, I couldn’t find this option in the current interface. Could you please indicate exactly where this setting is located in NTLite?
- This definitely seems to be an issue introduced with the new “Modern Setup” in Windows 11 24H2.
I will reach out to Microsoft directly to ask whether the lack of support for unattended domain joining via AutoJoin is a bug or a deprecated feature.
- I think your idea is a very good one: if NTLite detects the use of AutoJoin with version 24H2 (and possibly future versions, if the issue persists), it would be very helpful to have a warning or the possibility to switch to Legacy Setup automatically. This would prevent a lot of confusion for others.

Thanks again for your work and support!