Hi Steve_DiAcetis Thanks for the updates.
RE: Smaller downloads to client
Please explain the huge difference between lab and real world in terms of reduced install disk space requirement: by ~399MB or 8% vs ~2.8GB or 17%.
If you're talking about the inbox apps only, how exactly do you arrive at 399MB and 2.8GB? I can understand 399MB, e.g. roughly half of the apps doesn't need to updated. But 2.8GB... it's more than all inbox apps combined. What are you counting and comparing here?
RE: Faster installation [of cumulative updates]
You keep reducing the install time and CPU load, but you've also been deliberately slowing down the update process to minimize impact on other user / system activity. So the net result is still slow.
This makes perfect sense for the background update process. But when users checks for updates manually (which is a popular recommendation), they probably want this to complete faster. Any plans to speed this up?
RE: Reduced disruption
However, since .NET Framework is a separate update, it would not automatically get installed. Instead, once the new OS was booted, a separate scan against Windows Update would detect and install the .NET update, unfortunately requiring another reboot.
I'm glad you've finally admitted it after three years. But the number of reboots won't get reduced until the NET Framework team will stop forcing preview updates and now non-listed updates to GA https://twitter.com/vsterkin/status/1573947711795101697
Thanks!