New Build (#1709) adding 500MB system volume?

[BonzaiDuck]

This question affects my Macrium Reflect Backup Definition file, which I have now changed.

My system is dual-boot, Win7/Win10. Win 7 had always had only the "system reserved" 100MB volume.

When I first created my backup definition in Macrium, I had designated all the volumes on the system-boot disk which contains both OSes and boot system volumes for those OSes.

At the time I created the definition, there had only been the UEFI 300MB FAT32 volume and an additional 500MB volume/stub for Windows 10 in addition to the sys-reserved (100MB), Win 7 system volume and Win 10 system volume (C: drive when booting into Win 10). So "disk 2" was included in the backup definition with 100MB "system reserved," 120GB Win 7 volume, UEFI 300MB for Win 10, Win 10 volume, and 500MB additional stub for Win 10.

I now discover there is a second "stub" volume of 500MB for Windows 10.

Let me summarize again the current volumes on the 960 Pro "disk 2:"

100MB system reserved
120GB Win 7 boot-system volume
300MB UEFI
700GB Win 10 boot-system volume
500MB stub
500MB stub

So again -- the last and final 500MB stub did not exist when I created the backup definition file.

Did this second 500MB stub get created with the #1709 update? I have to add it to my backup definition.

 

[RLGL]

i am on build 17128, I have a:
500 MB NTFS
626 MB for boot system
1.99 GB recovery partition
69 MB allocated
The last fresh install I did was more than one year ago, I am going to wait until the ISO is released for the Spring Update and start fresh again.

 

[BonzaiDuck]

I was of course referring to the Fall Creators update. Apparently "1709" refers to the "version," and the build number for my system is 16299.309.

I had originally created the dual-boot system (Win7/Win10) on an SATA SSD -- a 500GB ADATA. I then had to clone it to my NVME 960 Pro. I had been through thick and thin early last year raising it to perfection. I'm averse to fresh installs unless something cataclysmic requires it.

I'd held off adding the Fall Creators Update until last month. I'd set the system to delay it for up to one year, but it seemed to have taken off on its own, and to my surprise -- installed without borking the dual-boot configuration. That was a hurdle I had to surmount with the 1703 version, so I was wary about the fall update.

I wish I knew why your disk volumes are different than mine. I'm just glad I caught the change and added it to my Macrium backup definition file.

 

[RLGL]

I am in the preview program Redstone 4. There are some releases to Redstone 5 out, when the spring update is released I will be able to see the next version previews The spring release is close, maybe two or three weeks.

 

[Ketchup]

I really don't know what either of your "stubs are for BD, so I am wondering if it's something Macrium did. In all fairness, for my desktop which is referenced in the pic above, I have had quite a few "issues" with these major releases. The most recent one caused all USB devices to stop working upon boot (an Asus software compatibility issue), so a fresh install was done just this past October with the latest release.

 

[BonzaiDuck]

I really don't know what either of your "stubs are for BD, so I am wondering if it's something Macrium did. In all fairness, for my desktop which is referenced in the pic above, I have had quite a few "issues" with these major releases. The most recent one caused all USB devices to stop working upon boot (an Asus software compatibility issue), so a fresh install was done just this past October with the latest release.

I just opened up Computer Management -> Disk Management and took a closer look. My two 500MB "stubs" are "Recovery Partitions." But -- I'm pretty sure -- there was only one of them before Creators Update #1703. I can't be sure if the second of these was added before or after #1709. But I had set up Macrium Backup to image only the first of them when the second one didn't exist. I'm actually thinking that the incomplete image of the disk would probably restore properly, or that Windows would decide what to do . . OR -- Macrium's recovery disk would fix it. No problem now, though. Just too many details to manage in my day-to-day computer maintenance schedule.

 

[RLGL]

As soon as I can grab a ISO for the next release, I will do a fresh install. Interesting to see the results in disk manager. Prior to the install the SSD will be wiped.