Win8 will not install: 0xE0000100

[Kamiel Kontrarie]

Title says it all: on a newly created virtual machine, with a newly created virtual disk, I cannot get Win8 to install; few seconds after the "Setup is starting" appears, I get the Error code 0xE0000100.

Web searching taught me this points to issues with the storage, often a pre-existing partition table. However, on my newly created VDI the partition table was empty. I even went so far as to create a single partition in it, then format that one, using DISKPART inside Windows. It all made no difference.

The disk image is created with
IMAGE=/vdi/win8.vdi
vboxmanage createhd --filename $IMAGE --size 262144
chmod 777 $IMAGE (probably too permissive, just to make sure)

It is then included with the new VM with
vboxmanage storagectl Win8 --name "IDE Controller" --add ide
vboxmanage storageattach Win8 --storagectl "IDE Controller" --port 0 --device 0 --type hdd --medium $IMAGE

[socratis]

In order to better understand the problem you need to submit some more information. Please read the following: Minimum information needed for assistance. As far as the "VBox.log.zip" goes, here's what you do:

1. Start the VM. Not from a saved or suspended state. Clean start.
2. Take the steps required to generate/observe the error.
3. Shut down the VM (if it hasn't aborted by itself). Not suspended, not paused. Shut down. If you can't shut it down by normal means, close the VM window and select "Power off".
4. Right-click on the VM in the VirtualBox Manager.
5. Select "Show Log..."
6. Save it (just the first log, VBox.log), ZIP it and attach it in your response (see the "Upload attachment" at the bottom of the form).

On top of that, we'd like to see the "recipe" of the VM, the ".vbox" file:

1. Right-click on the VM in the VirtualBox Manager.
2. Select "Show in Finder/Explorer/Whatever".
3. ZIP the selected ".vbox" file and attach it in your response.

[Kamiel Kontrarie]

Dear, thanks for quick reaction. I have created the requested zips, both the .vbox and the log. Please find them attached. Of course I will be glad to provide any further info you migtht require.

[mpack]

You are using an Ubuntu fork of VirtualBox, you are not using VirtualBox. You need to install VirtualBox (the real thing), or go to the Ubuntu forums for support.

[Kamiel Kontrarie]

OK, so I removed the existing package, download and installed the "real thing", 5.0.24, ran the same script again, to the same result.
New gzip log + config attached.

[socratis]

The default RAM allocation for a "Windows 8.1 - 64 bit" is 2048 MB. You changed that and set it to 512 MB. You have 14742 MB available at the time that you started the VM, so you can definitely afford 2048. Can you please change that and see if it helps?

[Kamiel Kontrarie]

Yes that seems to do the trick, installation is progressing now. Actually I set the memory to 4GB, as you observed there is no lack

Thanks very much!

Still you'll excuse my wondering why this issue could not be detected with the first configuration...

[Perryg]

Still you'll excuse my wondering why this issue could not be detected with the first configuration...

It probably could have been but other issues could have also caused this issue that could not have been detected due to it being a fork. We do not use the Ubuntu fork here and have no idea what they change.

[socratis]

Still you'll excuse my wondering why this issue could not be detected with the first configuration...

Because usually we stop reading after we see that a fork is being used. And it is the first line in the log after all
Glad you're proceeding.