Windows 10 21H2 Not allowing account creation on install?

[Tannah]

So I just had a annoying one, Updated to NTLite 2.3.3.8585 from a version from the end of December 2021, and I had what I thought was a operational XML image setup in NTlite, that I had used in December.
One of my computers needed a reinstall, so went into NTLite and updated to the latest windows updates, updated the Firefox msi to the latest. Believing everything should be fine. Set NTlite to creating the image. Tried installing the ISO and Lo and behold to my surprise the install ended on a login screen? Try again, with the same result? So start investigating. I know what I changed, so I start checking the windows update KB files (they turn out to be fine) check the firefox MSI as it has messed things up in the past (The firefox installer is operating as intended)?

So Bemused I start pulling out each update, trying to pear down the problem. Then start going though the XML file, looking for problem's referencing older XML's that I know that worked properly. After pulling everything out, and cross checking things. I go look in Unattended, everything looks fine? On a whim I change the: "Skip Welcome Center (SkipUserOOBE)" from grey (which is suppost be default?) to red (which sets it to False), and change: "Skip Windows Welcome (SkipMachine00BE)" from True to grey.
Try running the ISO though NTlite again. Then installing the ISO onto a machine, it gives me a account creation prompt now, and allows login.
But I don't see screens that normally popup when Skip Windows Welcome (SkipMachine00BE) is set to grey default?

To me it seems that the settings that are set to Grey (default) appear to be being passed over? So if these two setting are doing this are there other settings that are doing the same? Which may cause issues down the road?
I really don't know?

I'll add the XML, for you to look over, I don't have the older one that did not work.

Thank you for your insight into this.

 

[garlin]

SkipMachineOOBE & SkipUserOOBE have been deprecated since W8.

They still work (for now), but MS wants you to stop using them. SkipMachineOOBE's function was replaced by this block:

<OOBE>
        <HideEULAPage>true</HideEULAPage>
        <HideOnlineAccountScreens>true</HideOnlineAccountScreens>
        <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
        <NetworkLocation>Home</NetworkLocation>
        <ProtectYourPC>3</ProtectYourPC>
</OOBE>

Some experts will edit the Unattended XML, and add advanced options that NTLite doesn't currently support. NTLite will respect those extra lines and leave them alone. When SkipMachineOOBE & SkipUserOOBE are defined, they're flagged for your attention.

The proper way to skip UserOOBE is to create a local account from Unattended. Now if you want to use a MS account, this option doesn't work and you must walk thru OOBE. SkipUserOOBE without defining any account leaves W10 & W11 stuck in install.

Basically if you're on W10 or W11, don't touch those settings. When in doubt, use Auto-fill (all).

 

[nuhi]

I'll add the XML, for you to look over, I don't have the older one that did not work.

Well, as garlin explained, you probably skipped OOBE/user creation, and a user wasn't pre-defined.
That is why there is a warning about it on the Apply page if OOBE skips are enabled (try it just as a preview), so that user knows to pre-create one and setup will be fully unattended if using that option for some reason.

This is a Windows topic btw, there are no known tool issues in swapping true/false that you allude to.
Of course if proven otherwise, that would be of utmost importance to get fixed fast, so keep us updated of any weirdness.

Thanks.

 

[Tannah]

Thank you garlin. That explains why changing "Skip Windows Welcome (SkipMachine00BE)" did not have a affect.

That cancels one point of data I had for my hypothesis.

nuhi I managed to recover a older version of the XML I'll post it, if you would like to look over it.

If you look at the old OOBE:
</OEMInformation>
<OOBE>
<HideEULAPage>true</HideEULAPage>
<HideOnlineAccountScreens>true</HideOnlineAccountScreens>
<HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
<NetworkLocation>Work</NetworkLocation>
<ProtectYourPC>3</ProtectYourPC>
<SkipMachineOOBE>true</SkipMachineOOBE>
</OOBE>

Vs the working OOBE:
</OEMInformation>
<OOBE>
<HideEULAPage>true</HideEULAPage>
<HideLocalAccountScreen>false</HideLocalAccountScreen>
<HideOnlineAccountScreens>true</HideOnlineAccountScreens>
<HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
<NetworkLocation>Work</NetworkLocation>
<ProtectYourPC>3</ProtectYourPC>
<SkipUserOOBE>false</SkipUserOOBE>
</OOBE>

Thank you for all your insight

 

[garlin]

There's non-stop questions on-line why this or that combination doesn't work with SkipOOBE. No one has clear answers.
Follow MS' advice and remove all SkipOOBE lines. It makes it simpler to troubleshoot everything else.

<HideLocalAccountScreen> only applies to Windows Server.

 

[Tannah]

There's non-stop questions on-line why this or that combination doesn't work with SkipOOBE. No one has clear answers.
Follow MS' advice and remove all SkipOOBE lines. It makes it simpler to troubleshoot everything else.

<HideLocalAccountScreen> only applies to Windows Server.

Interesting, For me the odd thing is it was working. but then it stopped? Same Original Windows 10 iso? So it leads me to ask what stopped it from working? Why would the OOBE suddenly stop working with the exact same image, same XML. Just a different month, and newer version of NTLite?
You can see why I'm asking right?