After install Windows10 show OOBE error message

Hi,

Thank you for writing to Microsoft Community Forums.

A normal reboot should reset the OOBE and you should be able to select the options. I would suggest you to select keyboard layout as US English for the first time and once the installation is complete, you can add other keyboard layouts. You can also follow the suggestions provided by Zoe Mo in this TechNet thread.  

Regards,

Hi,

I had same issue, according changed keyboard layout as US English or reset that was not workable at my side.

We try on hot key"Ctrl + Shift + F3" to skip OOBE, it could pass through in to OS, 

after that when you reset or shut down yours OS, In next setup the OOBE was still occurred.

Would you mind shared yours suggestion to us?

Hi Microsoft,

I got the same issue as Neil. 

When I met this issue, I installed Windows 10 1803 version for comparison, but there was no issue as same as this. 

And I also installed  Windows 10 1809 and 1903 on E3827 and E3845 system, but there were not this issue. 

It's very, very funny, this issue was only happening to E3815 CPU, I didn't know and could not figure out what the root cause about this issue. 

Could anybody can help me to fix this issue?

Hi Microsoft

We find some workaround for now , but we want to know that reason and what is the root cause to solve it?

Thank you

[Workaround - Install graphics driver]

[Method 1]

1. In OOBE , open command line windows (shift+F10)

2. Install graphics driver manually

3. Reboot 

4. Finnish OOBE setup 

[Method 2]

1. In OOBE ,  crtl+shift+F3 to skip oobe

2. Install graphics driver 

3. reboot

4. Finnish OOBE setup 

God Damn ,idiot microsoft 

I have same question.

I am a technology company from Russia.

Plz , hurry fix this **** problem !!!

Although this processor is really suck....

---

oh microsoft  auto  hide my word!!

i repeat again

hurry fix this FUCxING problem!!!!!!!!!!!

Hi Microsoft,

I used the workaround that Neil provided, it does work.

Did Microsoft anyone can pick up this issue and fix it in next version or a patch?

Besides, I strongly suggest Microsoft should release a document to solve this problem!!!