Page 63 of 98 FirstFirst ... 1353616263646573 ... LastLast
  1.    14 Jun 2017 #621
    Join Date : Nov 2013
    Chicagoland
    Posts : 33,778
    Dual boot Windows 10 FCU Pro x 64 & Insider 10 Pro

    Quote Originally Posted by martyfelker View Post
    FAILURE. INACCESSIBLE BOOT DEVICE. However it was a BLUE screen of death not a GREEN screen of death. Does that give you any information MS?
    I've been watching your progress, Marty. You get an A+ for the attempt.

    I'm sure MS knew within hours of the release that it was a disaster.
      My ComputersSystem Spec
  2.    14 Jun 2017 #622
    Join Date : Nov 2014
    Floyd, VA
    Posts : 1,122
    Triple Boot Windows 10 IP Build 17025/Windows Server 2016/Debian Sid

    Quote Originally Posted by HippsieGypsie View Post
    I've been watching your progress, Marty. You get an A+ for the attempt.

    I'm sure MS knew within hours of the release that it was a disaster.

    Well thanks. I always learn something after each failure. I now know (and will report to the Feedback Hub) that build 16215 simply cannot handle any kind of multiboot setup.
      My ComputersSystem Spec
  3.    14 Jun 2017 #623
    Join Date : Nov 2013
    Chicagoland
    Posts : 33,778
    Dual boot Windows 10 FCU Pro x 64 & Insider 10 Pro

    Quote Originally Posted by martyfelker View Post
    Well thanks. I always learn something after each failure. I now know (and will report to the Feedback Hub) that build 16215 simply cannot handle any kind of multiboot setup.
    As Wynona pointed out that it indeed can be installed on a dual boot configuration. I'm on my 16215 partition now. CU build 15063 is on the other. Quite sure others have been fortunate as well.

    Oh and using Edge.
      My ComputersSystem Spec
  4.    15 Jun 2017 #624
    Join Date : Nov 2014
    Floyd, VA
    Posts : 1,122
    Triple Boot Windows 10 IP Build 17025/Windows Server 2016/Debian Sid

    Dora:

    I can understand why you aren't providing us any explanations about 16215 but for crying out loud why can't you take it off the WU servers??
      My ComputersSystem Spec
  5.    15 Jun 2017 #625
    Join Date : Oct 2013
    A Finnish expat in Germany
    Posts : 12,958
    Windows 10 Pro

    One of the errors I got when trying to upgrade laptop from 16199 to 16215 was this:

    Click image for larger version. 

Name:	image.png 
Views:	82 
Size:	99.8 KB 
ID:	139555

    Error during INSTALL_RECOVERY_ENVIRONMENT.

    Inspecting this a bit more I think I now know what happened. If I am right there's no way the upgrade could have worked, whatever upgrade method or workarund was used.

    Some background.

    If you let Windows installation to do the partitioning on a GPT disk, the 450 MB WinRE partition is set first on disk, followed by 100 MB EFI partition and hidden (not shown in Disk Management) small 16 MB MSR partition. The OS partition is then next, volume (partition) 4:

    Click image for larger version. 

Name:	image.png 
Views:	82 
Size:	149.9 KB 
ID:	139556
    (Screenshot: default EFI partitioning.)

    The problem is, the WinRE partition will need more space when subsequently upgrading to new builds but as it cannot grow when first on disk, EFI partition blocking its every effort to expand, Windows Upgrade creates a new WinRE partition after partition 4, Windows OS partition.

    Being directly after C: partition is a good place for WinRE partition because it can something that no other partition can: it can extend backwards, shrinking Windows OS partition C: as needed to "steal" more space from it to cater its expansion needs.

    That's why I use a diskpart script on clean installs or autounattend.xml answer file on deployments to partition GPT disk differently placing EFI partition first (green in screenshot), followed by hidden MSR partition, OS partition (blue) and finally WinRE partition (yellow):

    Click image for larger version. 

Name:	image.png 
Views:	82 
Size:	33.4 KB 
ID:	139557

    When an upgrade then needs more space for WinRE partition, it takes the space needed from C: shrinking it:

    Click image for larger version. 

Name:	image.png 
Views:	82 
Size:	25.9 KB 
ID:	139558

    (Above two screenshots from a Hyper- V VM on which I upgraded from 14393 through 15063 to 16199 to get screenshots.)

    Build 16215 upgrade totally screwed that, ignoring the already existing WinRE partition and instead of extending it as it should have done created a new WinRE partition (red in screenshot) placing it between Windows OS partition and existing WinRE partition:

    Click image for larger version. 

Name:	image.png 
Views:	2 
Size:	80.6 KB 
ID:	139559
    (Screenshot from my laptop, what actually happened.)

    However, although upgrade created this new WinRE partition and installed recovery environment on it, it then tried to use the old WinRE partition, got confused and upgrade failed.

    I still need to study this but I believe this is what happened. Confusion about what WinRE partition to use.

    Kari
      My ComputerSystem Spec
  6.    15 Jun 2017 #626
    Join Date : Dec 2015
    Posts : 5,900
    Windows10

    Quote Originally Posted by Kari View Post
    One of the errors I got when trying to upgrade laptop from 16199 to 16215 was this:

    Click image for larger version. 

Name:	image.png 
Views:	82 
Size:	99.8 KB 
ID:	139555

    Error during INSTALL_RECOVERY_ENVIRONMENT.

    Inspecting this a bit more I think I now know what happened. If I am right there's no way the upgrade could have worked, whatever upgrade method or workarund was used.

    Some background.

    If you let Windows installation to do the partitioning on a GPT disk, the 450 MB WinRE partition is set first on disk, followed by 100 MB EFI partition and hidden (not shown in Disk Management) small 16 MB MSR partition. The OS partition is then next, volume (partition) 4:

    Click image for larger version. 

Name:	image.png 
Views:	82 
Size:	149.9 KB 
ID:	139556
    (Screenshot: default EFI partitioning.)

    The problem is, the WinRE partition will need more space when subsequently upgrading to new builds but as it cannot grow when first on disk, EFI partition blocking its every effort to expand, Windows Upgrade creates a new WinRE partition after partition 4, Windows OS partition.

    Being directly after C: partition is a good place for WinRE partition because it can something that no other partition can: it can extend backwards, shrinking Windows OS partition C: as needed to "steal" more space from it to cater its expansion needs.

    That's why I use a diskpart script on clean installs or autounattend.xml answer file on deployments to partition GPT disk differently placing EFI partition first (green in screenshot), followed by hidden MSR partition, OS partition (blue) and finally WinRE partition (yellow):

    Click image for larger version. 

Name:	image.png 
Views:	82 
Size:	33.4 KB 
ID:	139557

    When an upgrade then needs more space for WinRE partition, it takes the space needed from C: shrinking it:

    Click image for larger version. 

Name:	image.png 
Views:	82 
Size:	25.9 KB 
ID:	139558

    (Above two screenshots from a Hyper- V VM on which I upgraded from 14393 through 15063 to 16199 to get screenshots.)

    Build 16215 upgrade totally screwed that, ignoring the already existing WinRE partition and instead of extending it as it should have done created a new WinRE partition (red in screenshot) placing it between Windows OS partition and existing WinRE partition:

    Click image for larger version. 

Name:	image.png 
Views:	2 
Size:	80.6 KB 
ID:	139559
    (Screenshot from my laptop, what actually happened.)

    However, although upgrade created this new WinRE partition and installed recovery environment on it, it then tried to use the old WinRE partition, got confused and upgrade failed.

    I still need to study this but I believe this is what happened. Confusion about what WinRE partition to use.

    Kari
    What happens if you delete the winre partitions before upgrading?

    I usually delete them anyway as I simply use Macrium Reflect backups if I want to roll back, or use an ISO to refresh etc.
      My ComputerSystem Spec
  7.    15 Jun 2017 #627
    Join Date : Oct 2013
    A Finnish expat in Germany
    Posts : 12,958
    Windows 10 Pro

    Quote Originally Posted by cereberus View Post
    What happens if you delete the winre partitions before upgrading?

    I usually delete them anyway as I simply use Macrium Reflect backups if I want to roll back, or use an ISO to refresh etc.
    Have not tested yet and honestly, as I found out that I can't connect to Hyper-V virtual machines in 16215, will not test with this built. Takes too much time to test as I then would be forced to restore 16199 because I really need Hyper-V.
      My ComputerSystem Spec
  8.    15 Jun 2017 #628
    Join Date : Jul 2014
    Serbia
    Posts : 10,430
    W10 Insider + Linux

    Quote Originally Posted by HippsieGypsie View Post
    I've been watching your progress, Marty. You get an A+ for the attempt.

    I'm sure MS knew within hours of the release that it was a disaster.
    Is that better than E, for EFFORT ?
      My ComputersSystem Spec
  9.    15 Jun 2017 #629
    Join Date : Oct 2014
    Arnold, MD
    Posts : 28,967
    Triple boot - Win 10 Pro, Win 10 Pro Insider (2) - (and a sprinkling of VMs)

    Quote Originally Posted by martyfelker View Post
    Had to use Unlocker 1.92 to delete a leftover $Windows~BT directory. Went back to slow ring (when will there be a release to the SLOW ring??)
    @martyfelker

    Marty, you said you thought that no 16xxx builds had been released to SLOW ring, that is I believe technically correct. But, 16193 ISO has been available for a while thru MS (Official Source - no gypsies selling out the back of a wagon).

    Download Windows 10 Insider Preview Advanced

    Click image for larger version. 

Name:	2017-06-15_04h53_24.png 
Views:	1 
Size:	85.6 KB 
ID:	139574
      My ComputersSystem Spec
  10.    15 Jun 2017 #630
    Join Date : Aug 2015
    LAKELAND, FLORIDA
    Posts : 267
    WINDOWS 10 PRO INSIDER PREVIEW

    Quote Originally Posted by martyfelker View Post
    Well thanks. I always learn something after each failure. I now know (and will report to the Feedback Hub) that build 16215 simply cannot handle any kind of multiboot setup.
    On My Computer, I had 199 on drive "C" the SSD and I multibooted to drive "D" the WD 1TB HDD. I just loaded "Cloned" 199 to "D" then using DVD (.iso) of 215 I loaded it over the "Windows Partition" on "D". Worked perfect on "D" and I was able to Multi-boot between C and D,
      My ComputerSystem Spec

 
Page 63 of 98 FirstFirst ... 1353616263646573 ... LastLast


Similar Threads
Thread Forum
Insider Announcing Windows 10 Insider Preview Build 15063 for PC and Mobile
847575696255864833 847208261287682050 846876148277555200 844957996446724097 844006426661933057 Source: Announcing Windows 10 Insider Preview Build 15063 for PC and Mobile - Windows Experience Blog
Windows 10 News
Insider Announcing Windows 10 Insider Preview Build 14955 for Mobile and PC
790991162647547904 790962075874922496 Source: Announcing Windows 10 Insider Preview Build 14955 for Mobile and PC | Windows Experience Blog PC:
Windows 10 News
Insider Announcing Windows 10 Insider Preview Build 14366 & Mobile Build 14364
UPDATE: 742889757512867840 Source: Announcing Windows 10 Insider Preview Build 14366 Mobile Build 14364 | Windows Experience Blog
Windows 10 News
Insider Announcing Windows 10 Insider Preview Build 14361 for PC and Mobile
740589771232137220 Source: Announcing Windows 10 Insider Preview Build 14361 | Windows Experience Blog PC:
Windows 10 News
Mobile Announcing Windows 10 Mobile Insider Preview Build 10586.63
685579851160408064 Windows 10 Mobile Build 10586.63 - The latest update is similar to cumulative updates and does not bring any new features. However, the update is expected to bring some bug fixes, as well as some under the hood changes. ...
Windows 10 News
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 06:57.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums