W10 1809 (x64,2nd update) can't pass OOBE Setup

[TeutonJon78]

VB: 5.2.22
Win10: 1809 2nd Update ISO, x64

Has anyone gotten W10 1809 to install normally in a VM? Every time I try it fails in some part of the OOBE preventing every getting to desktop. It just keeps looping back to the start of that part of setup. There are no problems copying the files.

I downloaded 1803 x64 to test it and it installs completely and cleanly, so it's something wrong with the interaction between VB 5.2.22 and 1809.

[socratis]

Have you searched for that error condition? Because it's not just VirtualBox, it happens in physical computers as well. A quick search for "Windows OOBE fails" returns as a first result a Microsoft article: Windows OOBE fails when you start a new Windows-based computer for the first time. There are many more articles that address that issue, see if anything can help you...

[TeutonJon78]

I have searched for it -- and tried the solutions over the past 2 days. It still won't get past the setup. I've run through it multiple times (like probably 20+ over 5+ attempts to install it), I've rebooted, and I've run the following command which is supposed to almost always getting it working:

Code: Select all

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

1803 works well. 1809 can't get past it -- and it fails at lots of different steps.

[socratis]

We need to see a complete VBox.log, from a complete VM run:

• Start the VM from cold-boot (not from a paused or saved state) / Observe error / Shutdown the VM (force close it if you have to).
• With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
• Save only the first "VBox.log", ZIP it and attach it to your response. See the "Upload attachment" tab below the reply form.

[TeutonJon78]

I have attached a log which shows 2 failures of the OOBE. The VM was ACPI shutdown directly after the second error.

I was able to get it complete just one try through OOBE, and that was by shutting down the VB instance and then cold booting back into it. I'm currently trying that again after these two failures.

[socratis]

00:00:04.908223 GUI: 2D video acceleration is disabled

And so is the 3D acceleration. Shutdown the VM and enable them in the VM settings » Display. You'll also notice that the max VRAM will jump from a max value of 128 to 256 MB after that; max the VRAM as well.

00:00:02.878642 VRDE: Warning: failed to launch VRDE server (VERR_NET_ADDRESS_IN_USE):
    VirtualBox Remote Desktop Extension server can't bind to the port(s): 3389

And since you're in the Display settings, disable the Remote Desktop Server. Its address is already occupied, most probably by your host's RDP server.

00:00:02.777257 Host RAM: 4094MB (3.9GB) total, 1961MB available
00:00:03.100401 RamSize <integer> = 0x0000000060000000 (1 610 612 736, 1 536 MB)

1536 MB for a Win10-64 is not that much, you're going to suffer. On the other hand, you can't afford too much more than that, you don't have enough available RAM in your host. Just FYI...

00:00:03.100614 [/Devices/efi/0/] (level 3)
...
00:00:03.100672 ICH9 <integer> = 0x0000000000000001 (1)

Why on earth would you choose a chipset that's clearly labelled as experimental and only for OSX guests? I honestly would like an answer on this. Change the chipset from ICH9 to the default PIIX3. And don't change the defaults as suggested by the template if you don't have a good reason.

Same goes for EFI, although this is supported for a Win10 guest. However there's not a single good reason why you'd like it enabled, so please disable it in your VM Settings.

[TeutonJon78]

I don't see why the need for the condescending tone.

00:00:04.908223 GUI: 2D video acceleration is disabled

And so is the 3D acceleration. Shutdown the VM and enable them in the VM settings » Display. You'll also notice that the max VRAM will jump from a max value of 128 to 256 MB after that; max the VRAM as well.

Those are the default settings, which you seem so set in requiring. Neither would play into OOBE failures.

00:00:02.878642 VRDE: Warning: failed to launch VRDE server (VERR_NET_ADDRESS_IN_USE):
    VirtualBox Remote Desktop Extension server can't bind to the port(s): 3389

And since you're in the Display settings, disable the Remote Desktop Server. Its address is already occupied, most probably by your host's RDP server.

If that is Host related rather than guest, then the GUI definitely doesn't make that clear. Either way, the required extension to make it work isn't installed, so I'm not sure that would have effect.

00:00:02.777257 Host RAM: 4094MB (3.9GB) total, 1961MB available
00:00:03.100401 RamSize <integer> = 0x0000000060000000 (1 610 612 736, 1 536 MB)

1536 MB for a Win10-64 is not that much, you're going to suffer. On the other hand, you can't afford too much more than that, you don't have enough available RAM in your host. Just FYI...

I usually give it 2 GiB, which still suffers either way. I dropped this one because I need the extra RAM to keep my browser open at the same time. But I'm not going for performance, I'm going for testing.

00:00:03.100614 [/Devices/efi/0/] (level 3)
...
00:00:03.100672 ICH9 <integer> = 0x0000000000000001 (1)

Why on earth would you choose a chipset that's clearly labelled as experimental and only for OSX guests? I honestly would like an answer on this. Change the chipset from ICH9 to the default PIIX3. And don't change the defaults as suggested by the template if you don't have a good reason.

Well, I changed this because my hardware is actually ICH10, and when I'm testing out an OS, I want to test it on as close of hardware as possible. No where in the GUI does it mention ICH9 is experimental. ICH9 is from 2007. According to the online manual, where it does say ICH9 is still experimental and introduced in VB 4.0 -- which released 2010-12-22. If VB can't manage to stabilize that in 8 years, I don't know why they still include it. And manual does NOT state it's only for OS X-- it says it's for modern systems like OS X (which isn't even the name anymore). I don't know what systems still support PIIX3 well, but they are all going to have support for ICH9 still. But I will test it with PIIX3.

However, I don't understand why you're advocating to keep only default settings here when you're saying to change the defaults above.

Same goes for EFI, although this is supported for a Win10 guest. However there's not a single good reason why you'd like it enabled, so please disable it in your VM Settings.

There are plenty of good reason to enable it -- mostly that every new machine sold in the last several years has it enabled by default. If someone is trying to emulate how such a system installs, which is exactly what I'm doing, EFI needs to be enabled to test that. Again, once past boot, that choice shouldn't matter. It should have no effect on the OOBE failing consistently.

The issue is that OOBE can run on all previous versions of Windows relatively fine, but fails miserably in 1809 with the EXACT same VM setup I've used in the past. I know the performance will be suboptimal, but it's been that way anyway, esp. since MS force enabled the Spectre/Meltdown patches.

Edit 1: Removing RDP and setting chipset to PIIX3 had no effect. Testing video acceleration and 256 VRAM.

Edit 2: Enabling 2d/3d acceleration had no effect either. Still breaks OOBE repeatedly.

Edit 3: I tested it on a more modern PC (i7700K, 16 GiB RAM) giving the VM 4 GiB of RAM, and the setup worked correctly. So it seems something is getting messed up with the timings running on old hardware. It's still interesting that other versions worked correctly historically up through 1803, but 1809 just won't work on the older hardware.

[BillG]

That is most likely correct. In fact the Microsoft article referenced about specifically states that it is a timing problem.

[socratis]

where it does say ICH9 is still experimental

Hover over the control. Read the tooltip...

[TLhM]

VB: 5.2.22
Win10: 1809 2nd Update ISO, x64

Has anyone gotten W10 1809 to install normally in a VM? Every time I try it fails in some part of the OOBE preventing every getting to desktop. It just keeps looping back to the start of that part of setup. There are no problems copying the files.

I downloaded 1803 x64 to test it and it installs completely and cleanly, so it's something wrong with the interaction between VB 5.2.22 and 1809.

I had the same issue and after several attemps, both with different versions of VB and different ISO files of Windows 10 1809, the solution that worked
in my case was to modify two settings of the VM:
increase the number of processor to 2
enable PAE/NX (in the same settings page)

After these changes I got a VM perfectly working (both for 32 bit and 64 bit versions)

Hope these can help

[ajp]

When trying to deploy Windows 10 Enterprise (x64) (1809 build) within Oracle VirtualBox (5.2.22 and 6.0.0) using Microsoft Deployment Toolkit, the installation stops after the restart of Windows 10 before it enters the OOBE phase with the error message "Windows could not complete the installation. To install Windows on this computer, restart the installation". If you click OK to the error message, the client guest restarts and the task sequence continues as expected.

"Windows could not complete the installation" Error

VirtualBox_Windows Client 1_28_12_2018_11_31_47.png (9.26 KiB) Viewed 6475 times

This error only occurs with the x64 edition of Windows 10 (1809); the x86 edition works fine as does earlier builds of Windows 10 x64 (1803). There is nothing wrong with the task sequence being used within Microsoft Deployment Toolkit (standard Microsoft out-of-the-box client task sequence) and if you deploy the Windows 10 (x64) operating system to a physical client using the same method (and task sequence) it works fine. Therefore it seems something specific to deploying Windows 10 x64 (1809) in VirtualBox.

Has anyone else seen this issue and does anyone have any suggested fixes?

[socratis]

Has anyone else seen this issue and does anyone have any suggested fixes?

Yes, and no suggested fix, because we can't find a common denominator. I'm merging your post with an existing one on the same topic, in "Windows Guests", where it belongs.

[ajp]

I have resolved the issue I was having by increasing the RAM of the virtual machine from 2GB to 4GB (3GB was not enough).

[MiloTheDev]

Hi,

I was recently installing Windows 10 Pro (unactivated) as a guset os, Finally, I got to the OOBE setup, And my result was, Well. A bunch of errors.
Such as: OOBEREGION, OOBEKEYBOARD, and OOBEZTP.
At last, The vm was Aborted. Then i gave up.

Any help would be apreciated.

VM (and host) Statistics:

Controllers and whats inside them: The same old stuff the template gives you.
ISO File's Website: Officail Microsoft
Host OS: Windows 10 Home
Host Model: Lenovo Ideapad 2in1 14
Host Archetecture: x64 (64bit)
Host Disc Capacity: 241 GB
Host Disc Free Space: 5.82 GB (w/ 20 GB VHD) <-------[im really working on cleaning dat drive)
Guest OS: Windows 10 Pro (duh)
Guest Model: VirtualBox VM (duh)
Guest Arcetecture: x86 (32bit)
Guest Disc Capacity: 20 GB (duh)
Guest Disc Free Space: to be honest i have no idea
Guest Base Memory: 1980 MB
Guest Status: The same old status the template gives you.


Bye! (for the same reason as always.)

[MiloTheDev]

Dude, I have the same problem..