Win10 build 1511

[SaliesBuzz]

A note for Brian K and Terabyte Support:
We have a client who has recently upgraded to Windows 10 586 1511.
He uses BootIT BM with limit primaries turned off, however there were only three actual partitions on the disk:
BootIT BM, Windows 10 and a Data Partition following that. The rest was free space.
He used to have other partitions when he used Windows 7 and Windows 8, but these have since been deleted.
The 1511 upgrade shrank the Windows 10 partition ny 450 Mb and inserted a 450 Mb Recovery Partition between Windows 10 and the Data partition.
The system reboots showing no errors in BootIT BM or In Windows 10.
Having moved the WinRE back into the main Windows 10 partition, he has deleted the 450Mb Recovery Partition. BootIT BM reports this correctly as 450Mb free space.
My surmise is that providing that there are less than 4 partitions, (as in standard MBR), the Windows 10 1511 upgrade does not cause a problem, even when the EMBR is present, (limit primaries turned off).
The situation I reported in my earlier post was when there were more than 4 primary partitions on the disk, the Windows 1511 upgrade attempts the shrink, writes the 450Mb Recovery Partition, which it fails to do and trashes the partition following that.
I still cannot believe that MS have been so stupid in not coding this so that it checks the MBR table correctly. However I am probably being very naive!

[Bob Coleman]

I mentioned this above, but to reiterate in light of the current discussion.

I have primaries not limited and have five partitions, one of which is an extended partition containing several logical partitions/volumes. When I did the upgrade, I made sure that all four MBR slots in the Win10 boot item were filled. The upgrade didn't create any new partition or trash anything. I'm GUESSING this is because the process saw four partitions and proceeded on the assumption that since all "four possible partitions" already existed another couldn't be created.

I also note that I'm using Windows 10 Home which may or may not be relevant.

[DrTeeth]

On Sat, 5 Dec 2015 15:39:07 PST, just as I was about to take a herb,
Bob Coleman disturbed my reverie and wrote:

>I also note that I'm using Windows 10 Home which may or may not be relevant.

My MBR is not full and I have unlimited primaries. No partition made.
My version of windows 10 is enterprise, only because I had to force
the activation as I wanted a clean install and did not want the hassle
of installing Win 7 first.
--
Cheers,

DrT

"If you want to find out what is wrong
with democracy, spend five minutes with
the average voter." - Winston Churchill

[Brian K]

DrTeeth wrote:
> No partition made.

DrT, can you look at your Win10 partition with IFW, Backup. Select the partition and click Information. What is the MiB to restore? How does this compare with the size of the partition (Used plus Free)? I found if there are sectors in use in the final 450 MiB of the partition then a Recovery partition isn't created.

[TeraByte Support]

no doubt they tried to make it safe, but it needs logic, not just math, the
newbie probably thought it was easy went alignment is more involved than it
seems. he/she needs at least something like:

if (newendlba>orgendlba) {
newendlba=orgendlba;
}
// and may not needed but you should do this
if (newendlba<=newstartlba) {
// something ain't right
}



"SaliesBuzz" wrote in message news:10653@public.image...

A note for Brian K and Terabyte Support:
We have a client who has recently upgraded to Windows 10 586 1511.
He uses BootIT BM with limit primaries turned off, however there were only
three actual partitions on the disk:
BootIT BM, Windows 10 and a Data Partition following that. The rest was free
space.
He used to have other partitions when he used Windows 7 and Windows 8, but
these have since been deleted.
The 1511 upgrade shrank the Windows 10 partition ny 450 Mb and inserted a
450 Mb Recovery Partition between Windows 10 and the Data partition.
The system reboots showing no errors in BootIT BM or In Windows 10.
Having moved the WinRE back into the main Windows 10 partition, he has
deleted the 450Mb Recovery Partition. BootIT BM reports this correctly as
450Mb free space.
My surmise is that providing that there are less than 4 partitions, (as in
standard MBR), the Windows 10 1511 upgrade does not cause a problem, even
when the EMBR is present, (limit primaries turned off).
The situation I reported in my earlier post was when there were more than 4
primary partitions on the disk, the Windows 1511 upgrade attempts the
shrink, writes the 450Mb Recovery Partition, which it fails to do and
trashes the partition following that.
I still cannot believe that MS have been so stupid in not coding this so
that it checks the MBR table correctly. However I am probably being very
naive!

[DrTeeth]

On Sun, 6 Dec 2015 14:57:14 PST, just as I was about to take a herb,
Brian K disturbed my reverie and wrote:

>DrT, can you look at your Win10 partition with IFW, Backup. Select the partition and click Information. What is the MiB to restore? How does this compare with the size of the partition (Used plus Free)?
Used + Free = MiB to restore.

I have to say that I am not aware of a large update being applied and
my Win 10 partition is up to date.
--
Cheers,

DrT

"If you want to find out what is wrong
with democracy, spend five minutes with
the average voter." - Winston Churchill

[Brian K]

DrTeeth wrote:

> Used + Free = MiB to restore.
>

That fits with what I noticed. You shouldn't get a Recovery partition with those numbers.

[TeraByte Support]

Microsoft would like the contents of your:

%windir%\panther folder

after doing the update that causes a problem.


"SaliesBuzz" wrote in message news:10653@public.image...

A note for Brian K and Terabyte Support:
We have a client who has recently upgraded to Windows 10 586 1511.
He uses BootIT BM with limit primaries turned off, however there were only
three actual partitions on the disk:
BootIT BM, Windows 10 and a Data Partition following that. The rest was free
space.
He used to have other partitions when he used Windows 7 and Windows 8, but
these have since been deleted.
The 1511 upgrade shrank the Windows 10 partition ny 450 Mb and inserted a
450 Mb Recovery Partition between Windows 10 and the Data partition.
The system reboots showing no errors in BootIT BM or In Windows 10.
Having moved the WinRE back into the main Windows 10 partition, he has
deleted the 450Mb Recovery Partition. BootIT BM reports this correctly as
450Mb free space.
My surmise is that providing that there are less than 4 partitions, (as in
standard MBR), the Windows 10 1511 upgrade does not cause a problem, even
when the EMBR is present, (limit primaries turned off).
The situation I reported in my earlier post was when there were more than 4
primary partitions on the disk, the Windows 1511 upgrade attempts the
shrink, writes the 450Mb Recovery Partition, which it fails to do and
trashes the partition following that.
I still cannot believe that MS have been so stupid in not coding this so
that it checks the MBR table correctly. However I am probably being very
naive!

[SaliesBuzz]

Entire contents of Panther Folder? This would appear to be compressed, as properties in File Explorer reports it as:
519MB 130mb on disk.
In any event with a 800Kb upload capability, this would take some time, (I live in "3rd world" France where fibre broadband is very sparse and they think 10MB download is Fast!).
Where and to whom would I upload it?

[TeraByte Support]

you could setup a dropbox (or other) account, upload then send an email to
support@ to download it.


"SaliesBuzz" wrote in message news:10989@public.image...

Entire contents of Panther Folder? This would appear to be compressed, as
properties in File Explorer reports it as:
519MB 130mb on disk.
In any event with a 800Kb upload capability, this would take some time, (I
live in "3rd world" France where fibre broadband is very sparse and they
think 10MB download is Fast!).
Where and to whom would I upload it?