Announcing Windows 10 Insider Preview Build 15002 for PC Insider

Page 34 of 34 FirstFirst ... 24323334

  1. Posts : 19,511
    W11+W11 Developer Insider + Linux
       #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.
      My Computers


  2. Posts : 1,524
    Windows 10 Pro (32-bit) 16299.15
       #331

    kado897 said:
    Well it looks like I've got it working in VirtualBox. Removing all trace of 3D acceleration seems to have done the trick. Still stuck on 1024x768 but at least it's progress. Now to do an image. Hope MR is OK.
    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
    1. get stuck on the Restart (if I'd let Windows Update attempt the upgrade) or
    2. 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.

    Announcing Windows 10 Insider Preview Build 15002 for PC-vb_systemzoom_broken.png

    Announcing Windows 10 Insider Preview Build 15002 for PC-systemsettingsbefore.png

    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:

    Announcing Windows 10 Insider Preview Build 15002 for PC-systemsettingsafter.png

    Announcing Windows 10 Insider Preview Build 15002 for PC-vb_systemzoom_working_a.png
      My Computer


  3. Posts : 50,055
    Windows 10 Home 64bit 21H1 and insider builds
       #332

    DavidY said:
    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
    1. get stuck on the Restart (if I'd let Windows Update attempt the upgrade) or
    2. 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.

    Announcing Windows 10 Insider Preview Build 15002 for PC-vb_systemzoom_broken.png

    Announcing Windows 10 Insider Preview Build 15002 for PC-systemsettingsbefore.png

    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:

    Announcing Windows 10 Insider Preview Build 15002 for PC-systemsettingsafter.png

    Announcing Windows 10 Insider Preview Build 15002 for PC-vb_systemzoom_working_a.png
    Interesting. Both my Win 10 VM are set to Legacy, all others are set to Default. They were probably created before V5.
      My Computer


  4. Posts : 1,524
    Windows 10 Pro (32-bit) 16299.15
       #333

    kado897 said:
    Interesting. Both my Win 10 VM are set to Legacy, all others are set to Default. They were probably created before V5.
    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.
      My Computer


  5. Posts : 2,832
    Windows 10 Pro X64
       #334

    Hi,

    CountMike said:
    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.
    Same impression as I have. They didn't have much of a choice.

    Cheers,
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 21:05.
Find Us




Windows 10 Forums