Windows 10 keeps preparing...

[EYES-T]

Hi,

I'm trying to install Windows 10 and all goes well during installation until it says "prepairing" ("voorbereiden" in dutch) and it keeps on the screen for hours, nothing happens.

Anyone who knows what's going wrong?

Thanks in advance for any reaction!

[hannibalstgt]

Hello,

I am just experiencing the same thing,
The network seems to be active and the preparing circle is spinning -
now for much more than an hour.

Regards
Wolfgang

[loukingjr]

In the VB storage settings for the IDE controller, try toggling the "Type", PIIX3 or PIIX4. Mine's set to PIIX4.

[hannibalstgt]

........... Mine's set to PIIX4.

Mine is also set to PIIX4

The .VDI file very very slowly grows.
Is that a good sign ?

Regards
Wolfgang

[loukingjr]

well, as I said, you could try switching to PIIX3. make sure the Host I/O cache is enabled. I never paid attention to the .vdi file growth but it shouldn't take anything remotely like an hour to install. I think mine took 10-15 minutes.

[Ed1975]

I think mine took 10-15 minutes.

^ this

[loukingjr]

I think mine took 10-15 minutes.

^ this

Ed, what does "^ this" mean???

[mhanor]

Either try the latest test build, or increase the VM CPU number to 2 (if your CPU has more than two cores). Also enable PAE/NX, in the VM settings.

[loukingjr]

unless the OP is installing the W10 32bit version there is no reason to enable PAE/NX. It should run with 1 core I imagine.

[Ed1975]

I think mine took 10-15 minutes.

^ this

Ed, what does "^ this" mean???

It means I am quoting the above post for truth.

You haven't been on gaming forums much, have you?

[loukingjr]

never, not once.

[hannibalstgt]

Hello,

after more than 3 hours the preparation finnally came to an end and the installation continued.

Problem:

Maybe PIIX4 and Host I/O cache disabled.

Regards
Wolfgang

[loukingjr]

Three hours is a long time. Was this a clean install or an upgraded previous Windows install? If it was a previous install and there wasn't much room on the .vdi it could have spent all that time moving files around.

It should have worked with PIIX4 and Host I/O enabled. As a matter of fact I believe Host I/O Cache is enabled by default for the IDE controller for any guest, most guests anyway.

[hannibalstgt]

Three hours is a long time. Was this a clean install or an upgraded previous Windows install? If it was a previous install and there wasn't much room on the .vdi it could have spent all that time moving files around.

It should have worked with PIIX4 and Host I/O enabled. As a matter of fact I believe Host I/O Cache is enabled by default for the IDE controller for any guest, most guests anyway.

Hello,

it was a clean install. The parameters probably had been not very well selected.
I used only 2 GB of RAM and the .vdi file (64 GB) was set for dynamic allocation.
For the IDE controller was PIIX4 set but the Host I/O Cache was individually disabled.
This was probably the biggest obstacle.

But now Windows10 64 Bit 9926 works really fine on VirtualBox 4.3.20

Regards
Wolfgang

[loukingjr]

Yes, having the HOST i/O cache disabled was not good. Glad it's working for you though.