New
#330
Seems to me that 15002 is the "One that got away" since it was leaked some time before the official update so they decided to let it out and 1507 was real target.
Seems to me that 15002 is the "One that got away" since it was leaked some time before the official update so they decided to let it out and 1507 was real target.
I had slightly different problems with VirtualBox, when trying to run the 32-bit version.
Just in case it helps someone, here's my experience and how I fixed it.
Anything with build 15002 or 15007 would either
- get stuck on the Restart (if I'd let Windows Update attempt the upgrade) or
- would not even boot at all (in the case of booting from the ISO).
In both cases, it would get stuck on the 'blue Windows Flag' screen, where you'd expect circling dots to appear below the flag - but nothing would appear and it just hung there.
The fix for me in VirtualBox seemed to be in the System settings. This is how it looked when it was broken, which I think was the default settings which VB had created for Windows 10.
Then I went into the 'Acceleration' tab within System settings, and changed the Paravirtualization setting to 'Legacy'. After I made the change, it looked like this:
I got lucky in that I tried the 15002 ISO with an old VM which had been created a while ago- probably before V5 as you suggest. The ISO would boot with that old VM but not a new one.
So I went through changing settings on the new VM to match the old one until I found that change to Legacy which seemed to make the difference.