Why Skip Welcome Center (UserOOBE) is still thewre in NTLite?

SM03

Member
As far as I know, this Skip Welcome Center (UserOOBE) option that is present there under NTLite Unattended, was a part of Windows VISTA

I.e. this was the Welcome Center (UserOOBE) in Vista

Windows_Vista_Welcome_Center_XP.png

And that SkipUserOOBE specifies whether to skip the Welcome Center pop-up window in Windows Vista.

So, I just wanna know why it is still there in the present NTlite build in this Windows 10 ERA?

12.png

& Furthermore, upon checking the NTLite OS support page here, the developer clearly states that current NTLite doesn't support VISTA.

So, my question is why it is still. Is there any use of SkipUserOOBE in Windows 10 then what is it?
Personally, I've tested by disabling that option (Set Skip Welcome Center (UserOOBE)=TRUE in NTLite) & I didn't notice anything.

I hope the DEV nuhi or anyone would answer & clarify this to me.

Thanks.
 
Last edited:

garlin

Active Member
Deprecated doesn't mean a feature stopped working, it means move to the new guidelines ASAP. There's a lot to unpack...

Windows ADK (7 & 8.1) and Windows System Image Manager (10) are the official tools to create custom images. NTLite parallels a great deal of the same functionality provided in both packages. WSIM continues to allow SkipMachineOOBE & SkipUserOOBE, and writes those tags in the answer file.

ua10.png


Reddit postings indicate SkipMachineOOBE still works on some builds to bypass network setup. Does that mean it won't go away in other builds? Who knows?

The reason you don't see any difference in enabling SkipUser, is because (paid) NTLite is generating all the unattended tags that supercede this functionality. If you removed the other lines from autounattend.xml except for SkipUser then you would see a difference.

Where NTLite could be vastly improved, is linking back to the MSFT docs to explain what many options do.
 
Last edited:

SM03

Member
Reddit postings indicate SkipMachineOOBE still works on some builds to bypass network setup. Does that mean it won't go away in other builds? Who knows?
I didn't ask about 'SkipMachineOOBE' here, rather I asked about 'SkipUserOOBE'.
SkipMachineOOBE works even in latest v20-04 Win10 ISo as I tried it, it completely removed/skip the Windows OOBE setup & take you directly to the login screen, if you didn't create a local account setup in NTlite then you can't login to the system anymore.

The reason you don't see any difference in enabling SkipUser, is because (paid) NTLite is generating all the unattended tags that supercede this functionality. If you removed the other lines from autounattend.xml except for SkipUser then you would see a difference.
I don't have a PAID license. So, I've tested all the options in Win ISO in the various combined scenario for testing & knowing & here are the outcomes with test options

ISO 1 1. Skip Windows Welcome (MachineOOBE)=TRUE
Outcome: 1. OOBE doesn't appear during installation for skipping Windows Welcome (MachineOOBE)
Direct login screen appeared but you can't log-into it.
Neither can connect or convert to online MSFT acc.

ISO 2 1. Skip Windows Welcome (MachineOOBE)=TRUE
2. Skip local acc+online acc+wireless setup= FALSE

Outcome: 1. Same as ISO 1.
2. No other difference observed for not skipping the local acc+online acc+wireless setup

ISO 3 1. Skip Windows Welcome (MachineOOBE)=TRUE
2. Skip Welcome Center (UserOOBE)=TRUE

Outcome: 1. Same as ISO 1.
2. No other difference observed for skipping the Welcome Center (UserOOBE


ISO 4 1. Skip Windows Welcome (MachineOOBE)=FALSE
2. Skip Welcome Center (UserOOBE)=TRUE

Outcome: 1. OOBE appeared during installation for not skipping Windows Welcome (MachineOOBE).
2. No other difference observed for skipping Welcome Center (UserOOBE)


ISO 5 1. Skip Windows Welcome (MachineOOBE)=TRUE
2. Skip Welcome Center (UserOOBE)=TRUE
3. Create/Enabled In-build Admin Local account in NTLite Setup

Outcome: 1. OOBE doesn't appear during installation for skipping Windows Welcome (MachineOOBE)
2. No other difference observed for not skipping the local acc+online acc+wireless setup
3. Logged into the system via created in-built Admin Account & can log in (connect) to online MSFT account
But no way to replace that in-build Admin account with Online MSFT acc,
You're bound to continue & use the in-built Admin account instead of logging into the MSFT Acc


ISO 6 1. Skip Windows Welcome (MachineOOBE)=TRUE
2. Skip Welcome Center (UserOOBE)=TRUE
3. Create/Enabled A Local USER account in NTLite during the setup of the Win ISO with a predefined USERNAME & PASSWORD

Outcome: 1. OOBE doesn't appear during installation for skipping Windows Welcome (MachineOOBE)
2. No other difference observed for not skipping the local acc+online acc+wireless setup
3. Logged into the system via created local account's credentials & can log in (connect) to online MSFT account.
If you login (connect) to your online MSFT account, the existing (local user created earlier under NTLite setup ) account will
auto-converted into your MSFT online account.
 

garlin

Active Member
I don't have a PAID license.
Well, it seems you ask for a lot of changes in return. I will answer your question one last time.

Whether OOBE works or not as hinted, is MSFT's call. They are creating confusion since it's not removed from ADK & WSIM. If you want to post a writeup sharing your exhaustive testing, great. Someone might be able to use the solution. NTLite is trying to be feature compatible (or bug compatible as it may be) with the MSFT tools.

If you've progressed beyond NTLite's features, then contribute by posting your scripts, templates or walk thru's. This isn't a debate society to score points by nitpicking arguments.
 

Kasual

Well-Known Member
"Skip Welcome Center (SkipUserOOBE)" option name is used for all windows versions, the same applies to component names and description.

SkipUserOOBE isn't really the same as Welcome Center in Vista.

This option (enabled) is used to hide the new user account name popup when a user name is set in unattended.

=======================================

The Welcome Center you referred to, is in Component removals as "Tips (Get started)", in Windows 7 is known as Getting started.
 

SM03

Member
"Skip Welcome Center (SkipUserOOBE)" option name is used for all windows versions, the same applies to component names and description.

SkipUserOOBE isn't really the same as Welcome Center in Vista.

This option (enabled) is used to hide the new user account name popup when a user name is set in unattended.

=======================================

The Welcome Center you referred to, is in Component removals as "Tips (Get started)", in Windows 7 is known as Getting started.
Kasual so if I keep that "Skip Welcome Center (SkipUserOOBE)" as true, what'd the real difference? Or if any?

Asking this because I see no difference in my 6 various tests mentioned in my earlier comment
 
Last edited:

Kasual

Well-Known Member
Kasual so if I keep that "Skip Welcome Center (SkipUserOOBE)" as true, what'd the real difference? Or if any?

Asking this because I see no difference in my 6 various tests mentioned in my earlier comment
False (default) means it will ask for user name
 
Last edited:

SM03

Member
The setup window will show up no matter how many user accounts are set.
no, I set both of these OOBE = TRUE with a local account created while making the ISO via the NTLite option & in my case, absolutely no setup windows or any OOBE appeared.
 

Kasual

Well-Known Member
Being asleep isn't good, post edited as "False" instead of "True", sorry about that.
in my case, absolutely no setup windows or any OOBE appeared.
Because the option skip the popups when:
no, I set both of these OOBE = TRUE with a local account created
There is always an error when no local account is set and both options are set to true.

Default options are set to "false" or "don't skip" the setup user account popup.
 

nuhi

NTLite developer
Staff member
nuhi

BTW, you did miss this one :)
Seemed like it was replied by others.
Basically the option SkipUserOOBE is there because admins asked for it, and it works.
Microsoft and me (not connected :)) do not recommend it, that is why on the Apply page there is a warning about it if option enabled.
But to achieve the same effect of skipping all those options, user needs to set many others, so I understand if they got used to that one to skip many.
 
Top