Build 27686 is out to Canary Channel Updated Blog

Back in days of yore when resources were limited, the 32GB limit allowed using half-words (i.e. 16bits) instead of full words (i.e. 32 bits). Today that seems extremely silly, but back when MS set the limit (maybe 25 years ago?) we had to limit things because RAM and other resources were extremely limited compared to what we have today. I'd say MS was probably very late making this change, but better late than never I guess.

I am not on the Canary builds but was wondering if anyone knew the motivation for what shows below. Is it just they want to be able to use FAT32 for the larger install files without special procedures?

[Storage]

• When formatting disks from the command line using the format command, we’ve increased the FAT32 size limit from 32GB to 2TB.

The file size limit for FAT32 is still the same, 4GiB.

The only thing they changed is allowing formatting of FAT32 for drives bigger than 32GB.

There was no reason for that 32GB drive size limit on FAT32, it was a completely arbitrary limit set by Windows. 🤐🤷‍♂️

My thought is to be modern/contemporary... all computer things are 'big' these days, it is/has become the norm; drives, especially. Big drives, partitions, amounts of RAM, chip metrics... we use/have bigger for everything, now. Small is "old school".

Just a thought 💭

Cheers,
Drew

Thanks CK, Downloaded installed on both gaming laptops with no issues. :)

I am not on the Canary builds but was wondering if anyone knew the motivation for what shows below. Is it just they want to be able to use FAT32 for the larger install files without special procedures?

[Storage]

• When formatting disks from the command line using the format command, we’ve increased the FAT32 size limit from 32GB to 2TB.