You do know it's a free tool? Made by a private person who doesn't make any money out of it, and all on MDL is done on a voluntary base....
Oh absolutely, but why is that any reason not to strive to improve? There is so much confusion using this tool, and there doesn't need to be. A simple fact such as "ONLY start the Toolkit with start.cmd" not even being included in the instructional readme is an issue. If that's not poor attention to detail I don't know what is. Lets not let emotion get in the way of development. Getting offended or disagreeing with someone who has pointed out an error or design flaw is counter-productive. We all want the Toolkit to improve. EDIT: Sorry for the edits, bad habit. Best to wait a minute or three...
Maybe MSMG has more important stuff to do, like having a real life? Who will know? You only need to use start.cmd to do the butchering stuff. People these days seem to think they can demand stuff, that's not how it works, when the dev or poster/threadstarter has the time and energy, they will.
Confusion? Okay, if you feel confused, use NTLite. Done. MSMG is doing this in his free time, the tool is FREE, if you want a better tool, use NTLite, done.
The Toolkit, when it was started, it was just more like an integrator tool with support for only Windows 10 and later was expanded to support Windows 7, Windows 8.1 and also the Server OS's. A lot of new features got added to the Toolkit in due time including Component removal, now it has become more like an AIO tool and at the same time bit complex too. The DOS batch scripting has it's own limitations when it comes to UI design and error handling which can restrict the Toolkit development and despite making the Toolkit to be more user friendly, still some people do struggle to use it and that's why I have been working on a GUI version to improve the Toolkit experience about which I had posted earlier here: https://forums.mydigitallife.net/threads/msmg-toolkit.50572/page-341#post-1436616 Due to the MDL forum's post restriction, The first post got reached the maximum number of characters allowed and I've been struggling to keep the first post to be complete every time when releasing an update and so due to space constrain I had to remove few sections in the first post regarding the usage of the Toolkit. But the Readme.txt present in the Toolkit folder, I have specified clearly the proper usage instructions for the ToolKit with dedicated instructions for specific OS's. Code: General Usage: ============== - Extract/Copy the Windows Source ISO/DVD Image/Disc contents to ToolKit's <DVD> folder. - Double Click on Start.cmd and Choose Yes to Run as Administrator. - Click on ToolKit's Command Window Control Box and Choose Properties. - If using Windows 7/Windwos 8.1 HOST OS then Go To Font Tab and Set the Font to Consolas and Font Size to 16. - Go to Layout Tab and Increase the Height to 1000 in Screen Buffer Size Group Box. - Agree to ToolKit's EULA by pressing 'A' Key. - Press Enter Key to Continue. Now, please do specify which part of the Toolkit you are feeling confused in using, I can help you out regarding the same.
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!