View original (French)

OOBEREGION, OOBKEYBOARD error Windows 10 in virtualization

Solved
guillaumegilbertsoucy Posted messages 369 Status Member -  
guillaumegilbertsoucy Posted messages 369 Status Member -
Hello,

I need to deploy a virtual machine with Windows 10 Pro x64, but the installation gives me several error messages.

Here are some screenshots to provide context and help you understand:

After selecting my region:



It loads and gives the following error:

OOBEREGION



If I click on “Try Again,” the same error occurs. If I click on “Skip,” it gives another error that is:

OOBEKEYBOARD



It continues to show errors until it arrives at this page where it is impossible to skip the error:



Here are the details regarding the host:

Host: Ubuntu Server 22.04 LTS
Virtualization: libvirt/QEMU

Regarding the VM configuration now: I’ve put the link because it’s very long.

http://pastebin.zsites.ca/view/4f6f47ca

The Windows 10 image file was retrieved from the Microsoft website.

I have also done research, but what I find does not resolve my problem. Here’s an example:

https://support.microsoft.com/en-us/topic/windows-based-computer-hangs-during-oobe-setup-tasks-c4ed5186-9266-de16-24a5-9bd1818b9df5

If any details have escaped me, please let me know and I will add them.

Thank you in advance for your help.

Guillaume

8 answers

  1.
    fabul Posted messages 42153 Registration date   Status Moderator Last intervention   6 066
     
    Hi,

    How much RAM have you allocated?
    0
  2. guillaumegilbertsoucy Posted messages 369 Status Member 8
     
    I initially allocated 1GB but I am currently trying with 2GB.
    0
  3. fabul Posted messages 42153 Registration date   Status Moderator Last intervention   6 066
     
    Put 4GB for 64 bit if you can (4096 MB)

    3328 MB for 32 bit
    0
    1. guillaumegilbertsoucy Posted messages 369 Status Member 8
       
      Okay, I'm trying this!
      0
  4. guillaumegilbertsoucy Posted messages 369 Status Member 8
     
    Hi,

    Unfortunately, the problem persists, even with 4GB of RAM.





    Guillaume
    0
    1. brucine Posted messages 24865 Registration date   Status Member Last intervention   4 172
       
      Hello,

      Solutions are proposed here, correction of a registry error (but hey, since the host isn't Windows...) or (solution 3) bypassing the regional installation settings that will then have to be entered manually:

      https://www.thewindowsclub.com/fix-oobekeyboard-oobelocal-ooberegion-errors-on-windows-11-10

      In case of failure, a more convoluted similar solution is described here:

      https://blogternet.com/virtualbox-windows-10-oobe-errors-ooberegion-oobezdp-oobekeyboard-fix/

      It is also mentioned that there may be an Internet issue during the operation, so it is suggested to disconnect the Internet for the installation.
      1
  6. guillaumegilbertsoucy Posted messages 369 Status Member 8
     
    Good morning,

    The solution proposed in this link https://blogternet.com/virtualbox-windows-10-oobe-errors-ooberegion-oobezdp-oobekeyboard-fix/ allowed me to skip OOBE, but after entering the requested information, Windows gives this error:



    Once the update is done, Windows restarts and asks me for the same information again (Language, location, keyboard, time zone). After entering this information again, it gives the same error again suggesting to update once more.

    Guillaume
    0
    1. brucine Posted messages 24865 Registration date   Status Member Last intervention   4 172
       
      I don't know.

      Could it be that the host's system settings are in a different region/language by any chance?
      0
    2. guillaumegilbertsoucy Posted messages 369 Status Member 8 > brucine Posted messages 24865 Registration date   Status Member Last intervention  
       
      However, no.

      Do you know if the problem could come from the fact that the VM's CPU has only 1 core?
      0
    3. brucine Posted messages 24865 Registration date   Status Member Last intervention   4 172 > guillaumegilbertsoucy Posted messages 369 Status Member
       
      Formally no, but I don't think so; if the material capacity was insufficient for the virtual machine, it would have refused to install, the same goes for Windows 10 which is not in principle concerned: the major risk is a slowdown in execution.

      While we're at it, I don't know why you say to go through QEMU when your screenshot shows Windows Sandbox: in this latter case, we might indeed have a problem since it only supports at minimum Windows 10 Pro with a 2-core processor, but I don’t understand: to use Windows Sandbox, does Windows 10 have to be installed first and then launched from there?

      There might also be a QEMU configuration issue; I don’t understand anything about it; the only way to be sure is to try virtualizing something else (another Linux distro, Windows 7 or XP...) or to attempt to virtualize through another means in a more graphical way, for example using VirtualBox.
      0
    4. guillaumegilbertsoucy Posted messages 369 Status Member 8 > brucine Posted messages 24865 Registration date   Status Member Last intervention  
       
      Windows 7 x64 and Windows XP are working normally.

      "Sandbox" is the name I gave to the Linux host that runs the Windows machines.
      0
    5. brucine Posted messages 24865 Registration date   Status Member Last intervention   4 172 > guillaumegilbertsoucy Posted messages 369 Status Member
       
      My bad; as for the rest, apart from a possible QEMU configuration issue, I don't know.

      It may also be that the Windows 10 image is defective as it stands or poorly deployed if it has gone through a custom installation file; this type of problem is more commonly documented with older versions of Windows 10 (particularly 1903/19H1), in any case we can try again with an up-to-date version if that's the case or download a new ISO if it is presumed defective.

      It also seems to me that the OOBE process requires an active internet connection, which is also a point to check.
      0
  7. guillaumegilbertsoucy Posted messages 369 Status Member 8
     
    The same problem persists. Maybe there's a timeout happening silently since the system only has 1 core and it's extremely slow because of that.

    I will soon receive about ten machines as a donation equipped with i5 processors with 4 cores, so I will install Ubuntu with QEMU and create just one VM and allocate 2 or 4 of the cores to it and try to launch the installation of Windows 10 again.

    If it still doesn't work, I will run the installation of Windows 10 directly on the physical machine, to see if the .iso image might be the issue.

    I will keep you updated.

    Guillaume
    0
    1. brucine Posted messages 24865 Registration date   Status Member Last intervention   4 172
       
      OK, Wait and See, that way we won't die idiots...
      0
  8. guillaumegilbertsoucy Posted messages 369 Status Member 8
     
    Hello,

    Just a quick update.

    I still haven't received the machines. It should be next week. ;-)

    Guillaume
    0
    1. guillaumegilbertsoucy Posted messages 369 Status Member 8
       
      Yes in the other one... sorry.
      0
  9. guillaumegilbertsoucy Posted messages 369 Status Member 8
     
    Hello,

    I managed to get the Windows 10 VM working. I followed the instructions from here: https://blogternet.com/virtualbox-windows-10-oobe-errors-ooberegion-oobezdp-oobekeyboard-fix/

    "ACTUAL STEPS
    Click Shift + F10 to access CMD.
    ???? CMD commands.

    1° net user administrator /active:yes

    2° net user /add test 4321

    3° net localgroup administrators test /add

    4° cd %windir%\system32\oobe

    5° msoobe.exe

    Congratulations you installed Windows on your virtual machine."

    After a few reboots and curses, it finally worked.

    Thank you for your help.

    Guillaume
    0
    1. brucine Posted messages 24865 Registration date   Status Member Last intervention   4 172
       
      Hello,

      You're welcome, I didn't do anything effective.
      0
      1. guillaumegilbertsoucy Posted messages 369 Status Member 8 > brucine Posted messages 24865 Registration date   Status Member Last intervention  
         
        But you pointed me to the website that helped me solve the problem. ;-)

        I had forgotten to post my screenshot from this morning:



        And here it is!
        0