There will be updates to expect later this week or next week, most likeley not a re-release of KB4512508 but a new CU.
This Cu fixed lots of errors, and it's good that the size is reducing, in order to avoid the 2016 LTSB problem, with its CU's over 1,5 GB and take eternities to update, for that I ditched LTSB 2016 entirely
Yes, I'm having stress too Well new versions use PSFX format that's why their size is much lower, but it should always increase when new CU came, because all of previous things should be in them
These are the all the latest 1809 updates then: Windows10.0-KB4486153-x64-NetFX480 Windows10.0-KB4503308-x64-Flash Windows10.0-KB4506998-x64-NetFX472 Windows10.0-KB4512534-x64-CU Windows10.0-KB4512937-x64-SS
These are all the current updates for 1809 (incl. new dotnetfx48 and LPs): https://forums.mydigitallife.net/th...-17763-xxx-pc-rs5.77945/page-216#post-1490183
It's a bit contradictory to what you said earlier regarding Windows10.0-KB4486153-x64.cab being the latest NetFX 4.8.0 and not needing CU (not needing the older Windows10.0-KB4506990.cab). That, and since NetFX 4.7.2 is separate, wouldn't you also need the Windows10.0-KB4506998-x64.cab?
This was the advise on the needs about dotnetfx48: https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-437#post-1541828 The dotnetcu also updates dotnet35, so it's needed anyway.
Please test things yourself for once, install 17763.1 as you want it and see what WU installs and what dotnetcu it actually uses in c:\windows\softwaredistribution\downloads\.
I have not used Windows Update (the actual feature/service) in YEARS. Its CAB-only or nothing . That's why I am bugging you so much.
yes there is, why wouldn't you want support for older applications written in dotnet 2 and 3, which fx 3.5 supports; the 4.8 is just the new version of the complete framework, which used to be 4.7.2. the net 3.5 is a windows feature for legacy support that is enabled via windows components.
Dotnetfx48 does not replace dotnetfx3, although most software doesn't need dotnetfx3 anymore, most people playing with the offline integration of updates still enable and update it offline.
Aaaaaand the update doesnt install if the system got resetbased. This time, the cause is different — amd64_microsoft-windows-c..cal.desktop.cortana_31bf3856ad364e35_10.0.18362.10013_none_85d197aae41b2565 has less files compared to the .1 version of same component, and the reverse patch got generated incorrectly, not containing the .1 versions of those files. Meaning the .10013 update has a bug possibly impairing install of any future updates on its top.
Curious but good to know, I ran the cleanup to compress the files but omitted the "/resetbase" flag for .1013 but it can probably be resolved on Microsoft's end in a future update then. Though a clean install of 20H1 might not be a bad thing either, oh well it's a insider update and things happen but good to know what the cause was. EDIT: It's been over a week or almost over two now since those came out (1012 and 1013) so the task scheduled cleanup could also have done it now for some of the systems updating early on when it came out and would then be affected as well I assume. Probably over two since I updated later yes it was early this month when those came out. EDIT: Wonder if a full update could also be a thing, just a bit larger but it gets the components installed and no diff or delta for the changes. Well it's probably solvable in a number of ways.