Windows 10 Build 10051 Problem

[TheBetaFan18329]

Hi everyone! I installed Windows 10 Build 10051 in VMWare Workstation 15. The setup finishes normally but when I get to the oobe, it restarts while it loads the user account setup.

Can someone help me please?

[Meow]

Hi everyone! I installed Windows 10 Build 10051 in VMWare Workstation 15. The setup finishes normally but when I get to the oobe, it restarts while it loads the user account setup.

Can someone help me please?

This is a known bug. Press Shift+F10 and add your user there.
Also you can enable the admininstrator account and use that.

[TheBetaFan18329]

Hi everyone! I installed Windows 10 Build 10051 in VMWare Workstation 15. The setup finishes normally but when I get to the oobe, it restarts while it loads the user account setup.

Can someone help me please?

This is a known bug. Press Shift+F10 and add your user there.
Also you can enable the admininstrator account and use that.

I tried enabling the administrator account and it still goes back to the oobe.

[Windows Thunderstruck]

Do the oobe as normal, but when you get to "checking connection", restart the vm as soon as it appears. You have to get the timing just right at that part.
Do not let it go blank, as if you restart at that part, you will be taken back to the oobe.

[Meow]

Hi everyone! I installed Windows 10 Build 10051 in VMWare Workstation 15. The setup finishes normally but when I get to the oobe, it restarts while it loads the user account setup.

Can someone help me please?

This is a known bug. Press Shift+F10 and add your user there.
Also you can enable the admininstrator account and use that.

I tried enabling the administrator account and it still goes back to the oobe.

Shift+F10 then regedit. Change SystemSetupInProgress, SetupType, OOBEInProgress and RestartSetup to 0. Then reboot.

[TheBetaFan18329]

Hi everyone! I installed Windows 10 Build 10051 in VMWare Workstation 15. The setup finishes normally but when I get to the oobe, it restarts while it loads the user account setup.

Can someone help me please?

This is a known bug. Press Shift+F10 and add your user there.
Also you can enable the admininstrator account and use that.

I tried enabling the administrator account and it still goes back to the oobe.

Shift+F10 then regedit. Change SystemSetupInProgress, SetupType, OOBEInProgress and RestartSetup to 0. Then reboot.

I changed the registry keys and this happens.

https://www.betaarchive.com/imageupload ... .71818.png

[Windows Thunderstruck]

Then you will have to re-install it then.
As i said before, do the installation as before, but when you get to oobe, go to audit mode by doing CTRL+SHIFT+F3. Then create a user account by using lusrmgr.msc.
After you create your account, go back to oobe, do as normal until you reach "checking connection".
You MUST restart as soon as it says that, and you have to get the timing JUST right. If it takes you back to oobe, try again
If done correctly, you should have a working 10051 vm!

[TheBetaFan18329]

Then you will have to re-install it then.
As i said before, do the installation as before, but when you get to oobe, go to audit mode by doing CTRL+SHIFT+F3. Then create a user account by using lusrmgr.msc.
After you create your account, go back to oobe, do as normal until you reach "checking connection".
You MUST restart as soon as it says that, and you have to get the timing JUST right. If it takes you back to oobe, try again
If done correctly, you should have a working 10051 vm!

I made my user account and got back to the oobe but how can I get the timing just right?

[Windows Thunderstruck]

Then you will have to re-install it then.
As i said before, do the installation as before, but when you get to oobe, go to audit mode by doing CTRL+SHIFT+F3. Then create a user account by using lusrmgr.msc.
After you create your account, go back to oobe, do as normal until you reach "checking connection".
You MUST restart as soon as it says that, and you have to get the timing JUST right. If it takes you back to oobe, try again
If done correctly, you should have a working 10051 vm!

I made my user account and got back to the oobe but how can I get the timing just right?

Restart it as soon "checking connection" appears.
It may take a few tries.

[TheBetaFan18329]

Then you will have to re-install it then.
As i said before, do the installation as before, but when you get to oobe, go to audit mode by doing CTRL+SHIFT+F3. Then create a user account by using lusrmgr.msc.
After you create your account, go back to oobe, do as normal until you reach "checking connection".
You MUST restart as soon as it says that, and you have to get the timing JUST right. If it takes you back to oobe, try again
If done correctly, you should have a working 10051 vm!

I made my user account and got back to the oobe but how can I get the timing just right?

Restart it as soon "checking connection" appears.
It may take a few tries.

Sometimes when I restart the VM, it says please wait on the boot screen and it goes into the recovery mode. Is this normal for it to do that?

[Windows Thunderstruck]

Then you will have to re-install it then.
As i said before, do the installation as before, but when you get to oobe, go to audit mode by doing CTRL+SHIFT+F3. Then create a user account by using lusrmgr.msc.
After you create your account, go back to oobe, do as normal until you reach "checking connection".
You MUST restart as soon as it says that, and you have to get the timing JUST right. If it takes you back to oobe, try again
If done correctly, you should have a working 10051 vm!

I made my user account and got back to the oobe but how can I get the timing just right?

Restart it as soon "checking connection" appears.
It may take a few tries.

Sometimes when I restart the VM, it says please wait on the boot screen and it goes into the recovery mode. Is this normal for it to do that?

If you restart three times in a row yeah.
What does it do now? Go back to oobe?

[TheBetaFan18329]

Then you will have to re-install it then.
As i said before, do the installation as before, but when you get to oobe, go to audit mode by doing CTRL+SHIFT+F3. Then create a user account by using lusrmgr.msc.
After you create your account, go back to oobe, do as normal until you reach "checking connection".
You MUST restart as soon as it says that, and you have to get the timing JUST right. If it takes you back to oobe, try again
If done correctly, you should have a working 10051 vm!

I made my user account and got back to the oobe but how can I get the timing just right?

Restart it as soon "checking connection" appears.
It may take a few tries.

Sometimes when I restart the VM, it says please wait on the boot screen and it goes into the recovery mode. Is this normal for it to do that?

If you restart three times in a row yeah.
What does it do now? Go back to oobe?

After I reset the vm when it is in the recovery mode, it goes back to the oobe.

[Windows Thunderstruck]

I think i ran out of solutions.
Either do 10049 (it is similar to 10051), but without the oobe bug.
Or, if you really want to do 10051, try the build's server version instead.
Either that, or use it in audit mode. (That's what i do for some of the v1703 enterprise builds) and create your account from there.

[Alphis]

i use vmware 12, i did that user trick and works fine here

[TheBetaFan18329]

I think i ran out of solutions.
Either do 10049 (it is similar to 10051), but without the oobe bug.
Or, if you really want to do 10051, try the build's server version instead.
Either that, or use it in audit mode. (That's what i do for some of the v1703 enterprise builds) and create your account from there.

I am using the build in audit mode and it is working fine! Thanks for the solution!