There are 2 types of dynamic updates: One is a cab file (du for sources), meant to be extracted and the content placed inside the ISO:\sources folder. There is also a dynamic update for CBS (integration by dism), this is at the moment only for 18362/3, not for 19041.xxx
It's only offered on WU for 19041 users who are enrolled in the slow ring, by official means or using OfflineInsiderEnroll by @whatever127 When manually installed, there is no need for any IP ring enrollment.
wait for 19042 build, microsoft don´t released on date because these bugs mentioned before cant be fixed only with CU, you remember about 17133 and 17134 versions right?
There, most likely, will be no 19042 build, that would mean a totally new compiled major build, like with 17133 & 17134 was, MSFT, most likely won't go that route again, but all is possible.
Everything can be fixed wia CU, that's the point of cumulative updates. Cumulative = increasing or increased in quantity, degree, or force by successive additions. (I never thought I'd quote Google)
Where is he wrong? Since 17133>17134 MSFT did everything different, with 17763.107, they first released an already updated (actually a refresh) ISO, supposed to be the official 1809 release, 17763.1 was shoved aside (almost up to the level MSFT denies it ever existed), this never happened before. Next they didn't even bother to release 1903 aka 18362.1 in ISO/ESD format, only on WU servers (that is UUP) and the first released ISO/ESD was 18362.30. Then they released a fake second major build with 3 something new features, by a 20kb enablement package, which actually only enabled the new features and bumped up the buildnr to 18363 when a 18362.32x+ CU got installed. Seems they went for the "CU will fix it" route to me
all depends what you needed change to fix the bug, in 17133 the MS need change a structural files to fix the blocking bug, and its need recompile all again later its never fixed on 17133 with CU
That actually is not what i said. When a new major build is released, then they will fix bugs by CU and not recompile a complete new major build, based on the experience from 1809 and up. But, your scenario is what i always thought they were planning to work toward, just a simple update (they call the current upgrades from major build to major build "feature update" and not what it actually is, a full upgrade) to move to new major builds (fake or not).
to be fair the pepup isn't big on my laptop but it has 16gb ram and run vms so lotsa pagefile actvity
You and squalles both have a point. In the end the exact numbers don't mean much anymore and MS would rather we forget that some builds ever existed.