Weird situation after upgrading to Win 10 ?

[swayzak]

Hello

I have just checked the partitions a fair while after upgrading to Windows 10 (from Win 7) - have also just updated to Creators version.

There appear to be some duplicate MBR entries (see attached).

What does this mean ? Can it be corrected easily if necessary ?

Thanks

[swayzak]

Anyone ?

[TeraByte Support]

nothing attached but you'd just follow the normal advice of checking which
partitions belong of the over lapped items and deleting the one that doesn't
(don't use any clear options). You can use "edit file" to look around to
ensure it's a good file system (partition) or resize then cancel it to
check, if one of the two over lapping items (marked with an "E") is good and
the other has problems, delete the one with problems.


"swayzak" wrote in message news:13954@public.bootitbm...

Hello

I have just checked the partitions a fair while after upgrading to Windows
10 (from Win 7) - have also just updated to Creators version.

There appear to be some duplicate MBR entries (see attached).

What does this mean ? Can it be corrected easily if necessary ?

Thanks

[swayzak]

Thanks

Can you not see the screenshot I attached eg. all those 450mb Windows RE MBR partitions (listed after each main OS partition) ?

[Brian K]

swayzak,

I can see your screenshot.

From an admin command (in each OS) prompt run...

reagentc /info

This will tell you which is the Recovery partition in use for that particular OS. Delete the others (without Clear Boot Sector).

[swayzak]

Thanks

Are these Win RE partitions a new thing ? I don't recall seeing them with earlier versions of Windows ?

[TeraByte Support(PP)]

They've been around for quite a while now. Basically, when Windows is installed or a major update is performed it will often resize the Windows partition smaller and create a new WinRE partition. It can do this even when the existing partition is large enough for the new WinRE version. I've also seen cases where it creates the space and doesn't create the partition. If you don't want this to happen you can fill the partition table when updating Windows so there's no room for another partition.

[swayzak]

Thanks

OK, so I can just leave them alone if I choose as well ? And they don't affect the EMBR of BIBM ?

[mjnelson99]

I tried to do an automatic update of the latest Win 10 version. It
failed. I suspect it was the 450 mb (or MB?) partition it did not like.

I created an image of the then version of Windows 10, then wiped the
drive of all Win stuff. It did maintain the 4 partitions, they were just
empty.

I already had a downloaded version of the Single Language Win 10. It
installed, no sweat. I needed that version since my computer language
had been changed from Spanish to English.
Mary

On 7/5/2017 11:39 AM, TeraByte Support (PP) wrote:
> They've been around for quite a while now. Basically, when Windows is installed or a major update is performed it will often resize the Windows partition smaller and create a new WinRE partition. It can do this even when the existing partition is large enough for the new WinRE version. I've also seen cases where it creates the space and doesn't create the partition. If you don't want this to happen you can fill the partition table when updating Windows so there's no room for another partition.
>
>

[TeraByte Support(PP)]

swayzak wrote:
> OK, so I can just leave them alone if I choose as well ? And they don't
> affect the EMBR of BIBM ?

You can leave them if you wish. From what I can see from your screenshot they're not causing any issues. I suspect they're not even being used as the ones that might be may not even be loaded into the MBR for the respective boot items.