What should i say, a lot of errors possible in the process, besides the script part. Be more precise what and how you did.
Neither MSMG's toolkit nor a toolkit I created accepts keyboard inputs in build 16193. This renders them useless. What to do?
For testing purposes it's easier to keep it simply in the "iso:\sources\" folder, it can be changed easily when something is wrong, putting it inside "iso:\sources\install.wim\windows\setup\scripts\" folder would need a new mount/unmount /commit action to change bits. At the end there is no difference, both work exactly the same.
Hey, Thanks for this but wanted to let you know. 7.2 kills the xbox app when you select, "All except xbox and store." At least on the 1703 Enterprise ISO.
You might be right, I don't think I removed from the component area but thought I would let ppl know, didnt' notice the issue with 7.1. lol Update: It was definitively an error with the update. Watched it remove xbox components right from the "Metro" options when you select "All but xbox and store." PS. This was on the official retail 1703 home and pro iso. Again, 7.1 does not do this. Hope this can help
Thanks for remember. I forgot this bug in copying files to C: \ I also had this problem. Whether to enable .NET Framework 3.5 before or after the affected pack is only Directx 9.0c. You can use my pack while MSMG does not update the Toolkit or install Directx after installing the OS. I remember reading something about this a while ago in the Hotfix Repository thread but I do not recall very well, about CU getting errors when integrating offline into 10240 builds. Part of the GUI version code is based on the command line version code. And the packs, too. The command line version is easier for other users to assist in debugging errors. I think it's good to keep this version until it's stable enough before launching the GUI version. I do not know if it was clear in my first post but I used Windows 10 LTSB 2016 as host OS in a VM to capture the image. By not being sure if my system and HD were affected or not with the permissions bug I preferred to do in a VM. For the tests I use the same system as host and source OS (LTSB 2016). I intend to soon test on Windows 7 source OS
... ..The tool is limited because removes only by dism, so the gui version will bring more options and means of removal more effective than only by dism....I think...xD
I have multiple copies of Windows 10 installed with Directx9 integrated and have had zero issues on them. Unsure of the Protected View thing in office because I don't use office, but I have zero folder permission issues.