Code: CabTool - extract DXTool.exe /CT FilePath.cab CabTool - create DXTool.exe /CT FolderPath Set MD5 hash in file name DXTool.exe /MD5 FilePath Set SHA1 hash in file name DXTool.exe /SHA1 FilePath Grant Full Admin permissions DXTool.exe /SAOD FilePath DXTool.exe /SAOD FolderPath oscdimg GUI DXTool.exe /GOscdimg FolderPath UPX GUI DXTool.exe /GUPX FilePath.exe Split sfx 7z DXTool.exe /7ZSplit FilePath.exe Export DLL Registry DXTool.exe /DRE FilePath.dll Extract windows updates DXTool.exe /AR /MUSIEX FilePath.msu DXTool.exe /AR /MUSIEX FilePath.cab Reg2Inf DXTool.exe /RTI FilePath.reg Inf2Reg DXTool.exe /ITR FilePath.inf Msi2Inf DXTool.exe /MTI FilePath.msi Registry Tweaks True AddOn Creator DXTool.exe /RTA FilePath.reg BETA version doesn't have them all yet
DID i need any other update example like dynamic update to fully update my RS2 15063 Currently i have downloaded these three updates : KB4022405 KB4038788 KB4038806 For intergration!
Hi, I would like to make a new fresh LTSB 2016 Lite iso file with all needed updates using MSMG Toolkit. 7.7 As the update repository is not updated since July, can someone can drive me to download the right files from MS. ? - Cumulative Update (think is kb-4038782 ) - But dis not found SS stack update version / name ?. Did I miss another one ? That is all I need, Flash will came as update later. Thanks
Hi Bluescreen, I'm not sure what update repository you're referring to that hasn't been updated (maybe drew84's list?), but abbodi1406 updated the list of updates available through WHDownloader just last week. Here's what he has listed for .14393 (LTSB 2016). The release dates for the updates is added at the end: KB4038782 cumulative update 2017/09/12 KB4035631 servicing stack 2017/07/31 KB4038806 Flash update 2017/09/06 KB3186568 .NET 4.7 2017/04/21
Been having issues with my ISP... as it stands, only 15063 [1703] is currently up to date.. will resolve the rest later
Thanks for pointing that. I was referring the link in the first post in the tread, witch is supposed to be up to date. https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-77#post-1177885 But it is not... I found the abbodi1406 ' post and made my ISO. Thanks
(to upgrade to Windows 10 RS2 from previous versions of Windows). In August my friend, a laptop with Win 10 1607, automatically downloaded the updates to Win 10 1703 and gave an error when updating. Then in September, through DISM, I installed all the updates from the list for Win 10 1607. I created the assembly Win 10 1703 with all the updates. And successfully updated from USB, to Win 10 1703. Then I made a cleaning with the help of DISM. There are "three updates" left in the Installed Updates list.
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.