What's the windows manual setup feature under the Remove Advanced Windows Components menu? Also I didn't install dotnet 4.7.1 on the computer I'm making this ISO on and MSMG toolkit is working fine... It's W10-RS4 so it came with 4.0 preinstalled. So I guess it doesn't need that specific version? Also: Will I mess anything up by applying the same option twice? Like rebuild source image or remove cortana? Also: xbox removal and some other stuff doesn't work... (from my previous install with dotnet 4.7.1 included)
Enabling dotnetfx3 (step 6 in your list) sets the pending flag, after that a cleanup can't be performed. There is also no need for step 4 and 5, doesn't do anything special to unmount and remount.
Thanks for the reply, So I could just do: 1. Added fr-FR language pack 2. Integrated CU KB4103714 (OS Build 16299.461) 3. Perform Cleanup 4. Apply changes and save to source image. 5. Re-mount source ( or just skip to Step 6 and do step 4 and 5? ) 6. Add .NET Framework 3.5 7. Step 4 and 5 8. Create my ISO
Thanks again for the reply, I have one last question... How do I correct that pending.xml warning or I just don't do the cleanup? And do Apply changes and save to source image.
Now you know what sets the pending flag (adding dotnet35) you can play with the order of doing stuff. It should be done after the cleanup.
I noticed this and I asked the same question here earlier, hoping that @MSMG would give an explanation. Using "diff" in Linux I recursively compared contents of two ISOs processed with NTLite using exactly the same settings. I found the differences were in Windows NT Registry hives. I binarily compared the respective files. I saw the differences but couldn't understand them because I don't know the specification of the registry file format. You probably noticed I said NTLite - not MSMG Toolkit. The size differences between outputs were smaller using NTLite so I rolled with that. You would have to repeat the same process for the Toolkit to see if it's just registry hives or more.
Intriguing. So there may well be something changed that I don't know about - more importantly, how does it effect the final result. It's attention to detail like mine that can help bring bugs and discrepancies to the surface. People should stop being so dismissive and accepting errors as normal.
I completely agree with you on deeper level. I feel exactly the same, it's like you took those words out of my mouth. At this point it's a relief to see there are other people who have extreme attention to detail and understand it's value and use, it's much too rare! It seems like tons of blatantly obvious bugs, errors, and design oversights go completely unacknowledged or dismissed entirely these days. Not to be rude to MSMG, the comment is a general one, aimed at a lot of different software. But yes, MSMG toolkit and part of it's design and use is included to a degree.
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!