Looking forward to hearing news on your progress with the GUI. But, at the same time, slightly worried of the learning curve!
@MSMG regarding your gui for msmg toolkit, could you make sure that it is accessible? like the gui of nsudo is? if you stop developing the cli version of msmg toolkit, this current one and the gui is not accessible to screen readers then I will be stuffed. I use nvda the free screen reader if this helps. Majid Hussain
@MSMG 3 bugs when using "Integrate WHD General Updates" 1. Only Boot.wim & Install.wim integrate Cumulative Update. WinRe.wim doesn't integrate Cumulative Update. 2.Also doesn't integrate Intel Microcode update to WinRe.wim. 3. It Integrate some wrong update pack which is not for WinRe.wim such as kb4535680 (Windows 10 LTSC 2019).
Hi there, I have a quick question: where do I place the custom XML file for the start menu so it will be implemented by the ToolKit? Thanks for the help!
I ve used Windows 10, Version 2009 - 20H2 (build 19042.631). I ve cooked it wit toolkit 11.3 and after tests in vmware, i ve launched windows update. I had the same issue. I ve restarted from the beginning but this time i ve integrated in the WHD folder, the KB4601319-x64 (msu downloaded from microsoft catalogue). After the install process in vmware, i ve changed the windows update service state from (originally) manual (desactivated) to automatically (start). No more issue. Windows update installed all updates including the KB4601382. Hope this will help to solve your issue.
Yes it will take time and resources to process the protected code in the ToolkitHelper, trying to reduce the MUI code size to minimize the time and resource. You can get the list of components by executing the below command Code: ToolKitHelper.exe <Mount-folder> /? To save the output to a file use the command Code: ToolKitHelper.exe <Mount-folder> /? > packages.txt To copy the output to clipboard Code: ToolKitHelper.exe <Mount-folder> /? | clip