@Windows user: the problem only happens with Build 9901. With other builds it installs in a few minutes. Maybe this is a build bug?
Hmm..maybe it's a hardware specific bug in this build? What are the settings that you used when creating the VM?
I used Hyper-V instead of Vmware because the problem is the same. Anyway, I'm on Windows 9879 host. I assigned only one core to the cpu, 80 GB of HDD (a traditional one), 3GB of RAM and I selected the 2nd generation of Hyper-V with Efi support.
It should work with that configuration, maybe it's a bug that is preventing installation ...it installed fine in VMWare on my PC...I used VMWare Player, try to install it in that & don't forget to do the efi trick in the settings
@Windows user: This happens on VirtualBox, Vmware and Hyper-V. It always stuck on Getting Ready. So, Maybe, is a problem of Win10 build 9879. What host system do you use?
Probably that's the problem, 9879 isn't a good build at all...9860 was pretty stable...try installing Windows 8.1 & then trying 9901 on VM or alternatively you can just install it directly on your PC since, Ms doesn't really care about leaks...it's safe to install & use it like any other tech preview build. Only problem is that you would have to reinstall Windows from ISO when the Consumer preview is released.
@Windows user: No, at this point, I prefer to stay on Build 9879 and wait for another month in order to get the next official build. I wanted to install this 9901 build to test the programs that I use currently on build 9879 to see if there were problems after the changing to kernel 10.0
Just wait for a few weeks then ,maybe the programs/drivers you use will also get updated for the new kernel. This build isn't really representing the consumer preview anyways...it just has a few features from it & most probably the programs you use won't be affected by the 10.0 kernel..as programs which aren't updated for Windows 10 are supposed to see the kernel as 6.3 (Windows 8.1) hence, ensuring compatibility.
I had this problem with the last 2 official builds when installed in Hyper-V. If found out that sppsvc consumed 100% CPU in the background and killing it made the installation proceed instantly. Press Shift+F10 to open Command Prompt, then you can use powershell and get-process | select Name,CPU to list CPU time of all running processes, and net stop sppsvc to stop the service when necessary.
I doubt it takes that long. However, from the moment I booted to the USB (Kingston 8GB HyperX USB 2.0), to the moment I was at the Windows 10 9901 desktop was approximately 10 minutes on the dot (which was ironic). I did not create a new machine and instead just chose one of the ones I already had in my microsoft account. So, yeah 1.5 hours seems wrong to me, especially when I'm on a 6 year old x58 platform. I installed to a RAID0 array though comprised of Samsung 840 Pro's, but everyone says RAID0 does not speed up anything, so that can't be it, lol.
Windows 10 January Technical Preview en-us zn-cn pt-br en-gb ja-jp ru-ru de-de fr-fr ko-kr it-it es-es zh-tw sv-se fi-fi tr-tr ar-sa nl-nl cs-cz pl-pl th-th