I had coded that before the RS4 release and it was based on the Image Info provided by DISM ImageMajorVersion.ImageMinorVersion.ImageBuild.ImageServicePackBuild.ServicePackLevel Windows 10 RS3 10.0.16299.15.0 Image Information Code: C:\ToolKit>dism /get-imageinfo /imagefile:dvd\sources\install.wim /index:8 Deployment Image Servicing and Management tool Version: 10.0.17133.1 Details for image : dvd\sources\install.wim Index : 8 Name : Windows 10 Pro Description : Windows 10 Pro Size : 10,521,784,395 bytes WIM Bootable : No Architecture : x86 Hal : <undefined> Version : 10.0.16299 ServicePack Build : 15 ServicePack Level : 0 Edition : Professional Installation : Client ProductType : WinNT ProductSuite : Terminal Server System Root : WINDOWS Directories : 14612 Files : 76771 Created : 30-09-2017 - 20:15:39 Modified : 14-11-2017 - 12:37:43 Languages : en-GB (Default) The operation completed successfully. Windows 10 RS3 10.0.16299.15.334 Image Information Code: C:\ToolKit>dism /get-imageinfo /imagefile:dvd\sources\install.wim /index:8 Deployment Image Servicing and Management tool Version: 10.0.17133.1 Details for image : dvd\sources\install.wim Index : 8 Name : Windows 10 Pro Description : Windows 10 Pro Size : 11,872,373,344 bytes WIM Bootable : No Architecture : x86 Hal : <undefined> Version : 10.0.16299 ServicePack Build : 15 ServicePack Level : 334 Edition : Professional Installation : Client ProductType : WinNT ProductSuite : Terminal Server System Root : WINDOWS Directories : 15713 Files : 83044 Created : 30-09-2017 - 20:15:39 Modified : 12-04-2018 - 17:03:47 Languages : en-GB (Default) The operation completed successfully. Now see the difference for RS4 Windows 10 RS3 10.0.17133.1.1 Image Information Code: C:\ToolKit>dism /get-imageinfo /imagefile:dvd\sources\install.wim /index:1 Deployment Image Servicing and Management tool Version: 10.0.17133.1 Details for image : dvd\sources\install.wim Index : 1 Name : Windows 10 Pro Description : Windows 10 Pro Size : 10,340,964,006 bytes WIM Bootable : No Architecture : x86 Hal : <undefined> Version : 10.0.17133 ServicePack Build : 1 ServicePack Level : 1 Edition : Professional Installation : Client ProductType : WinNT ProductSuite : Terminal Server System Root : WINDOWS Directories : 15012 Files : 77402 Created : 25-03-2018 - 10:03:39 Modified : 12-04-2018 - 15:10:22 Languages : en-GB (Default) The operation completed successfully. Windows 10 RS3 10.0.17133.73.73 Image Information Code: C:\ToolKit>dism /get-imageinfo /imagefile:dvd\sources\install.wim /index:1 Deployment Image Servicing and Management tool Version: 10.0.17133.1 Details for image : dvd\sources\install.wim Index : 1 Name : Windows 10 Pro Description : Windows 10 Pro Size : 10,717,678,074 bytes WIM Bootable : No Architecture : x86 Hal : <undefined> Version : 10.0.17133 ServicePack Build : 73 ServicePack Level : 73 Edition : Professional Installation : Client ProductType : WinNT ProductSuite : Terminal Server System Root : WINDOWS Directories : 15321 Files : 79370 Created : 25-03-2018 - 10:03:39 Modified : 12-04-2018 - 15:38:30 Languages : en-GB (Default) The operation completed successfully. It's bit confusing regarding the DISM/CMD prompting the version like below, whether the 1 belong to SPB or SPL. Deployment Image Servicing and Management tool Version: 10.0.17133.1
I work for a pretty big school district and I'm in charge of making our district windows image... where is the option to integrate a XMR BTC Miner... lol. j/k of course but that would be hilarious
So I'm working with the updated toolkit and im having trouble stripping out cortana. Keeps saying package doesnt exist. I've tested in a VM shes still there.
Just a short question: Any plans on re-adding the option to remove Telemetry on >RS4? I know that this component has been merged, so ToolKitHelper needs to take care of this I guess? If ToolKitHelper removes something, does this break updates (or, do updates simply put it back)?
I'm new to this Sorry if I miss something Whats the difference between Store ESD and ESD in Convert Option
what's the point from downloading net framework 3.5 packs !!? when you can integrate that from the iso of all windows versions using: DISM /Image:"%mountedimg%" /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:"%windist%\sources\sxs"
Yes the Telemetry removal will be added when I do update the ToolKitHelper.exe and it take some time. It's too early for me to say if the ToolKitHelper component removal will break the updates or not, lets see when I do finish updating the ToolKitHelper.exe and test it.
- Windows Store ESD Image is the ESD Image which you get from Microsoft, which is encrypted and also contains Boot.wim, Installation Media Setup files . - Normal ESD Image is the one which the user creates and later wants to convert them back to wim.
.Net Framework 3.5 Pack is optional, you don't need it if you have it in sxs folder, it's just provided as a repository for ToolKit. The ToolKit first checks for sxs folder for .Net Framework 3.5 files and if it's not found then it will look for <Packs\NetFX35\<OS>> folder. The Windows 8.1 .Net Framework 3.5 Pack provided by ToolKit is a multi-language Pack, it will be helpful when dealing with multi-language image. Also for Windows 10, you can have all the .Net Framework 3.5 files for each Windows 10 versions in a common place.
... Thanks for the release the Toolkit 8.3 however I am in doubt, what is this MSMG DELTA TOOLKIT 8.3 ?
Earlier, Someone had requested for ToolKit.7z with only the updated/changed files so that they don't need to download the whole ToolKit.7z and that's the delta file which can be extracted to a earlier ToolKit folder. I think from next time it's better to use the SmartVersion to create a delta differential file.