Insider ISOs - can't get past OOBE stage

Hi guys
i need help,
what is the password for the orphaned defaultuser0 ?
its password prompting me to access lusrmgr.msc , activating windows10 etc.

Somebody, anybody, please, explain to me the necessity of complicating the install process so much, that the average system won't take the install/update, without jumping through circus hoops, and turning flips Simone Biles wouldn't attempt? What does it benefit to make the implementation so complex, some people just give up because it's too complicated? The simple task of creating accounts is now put to command prompt status that you need to work around the normal startup to get to. This is ridiculous!!!

Kari said:

Your post makes no sense.

Windows Setup and installation is fairly simple. Yes, it involves a few mouse clicks, entering the initial username and so on, but it is simple and works perfectly.
When complaining about this or that in Windows Setup, it would help us to reply if we knew what have you done, what is not working, what error messages you are seeing, and so on.

Kari

I made a USB flash to install Windows 10 1903. The install ran into the OOBE pages and stuck. I am on this thread because it was NOT simple. I am going to try the same install with an .iso disc and see what it does, but try to tell me about a "few mouse clicks" when I gotta delete a "defaultuser0" account, login with an "administrator" account, go elevated command prompt to create the account that I want, when I used to do all of that in the install. And when it was over, all that was left was personalizing. How can you equate this abortion with "simple"? Maybe for you, since you are obviously smarter than me. But it is anything but "simple".

- - - Updated - - -

Kari said:

Your post makes no sense.

Windows Setup and installation is fairly simple. Yes, it involves a few mouse clicks, entering the initial username and so on, but it is simple and works perfectly.

When complaining about this or that in Windows Setup, it would help us to reply if we knew what have you done, what is not working, what error messages you are seeing, and so on.

It is impossible to give you any sound advice based on your post.

Kari

Kari, you said my post made no sense. Well, I just did the install from a .iso disc created from MCT, and it did exactly the same thing. I just went through the command prompt version of creating an account, and it is still not plain to me how this way is "simple". I appreciate all of the advise that I got from this thread, but my question remains, as do my opinion on this exacerbated process of something that, for years, was truly, simple.

TheRedeemer said:

Thanks TR3X77, I was able to get past the OOBE errors with your work-around on a fresh Win 10 install.

Landed on one of the OOBE errors, then brought up the cmd prompt with Shift+F10 and typed:

Code:

net user administrator /active:yes

net user /add owner mypassword

net localgroup administrators owner /add

cd %windir%\system32\oobe

msoobe.exe

Then I waited a full 15 minutes and powered off via the switch, since it was not continuing.

After powering back on it continued setup and eventually put me on the Administrator desktop, so I chose log off, and logged into the "owner" account I created earlier. Then brought up lusrmgr.msc and disabled the Administrator account, and deleted the "defaultuser0" account that was orphaned during the failed setup due to the oobe errors.

its continuing ! are you solving the problems of november in the future updates that kill all vm's, it sure looks like it . have you any idea how much you are currently loved ??? thankyou if only all searches was made of yur type of answer , the timing for me could not be more ferfect . with the google bottlneck of irrelevant answers searched. Have a very good 40 years !

- - - Updated - - -

i never want to close this page again !

Kari said:

One thing that you could try is Sysprep, it is pretty good in fixing OOBE.

When you come to region selection screen, press SHIFT + F10 to open Command Prompt and enter following command:

%windir%\System32\Sysprep\sysprep.exe /oobe /reboot

This clears current GUIDs and SIDs, restarts computer and runs OOBE again. Takes a minute or so.

I am not saying this resolves your issue, but it has done it for me quite often when OOBE for one or another reason cannot finish setting up Windows.

Kari

Thank you , i resolved with that and the default0 user creation ,thank you thank you ...

For others with this and like problems; at least on standard machines: Had this and other problems (like "missing drivers") during installs and wasted absurd amounts of time on them. Seldomly, it's possible to hack your way all through... But in all my cases there's been a reason for all the trouble. So I highly recommend:
1) testing your hardware, especially the RAM. Naturally, memory problems will result in all sorts of strange errors - and trying to solve them is nothing but waste of time...
2) check your media! For some odd reason M$ installers do not check the integrity of the install files... So even though the install starts fine - errors might be the reason for subsequent errors (like the "missing driver")

Happy hunting!

After two years of Feature Update failures, my HP Compaq nc6120 is finally running 1909. I did a fresh install from a USB .iso using WintoHDD and battled past the dreaded OOBE using Shift F10 and:
net user Administrator /active:yes
net user /add user_name mypassword
net localgroup administrators user_name /add
%windir%\System32\Sysprep\sysprep.exe /oobe /reboot
Thanks for suggesting this work around, but can anyone explain why it gets past the endless OOBE loops and why it's needed?
Brian

To solve the oobe problem you press and hold the shift key and F10 key together then click on the clock settings in the lower left corner of the screen then click on the home menu then update and security then recovery then select reset this PC and select keep my files, then click on reset. reset takes 90 minutes to complete.