Win10 build 1511

[Brian K]

My main computer has an SSD with BIBM and multiple primary partitions. The Win10 Boot Item has only one slot filled. Win10. Upgrading to ver 1511 caused the Win10 partition to be resized 450 MiB smaller with the creation of a Recovery partition in the space. There was no partition overlap.

My test computer has an SSD with BIBM and multiple primary partitions. The Win10 Boot Item has only one slot filled. Win10. Upgrading to ver 1511 didn't cause the Win10 partition to be resized 450 MiB smaller. Winre.wim remained in the Recovery folder in the Win10 partition.

Confusing.

[SaliesBuzz]

I think that this may be because the Recovery Environment was already present in the partition you were upgrading, hence my suggestion to check this before upgrading to 1511 using reagentc.exe /info from an elevated command prompt.
I agree that it is confusing. Do you have EMBR or GPT on your SSD?

[Brian K]

SaliesBuzz,

That's why it is confusing as both disks were EMBR disks, both Win10 partitions were the same size and both Win10 partitions contained a Recovery Environment.

[TeraByte Support(PP)]

Brian,

Does the partition that didn't get resized show enough shrink space available?

I assume it updated WinRE on the Windows partition.

[Brian K]

Paul, both partitions were 40 GB with 15 GB free space. Yes, Winre.wim (in the Win10 partition that wasn't resized) was updated.

[TeraByte Support(PP)]

I didn't just mean free space. Does Disk Management actually show that a shrink could take place? Just wondering if there was something blocking the resize and that's why it didn't do it.

[Brian K]

Paul, I get it now. IFW Information on the Win10 partition shows 28974 MiB Used, 11026 MiB Free and 40000 MiB to Restore.

Disk Management said I could shrink the partition by 6513 MB but the shrink failed with "There is not enough space available on the disk to complete this operation". I tried shrinking by 450 MB and this was successful. I tried shrinking by a further 5000 MB and this was successful.

Edit... I'll try again with compacting the Win10 partition to "30000 MiB to Restore" and then do the ver 1511 upgrade.

[Brian K]

This time Win10 was resized 450 MiB smaller and a Recovery partition was created. It looks like those sectors in use at the end of the partition were blocking the resizing. Strange, because Disk Management could do the resize.

[Brian K]

More tests. 40000 MiB partition. The data was Compacted to "39536 MiB to Restore" The ver 1511 upgrade caused a Win10 partition resize and produced a Recovery partition.

40000 MiB partition. The data was Compacted to "39695 MiB to Restore" The ver 1511 upgrade didn't cause a Win10 partition resize or produce a Recovery partition.

This suggests that any Sectors in Use in the final 450 MiB of the partition will prevent a resize.

[SaliesBuzz]

Great work and patience from Brian K.
As further info I have attached some screen grabs of the BCD Store on a computer that was recently upgraded to Win 10 1511.
This was originally a Win8.1 Pro system and before that Wndows 8 Enterprise. in all cases the upgrades have been carried out as an "in-place" upgrade.
[attachment=2]Windows Boot.JPG[/attachment]
Note the multiple entries for Windows Recovery Environment that are created.
The correct recovery entry is:
[attachment=1]01-Recovery.JPG[/attachment]
Only one of them is the correct one, as shown by the GUID file attached.
[attachment=0]01-Recovery-GUID.JPG[/attachment]
This may also help explain the bizarre behaviour of the Microsoft "Upgrade" process!