@MSMG I just loaded up the source I was working on earlier and tried to access the convert menu, but the integrate menu is appearing in it's place - earlier I had no problem getting to the convert menu. I did mention this a few weeks ago and you acknowledged so I'm assuming you couldn't reproduce the bug. I don't know much about this (or I'd narrow it down myself to help) but I'm a quick study. So let me know what details you need to get a lead on this and I'd be glad to help. EDIT: After Cleanup, Apply & Save, then Rebuild, Option [3] Convert is available and does not bring me to [2] Integrate.
When rebuild has been able to run it's already unmounted, so you have to remount to integrate anything, why first unmount (apply and save) and next want to integrate some more, it's unnecessary.
Thank you so much MSMG ; I have seen the installation results with Turkish Enterprise x64. Interestingly i have never managed to install in a smooth way I am using full Autounattend.xml for installing Windows , can that be the reason ? (when i dont remove telemetry and defender , the installation is smooth) If not , can you write the order of removal process please ? I am not integrating any updates to cropped iso , just removing all apps , windows components and advanced windows components Thank you
How did you create your autounattend.xml? Did you use a generator from a website? From my personal experience using unattend generator never worked. It always give me errors. Now I prefer using WSIM from ADK and it works very well.
As you reported earlier about this I checked with W10 Pro Workstation Image - Deleted all indexes except Pro Workstation - Mounted the Image - Removed Components - Cleanup - Applied - Rebuilt - Choose [2] Convert - The Convert menu was shown May be some environment variable might have changed in the one of the steps you are doing, that's why it's jumping to integrate menu, try closing the ToolKit once and run it again.
May it's the Autounattend.xml that might contain an entry related to the removed components and thus causing the error and I think it might be CEIP or WER.
I use autounattend.xml generated from WSIM for many years and it always went smooh so far until i attempted to remove defender and telemetry with MSMG toolkit..Thank you for the answer anyway
Thanks for the answer Let me try to install Windows without unattend.xml to see if there will be an error or not and i will tell you the result later Have a good day and thanks
Of course not enough. I want to completely dissolve it before entering the system interface. In this way, every time the system is installed, there is no need to set it up again. Maybe you can understand it... Thanks.
Okay, but how can I classify the downloaded stuff windows10.0-kb4338832-x64_961806f0d9d52c7df32346349c5101f1ab2032a0.msu Windows10.0-KB4340917-x64.msu Windows10.0-KB4343669-x64.msu
When you download the updates using WHD Downloader, it gives information regarding the update being downloaded, note down which update KB###### represents what. Trim down the updates filename (windows10.0-kb4338832-x64_961806f0d9d52c7df32346349c5101f1ab2032a0.msu) to (windows10.0-kb4338832-x64.msu). Copy the respective update file to the specified directory in the Toolkit packs folder.
So I should manually look up the KB numbers and find the respective categories from articles on the Web. No shortcut. Did I understand you correctly?