Ok. One more thing. Empty subfolders will not be downloaded from mega even I have selected, e.g. ten subfolders. (download as zip) So, can You include these empty subfolders (for Packs folder) into Toolkit distribution archive?
It is just empty subfolders in Packs folders. Problem is, I have to make manually new subfolders every time, now. E.g. CustomRegistry\w10\x64. New folder option, three times.
Yes, will move all the Custom related things like Custom Files, Registry, TS, WinRE etc which are just place holders to something like <ToolKit\Custom> folder so that it will ship along with the main archive instead as Pack files.
I have just begun my own testing of v9.4 Toolkit, but thank you once again @MSMG for your very hard work! Currently using my old method below, so this will change as I progress - I will update soon. Spoiler: METHOD Extract ISO (1 > 3) Select source (1 > 1) (also mount boot and recovery images) Integrate Win32 calculator (3 > 3 > B) Remove all metro apps (4 > 1 > 1 > 8) Tweaks for Task View, App Downloads, Photo Viewer (5 > 5 > B/D/J) Cleanup (6 > 1) Apply changes to image (6 > 2) Rebuild (6 > 1) Convert WIM to ESD (2 > 4) Make ISO (7 > 1) The README.txt says: So should I do a cleanup after integrating Win32Calc before removing apps?
Please do not take me as grammar nazi (even my ChinEnglish is poor ), but You know: Code: echo.Making Custom Registry compatiable with ToolKit's Image Registry...
Yes all feature integrations other than .NET FX 3.5, Updates and custom features need to be done before the removal.
Spoiler: METHOD Extract ISO (1 > 3) Select source (1 > 1) (also mount boot and recovery images) Integrate Win32 calculator (3 > 3 > B) Cleanup (6 > 1) Remove all metro apps (4 > 1 > 1 > 8) Tweaks for Task View, App Downloads, Photo Viewer (5 > 5 > B/D/J) Cleanup (6 > 1) Apply changes to image (6 > 2) Rebuild (6 > 1) Convert WIM to ESD (2 > 4) Make ISO (7 > 1) Is the above method correct (ignore menu numbers and choices just now)? I have added what I believe is the needed extra step in bold. During testing I too have noticed that Toolkit Helper takes about 30 seconds per item. I believe it was 20 seconds with v9.3.2.
Yes, nowadays I do skip typing the words which I do have in my mind and later do correct them often by re-checking. Also due to very fast typing some times I do misplace the characters or do skip it, now I have corrected it in the script. Code: echo.Making Custom Registry compatible with ToolKit's Image Registry...
Yes the steps are correct. And yes as said in my previous post, it's due to the code-protection added to the ToolKit's removal program which takes more time to process and execute and now the MUI data for v1809 has increased due to in-depth removal and so it has increased the time it takes to execute.
I understand, but is my Cleanup step needed at such an early stage? If it is best to do a cleanup Thank you. I wanted to be sure that the additional Cleanup step was needed so early in the process.
When I tested the cleanup image only after the component removal the DISM gave error and so re-tested it again by doing the cleanup one time before the removal and then the post removal image cleanup worked properly. So this early step was added.
I see. I am still testing right now and I need to redo my work because of typo when using your Toolkit.
I didn't realize that if I integrate windows updates after removing components to my image (18362.1) all my components come back. I thought only windows update will restore all my components I removed. Does this mean that we are stuck with 18362.30?
This is now my updated method, yet to test in virtual machine though: Spoiler: METHOD Extract ISO (1 > 3) Select source (1 > 1) (also mount boot and recovery images) Integrate Win32 calculator (3 > 3 > B) Cleanup (6 > 1) Remove all metro apps (4 > 1 > 7 > 8) Remove Connect, Onedrive, People, Skype, Store, Xbox, Game bar, Xbox ID (4 > 1 > 6 > E/N/P/T/Z/1/2/3) Apply SSU and CU updates (3 > 4 > 2 > 1 > 4) Apply setup media update (3 > 4 > 2 > 2) Tweaks for Task View, App Downloads, Photo Viewer (5 > 5 > B/D/J) Cleanup (6 > 1) Apply changes to image (6 > 2) Rebuild (6 > 1) Convert WIM to ESD (2 > 4) Make ISO (7 > 1)
ok so its my first time using program.. and to be sure this image wont work Image : Install.wim Image Index No : 6 Image Name : Windows 10 Pro Image Description : Windows 10 Pro Image Architecture : x64 Image Version : 10.0.18362 Image Service Pack Build : 239 Image Service Pack Level : 0 Image Build : 18362 Image Edition : Professional Image Flag : Professional Image Installation Type : Client Image Default Language : en-US if i need to download.. 10.0.18362.30 1903 should i go for the 1809 instead.? another question the program will allow me to remove stuff. just the program alone right.?... so the packs are optional.?? or are the packs required or added so you dont have to install them later.?