There will be a slight difference in each image creation and this can be due to the DISM compression algorithm used to create the image. The file/registry comparison will be same and if you want to cross check it, then you can use the tools like Beyond Compare or ExamDiff Pro to see the difference. For Registry hives you need to export them to registry files and then compare it using the above tools, some registry keys it will be in hex format which can be again opened in the registry editor to see the difference.
Hi, how to integrate apps like bing weather? I put files: "Microsoft.BingWeather_4.20.1102.0_neutral_~_8wekyb3d8bbwe.AppxBundle" & "Microsoft.BingWeather_8wekyb3d8bbwe.xml" into "\Packs\Apps\w10\" but it didnt show up in program.
At present the Toolkit can only integrate the Apps for Windows 10 TH1-RS3 OS, for RS4 you will have to wait until the Toolkit is updated. For integrating any App you need three files - App file (.appxbundle) - App's dependency files (.appx) - App's license file (.xml)
Why does the readme say that integrating .NET 3.5 is one of the recommended steps? Is it necessary for some reason when making the iso? I was planning on installing .NET once the system's live. Thanks!
No it's not so important, only some older software still needs it to be installed. You can install it whenever you want/desire.
Just disable cortana and remove the windows search component and you'll have a ltsb-like search app...
Would it be possible to get a menu or, probably easier, a payload listing for the bits and bobs under add or remove Windows Features? I might be missing something but couldn't see these packages. Most of them go unused, had trouble finding all the strings to remove them all - but go close with zero issues. The main issue with /remove under 10 is that it won't remove payloads due to MS's desire to have an uncompromised reset function.
@BearPaws: It's looking for the wrong filename. Dart_w10.tpk is the file, but the toolkit looks for Dart_w10_.tpk The cabfile has the same issue, it looks for a file with ".." instead of a single ".". Besides that, the version is not correct (10.0.17.133 needed, but 10.0.17.134.1 present). Try renaming or put the correct files and it should work, probably a glitch in the toolkit. Also note that the latest insider builds are not supported by the toolkit. Cheers.
Is there any "safe" way to use MSMG toolkit and NTlite (free) on the SAME iso? I'm asking because the free version of NTlite has some features MSMG lacks (and vice versa). I remember reading (IDR where) a post saying they use different backends and could interfere with each other's changes. But that problem should be avoided if they modify separate parts of the iso, right? For example, can I first use Ntlite to remove whatever's not available in MSMG, and then put the resulting iso through MSMG to remove the remaining components? Thanks!
Cortana and StartMenu Search are integrated, removing Cortana will also remove the search in StartMenu and Settings. The best you can do is to disable Cortana.
If I'm correct you are referring to package list for removing the components present in the Windows Features. You can use the install_wim_tweak.exe tool to get the package list for the Windows Features.
Thank you for the reply, I will do the rename and try that... I am currently using Windows 10 Build 1803 as my base image. I was just wondering is the language pack version for RS4 is 10.0.17.134.1 or 10.0.17.133? as you said that 10.0.17.133 is not the correct version for RS4. Thanks again
You can use it, first use NTLite and then ToolKit, the reason I don't provide support for servicing source images already serviced by other tools is that: - The Toolkit right now uses two methods for component removal the DISM and manual (ToolKitHelper.exe). - The NTLite uses it's own method of component removal which I believe is the manual method because using DISM method you can not choose what to remove and what to not in a package. Those who are familiar with these both tools can only know how to use it in a right way without corrupting the source image. The ToolKit's manual method (ToolKitHelper.exe) also do provide some extra component removal which is not present in the ToolKit Menu and this has been added for testing purpose and will be later added to ToolKit Menu and there by replacing the DISM method completely. The next update to ToolKit will support removing extras components for RS4 through (ToolKitHelper.exe).
Thanks for the reply, I am using 17133.1.180323-1312.RS4_RELEASE_CLIENTCONSUMER_OEMRET_X64FRE_EN-US.iso as my base image. I now see where is the problem. Thank you MSMG!