Hi Hm, actually I'm having problems to get key-strokes being accepted in the Remove-Panel. I'm typing 'A' ( for Example ), but this Letter vanishes as soon as I let go the key and nothing happens. 'X' for ' back ' is being accepted. I tried to change the Rights of the Folders, but vain. Thanks for a Hint in Advance
May be its the spaces in the font filename creating issues, do try removing the spaces in the filename.
Just copy all the updates to <WHD\w10\x64\10.0.19041> and use the menu Integrate Updates->Integrate WHD Updates Menu-Integrate to Windows Installation Image.
OneDrive Package names Microsoft-Windows-OneDrive-Setup-Package Microsoft-Windows-OneDrive-Setup-WOW64-Package
When you press A to select all components the + sign prefixed to component name will change to - sign, this means all components are selected. Now go to previous menu (3->1>2 - Start Removing Windows Components) to start removing the components.
I have checked with fonts that have no spaces in their names with the same error. As far as I can see the path variable referred to in the error is the copy path that the fonts are copied from? Indeed Code: $fPath = "$($folder.getDetailsOf($obFont, 194))" is empty Someone more knowledgeable than myself on powershell scripts may know what is going on? Anyway it's not essential for me right now. Thanks for your help.
Will I need to mount registry keys to remove packages? Do I need to use your script to show hidden packages in this case?
Removing (sensibly) any packages (incl. hidden and System Apps) is the most wanted function for me since long ago. At the very least, for LTSC.
Due to a Front-End / Back-End splitting I have a question (LTSC). 1) Let's say I want to keep only WindowsStoreClient ( System App | Back-end ) to have a Store in semi-functional condition (ability to install Apps using PowerShell or install UHD drivers) 2) I don't need Xbox at all. Is it reasonable for me to remove Xbox completely, incl. XboxClient ( System App | Back-end ) ? And keep WindowsStoreClient ?
It's a MSI file embedded into a cab file, you can't integrate it, may be a custom pack can be created for it.
Microsoft has been combining or merging packages deep into other packages make it difficult to remove them with standard method. By default, In LTSC there are only Windows Store and Xbox back-end clients, yes you can remove Xbox back-end client. The reason for splitting Store and Xbox into back-end and front-end was to make it easier to make a LTSC like build from normal editions.
Hello! I built the Windows 10 version : 21H1_19043. 899. I would like to ask : will the MSMG Toolkit v. 11. 4 support integration of components (calculator, DaRT, DirectX 9c and others)? Thanks.
For Integration there's no restriction for CU version, only for removal the Toolkit requires the CU version specified in the changelog.
https://forums.mydigitallife.net/threads/msmg-toolkit.50572/page-793#post-1606110 Sent an 2021-03-16 updated file in the link above. Spoiler: CHANGELOG 2021-03-16 Merged with Toolkit 11.3 and 11.4. *Some Custom Toolkit Tweaks and Remove Menu minor fixes and code improvement. Returned to the Toolkit standard aspect Ratio. In this way, all the menus that require more space to show the menus on the screen, have been divided into more screens. just press B to Back and N to Next. This, just to avoid the use of scrolling with each choice made in the menu, which you are working on. Get ImageBuild from updated Image system, implemented to correct the error in the automated making ISO label and file name. All the environment and path variables for the packs were concentrated in some sessions, at the beginning of the custom toolkit. This way it is easier to reset the variables at each integration performed. Also so that the multiple choice system facilitates the multiple integration of features sequentially. Multiple choice has been implemented within the integrate menu, for all features that are submenus. In other words, if it is a sub menu, a negative sign will appear as a default. If it is to integrate this signal it will become positive. To apply the integration you must go back to the "Integrate Menu" and choose "Start Integration". In the options without signaling, integration will occur as soon as you select. These are the submenus mentioned: IntLanguagePacksMenu (tested) IntDriversMenu IntInboxAppsMenu IntRSATMenu IntOfficeUWPAppsMenu IntDaRTMenu (tested) IntThinPCpkgsMenu IntGamesMenu (tested) IntCustomFeaturesMenu (tested) Note: As I said earlier in the post below, these changes were made in order to implement the multiple choice system in the menus but there may be variables that do not get the values set and end up breaking something. We always think that we thought of all the possibilities until we found something new to be corrected or improved. As I said before, I can't test everything here for lack of storage space. Then, for final images of daily use, make integrations with the Official Toolkit. Removal, Customizations, Tweaks, can be done with Custom, if you want. So, it is necessary that this part be tested by volunteers. I am grateful for the feedbacks. Thnks!