oobeSystem is gone?

[prlw1]

oobeSystem is gone?

[pbatard]

Log, Log, Log, LOG!!!!

You are asked for a log. It is not up to you to decide whether it's needed or not.

I simply cannot answer your question as you are not providing enough data about the actual environment Rufus ran in. You believe you do, but you actually don't.

Also, oobeSystem is unrelated to local account creation. Instead it deals with the BitLocker and data collection option.

Since you are taking a shortcut, and did not provide a log, I will take one too: My guess is that your issue has everything to do with BitLocker, so please disable the BitLocker option and report what happens.

[pineapple63]

Using the limited amount of information you gave, i did manage to reproduce the issue on one of my systems

rufus.log

I am going to try a few things to see if i can figure out what is causing the error

[prlw1]

I rewrote the USB stick to get the log, @pineapple63 has posted an equivalent - thanks!

I tried again just deselecting the bitlocker option and saw the same apparent behaviour.

I failed to boot another OS to get at the Panther directory.

[pineapple63]

From what i can tell, it seems to be the regional options selection that causes the error
I created a USB using a retail ISO image to see if something funky was going on with the media creation tool ISOs
rufus3.log
and the USB created from the retail ISO gave the same error

And just to clarify, when i created a USB without the regional options selected
rufus2.log
I did not get the error, and i was able to complete the OOBE setup

[pbatard]

Then this has to be the new TimeZone setting from 10d33c6.

I guess this needs to be moved out of Microsoft-Windows-International-Core and into Microsoft-Windows-Shell-Setup.

[prlw1]

Indeed! Using rufus built from 83b1e73 got me a successful install! (with the same options as in original report)

[pbatard]

This issue should be fixed in latest builds.