"The Specified Domain Either Does Not Exist or Could Not Be Contacted" Error-Win. 10 1903 Eng.-Int.

dkdubya2

New Member
Hi,

After starting fresh with a newly downloaded ISO of Win. 10 Pro 1903 English-International via Rufus, trying to create a local user admin, & doing all of the intergration to spec with an attempted created local user, when doing a test-install using Virtualbox, after having to unlock the screen using VM key combo Right "Ctrl" + "Delete", I have encountered the exact, same error that the user "lagah" posted earlier on January 6th of this year (see link to post below), "The Specified Domain..." when I am also not adding a domain, but unlike lagah, I didn't try using an enabled built-in admin as I read this could leave me wide-open, security-wise.

And despite attempting a 3rd integration using Nuhi's suggestion to lagah by copying "Copy to install image", & also to boot (not using OOBE or my own setupcomplete) as I'm only deploying one wim, I am getting the same error with no options to get out of it, no rebooting to safe mode to troubleshoot, nothing. FYI, I am using the latest NtLite update.

The source ISO successfully test-installed, but after dealing with various issues over the past few weeks towards a workable, ideal slipstreamed Win. ISO, I am literally at my wits end & completely burnt-out. Please see the attached screencaps, the autounattend file (with private info edited out), & the NtLite.log. Ironically, I've had a Microsoft account since 2013, so their forcing Windows users to create one is a non-issue for me, I'd be more than happy inputting my Microsoft account user & pass to a slipstream, if that would help.

I didn't see that lagah replied publicly on his posted thread that the issue was resolved, so I hope there is help for ME here to resolve my own, it's sorely needed, thanks.


-dkdubya2

P.S. The error also includes a "No Internet" notice, though I enabled internet access in the integration, & in the VM settings.


Locked Screen Error Win. 10 1903 Eng-Int. Version.JPGSpecified Domain Error Win. 10 1903 Eng-Int. Version.JPG

 

Attachments

  • autounattend.xml
    3.2 KB
  • NTLite.log
    32 KB
Last edited:

nuhi

NTLite developer
Staff member
Hi,

It's as if the user wasn't created, and I've never seen that.
Maybe there is a username limitation that wasn't accounted for, potentially a space in it is not allowed then it was skipped.
More info here on forbidden characters, if confirmed that the UI didn't block it, let me know a similar name which I can use to replicate the issue.

I'm assuming the Administrator account wasn't unlocked using the added user, this prompt is just because it had no other user to show.

Don't spend much time on it, it's now a question of what broke, there are logs and a full preset that I might require if the above didn't help, so keep one failed install aside.

Thanks.
 

dkdubya2

New Member
Thanks,

Since I've done a few sessions, I saved a notepad with the main Unattended settings I want to use, it was spelled like this, including the small-case letter, space, & dash, similar to a local account username spelling I have for my Windows 7:
LKBs Now-Viva

And yes, as I stated, no Built-in Admin. due to security concerns, & no auto logon for the local account, just the user, pass, & description, which was equal to New-Start User. One thing I didn't mention, was that due to no internet within the Windows install (it was enabled in the VM settings), the update configuring was rolled back before the machine restarted to said main error.

Since you didn't mention them, I'll assume the two extraction errors I saw in the NTLite.log, Service TSFairShare description & Service WinQuic description respectively, are either the norm, or are inconsequential.

Wish I could have found a way to go into safe mode to grab the setup.log for you, but it just booted into the same error when I rebooted & tried. I DID proactively save the failed install ISO, but at 12.1 GB don't know how I could send you if you need it to analyze, but please advise if you can-I will take your advice to not dwell on it & take a break for the holiday, thanks again.
 
Last edited:

nuhi

NTLite developer
Staff member
OK, tried the username as instructed, plus your autounattend.xml with manual editing to fit the test.
No issues.

But then I saw the key point in your further info, the reboot before the end of setup, that's what skipped the user creation.

OK, so let's focus on the update failure, send me a preset and explanation what was done to the image to produce the error?
Also why is it 12GB, integrated many drivers/apps or it's a custom captured WIM of a pre-setup deployment?
 

dkdubya2

New Member
Hi,

Looking at the attached preset I edited for privacy reasons, I only noticed the hosted VM build is different than the loaded WIM, & that I accidentally integrated a Sysvol regtweak (of many other used regtweaks ) to allow local logon when I'm not using a AD domain at all, this latter bone-headed tweak may likely be the wrench thrown-in producing the error, I highlighted both in boldface for you.

I also recall that I may have copied in the OEMSetupcomplete.cmd, another possibly cause of the autoattend.xml bypass, maybe? But clueless as to why the update configuring fails, I've watched in frustration the updating get too 98% before the "undoing".

I'm only using the Pro. Ed. WIM, & besides only 2 updates (no extra integrated drivers), I am integrating about 5GB of applications in post-setup, so this should explain the ISO size. Please let me know what you discover, thanks.

Off-topic: I was curious, is the Netlogon being greyed out in services for a loaded image the norm? It prevents any changes, including resetting the service.
 

Attachments

  • Auto-saved session {28B60A3D-BA82-4241-A016-47E72600B207}.xml
    25.4 KB
Last edited:

dkdubya2

New Member
Dear Nuhi,

I have since downloaded the Win10_1903_V2_English_x64.iso which again, tested normally in a VM, & have done 4 more sessions, even doing a Host Refresh sans the setup.exe upgrade running on the VM to properly integrate updates with DISM cleaning, to address your concerns about possible update failure, & created 4 different custom ISOs, ALL which have failed via VM testing.

I should also point-out, that I did one ISO without removing any components, & one ISO without any extra tweaking at all, & still came up short with an update component rollback error.

So at this point, after using NtLite since mid-April to today to no avail, I must lean on you for a solution; this time after the last rollback, I was able to create a notepad via CMD of the combined setup & image partition error logs respectively, along with saving the autounattend.xml, last session preset, & Ntlite.log (please see all of the attached.) I can also create a ISO of the last slipstreamed install files without the huge post-setup files, to send you privately if needed for analysis (you use Google Drive?).

The only consistent error I have noticed in the setup.log, are multiple "Global-root HDD bcd path or files not being found errors" (=02); however, for the last ISO I chose not to copy into the boot.wim to avoid posible corruption, so I still haven't a clue, but was hoping you could find one for me to help finally fix this issue.

I really like NTLite's capabilities , but it serves me no purpose if it won't work for me.

Thanks.

-dkdubya2
 

Attachments

  • Auto-saved session {39F79DBF-87CD-49A7-BB62-8198EB283522}.xml
    26.2 KB
  • autounattend (6-8-21).xml
    4.8 KB
  • NTLite.log
    33.5 KB
  • Windows 10 1903 (U.S.) Setup.log (6-8-21).txt
    237.1 KB

dkdubya2

New Member
As a proactive troubleshooting measure, I removed my Windows 10 trial VM that uses an earlier build (was close to expiring anyway), & am now using an attached "Activated" 1903 Build ISO I found online as a Virtualbox VM to match the build I'm trying to slipstream & see if this make any difference.

However, seeing ALL of the junk in this working attached ISO version Win. 10 VM for the very 1st time, only strengthens my resolve to create a slipstreamed version of Win. 10 to get rid of it, it's shocking to me just how bloated windows really IS now!
 

dkdubya2

New Member
This is the latest issue that comes at the very end of the VM test install, I added a local user & a guest user in the autounattend, then checked the outside autologon option with the main local user & pass info. If I can lick this issue, I think I'll finally be good to go for a working slipstream: Windows could not parse or process error.JPGInstall Windows Error.JPG
 

nuhi

NTLite developer
Staff member
Hi,

Looking at the attached preset I edited for privacy reasons, I only noticed the hosted VM build is different than the loaded WIM, & that I accidentally integrated a Sysvol regtweak (of many other used regtweaks ) to allow local logon when I'm not using a AD domain at all, this latter bone-headed tweak may likely be the wrench thrown-in producing the error, I highlighted both in boldface for you.

I also recall that I may have copied in the OEMSetupcomplete.cmd, another possibly cause of the autoattend.xml bypass, maybe? But clueless as to why the update configuring fails, I've watched in frustration the updating get too 98% before the "undoing".

I'm only using the Pro. Ed. WIM, & besides only 2 updates (no extra integrated drivers), I am integrating about 5GB of applications in post-setup, so this should explain the ISO size. Please let me know what you discover, thanks.

Off-topic: I was curious, is the Netlogon being greyed out in services for a loaded image the norm? It prevents any changes, including resetting the service.
Hi,

not sure what the question is regarding the first part, seems like you're on top of it.

Netlogon service is needed for Start Menu deployment, so thus protected.
 

nuhi

NTLite developer
Staff member
Dear Nuhi,

I have since downloaded the Win10_1903_V2_English_x64.iso which again, tested normally in a VM, & have done 4 more sessions, even doing a Host Refresh sans the setup.exe upgrade running on the VM to properly integrate updates with DISM cleaning, to address your concerns about possible update failure, & created 4 different custom ISOs, ALL which have failed via VM testing.

I should also point-out, that I did one ISO without removing any components, & one ISO without any extra tweaking at all, & still came up short with an update component rollback error.

So at this point, after using NtLite since mid-April to today to no avail, I must lean on you for a solution; this time after the last rollback, I was able to create a notepad via CMD of the combined setup & image partition error logs respectively, along with saving the autounattend.xml, last session preset, & Ntlite.log (please see all of the attached.) I can also create a ISO of the last slipstreamed install files without the huge post-setup files, to send you privately if needed for analysis (you use Google Drive?).

The only consistent error I have noticed in the setup.log, are multiple "Global-root HDD bcd path or files not being found errors" (=02); however, for the last ISO I chose not to copy into the boot.wim to avoid posible corruption, so I still haven't a clue, but was hoping you could find one for me to help finally fix this issue.

I really like NTLite's capabilities , but it serves me no purpose if it won't work for me.

Thanks.

-dkdubya2
If you have updating issues without removals and update cleanup, or disabling services, then your image is broken or you're using some external tweak that breaks it.
If you solved this in the meantime judging by newer post, let me know what it was for more info.
 

nuhi

NTLite developer
Staff member
This is the latest issue that comes at the very end of the VM test install, I added a local user & a guest user in the autounattend, then checked the outside autologon option with the main local user & pass info. If I can lick this issue, I think I'll finally be good to go for a working slipstream:
Please attach the preset causing it, otherwise how can I know.
My guess is a (wrong/unnecessary) product key in the Activation box, try without it, or unsupported character in the name/computer name.
Just a guess, best is to send me the preset - maybe PM it if has private info.

Thanks.
 

dkdubya2

New Member
Okay,

Thanks for replying to all of my comments.

From what I read myself in the log, the Windows Retail Product Key I used was validated, but it looks like setup couldn't see either my owner, or my organization name, despite my inputting them to what I thought was to spec.

In any case, I will privately send you all I was able to attach from the failed install, along with the preset, but of course it will help if your discovered answers are posted here for everyone to read and learn. I just hope this issue (if resolved), will be the last one.

By the way, the Windows Update component remains greyed-out despite my disabling protections as suggested in this other post for me to try removing it, so please let people know what has changed that continues to protect WU: ntlite.com/community/index.php?threads/remove-windows-update.346/#post-18338
 

nuhi

NTLite developer
Staff member
Got the files, thanks.

First steps:
- remove the product key from the activation box (the "Specialize" section, which actually popped up in your screenshot)
- now that I see you add gazillion of REG files, skip those as it is not part of the tool to be debugging here
- also do not disable protections if you want support, otherwise is the plan to ignore some issues and learn about all the protections along the way, retesting them...too much time wasted. I suggest to first start with a working set, then slowly expand.

Do these 3 and it must work.

WU service is not locked that I can see, nor with protections on.
A component (not service), is locked by compatibilities like OOBE, Activation etc, those are listed on the right of the component, under "Extra info".
Go to toolbar - Compatibility - and turn off those you don't need, but I doubt that you won't want to keep that component.

Let me know how it goes.
 

dkdubya2

New Member
Finally, success!

As per your advice, I was able to create a working Win. 10 ISO (no post-set up files) which I have saved, so I am currently doing another session to see what I can can safely add and/ or remove without any issues for a final desired ISO.

BIG SIGH, thank you SO much!
 
Top