Here's the way abbodi1406 determines the Release Date for updates, as shown in WHDownloader: The date is pulled from the "Build Date" field in the pkgProperties.txt file from inside the .msu. For example, the Build Date shown in Windows10.0-KB4038788-x64-pkgProperties.txt is "2017/09/06" and that would normally be the Release Date shown in WHDownloader. But since the CUs are so large and released so often, he doesn't download every one of them. Sometimes he just uses the date reported by the server. And more recently, uses the dates of public release. That's why the Release Date shown in WHDownloader for KB4038788 is "2017/09/12" (and not "2017/09/06"). And that's why I was confused earlier. Thanks to abbodi1406 for explaining his current process to me.
Appreciate the info.. The Dates that i've used for 1703 are from the catalog, however.. normally it would be the date when update first surfaces here at MDL
FAST or SLOW = Insider Preview builds, Release_Preview still is for early access to updates. But i only keep up with the current official release and the IP build releases, not older ones.
@ laser2016 hehe very strange when installing this KB4038801 x64 on my system take a lot of time so I think my O.S. enter in infinite looping but not really take very very time to conclude
Cumulative updates for windows 1607 should be installed only once in a while. On a SSD, it takes 30 minutes to install and then 30-60 mins for `getting windows ready, dont turn off off your computer'. Basically, you are locked out when it is getting ready. Imagine doing this for 2 times a month. As to the latest and greatest 1703, frequently icons and taskbar do not load on startup. This happens 1 out of 3 times. Sign out/sign in does solve it. This happens on all my systems (all are 2016-17).
It does take a while to install but an hour sounds excessive particularly for a SSD which should be far faster than a traditional HDD though each system is unique so no doubt some take far longer to update and some are faster with this whole process. Entire installation is over in about an hour total and the main time of that is the initial download and install phase, opening up that express cab file showed some 28000 files in the latest CU so no wonder it takes time for the OS to process all that but the reboot and then going up to 100% completion is pretty quick here. Though it does take a little while for the DISM command to clean up the leftover data afterwards too but that step is optional, deletion of old files is faster but compression is safer if the update ever needs to be uninstalled or reverted. EDIT: Being cumulative updates I assume it's going to be the same for RS3's update system with the first few possibly going pretty fast and then as more files are built up and modified the later updates will start seeing longer install times due to the sheer amount of files that are updated.
I am running LTSB 2016 as well on a laptop with SSD (Samsung SSD 840 Pro). I am installing every cumulative update as it is being released. This takes 5 to 10 minutes at the MOST each and every time. No joke! I also run a few more computers with 15063 and I can absolutely confirm the desktop issues with the disappearing icons (or not appearing at all after boot and it´s randomly happening here too). Additionally, the "Save As" / "Open" dialog (regardless which program) was randomly not working either in 15063 for me. Those are the reasons I´ve upgraded them to 16299.15 already today and so far, no more disappearing desktop icons and menus
I got KB4023057 some days ago on my 1607. Anyone know what it is?? It install something named remsh.exe