Spoiler Thnks to @tempdrive1 for Validate XML code, repport bugs and testing. Thnks to @Enluaphelis for repport bugs and testing. Download in attachment.
Things are getting better each day! Well done! Please feel free to adjust the display text/color after the Write-Host commands for the xml syntax verification - I just put there something as per my standards. What would be interesting to see as an additional automation in my opinion, is that since the removal of CloudHostExperience breaks OOBE, as soon as people select it for removal, the Toolkit would prompt (with a one-liner explanation) for a username (mandatory) and a password (optional) as a bare minimum. At this point they will be stored in variables. Then, when the component removal actually takes place and CloudHostExperience will be really removed (they have not unselected it), as soon as the component removal is done, you could already deploy the autounattend.xml into the DVD folder with the username (and password) filled in if this file is not present at this point (i.e. the user did not generate it or copy it manually). Alternatively the prompt for user account information could be done right before the component removal takes place, it makes no difference in the end. This would serve as a preventive method for broken installation attempts for users who are not aware or do not care about managing autounattend.xml in general.
Something like: if there is no autounattend, it does not display or make the CloudHostExperience option available to the user. If it exists, the option will be available. But it's better to do as in IMCK, I made a note appear in the Main Menu to alert the user to write autounattend. About these changes, and aesthetics is better for MSMG to decide. I put a lot of notes, in the menus and such, but a lot of people think it gets too polluted. I think more information is better. But there's a "less is more" vibe that I'm not really in favor of. There are cases and cases. Each must be well thought out. There are people who would like nothing to be displayed on the screen, just a progress bar would be fine. I like to know what's going on underneath.
The issue with your proposal for CloudHostExperience would cause some inconvenience, as people most likely would add autounattend.xml after the components were removed - meaning they would not return to see CloudHostExperience to show up, let alone run the component removal again. Display text is always nice to have, but don't expect people reading and following instructions. If the earlier versions of the Toolkit required almost no attention to manage, nobody would like put in more effort to have nearly the same outcome than before. There are people who would like nothing to be displayed on the screen, just a progress bar would be fine. I like to know what's going on underneath. This is the easiest thing you could solve in everyone's favor: set a variable for DEBUG, if it is TRUE or 1 or something, you display all details, if it is off, then you display the bare minimum. Fast and easy-to-use tool with stable results is what everyone is looking for even if new features will be added. Both of these suggestions (automatic autounattend.xml creation for CloudHostExperience removal and Debug information display) are low-effort implementations with your skills. And, of course, I look forward to have the removed component detection added as well!
Yeah I thought about it. But the detail is that people new to the tool are attracted to removing everything that is available. I myself was like that today my removal comes down to a removal preset that I call "Personal Work" and it is a preset that removes between 40 and 50 components out of 174 components. That's why I commented about preventing the option from being displayed. But the option to put a note in option 5 of the main menu is better. So the user is carefree and when returning to the Main Menu, he will see the note. Regarding this, let's wait for @MSMG to take a position on this. The person will see the comments here and eventually, with the various updates that occur during the month, he ends up gaining experience and learning how the tool works before giving up because he finds some stones in his path, right from the beginning. This debug thing is good for the future, yes, but something like a log generator for parts of the script. I was thinking of doing something like activating a help by command line, but in batch it seems a bit complicated with a code of this size. Let's see if everything goes well this time. I hope so. But if you encounter problems, let us know.
Now it finally worked! Thank you guys! Also, why did option to remove UndockedDevKit disappeared? @inTerActionVRI @tempdrive1
UndockedDevKit it was never available in the menus, only via list. You can check this out in the Toolkit 13.4 release post.
somehow I am installing a windows without firewall, I am forgot not to not remove firewall before modding the iso I am removing the firewall using toolkit helper method is there a way for me to install windows firewall into my system after the iso is installed?
I can't seem to remove Microsoft-Windows-PowerShell-ISE-FOD-Package using DISM method. It's been a long time since I used the toolkit to remove this specific package but as far as I remember it used to work. Also, why is there no option to import your own autounattended.xml? I know it's not too much trouble to just drop it manually in the folder but still...
Add the below entry to Toolkit's <\Bin\Lists\RemovePkgsList.txt> file and choose the option Remove -> Remove Windows Components using Package List -> Remove Windows Components Using Package List (DISM Method) menu. Microsoft-Windows-win32calc-Package
Good morning. I just installed the ".1928 "update and I noticed that they have associated the "Stamp" button to take screen shot of the screen. Having the Lite version of W11 created with ToolKit (without app) which app should I re-install? thanks
If so, you need to keep CloudExperienceHost CapturePicker ScreenSketch. Maybe you need something from the Store too. You can use Windows button + Print Screen The image will be automatically saved in the folder "%UserProfile%\Pictures\Screenshots".