Announcing Windows 10 Insider Fast Build 16257 PC + 15237 Mobile  

cereberus said:

Actually, the old system had some pluses as 240 d/£ which meant you could share exactly with 3 persons for example.

Interestingly bookie odds were all designed to always return an exact whole number of pence for each whole pound wagered. Since decimalisation, they often have to round up or down to nearest new pence.

I didn't know that but then I'm not a gambler.

It used to be fun totalling up what your shopping cost.

HippsieGypsie said:

What about what Cliff S has mentioned about failed updates in that it may create a recovery partitions? I don’t know the process enough to know when it creates them, but I would think that’s performed after reboot?

In my case for instance I deployed a customized 16251 image, you could call it a clean install, a week before 16257 was released using an answer file to partition disks (an XML script) creating 450 MB recovery partition after C: (yellow highlight in screenshot below).

Build 16257 upgrade a week later went smoothly without issues although it took hours. As per how this works (should work) and how it has worked before, upgrade should have expanded original recovery partition backwards by shrinking C: and taken required extra space from it. Upgrade shrunk C: as it should, but instead of expanding original recovery partition using that space it created a new 783 MB recovery partition (green highlight) between C: and original recovery partition.

cereberus said:

The only important imperial measurement in UK is the Pint used in pubs.

Kari said:

In my case for instance I deployed a customized 16251 image, you could call it a clean install, a week before 16257 was released using an answer file to partition disks (an XML script) creating 450 MB recovery partition after C: (yellow highlight in screenshot below).

Build 16257 upgrade a week later went smoothly without issues although it took hours. As per how this works (should work) and how it has worked before, upgrade should have expanded original recovery partition backwards by shrinking C: and taken required extra space from it. Upgrade shrunk C: as it should, but instead of expanding original recovery partition using that space it created a new 783 MB recovery partition (green highlight) between C: and original recovery partition.

Yep, that is wrong. Thanks for testing this. But it seems this only happens when you have that extra partition after the original Recovery partition? Only partitions I have on my system are the System, Windows and Recovery, and I have upgraded a few times.

slicendice said:

But it seems this only happens when you have that extra partition after the original Recovery partition?

No, this also happens if disk is partitioned by default settings (recovery partition first). It does not happen on all machines, and not always even on effected machines, but when it happens when recovery partition is volume 1, then the first additional recovery partition is created after C: drive, next one again after C: but before the first additional recovery partition and so on.

Only common factor I have been able to find at this point is that additional recovery partitions seem to be created only when upgrading from WU (clicking Restart now), whereas when upgrade is done from ISO it usually does not create extra recovery partitions.

This is also happening on generation 2 (UEFI/GPT) Hyper-V virtual machines, again not always but occasionally.

Getting weirder and weirder with each test :)

Kari said:

...
... ....
Getting weirder and weirder with each test :)

Interesting and weird! Why does this happen for some and others not?

I always hit the WU Restart Button. But as I stated earlier, my partitions are in correct order and I don't get these extra partitions. But my Recovery partition is 1GB in size, not 450MB. Maybe this is why?

slicendice said:

But my Recovery partition is 1GB in size, not 450MB. Maybe this is why?

There are clear rules as when recovery partition size should / will be increased:

• If the partition is less than 500 MB, it must have at least 50 MB of free space.
• If the partition is 500 MB or larger, it must have at least 320 MB of free space.
• If the partition is larger than 1 GB, we recommend that it should have at least 1 GB free.

(From UEFI/GPT-based hard drive partitions | Microsoft Docs)

Now I've had enough of Edge. It's a freaking pain to surf the web because of all the freezing and hick ups. I spend more time trying to make right-click work and waiting for something to respond than actually opening up pages and reading them.

Here comes Chrome! Thank you Google! :)

HUH!?!?

I tried to figure out what was causing the Touch Keyboard to show up every time I login. But now the problem is gone.

I have no idea what I did or did not do...the problem just vanished...POOOFF!!! :)

So I decided after the recent underwhelming Fast Ring upgrades (eye control is a good feature but one I will not use) to join the "Superfast Ring" (as I call the Skip Ahead) but missed the boat :-(.