Hello and Thanks! That version fixes the error when installing image with AutoUnattend, right? Also, is configuring password and username beforehand in AutoUnnatend necessary when CloudExpHost removed? Or I can do that in install process?
Read this: Then you need to specify at least the username. If you don't remove CloudExperienceHost and you create autounattend without specifying username. You must be prompted during installation. Give a try. This got me thinking of another improvement... But it should not affect the operation, it will only reduce the User's interaction with the function of creating autounattend. After all, if you don't create a user, why ask for a password? Am I right?
Hi @inTerActionVRI did you know if removing WiFi Network Manager (WiFi Sense) cause issues in a laptop? Like not connecting to a Wireless network Just asking due the unavailability to test in a laptop, I keep this component due the fact I don't know if could cause some issues.
I use a laptop on a daily basis. I always remove it, never had any problems. Disabling ActionCenter (NotificationCenter) "this is a registry tweak" causes problems with displaying taskbar functions. Wifi, VolumeControl, clock none of them show their functions when clicked. I don't know if the removal of ClientCBS or some other component is related.
I forgot to say that before proceeding with the mount, if the image is not supported this message will appear. The one I sent yesterday was without color, but the message is present I posted today's update in the previous post. In the link below. https://forums.mydigitallife.net/threads/msmg-toolkit.50572/page-1286#post-1794123
@inTerActionVRI I also have a question: Which Windows edition is more preferred to be customized in MSMG: IoT LTSC 21H2 or Pro 21H2? As far as I know, in LTSC a lot of things such as MS Store, OneDrive and etc. are disabled and not removed, which means these things are hidden in registry and not completely removed in the way MSMG Toolkit does. So, when applying removal tweaks in Toolkit on IoT LTSC image the toolkit skips a lot of things cause it sees that these are not being present in the image cause these things are disabled already. And when doing removal on Pro, it sees that everything is enabled and it removes them the right way instead of skipping. Am I right? Or even when applying on LTSC it removes even though it skips components which Toolkit considers not being present in the image cause it were disabled? (sorry for my english, I'm not a native)
Just my 2 cents worth...I always disable notifcationcenter and I've never had a problem with taskbar/system tray icons/functions. But I've never tried to remove clientCBS either Disabling the ClipSvc will break those functions.
Following inTerActionVRI's MSMG Toolkit fix, I have updated the Ventoy-Power Ultimate Boot Disk II package to address the changes in MSMG Toolkit version 13.4 and also improve the graphical user interface of the guide. Going forward, updates will only occur when major new features are added to MSMG Toolkit and will be posted in this thread. As always, users' comments, feedback and corrections are welcome.
Hello. It is your Ventoy version? I thought default Ventoy supports booting from ISOs made in MSMG. I never had any problems booting my custom ISO from Ventoy. Can you explain for what exactly your version is intended?
I had and have this problem until today, only in windows 11, in builds 22000 and 22621 to 22631. It's best to leave Notification Center enabled. Could it be something particular to the ISOs in pt-BR? I don't know. It's up to test.
@MSMG , According to the original code, the three formats are as follows: 9 or less, more than 9, less than or equal to 99, and greater than 99. However, according to the original code, when I tried to select the source image, when there were more than 9 indexes, ToolKit crashed. I made a little change to this part of the code, in ToolKit v13.4 lines 24654~24661： from Code: if "%%b" neq "arm64" ( if %%a leq 9 echo.^| %%a ^| %%b ^|%%c>>%ImageInfo% if %%a gtr 9 if %%a lss 99 echo.^| %%a ^| %%b ^|%%c>>%ImageInfo% if %%a gtr 99 echo.^| %%a ^| %%b ^|%%c>>%ImageInfo% ) if "%%b" equ "arm64" ( if %%a leq 9 echo.^| %%a ^| %%b^|%%c>>%ImageInfo% if %%a gtr 9 if %%a lss 99 echo.^| %%a ^| %%b^|%%c>>%ImageInfo% if %%a gtr 99 echo.^| %%a ^| %%b^|%%c>>%ImageInfo% to Code: if "%%b" neq "arm64" ( if %%a lss 10 echo.^| %%a ^| %%b ^|%%c>>%ImageInfo% if %%a geq 10 if %%a lss 100 echo.^| %%a ^| %%b ^|%%c>>%ImageInfo% if %%a geq 100 echo.^| %%a ^| %%b ^|%%c>>%ImageInfo% ) if "%%b" equ "arm64" ( if %%a lss 10 echo.^| %%a ^| %%b^|%%c>>%ImageInfo% if %%a geq 10 if %%a lss 100 echo.^| %%a ^| %%b^|%%c>>%ImageInfo% if %%a geq 100 echo.^| %%a ^| %%b^|%%c>>%ImageInfo% Why +1 on the number of indexes (%%a) that limit is really just a simple math question.
Calm down, man! I provisionally made it available, because it wasn't fair that something I did, which was buggy, remains in your way. About autounattend.xml corrections were made considering the autounattend he provided. About the Support Warning message: about the added color and about where the message will remain displayed... We have to wait for the final word from the MSMG. After all, this can change according to his ideas.
Talking about warning message, why it appeared when I imported LTSC 2021 in your current test version?
Ventoy can boot any Windows ISO you put on it. My download just contains files that can configure Ventoy's interface to look the way it is pictured in my post as well as give guidance about using MSMG. I hope that helps.
Yes, I used Toolkit_TESTING. I just entered username with (S) command and applied that using (W). Any other steps like machine name, organization name - I skipped those. I'll send my autounattend.xml file tomorrow, since I need to recreate ISO again and don't have enough time for that at the moment. (btw, I tested it on LTSC iso, also pls could you check my previous question about Pro/LTSC thing, I need some clarity on that question)