Then remove the current CU and revert back to the previous one. Don't know if you now are on 17763.195, 17763.253 or 17763.288.
Release Preview Channel: https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-363#post-1496310
im running an old cpu FX8350 on an old mother board with a bios date 01/12/12 so far my windows 10 pro ver is 1809 17763.253 I just don't get the cu update right away when its released because some problems don't show up till later after its fixed again! I try not to disable to much because it causes other problems later on
kb4462930 is an old Flash update, not needed when you integrate the most current one. kb4469344 is an old DISM DU, superseded by the CU it was released with. These are the needed updates for a 100% uptodate 1809 (17763.288): Code: windows10.0-kb4470788-x64/x86_SSU_17763.164.cab Windows10.0-KB4480979-x64/x86_Flash_Jan_8.cab Windows10.0-KB4480056-x64/x86_Dotnet_CU_Jan_8.cab windows10.0-kb4476976-x64/x86_CU_17763.288.1.9.cab
2018-11 Update for Windows 10 Version 1809 for x64-based Systems (KB4470788) is the last SSU that released on 04.12.2018 & which is integrated with this Windows 10 17763.194 EN-GB MSDN (Dec 2018) ISO. So theoretically, if anyone wants to make an up to date ISO based on that MSDN dec 2018 v194 ISO, then the 'windows10.0-kb4470788-x64/x86_SSU_17763.164.cab' will not require, it only requires the latest following KB4476976 CU (17763.288) 2019-01 SU For AFP (KB4480979) & 2019-01 CU For DotNet (KB4480056)
Never use a previously updated iso, so the lists we post are for use on a clean 17763.1 iso. LTSC never got december refresh (17763.194) iso's and server neither, only Consumer and Business did.
The only issue I know of in failing to do that is bloats up the size of the image installing updates on top of updates. Is there some other issue that can result from failing to start with the initial release?
When you are planning to integrate updates anyway, it's best to start with a clean iso, 17763.1, it has no previously, and at the day of release superseded, updates in. /resetbase can remove superseded components but will break windows functionality and won't remove previously integrated SSU.
I found /ResetBase actually has a pretty negligible effect on the size of the image, /StartComponentCleanup really reduces it with or without the /ResetBase switch. So yeah it's not worth disabling the Reset Windows feature.
/resetbase will decrease the size of the wim file significantly, but the amount of saved space relies on the amount of superseded components it can remove, on a 100MB cu it's not as much as when you integrated a 600MB or, like on 2016 LTSB 1GB+ CU, then it will shave off a big chunk of the filesize. /Cleanup-Image /StartComponentCleanup will not remove the superseded components but only delta compress them, a bit less gain at the filesize part.