I always use the install.wim from the originally released iso and put it in the most current released iso. This way there is no superseded CU inside the install.wim to offline update and the most current iso updates are implemented (iso:\sources updates).
I don't remember now, but I was seeing some file which are present in both. A few, though. There are lots of folders to check. Edit: offlinelsa.dll is just one example. It's present in both. But yes, there are files in SU which are not available in CU.
I was referring to the manifest files. That's the important thing to look at when comparing updates. As an example: "amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.16299.96_none_2c40cc7f3876f2b7.manifest" exists in KB4054022, but not in KB4051963. There are no overlapping manifest files between the two updates. Sometimes they do overlap. And if one update contains all the manifests from the other and are newer (> .96 in this case), then the other update is superseded and not needed. But in this case, they're two completely separate updates.
Those who got SSU KB4054022 "suddenly", do you have Release Preview Ring enabled? and how did you installed CU KB4051963? P.S. in ver 1709, WU no longer handle or install Cumulative Updates, UUP handle it now and maybe SSU likewise too
Yes, i have Release Preview ring set on my main system but not on my wife's laptablet, it also got the ssu without showing it in update history (when the current cu installed). CU installed by WU on both.
so if I want to install KB4051963 in a offline and clean installation of Windows 10 1709, I have to install KB4054022 first ?
On one installation KB4051963 was on WU and installed, but not KB4054022. On another installation (same Laptop) no updates appeared, still on 16299.64. That seems quite strange.