I have a $99 10" tablet with 32GB, 2GB RAM and Z3735F CPU running Anniversary Update just fine (surprisingly well I would say)... but the only way that AU would install was from a 8GB USB stick built with the Windows Media Creation tool. A clean install of AU left 17GB free of 28.4GB. I don't think this is anything a general consumer would go through though, so probably most of these devices will effectively be left on the November update from last year.
But, I wanted to point out that saying the AU update is too large for 32GB devices is factually incorrect.
Re:OpenBSD on HP Stream 7
by Sanddancer on Saturday September 10, 2016 @04:45PM
(#12470800)
I'm thinking part of the problem is that you end up with a layer cake of recovery partitions. HP's then MS's, etc. I ended up deleting and resizing partitions on mine to get me the extra space needed to get it usable.
> As a side note, it's a shame that the Anniversary Update requires so much space.
It is a great shame. Windows 8 tended to use WIMBoot on these type of machines. That uses huge amounts of space and causes some problems for updates. https://technet.microsoft.com/en-us/library/dn594399.aspx
Windows 10 tends to use CompactOS. https://msdn.microsoft.com/windows/hardware/commercialize/ma...
So they fixed one thing, and then broke it by imposing a weirdly large drive size limit.
Makes me wonder what a real Surface Mini would have been like!
As a side note, it's a shame that the Anniversary Update requires so much space. With the new emphasis on Chromebook-class Windows computers (the new netbooks), it's going to be important to keep all of these $99-$299 Windows 10 computers updated.