Search the Community

I see that the "Alphawave's Downloader" feature in Win Toolkit is (trying to) use the update's release date for the downloaded file's timestamp. Thanks very much for that! I just used Win Toolkit v1.4.36.2 to download all 433 "New Updates [Recommended]". Checking the results for Last Modified date in Windows Explorer: All of the updates in the Security subfolder reflect the download timestamp (not the release date)Most of the updates in the General subfolder reflect the download timestampA few of the updates in the Hotfix subfolder reflect the download timestampAlso, in the "Downloaded" tab of the Downloader, for those files that (incorrectly) show the download timestamp in Explorer, the "Downloaded" column accurately reflects the download date. But for files that correctly show the release date in Explorer, the "Downloaded" column also shows the release date, which is a bit misleading. Perhaps this column can instead show the Created date? (but still keep the "Downloaded" label...) Looking deeper, I see that some (but not all) of the files that do show release date in the Last Modified timestamp have other timestamps that don't look right. For instance, Windows6.1-KB2800095-x64.msu (in the Hotfix subfolder): Created: ‎Friday, ‎February ‎28, ‎2014, ‏‎1:36:10 AM <--- ??? Modified: ‎Wednesday, ‎January ‎29, ‎2014, ‏‎12:11:13 AM <--- actual release date Accessed: Friday, ‎February ‎28, ‎2014, ‏‎1:36:10 AM <--- ??? Are these Created and Accessed timestamps actually taken from the source file? If so, then my previous suggestion to use the Created date may not be of any use. Perhaps you can set just the Modified date, and let the filesystem handle the Created and Accessed date? Minor nit: This feature uses functionality provided by the user "Alphawaves" @ MDL. So it should be labeled "Alphawaves' Downloader" (note the relocated apostrophe). Thanks! (Peter)