I am actually using the Toolkit from a VM (with a system I created with an earlier version of the Toolkit), which only has 4GB configured. Currently it is apply the changes to the image, but the system's memory usage (in Task Manager) is only 1.4GB. The Toolkit.cmd is the latest one uploaded to the website, dated yesterday. Maybe some more effort for you then: at the startup of the toolkit, ask whether colorblind mode is needed, and if not, make everything dark, permanently ;-)
@MSMG will see our conversation and will probably verify this. I'll think about it and how it goes on IMCK.
@MSMG, echo. [33] %C_UIXaml20% [47m[30m Microsoft UI Xaml 2.4 ^(Microsoft.UI.Xaml.2.4^) echo. [34] %C_UIXaml20% [47m[30m Microsoft UI Xaml 2.7 ^(Microsoft.UI.Xaml.2.7^) The variables shoud be respectively changed to C_UIXaml24 and C_UIXaml27? The present Code: [47m[30m can be: Code: [106m[30m Than you need to check the conflict colors like BackGround with BackGround. Below some example of that so, this: Code: [47m [40m should be: Code: [47m[30m This: Code: [47m[42m should be: Code: [47m[32m This: Code: [47m[105m should be: Code: [47m[95m Note: here ascii chars dont show up. begining with 4 or 10 are background begining with 3 or 9 are foreground 4 and 3 are the normal ones 10 and 9 are the light ones Code: set "B_Black=[40m" set "F_Black=[30m" set "B_Red=[41m" Normal set "F_Red=[31m" Normal set "B_Green=[42m" Normal set "F_Green=[32m" Normal set "B_Yellow=[43m" Normal set "F_Yellow=[33m" Normal set "B_Blue=[44m" Normal set "F_Blue=[34m" Normal set "B_Mag=[45m" Normal set "F_Mag=[35m" Normal set "B_Cyan=[46m" Normal set "F_Cyan=[36m" Normal set "B_White=[47m" Light Gray set "F_White=[37m" Light Gray set "B_DGray=[100m" Dark Grey set "F_DGray=[90m" Dark Grey set "B_LRed=[101m" Light set "F_LRed=[91m" Light set "B_LGreen=[102m" Light set "F_LGreen=[92m" Light set "B_LYellow=[103m" Light set "F_LYellow=[93m" Light set "B_LBlue=[104m" Light set "F_LBlue=[94m" Light set "B_LMag=[105m" Light set "F_LMag=[95m" Light set "B_LCyan=[106m" Light set "F_LCyan=[96m" Light set "B_BWhite=[107m" Bright White set "F_BWhite=[97m" Bright White Note: here is missing the ESC ascii char.
Can you make the Registry tweaks from the menu be pre-selectable before applying each individually? I don't use all of them, so now I need to go over them one by one, since they are applied immediately. It would nice if it would work the same way Component Removal does, and there should be a 3rd option within the same menu after you selected everything to start applying the changes accordingly. Furthermore, while I disabled the Compatibility mode entirely, even with careful attention it seems I am breaking the search option is start menu, and the only thing I see marked related is Windows Search, which I did not select for removal. The Start Menu components are also kept, so I am not sure where I am making the mistake - and I think it is not listed somewhere as needed for Search to function (in Start Menu). Instead of "Recommended", there should be a separate option for Start Menu, that does not touch Start Menu and searching in Start Menu, because if you can't search there, it is broken in my opinion. And since there is an option to let everything be removed, it should not cause too much of a trouble, I believe. Fyi, I managed to acquire a 19041.1 .iso, so I am working with that now. Previously (working with the official 19044.1288 Home/Pro image) I was not facing this problem when I was selecting stuff individually. So probably I might have made a mistake here, but I just do see what - and working with 4 Editions (Home, Home N, Pro, Pro N) for the 3rd time is starting to feel like taking forever. When I go back to the Compatibility menu after I have selected components for removal but before removing them, adding back the compatibility option does not seem to override the selections with * (star). I wanted to add back Shell Search - assuming that could be related to the above -, but I did not see the * anywhere. It was just a quick test, I can do more later, but maybe you could check on it as well, please.
I went through this problem. Because there are interlocks as you enable or disable something. I got around this problem by creating redundancy before going back to the Select Components menu. Tomorrow I'll send the code here. Now it's already 3 am. @MSMG, a suggestion... I think it's interesting to put the [C] Compatibility option right above the [1] Internet Menu option It would be more intuitive.
@MSMG I was trying to add the Realtek Audio Console to my live installation Cant get that working so I will try to integrate it via the toolkit, along with a bunch of other appx extensions. The below shows the files I am using. But it doesn't seem to be working. Are these the correct files? Spoiler: APPX files Microsoft.HEIFImageExtension_1.0.61171.0_neutral__8wekyb3d8bbwe.appxbundle Microsoft.HEVCVideoExtension_2.0.61931.0_neutral__8wekyb3d8bbwe.appxbundle Microsoft.MPEG2VideoExtension_1.0.50901.0_x64__8wekyb3d8bbwe.Appx Microsoft.VCLibs.140.00_14.0.32530.0_x64__8wekyb3d8bbwe.Appx Microsoft.VCLibs.140.00_14.0.32530.0_x86__8wekyb3d8bbwe.Appx Microsoft.VP9VideoExtensions_1.0.61591.0_neutral__8wekyb3d8bbwe.appxbundle Microsoft.WebMediaExtensions_1.0.61591.0_neutral__8wekyb3d8bbwe.appxbundle Microsoft.WebpImageExtension_1.0.62011.0_neutral__8wekyb3d8bbwe.AppxBundle RealtekSemiconductorCorp.RealtekAudioControl_1.44.302.0_neutral__dt26b99r8h8gj.AppxBundle Spoiler: Sample DISM Error ------------------------------------------------------------------------------- Integrating Google's VP9 WebM Video Codec Plugin Provisioned Appx Package... ------------------------------------------------------------------------------- Error: 87 The /PackagePath: option is missing a required argument. For more information, refer to the help for the /PackagePath: option. The DISM log file can be found at H:\msmg135\Logs\Dism.txt extensions.quarantinedDomains.enabled Spoiler: DISM log 2023-08-04 12:19:28, Error DISM DISM.EXE: Failed validating command line: H:\msmg135\Bin\x64\DISM10\Dism.exe /English /ScratchDir:H:\msmg135\Temp\DISM /LogPath:H:\msmg135\Logs\Dism.txt /LogLevel:3 /NoRestart /Image:H:\msmg135\Mount\Install\1 /Add-ProvisionedAppxPackage /PackagePath: /DependencyPackagePath:H:\msmg135\Packs\Apps\w10\Microsoft.VCLibs.140.00_14.0.32530.0_x64__8wekyb3d8bbwe.Appx /LicensePath:H:\msmg135\Bin\AppLicense\Microsoft.VP9VideoExtensions_8wekyb3d8bbwe.x64.xml The packagepath is not populated for the following... Spoiler: Failed integrations Microsoft.HEIFImageExtension_1.0.61171.0_neutral__8wekyb3d8bbwe.appxbundle Microsoft.HEVCVideoExtension_2.0.61931.0_neutral__8wekyb3d8bbwe.appxbundle Microsoft.VP9VideoExtensions_1.0.61591.0_neutral__8wekyb3d8bbwe.appxbundle Microsoft.WebpImageExtension_1.0.62011.0_neutral__8wekyb3d8bbwe.AppxBundle ...some time later... If I understand things correctly, the problem is related to the fact that the extensions are .appxbundle and not.appx. Let's take HEIF as an example; Changing line 9735 from Code: for /f %%i IN ('"dir /b *HEIFImageExtension*%ImageArchitecture%*.appx" 2^>nul') do if exist %%i set "HEIFImageExtension_Appx=%Apps%\%%i" to Code: for /f %%i IN ('"dir /b *HEIFImageExtension*.*xbundle" 2^>nul') do if exist %%i set "HEIFImageExtension_Appx=%Apps%\%%i" Appears to fix the problem. And for the most part these extensions seem to be architecture neutral. So there were two changes needed to that line of code. Can someone please verify I'm on the right track. Once confirmed I'll go and change the 4 lines of code to cater for the .appxbundle files and build my image. Also, just follow my logic here; if my observations are correct, and no one has detected this previously then one must wonder if anyone is using these extensions, which then makes me wonder, do I really need to integrate them at all?
Getting the following error: "The selected source image build does not support custom component removal, However it supports DISM component removal. For component removal, use Remove Windows Components using Package List (DISM Method) menu." Any ideas? Never seen it happen before.
Just check the Toolkit changelog or readme for the supported builds. When there was no such message people kept using unsupported ISOs. That's why the alert was placed.
Why in v13.5 i see only "[1] Remove Windows Components Using Package List" in "Remove Menu"? P.S. Will try another ISO.
@MSMG, in 65 option, C_GamingApp is missing. from: Code: if "%%#" equ "65" if "%C_XboxApp%" neq "*" ( if "%C_XboxApp%" equ "+" ( set "C_XboxApp=-" set "C_XboxGameOverlay=-" set "C_XboxGamingOverlay=-" if "%C_XboxIdentityProvider%" neq "*" set "C_XboxIdentityProvider=-" set "C_XboxSpeechToTextOverlay=-" set "C_XboxTCUI=-" ) else ( if "%ImageBuild%" equ "17763" ( if "%C_NETNativeFramework16%" neq "*" set "C_NETNativeFramework16=+" if "%C_NETNativeRuntime16%" neq "*" set "C_NETNativeRuntime16=+" ) if "%ImageBuild%" geq "18362" if "%ImageBuild%" leq "19045" ( if "%C_NETNativeFramework17%" neq "*" set "C_NETNativeFramework17=+" if "%C_NETNativeRuntime17%" neq "*" set "C_NETNativeRuntime17=+" ) if "%C_VCLibs140UWP%" neq "*" set "C_VCLibs140UWP=+" set "C_XboxApp=+" if "%C_XboxCore%" neq "*" set "C_XboxCore=+" ) ) to: Code: if "%%#" equ "65" ( if "%C_XboxApp%" neq "*" if "%ImageBuild%" geq "17763" if "%ImageBuild%" leq "19045" ( if "%C_XboxApp%" equ "+" ( set "C_XboxApp=-" set "C_XboxGameOverlay=-" set "C_XboxGamingOverlay=-" if "%C_XboxIdentityProvider%" neq "*" set "C_XboxIdentityProvider=-" set "C_XboxSpeechToTextOverlay=-" set "C_XboxTCUI=-" ) else ( if "%ImageBuild%" equ "17763" ( if "%C_NETNativeFramework16%" neq "*" set "C_NETNativeFramework16=+" if "%C_NETNativeRuntime16%" neq "*" set "C_NETNativeRuntime16=+" ) if "%ImageBuild%" geq "18362" if "%ImageBuild%" leq "19045" ( if "%C_NETNativeFramework17%" neq "*" set "C_NETNativeFramework17=+" if "%C_NETNativeRuntime17%" neq "*" set "C_NETNativeRuntime17=+" ) if "%C_VCLibs140UWP%" neq "*" set "C_VCLibs140UWP=+" set "C_XboxApp=+" if "%C_XboxCore%" neq "*" set "C_XboxCore=+" ) ) if "%C_GamingApp%" neq "*" if "%ImageBuild%" geq "22000" if "%ImageBuild%" leq "22631" ( if "%C_GamingApp%" equ "+" ( set "C_GamingApp=-" set "C_XboxGameOverlay=-" set "C_XboxGamingOverlay=-" if "%C_XboxIdentityProvider%" neq "*" set "C_XboxIdentityProvider=-" set "C_XboxSpeechToTextOverlay=-" set "C_XboxTCUI=-" ) else ( if "%ImageBuild%" geq "22000" if "%ImageBuild%" leq "22631" ( if "%C_NETNativeFramework22%" neq "*" set "C_NETNativeFramework22=+" if "%C_NETNativeRuntime22%" neq "*" set "C_NETNativeRuntime22=+" ) if "%C_VCLibs140UWP%" neq "*" set "C_VCLibs140UWP=+" set "C_GamingApp=+" if "%C_XboxCore%" neq "*" set "C_XboxCore=+" ) ) ) Note: I assumed that for w11 GamingApp these components in else, should look like this: Code: ) else ( if "%ImageBuild%" geq "22000" if "%ImageBuild%" leq "22631" ( if "%C_NETNativeFramework22%" neq "*" set "C_NETNativeFramework22=+" if "%C_NETNativeRuntime22%" neq "*" set "C_NETNativeRuntime22=+" ) But I don't know if it's right. Please take care of this part. and in WindowsApps Menu if /i "!MenuChoice!" equ "A" ( from: Code: if "%C_XboxApp%" neq "*" set "C_XboxApp=-" to: Code: if "%C_XboxApp%" neq "*" if "%ImageBuild%" geq "17763" if "%ImageBuild%" leq "19045" set "C_XboxApp=-" if "%C_GamingApp%" neq "*" if "%ImageBuild%" geq "22000" if "%ImageBuild%" leq "22631" set "C_GamingApp=-"
@tempdrive1, This is the redundant exit recheck code for X option on ComponentsCompatibilityMenu : Code: if /i "%%#" equ "X" ( :: Recheck Filter if "%CC_ApplicationGuardContainers%" equ "-" if "%CC_Hyper-V%" equ "-" set "C_RemoteDesktopServer=+" if "%ImageBuild%" geq "19041" set "C_InputApp=*" if "%CC_Recommended%" equ "-" ( if "%CC_MicrosoftOfice%" equ "-" if "%CC_TouchScreenDevices%" equ "-" if "%ImageBuild%" geq "17763" if "%ImageBuild%" lss "19041" set "C_InputApp=+" if "%CC_OOBE%" equ "-" ( if "%CC_MicrosoftStore%" equ "-" set "C_CloudExperienceHost=+" if "%ImageBuild%" lss "19041" set "C_UndockedDevKit=*" if "%ImageBuild%" equ "17763" set "C_WindowsErrorReporting=*" if "%ImageBuild%" geq "19041" if "%ImageBuild%" leq "22631" set "C_WindowsErrorReporting=*" ) if "%CC_VisualStudio%" equ "-" ( if "%ImageBuild%" lss "22000" set "C_EdgeWebView=*" if "%ImageBuild%" geq "22000" if "%ImageBuild%" leq "22631" set "C_EdgeWebView=+" ) if "%ImageBuild%" equ "17763" set "C_StartMenuExperienceHost=*" ) if "%CC_Printing%" equ "-" if "%C_PrintDialog%" equ "-" set "C_PrintDialog=+" if "%CC_ShellSearch%" equ "-" if "%ImageBuild%" geq "19041" set "C_Cortana=+" if "%CC_TouchScreenDevices%" equ "-" ( if "%CC_ModernAppSupport%" equ "-" ( set "C_VCLibs140UWP=+" if "%ImageBuild%" equ "17763" set "C_VCLibs140UWPDesktop=*" if "%ImageBuild%" geq "18362" if "%ImageBuild%" leq "22631" set "C_VCLibs140UWPDesktop=+" ) ) if "%CC_XboxApp%" equ "-" ( if "%ImageBuild%" geq "20000" set "C_XboxApp=*" if "%ImageBuild%" lss "22000" set "C_GamingApp=*" if "%ImageBuild%" geq "17763" if "%ImageBuild%" leq "19045" set "C_XboxApp=+" if "%ImageBuild%" geq "22000" if "%ImageBuild%" leq "22631" set "C_GamingApp=+" ) goto :SelectWindowsComponentsMenu ) ) goto :ComponentsCompatibilityMenu ::-------------------------------------------------------------------------------------------
@MSMG I have spotted an issue with that I didn't see during my previous testing when posting here. The Gaming option has returned in Settings, although I believed I removed it with my RemovePkgsList.txt list. Spoiler: RemovePkgsList.txt GameExplorer WalletService OneDrive MapControl PeopleExperienceHost RetailDemoContent SecureAssessmentBrowser SkypeORTC WindowsMixedReality XboxClient XboxGameCallableUI 3DViewer AdvertisingXaml Alarms BingWeather CalculatorApp Camera CommunicationsApps Cortana FeedbackHub GetHelp Getstarted HEIFImageExtension Maps MixedRealityPortal OfficeHub OfficeOneNote Paint3D People Photos ScreenSketch SkypeApp SolitaireCollection SoundRecorder StickyNotes StorePurchaseApp VP9VideoExtensions Wallet WebMediaExtensions WebpImageExtension XboxApp XboxGameOverlay XboxGamingOverlay XboxIdentityProvider XboxSpeechToTextOverlay XboxTCUI YourPhone ZuneMusic ZuneVideo I shall retest when I have more time to ensure I followed my method correctly. Edit I have quickly done some checks and I think I have found the problem - some of the app names for removal with ToolKitHelper.exe have changed. Can somebody please confirm that the below are correct. I have formatted OldAppName=NewAppName to avoid confusion. WindowsStoreClient = WindowsStoreCore XboxClient = XboxCore WindowsStoreApp = WindowsStore There may be more, but these are what I can see for my 10 list for now. I shall update my list tomorrow, when I have more time.
Thank you for your efforts. My real issue is the broken Start Menu search, however, and I was able to narrow it down to the Remove Windows Apps Menu (it was working until I started removing stuff from there). I was removing everything with the earlier Menu structure, and looks like now my whole day will be spent on finding the differences between old and new unfortunately and explicitly pointing out what breaks it. Keeping only Microsoft .NET Native Framework Package 1.7, Microsoft .NET Native Framework Package 2.2, Microsoft .NET Native Runtime Package 1.7, Microsoft .NET Native Runtime Package 2.2, Microsoft UI Xaml 2.0, Microsoft Visual C++ 2015 UWP Runtime Package and Microsoft Visual C++ 2015 UWP Desktop Runtime Package did not resolve the issue, even though those were the most outstanding and new list items. Already on the latest version of Toolkit.cmd by the way. Additionally, and it would be nice if there was an inidication which .iso is being extracted, because I can use * (star) without issues if I have multiple .iso files in the folder.
Explain a little better this use of * (asterisk) and the relationship with the number of ISOs in the folder. I see no relationship between one thing and the other. Note 1: I have my mind fixed on the * (asterisks) in the Compatible Menu (If you retain the compatible menu with + sign, the components related with that options will remain with the asterisk sign and staying blocked for removal). When you change in compatible menu to - sign, the components will change the sign frim * to +. so anyway you will need to select them for removal. If you can remove components with * sign, please inform whats components are not be blocked. Note 2: When removing via lists, there is no such filter unless an option is added to read the user's list. @Feartamixg, this would be very good for you to work with just a generic list for w10 and w11 for example. Keep the Search option from the compatible menu with the + sign.
As per the last post, by * I only refer to extracting .iso data. So * picks up any naming pattern in the ISO folder when using Toolkit menu 1 [ Source ] - 3 [ Extract Source from DVD ISO Image ] I always have been lazy to enter the .iso filename, so I just used * and it worked - but it also works with multiple .iso files inside Toolkit ISO folder, which should raise some concerns. I assume that the first found filename will be used for extraction, but I was too lazy with verifying this as the other, real issue keeps me occupied. I will need a solid base to make progress with my project, which I do not have right now. So, as for the broken Start Menu search, I managed to make some progress in backtracking the issue, and it appears that it originates from v13.4. The last image I created was actually with v13.3, which still works fine doing the same things (and by same I mean taking back an image with 1-5 menu option component removal and then using Remove Windows Apps Menu in v13.3; so 13.4+ seems to break Start Menu search if I fully clear Remove Windows Apps Menu) I will be soon ready with the proper diagnosis - need a few more hours as I have to create several more images and compare the changes between v13.3 and v13.4 if they are originating from Toolkit.cmd. FYI, I have not incorporated the code you have posted last time as it makes little to no difference right now, nor did I have time to review it. I assume it forces back the * option for the Component Removal prevention if I would revisit the Compatibility options. If so, it should be included in Toolkit.cmd as soon as possible. I am also checking on newer releases and I am using the latest one currently, however, it seems to be irrelavant for resolving the broken Start Menu search as of now. Your efforts are highly appreciated nonetheless.