Win10_1909_Swedish_x64iso. Now i have tried it with both W.Pro and Home version. Same result. I get 2 different error codes on 2 updates. 0x800f0982 and 0x800f081f. None of the solutions i can find on the net helps.
The component removal for v1909 requires a image with CU version v418 as the base or with the latest CU. Did you integrated the required latest update before the component removal?
How do i select multiple choices to be removed? It seems to get only one choice by time. Is there a seperator i could use?
Part of me agrees with @Yanta however it must be recognised and respected that the GUI is the only way forward once it is released. There is no reason to hold sentiments unless the GUI is a train wreck - and if I know you @MSMG it will be something that will be amazing and is better at everything than the current ToolKit is. I suspect the GUI is going to be easier to maintain and therefore you may become efficient enough to focus your time on fixing the other problems you mention. This can only be a good thing for everybody and I do hope that people see this. If there is one thing I would like from the GUI, that would be to save a template for future use of what work should be done to an image, to avoid repetition. This can help us speed up testing for the new ToolKit and help you to fix problems. I have a suspicion we might see ToolKit v10 before the GUI is released. Or perhaps the GUI is going to be v10? Either way, I look forward to the new ToolKit. I don't know if you have created a new thread yet, but I would be happy to try and test the new GUI (while obviously respecting the fact it is not complete). I am sure others would also love to test and contribute ideas.
I seem to have a knack for being misunderstood. I'll try and rephrase. "MSMG Has done a phenomenal job with the toolkit. It works well, and is a fantastic achievement. IMHO It is so great that when it is retired it will be a sad day". That's all I was trying to say. I have no illusions about the direction things are headed, and I respect MSMG's decisions. geez, it's his project.
Indeed I do, and you have a massive workload that you have taken upon your shoulders, with other than feedback from users, it seems to be a solo task. That's certainly commendable, but geez, you must feel totally overwhelmed at times. I wasn't asking "when" I was asking, "Where on your radar is it". Two completely different things. No need to apologize for delays, as I said it's your project.
For the name of GUI & CMD version,You may use one name,Instead of different name for GUI version. For the current CMD,you may name it "MSMG ToolKit CMD version"; For the GUI Version,you may name it "MSMG ToolKit". This is an advice for the future version. Another point,for the future GUI version,it should support localization language for software interface.
@MSMG ,For the toolkithelper,in v1903/1909,these builds have the first few digits of the OS Build number are the same,both are 1836x. so,if the toolkithelper decided build number is use "10.0.1836",it can bypass the update restrictions(enablement update).other for remove v1903/1909's compnents codes constant. In this way, the task of merging the code for removing components from the two versions v1903 and 1909 in toolkithelper can still be completed without being affected.
where I copy my xml file for use with the menu ? 4 > 6 "Import custom StartMenu layout from XML file"
Hi all, I want to thanks everybody involved with the develop of MSMG Toolkit and its community, it's really awesome. Anyways i'm a newbie with ISO installation customizations ect so please "bare with me" xD Now my problem is that i wanted to integrate my audio and gpu drivers as when I install a fresh win 10 they are never up to date, but i really can't find a way to itegrate them right... So my question is if it's possible to extract the files needed from the already installed drivers ? Cause when i try to extract the exe from the nvidia installation or from the cab archive of the Realtek audio drivers there's just so much stuff that comes out and i really don't know which files to pick up.
I have some doubts ... Why can't Restricted Codecs (IntMMRC) be integrated into Customer Edition images? Only on Server images. If I edit and enable to integrate the Restricted Codecs (IntMMRC) in these images, what can I expect as errors? Note: I'm with the 1909 H2 Customer Edition. @MSMG, would it be very complex to implement a functionality of: "selection of the options you want to apply" and, one to apply the customized selection at once? I saw this feature in KMS_VL_ALL_AIO, which allows you to set "yes" or "no" to run checks and applications for windows and office. Thanks in advance for your attention! Edited: to add a note
Hint: Use Double Driver to get drivers from live operating system first. Download: Google BooZet Freeware & download Double Driver. Code: Mount install.wim: Dism /Mount-Image /ImageFile:C:\install.wim /Index:1 /MountDir:C:\mount Add a driver: Dism /Image:C:\mount /Add-Driver /Driver:C:\drivers\xxxxx.inf OR Add drivers: Dism /Image:C:\mount /Add-Driver /Driver:C:\drivers /Recurse
Yes, I can confirm the current Windows 10 VC pack causes installation to fail when integrated into 2004 (19041.208). Hoping this gets fixed soon, this saves me a lot of grief on several systems.
In readme.txt it is written: " Known Issues: ============= - Windows 7/8.1/10 v1507/v1511/v1607/v1703/v1709/v1803 Component removal has been removed temporarily. " What does it mean? Can't I remove components from the ISO-image of Win 10 1703 build 15063?