KB4020001 file revision 168, KB4016240 file revision 250, KB4020001 is useless. KB4020002 file revision 168, KB4016240 file revision 0, KB4020002 is not useless.
OK, so I'm trying to understand something here. What's the use of integrating KBs to Win 10 when all you need is a clean install, latest CU msu and then run Win Update for latest security updates. Doesn't it take less time? I mean for desktop users, not deployment. I must be getting too old.
There really is no use, but when you want to do it properly, it's: 1. Integrate Servicing Stack (when available), (enable dotnetfx, if wanted), integrate CU and Flash update in install.wim 2. Integrate Servicing Stack (when available) and CU in winre.wim 3. Integrate Servicing Stack (when available) and CU in boot.wim And this all can simply be done by abbodi1406's W10UI script
kb4020001 to WinRe & Boot.wim index 2 (WinPE-SRT-Package) kb4020002 : extract and add files to ISO\Source & Boot.wim index 2 (Source) & WinRe (Source)
Boot.wim/1 also have SRT kb4020002 is only for iso\sources boot.wim/2 don't have the files to be replaced, and its "sources" is updated with CBS packages winre.wim don't have any "sources" files since Windows 8, except recovery environment starter
That's the old insider CU (15063.13 (or 14) at that time). The one who got installed first and later retracted and 4016251 was left. Thanks for confirming my suspicion it was incorrect info
Thanks tavrez, Oversight from when not being able to edit original review, Now Corrected. Will concur, going forward