I used uupdump, got only the Professional edition, no other editions on the iso. Gonna try the comoression
I compared 3 online systems after trying to install (via Settings) the "Wireless Display" component: 1) processed MSMG with Internet access but with disabled Windows Update 2) original with internet access 3) original without internet access The component I needed was successfully installed only on system #2. After that, using the command: Code: Dism /online /Get-Packages > C:\work\list.txt I determined that the packages Code: Package Identity : Microsoft-Windows-WirelessDisplay-FOD-Package~31bf3856ad364e35~amd64~ru-RU~10.0.22621.1 State : Superseded Release Type : OnDemand Pack Install Time : Package Identity : Microsoft-Windows-WirelessDisplay-FOD-Package~31bf3856ad364e35~amd64~ru-RU~10.0.22621.608 State : Installed Release Type : OnDemand Pack Install Time : 31.07.2023 15:40 Package Identity : Microsoft-Windows-WirelessDisplay-FOD-Package~31bf3856ad364e35~amd64~~10.0.22621.1 State : Superseded Release Type : OnDemand Pack Install Time : Package Identity : Microsoft-Windows-WirelessDisplay-FOD-Package~31bf3856ad364e35~amd64~~10.0.22621.1105 State : Installed Release Type : OnDemand Pack Install Time : 31.07.2023 15:40 present only in system #2. So, this is just such a "Modern" mechanism for installing components and MSMG has nothing to do with it. By the way, those components that can still be installed / removed from the Control Panel are installed without problems in all systems.
@MSMG If I add this option in the menu Code: echo. [D] Revert to Default the way I changed the script below will it work? Code: if /i "!MenuChoice!" equ "D" ( if "%ImageBuild%" geq "17763" if "%ImageBuild%" leq "19045" ( set "C_3DViewer=+" set "C_AdvertisingXaml=+" ) set "C_Alarms=+" if "%ImageBuild%" geq "22000" if "%ImageBuild%" leq "22631" set "C_BingNews=+" set "C_BingWeather=+" if "%C_DesktopAppInstaller%" neq "*" set "C_DesktopAppInstaller=+" set "C_CalculatorApp=+" set "C_Camera=+" if "%ImageBuild%" geq "22000" if "%ImageBuild%" leq "22631" set "C_ClientWebExperience=+" if "%ImageBuild%" geq "22621" if "%ImageBuild%" leq "22631" set "C_Clipchamp=+" set "C_CommunicationsApps=+" if "%ImageBuild%" geq "19041" if "%ImageBuild%" leq "22631" set "C_Cortana=+" if "%ImageBuild%" geq "22621" if "%ImageBuild%" leq "22631" set "C_Family=+" set "C_FeedbackHub=+" set "C_GetHelp=+" set "C_Getstarted=+" set "C_HEIFImageExtension=+" if "%ImageBuild%" geq "22621" if "%ImageBuild%" leq "22631" set "C_HEVCVideoExtension=+" set "C_Maps=+" if "%ImageBuild%" geq "17763" if "%ImageBuild%" leq "18363" set "C_Messaging=+" if "%ImageBuild%" geq "17763" if "%ImageBuild%" leq "19045" if "%ImageArchitecture%" equ "x64" set "C_MixedRealityPortal=+" if "%ImageBuild%" equ "17763" if "%C_NETNativeFramework16%" neq "*" set "C_NETNativeFramework16=+" if "%ImageBuild%" geq "17763" if "%ImageBuild%" leq "19045" if "%C_NETNativeFramework17%" neq "*" set "C_NETNativeFramework17=+" if "%ImageBuild%" geq "18362" if "%ImageBuild%" leq "22631" if "%C_NETNativeFramework22%" neq "*" set "C_NETNativeFramework22=+" if "%ImageBuild%" equ "17763" if "%C_NETNativeRuntime16%" neq "*" set "C_NETNativeRuntime16=+" if "%ImageBuild%" geq "17763" if "%ImageBuild%" leq "19045" if "%C_NETNativeRuntime17%" neq "*" set "C_NETNativeRuntime17=+" if "%ImageBuild%" geq "18362" if "%ImageBuild%" leq "22631" if "%C_NETNativeRuntime22%" neq "*" set "C_NETNativeRuntime22=+" if "%ImageBuild%" geq "22000" if "%ImageBuild%" leq "22631" set "C_NotepadApp=+" set "C_OfficeHub=+" if "%ImageBuild%" geq "17763" if "%ImageBuild%" leq "19045" set "C_OfficeOneNote=+" if "%ImageBuild%" geq "17763" if "%ImageBuild%" leq "18363" set "C_OneConnect=+" if "%ImageBuild%" geq "22000" if "%ImageBuild%" leq "22631" set "C_Paint=+" if "%ImageBuild%" geq "17763" if "%ImageBuild%" leq "19045" set "C_Paint3D=+" set "C_People=+" set "C_Photos=+" if "%ImageBuild%" geq "17763" if "%ImageBuild%" leq "18363" set "C_Print3D=+" if "%ImageBuild%" geq "22000" if "%ImageBuild%" leq "22631" set "C_PowerAutomateDesktop=+" if "%ImageBuild%" geq "22621" if "%ImageBuild%" leq "22631" ( set "C_QuickAssist=+" set "C_RawImageExtension=+" ) set "C_ScreenSketch=+" if "%ImageBuild%" geq "17763" if "%ImageBuild%" leq "19045" ( set "C_ServicesStoreEngagement=+" set "C_SkypeApp=+" ) set "C_SolitaireCollection=+" set "C_SoundRecorder=+" set "C_StickyNotes=+" set "C_StorePurchaseApp=+" if "%ImageBuild%" geq "22000" if "%ImageBuild%" leq "22631" ( set "C_Terminal=+" set "C_Todos=+" ) if "%ImageBuild%" geq "18362" if "%ImageBuild%" leq "19045" if "%C_UIXaml20%" neq "*" set "C_UIXaml20=+" if "%ImageBuild%" geq "22000" if "%ImageBuild%" leq "22631" if "%C_UIXaml24%" neq "*" set "C_UIXaml24=+" if "%ImageBuild%" geq "22621" if "%ImageBuild%" leq "22631" if "%C_UIXaml27%" neq "*" set "C_UIXaml27=+" if "%C_VCLibs140UWP%" neq "*" set "C_VCLibs140UWP=+" if "%ImageBuild%" geq "18362" if "%ImageBuild%" leq "22631" if "%C_VCLibs140UWPDesktop%" neq "*" set "C_VCLibs140UWPDesktop=+" set "C_VP9VideoExtensions=+" if "%ImageBuild%" geq "17763" if "%ImageBuild%" leq "19045" set "C_Wallet=+" set "C_WebMediaExtensions=+" set "C_WebpImageExtension=+" if "%C_WindowsStore%" neq "*" set "C_WindowsStore=+" if "%C_XboxApp%" neq "*" set "C_XboxApp=+" set "C_XboxGameOverlay=+" set "C_XboxGamingOverlay=+" if "%C_XboxIdentityProvider%" neq "*" set "C_XboxIdentityProvider=+" set "C_XboxSpeechToTextOverlay=+" set "C_XboxTCUI=+" set "C_YourPhone=+" set "C_ZuneMusic=+" set "C_ZuneVideo=+" )
I see these three cumulative updates on Microsoft catalog after the supported Windows 11 22h2 version. Cumulative Update for Windows 11 for x64-based Systems (KB5028182) Cumulative Update Preview for Windows 11 for x64-based Systems (KB5028245) Cumulative Update Preview for Windows 11 Version 22H2 for x64-based Systems (KB5028254) 1. Do I need to download them all in order and install one by one or just integrate the latest one? 2. Do I need to integrate .NET updates too(there are so many) or just ignore them? 3. What's the proper way to install these updates? I've struggled with them in the past and would like to know the exact steps to avoid a bad install again. Thank you!
Back in late May I asked about the Audio Console for Realtek and @MSMG kindly provided the package name for me. Well, I've been so busy with things I haven't had a chance to try it until today. I used the following command to install, and it took less than a second. Spoiler: DISM DISM.exe /Online /Add-ProvisionedAppxPackage /PackagePath:RealtekSemiconductorCorp.RealtekAudioControl_1.41.294.0_neutral_~_dt26b99r8h8gj.AppxBundle /DependencyPackagePath:Microsoft.VCLibs.140.00_14.0.30704.0_x64__8wekyb3d8bbwe.Appx /skiplicense It responds that it completed successfully. When I attempt to run the audio console it crashes immediately upon attempt to open. Given I removed almost everything using toolkit v13.3 when the ISO was created, I'm wondering if I may have removed something the audio console uses? I've also just built a new PC for myself:MSI Z790 Ace, 64GB DDR5-6400CL32 RAM, 4x2TB Kingston PCIe4 SSD, RTX 3080 Ti GPU, Corsair H150i cooler, HX1200i PSU, The motherboard is using an ALC 4082 codec and I've installed the USB Audio drivers from the MSI website.
@MSMG, @inTerActionVRI, I tested the latest Toolkit.cmd, and here are my findings and suggestions: I changed the default color to black background and white text from the options, however, when line coloring is used, it breaks the main settings (see attachment - this happens as soon as I load a menu with line coloring added), and as soon as I enter an option, the background will be reset to blue. Additionally, whenever I enter a sub menu and press Enter (without any input specified), it automatically exists that sub menu. I can hit Enter after I have input a valid option, and then it will not exit the same sub menu. I personally think the background colors are not so much user friendly - they are a bight to bright and not "matching" (blue, green, pink). I would suggest to have the default background color set as black everywhere, and where you have now the green background text for "Compatibility", the background should still be black, but the text should be green. Similarly the "Depends On" should be black background and red text, and wherever you have warning added, it should also look like that. "Depends On" and "Compatiblity" could also be fully capitalized, and perhaps the extra spacing could be removed. In short: exchange the background color to text color and keep a matching background everywhere. The gray background for the text right next to the option is OK actually, just because it should be a bit more noticeable. There is just too much color included, and generally speaking a black background always works and is mostly used in command line-based applications, such as this one. And the full line background color for this additional text feels also weird (it should be exactly as wide as the text, or maybe 1 extra character before and after, kindly like how it is with the component titles, but as soon as you resize the window, it goes for the whole line). Additionally, you could reduce the length of the option list by skipping the empty lines as the different colors are already work as separators. Without a doubt all this would take quite some effort again, but it would be so much more appealing to the eye in my opinion.
Just an example: People with color blindness cannot see red letters on a black background. The color scheme has to be well contrasted to suit everyone. As for the background to be completely black again, you forgot to finish the line with the default color. At the beginning of a line there must be the foreground and background color at the end of that same line there must be the respective colors for reset. 0m is the default black background and white lettering. In the case of the toolkit you have to check what the reset values are, go to the end of a line that you haven't changed and check it out. If you want several subsequent lines to be the same color put the reset only at the end of the last line of that block of echoes.
I did not change colors by editing, I was using the Toolkit's options, which are now seemingly rendered unusable. I understand the concern about the color blind, although I do not have the experience to comment on. These colors are making my eyes burn, but it's fine, because I do not need to use the Toolkit often.
From what users are reporting this is happening ramdomically. Really, I was even thinking that it was solved with the version that MSMG released yesterday. Bala1 who had had this problem, said that it was no longer happening. But today it happened to you. If you're using yesterday's toolkit.cmd testing version, then this color scheme has become very unstable. Perhaps it is consuming too much memory. I have 20gb DDR4. So considering the memory, maybe it is why I had no problems with scrolling through the menus. Perhaps more people with up to 8Gb RAM will bring their feedback on this. Since I started using dark themes I started to realize how bad light colors are for me too.
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.