Share via

"Something went wrong ooberegion " when booting Windows 10 ISO via VirtualBox 5.22

Anonymous
2018-11-27T09:30:29+00:00

I have the latest version of virtual box installed on my laptop

HP Pavilion G6

8GB of Ram

windows 10 home 64bit

I am running the latest version of virtual box 5.22 to be precise, i have created a VM and allocated in 60GB of hard disk space and 2048MB of memory, i can also confirm i have installed the latest extension packs to support functionality of Virtual Box.

I downloaded the latest version of Windows from the official Microsoft Website and then proceeded to mount the ISO onto my newly created VM

When i start the VM the initial set up of windows goes fine, i can select my operating system and select the partition i would like the ISO installed on

once the initial set up completes i am prompted with a "just a moment spinning orb" eventually after around 15 minutes or so i am prompted with an error message

"Something went Wrong" 

OOBEREGION

you can skip or try again

i have tried to skip this process and try it again but it doesn't seem to work and i am now stuck in an endless cycle, i know this can work as i have already successfully mounted Windows Server 2016 onto separate virtual machine.

i noticed Microsoft uploaded a "workaround" for this type of fault

https://support.microsoft.com/en-gb/help/4020048/windows-oobe-fails-when-you-start-a-new-windows-based-computer-for-the 

but unfortunately this provides no fix and basically tells you to reboot your machine, i have contacted virtual box and it is not a fault with their software, 

can you please provide a fix on this issue or confirm if Virtual Box and Windows 10 even work together 

would i be right in thinking that Windows 10 does not work with VirtualBox's latest version?

PLEASE HELP

Windows for home | Windows 10 | Install and upgrade

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

21 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2019-04-06T20:46:33+00:00

    Thanks ДмитрийКабанов,

    This worked for me. Just to recap, this is what I did that worked for me:

    1. Shift+F10 to get command prompt when you see the error, and enter the following commands
      • net user administrator /active:yes
      • cd oobe
      • msoobe
    2. The machine reboots (or doesn't - I forgot to take a snapshot before wrecking my installation, and on the second attempt it didn't reboot at all)
    3. It gets stuck on a screen that says "just a moment" with a spinner going round.
    4. Reset the machine (Host+R)
    5. The machine boots (I got a "invalid username" when it started up on the second attempt) and the installation continues.

    Was this answer helpful?

    70+ people found this answer helpful.
    0 comments
  2. Anonymous
    2018-11-28T09:02:45+00:00

    Hi,

    Thank you for writing to Microsoft Community Forums.

    I would suggest you to try and reinstall the Windows 10 on the Virtual Box and check if you get the same error message.

    Please follow this article: Step-By-Step: Installing Windows 10 on Oracle Virtual Box

    If you still face issues during re-installation, press Shift + F10 key. This should open the command prompt.

    In the command prompt, copy-paste the following:

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

    For further help, please post your question inTechNet forum.

    Hope it helps.

    Rohit Raina

    Microsoft Community - Moderator

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments
  3. Anonymous
    2019-04-11T02:42:31+00:00

    I don't have virtualbox but this did it for my real computer

    The only thing is that host+r does nothing for me so I just held the power button down.

    Was this answer helpful?

    9 people found this answer helpful.
    0 comments
  4. Anonymous
    2019-04-18T18:46:44+00:00

    WOW This worked thanks edklinus

    Actually, the Russian person deserves the credit, that one came up with it, edklinus just translated it.

    Was this answer helpful?

    7 people found this answer helpful.
    0 comments