not all as theese three cumulatove updates in catalog . 1 final august cu 2. final augist DCU 3. Preview CU only one is needed among them decide which one you need. plus same applies to .net cu too
UP to date images are up to date, for 30 days or less (maybe 15 days or less if you count optional/preview CUs), then they will get automagically the same CU that the RTM gets, requiring just one reboot or two in the worst case. In short there are few pointless works like updating an ISO past Win 8.1. It still makes some sense on LTSB 2016 that has huge cumulative updates and that gets selected packages via WU It still makes sense on builds that reached the end of service like 1511/1703/1709/1803/, but after that is a waste of time.
My ISOs usually are .1 releases. One run of Win10UI.cmd with the latest updates and the thing is current. Why should I integrate updates? Exceptions: - If .1 release is flawed or dangerous (like 17763). - Windows 7, due to the ESU and SHA2 clusterf*ck. - To create a "final" ISO for older and EOL OS. - "Enablement Package" branches that require a certain minimum version for the EP to work.
Even W/O taking the ESU in account, taking a live OS from RTM to last update requires a degree, 3 GB of downloads, one afternoon to accomplish the task, and many reboots. Win8 is even worse given WU is not able to detect any update until you install manually a dozen of packages. So Yes, having an updated ISO in such cases is almost mandatory. But Win10? One download, one reboot without even touching a single button or checkbox. (Not to mention that the whole idea of installing it using the ISO and setup.exe like in win95 days is already pretty stupid by itself...)
You can find all needed updates per build here: Win 10: 1809: https://forums.mydigitallife.net/posts/1490183 1904x: https://forums.mydigitallife.net/posts/1571109 Win 11: 22000: https://forums.mydigitallife.net/posts/1669627 2262x: will be updated later tonight Best to use W10UI, it will offline update the Winre.wim too.