Any answer to this question I asked previously? On a couple of recent Windows 11 builds where I used Toolkit's package removal list or checked off item removals from the menu instead of DISM, I have ended up with a file in the Windows sources folder called "gatherthestate.exe", which replaces everything else that was in that folder execept install.wim and pid.txt. This prevents me from modifying my $OEM$ entries. Any idea of what causes this behavior and how to avoid it?
What recent builds? After 22631 build? When you first asked I looked it up, but this is something relatively new. I even thought it could be some malware like Ransonware. But I didn't find anything significant. We have to wait... If anyone has any more information. Will respond. I'm also curious about this.
May be its the gatherosstate.exe file which is retained when you remove the ManualSetup component, this file is related to Free upgrade of your license from Windows 7/8.1 to Windows 10/11.
Okay thanks. I also thought it is because of my custom regfiles I used to apply but when I ditched them issue persist. Also tried multiple times and with multiple options in autounnatend and literally spend all day with this issue and no luck. Hope you will help.
When the ISO folder is empty, the Toolkit gives the below error and waits for the user action Code: =============================================================================== MSMG ToolKit - Extract Source from DVD ISO Image to <DVD> folder =============================================================================== Toolkit's Source <DVD> folder is not empty... Do you want to remove it & continue ? ['Y'es/'N'o] : Y DVD ISO Image folder <ISO> is empty... Please copy DVD ISO Images to <ISO> folder... =============================================================================== Press any key to continue . . . When the ISO filename entered is not found, the Toolkit gives the below error message and waits for the user action Code: =============================================================================== MSMG ToolKit - Extract Source from DVD ISO Image to <DVD> folder =============================================================================== Toolkit's Source <DVD> folder is not empty... Do you want to remove it & continue ? ['Y'es/'N'o] : Y ------------------------------------------------------------------------------- ####Starting Extracting Source from DVD ISO Image to <DVD> folder############## ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- ####Getting DVD ISO Image Options############################################## ------------------------------------------------------------------------------- Enter the ISO Image filename without .iso : Windows11_InsiderPreview_Client_x64 Can't find the specified DVD ISO Image in <ISO> folder... Please enter the correct DVD ISO Image filename... =============================================================================== Press any key to continue . . . A message with full file path entered can be added, it will added in next version. Regarding the Tweaks / Components / Apply section automatically returning to main menu without the user interaction, will check if there's anything need to be fixed.
After the error, can you bring to us the Windows\Panther folder? Create a zip from that folder and attach it here. We can more easily identify the problem with the logs. Try to use your autounattend with untouched ISO or make an ISO with no reg tweaks. Check your reg files for CurrentControlSet and replace all of them for ControlSet001.
Hi @MSMG, After some testing based on your reply, I think I was able to reproduce the issue: when the text "Press any key to continue . . ." is displayed for the "pause" command, if I press the up (or any other) arrow on the keyboard, the next time this message will be displayed, it will be skipping it immediately, as if there would be an extra key press in the buffer or something. This is most likely the issue in other places as well, as I tend to use the up arrow unconsciously a lot for such messages, and I am not sure if anything can be done about it from a technical point. Just tested it with a .bat having this only command two times in it, and the second is skipped. I have never noticed this behavior before. Apologies for the extra trouble. The full path displayed in case an invalid path is provided would still be appreciated.
@MSMG I have put the registries that I want to insert into the ISO in C:\Users\DFA\Desktop\Toolkit_v13.4\Custom\Registry\w10 but I can't find the option to embed them. Thank you
Long path... Use short path like C:\MSMG This is to avoid errors when start removing components. To import your reg files the option is in Customize Menu.
You need to read this very carefully. You may need alternatives for the broken features like StartMenu, SearchApp, etc. I understood that the Start Menu only breaks in W11. But I'm not sure of the behavior on W10. Who knows MSMG, may say more about it in the future. I believe that the removal of these components still needs testing. I will do the test, but I will not remove all these recently added components for removal. This is very experimental. For the autounattend test I will only remove the CloudExperienceHost component. I have a specific point to make about autounattend. Did you leave, in addition to the machine name, any other fields empty? For example: empty password field? I was here thinking that if I leave the password empty, it may be necessary to activate AutoLogon. Also, testing required.
We have to wait... If anyone has any more information. Will respond. I'm also curious about this.[/QUOTE] @inTerActionVRI. Yes. That must be the culprit. Thanks. EDIT: Sorry to quick at the keyboard. MSMG provided the answer.
MSMG provided that answer for you. https://forums.mydigitallife.net/threads/msmg-toolkit.50572/page-1278#post-1792852 Hope it can clarify something.
@o0o01zr0dy, I ran into a problem similar to yours related to AutoUnattend.xml. I'm already sending a modification to @MSMG, attached here. Please check if the AutoUnattend.xml generated in this version solves the problem you are having? I tested removing everything and putting all the steps you mentioned. I only kept: ClientCBS ShellExperienceHost StartMenuExperienceHost UndockedDevKit I integrated Custom Files with a Dark Theme and there respective Tweaks. Spoiler: Screenshots
Removing ShellExperienceHOST also breaks Start menu for Windows 10 v1809 17763, From Windows 10 v1903 it was separated into StartMenuExperienceHost.