Yes brother you are right I checked the removal list and i saw that there is new item on the list which is "StartMenuExperienceHost" I think i should not remove it , i will try again Thank you so much
i just want to make a clean AF msmg build of the new windows enterprise LTSC 2021 iso. I usually skip updates or only install security fixes or security updates.
hi, @MSMG thank you for answering my question sir, I am very greatful. for others. make your custom images. when a new version of windows 10/11 getts released, customize that iso. when new components are added. perform a inplace upgrade using the customized iso. should be okay. Majid
@MSMG, So from what I understand, our discussion could be beneficial for your work, which is good news! Do you think you can do something about WMR and RDC Resetbase issues? I have finished what I wanted for my script and it looks stable enough, but I have not been looking into further testing on possible Resetbase fixes that would work for everyone (normal update deployment and my preferred way). I should be able to proceed with it these days. The below part is not so important, please feel free to ignore it. Spoiler As I cannot see inside your black box, it is difficult to understand what you are exactly doing even with your descriptive wording. The Readme.txt specifies twice about the requirement of source image with specific CU integrated is needed for component removal. This is what I found in readme.txt: Windows 10 v1809/v1909/v2004/v20H2/v21H1/v21H2/v22H2, Windows 11 v21H2/v22H2 - Component Removal requires a source image with supported cumulative update integrated. Taking the changelog into account as well, where you specify for each month the CU support, which is built up on the previous releases (hence cumulative) literally tells me that everything that you tested for earlier updates has to work for the latest release of yours as well: The ToolkitHelper contains only the list of files and registry keys to removed or modified and the functions to execute that list This is exactly what I was talking about it in one of my latest post with the XML stuff: - You already tested the CUs from the past as per the changelog, this implies that no restesting is needed - These Registry keys and files are pretty much a fixed list (minor additions to be expected when they get updated, but as I wrote, the changes would be pretty much all the time within the files themselves or under the keys that you are already touching, so the impact should be negligible) Again, let me show one of the many ways this could be handled, I will try to use an example as much explicit as possible, but the values referenced are pure fictional and should not be used for any purpose by anyone: <BulildNumberMin>19044</BulildNumberMin> <BulildNumberMax>19045</BulildNumberMax> <MinimumPatchVersion>1</MinimumPatchVersion> <MaximumPatchVersion>3086</MaximumPatchVersion> <Component>WindowsMixedReality</Component> <ToolkitActionList> <1>reg delete HKLM:\TK_COMPONENTS\CanonicalData\Deployments\dual_percep..nsixdof.inf_31bf3856ad364e35_10.0.19041.1*</1> <2>reg delete HKLM:\TK_COMPONENTS\DerivedData\Components\amd64_dual_perceptionsimulationsixdof.inf_31bf3856ad364e35_10.0.19041.*</2> <3>rmdir /s /q c:\TK\mount\1\windows\amd64_dual_perceptionsimulationsixdof.inf_31bf3856ad364e35_10.0.19041.*</3></ToolkitActionList> You test it for each month's CU, and when it passes, you add store the MaximumPatchVersion to support that CU, while it also reflects the past. If something is added only recently by you for removal, you do a conditional check as part of the step added to ToolkitActionList, which makes it backward compatible, where the data did not exist. When I perform the cleanup (removal of the newly added or re-added components), I refer to fixed paths - versioning, which can be dynamic in the name does not matter when using pattern matching, it works for any version. When a component gets a new Registry path as part of the enhancements, I simply add it to the processing list, but there is very little hardcoded reference, or most likely just a new parent path if they follow their own naming convention patterns, so mostly I work with parent paths and manage the relevant child keys/files dynamically based on some naming convention. I cannot imagine how you could do it differently - and you may say my imagination is very limited. Additionally, I personally would not work .1 version images, i.e. anything which is not officially released. One of the reasons would be that I assume that the Insider images would contain data/feature that was removed prior public release. On the other hand, official support from your end should start from the first public release, anything, that comes later (CU, updated public release, which is essentially a CU updated image as you know) is pretty much handled based on the above example. People can only access the public releases anyway (I don't understand the fuzz about ESD, and it looks like I do not need it currently). No need to keep millions of images to test at all. Here is what I would do when a new component removal support is added (like InputApp System App for instance), focusing on Windows 10 21H2 1. Test it on the CU when it was introduced (KB5026361, v10.0.19044.2965) 2. Test it on the first public release image (v10.0.19044.1288) If it works on both, it works on everything inbetween. And it is not like people will be using KB5019959 (v10.0.19044.2251) to integrate these days. I will not be pushing on this topic furthermore as Windows 10 21H2 with official release version 19044.1288 seems to be working as I need it to. But perhaps you got some ideas for compatibility support, which may also ease your work again. I don't care how much it does not work with Windows 11, from the looks of it, it will be short-lived anyway (if Windows 12 is really coming next year), if others want to / need to struggle with it, that's just... sad. To be fair, improvements require gambling on new ideas, given how good every 2nd major release worked out historically, I am sure things will be better for the next major release.
hi quick and simple question, is there a index of combability issues found by users somewhere on the internets? I was wondering if i could remove the unified telemetry client and using google i found out in this thread that it causes issues with driver download from windows update and sticky notes, stopping windows update installing drivers is a good thing but i do like my sticky notes.
In Windows 11, Settings > Personalisation > Taskbar. Is it possible for the ToolKit to hide the Search from the taskbar and also choose if we want to change the taskbar alignment to left or right?
Hi @MSMG @inTerActionVRI Recently I edit a ISO and the search menu not works, could you direct me to the right component which may I remove by accidentally? Here's my System Apps Removal list: =============================================================================== MSMG ToolKit - Remove System Apps Menu =============================================================================== [01] + AAD Broker Plugin - Credential Handler for Microsoft Azure Logon | Needed for: Microsoft Account, Windows Store [02] + Accounts Control - App to add Microsoft Account for Microsoft Apps | Needed for: Windows Store [03] - Add Suggested Folders to Library Dialog [04] - App Resolver UX - Modern Open With Dialog [05] - Assigned Access Lock App - Windows Kiosk Mode | Depends on: Assigned Access [06] + Async Text Service - Messaging extensions for People and Maps Apps [07] + Bio Enrollment - Windows Hello Setup [08] - Calling Shell App - App to host call progress on shell [09] + Capture Picker - A system picker UI control to select an item on the screen to capture | Depends on: ClientCBS [10] - CBSPreview - App for Camera Barcode Scanner [11] - ClientCBS - User Experience for Windows (Includes InputApp, Screen clipping, Windows 11 Startmenu) | Needed for: Touch screen devices, Windows Store [12] + CloudExperienceHost - Out-of-box Experience (OOBE) | Needed for: OOBE, Sysprep Generalize, Windows Store [13] - Content Delivery Manager - Automatic installation of sponsored or promoted apps, suggestions and Ads | Needed for: OOBE & Microsoft Account [15] + Credential Dialog Host - Authentication (Sign-in) shell support for Windows Hello [16] - ECApp - Modern UI Dialog App for Eye Movement Control | Depends on: WindowsMixedReality [17] - Edge Classic Browser [18] - Edge Developer Tools Client - An extension to edge containing tools for web developers | Depends on: Edge [19] - File Explorer - Modern File Explorer App [20] - File Picker - Modern File Picker Dialog [22] + Lock App - Container App for Apps and Messages on the Lockscreen [23] + Map Control [24] - Narrator Quick Start - QuickStart Guide for Narrator | Depends on: SpeechRecognition [25] - NcsiUwpApp - Network Connectivity Status Indicator (NCSI) [26] - OOBE Network Captive Portal - Captive Network Portals support during OOBE-Phase of Windows | Depends on: CloudExperienceHost [27] - OOBE Network Connection Flow - Connection Flow Network Portals support during OOBE-Phase of Windows | Depends on: CloudExperienceHost [28] - Parental Controls - App for Parental Controls [29] - People Experience Host - People Bar (People Hub) [30] - Pinning Confirmation Dialog [32] + Print Dialog - Modern Print Dialog | Needed for: Printing [34] - Retail Demo Content [36] - Secure Assessment Browser - Special Windows Mode for Exams (Take Test App) | Depends on: WebView2SDK [37] + Setting Sync - Sync settings between your Windows PCs and devices [38] + ShellExperienceHost - Shell Experience Host | Needed for: Start menu, Taskbar Calendar, Clock, Network Flyouts [39] - Skype ORTC [40] + Smart Screen - Windows Defender SmartScreen Functionality for Modern Apps [41] + StartMenuExperienceHost - Start Menu | Depends on: ShellExperienceHost [43] - Webcam Experience [44] - WebView2 Runtime [45] - Win32 WebView Host - Desktop App Web Viewer [46] + Windows Defender App [47] - Windows Mixed Reality [48] - Windows Reader (PDF) | Depends on: Edge [49] + Windows Store Back-end Client [50] + Xbox Console Companion Back-end Client [51] + Xbox Game Callable UI - Xbox Live [52] - XGpu Eject Dialog - Modern Dialog App for safe removal of external GPUs Maybe the ClientCBS is required to search menu in Windows 11? Not sure about it, I remove this component, just notice this one after I start edit another ISO.
Do not remove "ShellExperienceHost" and "StartMenuExperienceHost" This can solve your problem or you can try to use Removepkgslist of previous version of MSMG_Toolkit_13.3
The both components you mentioned I keep and in the previous build I use basically the same list and no issues. Maybe is ClientCBS, need to confirm
Hello, I upfully run the Toolkit, anyone can tell me how to uninstall Microsoft-Windows-win32calc-Package from my install.wim please