Integrate new OOBE bypass (ms-cxh:localonly) in a autounattend.xml script??

jimbo45 said:

I think you guys are flogging a dead horse here. If you need to deploy Customized Windows to a load of machines there's nothing wrong with the proper recommended sysprep method.

For domestic users a lot of this "eseoteric stuff" is Way over the Top.

Click to expand...

That depends on what exactly it is that you want to achieve with unattended deployment, which is not clear from the OP.

hdmi said:

That depends on what exactly it is that you want to achieve with unattended deployment, which is not clear from the OP.

Click to expand...

Have to agree with that.

Cheers
jimbo

Hey @rafaelsouzams, I am the guy who originally found the command around 6 months ago.
To give you an understanding about how ms-cxh://localonly operates, you have to understand what it executes.

The uri is linked to a system UWP package called CloudExperienceHost. CloudExperienceHost begins to run as soon as you see the Just a Moment spinner before hitting the oobe. This means you cannot load the window during the windows boot sequence, you have to wait until the defaultuser0 user is signed in.

Maybe if you add a delay or integrate the execution as a service with delayed start you can get the outcome you are asking for.

I am interested to see how you go with this. Lmk of you want some more info.

Cheers
-thePineapple