So i'll try with mhussain advice and looks like it will resolve my last question too (to edit those french name to fr-fr and fr-ca)
To make this work, restore the menu. Comment the line. To do this, you need to navigate to the ":: Multimedia Components" section and put "rem" in front of the codeline of the application you want to keep. Then select remove all and it will remove only the non-commented lines. Code: rem if "%Component%" equ "WindowsPhotoViewer" call :RemoveWindowsComponent "%InstallMount%\%%i", "Windows Photo Viewer", "WindowsPhotoViewer" rem if "%Component%" equ "WindowsPhotoViewer" call :RemoveWindowsComponent "%InstallMount%", "Windows Photo Viewer", "WindowsPhotoViewer" Just like that.
I see into the sector code. Thanks! Very good info to know, Thanks! For change a subject... When I remove the file association for Metro apps, the Start menu breaks, not syncing apps that were kept installed, such as Calc, Photos, Solitaire Collection, etc. Note 1: That's almost certain! Note 2: I already say that the custom layoutmodification for StartMenu does not cause this problem. Now I am checking my "*.reg" files. This week I confirm. I am finishing the last tests for confirmation. Edit: Just to confirm... There were errors in my "*.reg" files for Windows Explorer and Windows Search settings. Nothing related to "RemoveMetroAppsAssociations".
Thank you , any way to remove cortana from delete list, so i delete all components and not include cortana, instead of removing one by one, which will take me a long time ?!
I had forgotten that I asked this question. Thank you so much for always answering each and every question!
Excludes the store, which is the procedure for installing appx files, I want to install Dolby Atmos Premium.
After the Search fix in the recent update of the MSMG Toolkit the 2 methods apparently remove only the Cortana app leaving some files related to Cortana to maintain compatibility with the Search app. MSMG has already talked about this: https://forums.mydigitallife.net/threads/msmg-toolkit.50572/page-769#post-1601059 That's because MSMG Toolkit has a fix for Cortana in the recent update that keeps some Cortana related files in the Windows folder and some registry entries to maintain search compatibility in the Start menu. Those things that are maintained may be being detected by NTLite. However NTLite removes everything related to Cortana it seems that it has the problem with the search in Start menu. NTLite has not yet corrected this problem.
Getting this while trying to select pro - Cant convert esd to wim. And my other install.wim, i cant even select pro.
Is there any difference between the ISO converted from ESD and the direct ISO file ?. I mean is the ISO converted from ESD ( 19041.264.200511-0456.vb_release_svc_refresh_CLIENTBUSINESS_VOL_x64FRE_en-us.esd) better to service with MSMG 10.0 than en_windows_10_business_editions_version_2004_updated_may_2020_x64_dvd_aa8db2cc.iso ? Thank you.
I am assuming you are working with the latest stable Windows 10 build 2004 / 19041.264? In the ToolKit folder, check Bin\Lists where you will find the file RemovePkgsList_W10_10.0.19041_Template.txt. Use this to build up your RemovePkgsList.txt file. You have these in the above list which you want to remove: Code: Advertising Xaml Alarms & Clock App Therefore add the below to RemovePkgsList.txt: Code: ToolKitHelper:AdvertisingXaml ToolKitHelper:Alarms You will quickly learn.
Is that possible to extract the Enterprise part alone from the ESD ?. Kindly let me know the procedure. Thanx
1909 19H2 18363.836 And, what about CallShellApp? Does ToolkitHelper support its removal? I ask because the codeline is not in the script. If I add the following commands, would it work? Code: call :RemoveWindowsComponent "%InstallMount%\%%i", "Call Shell App", "CallShellApp" call :RemoveWindowsComponent "%InstallMount%", "Call Shell App", "CallShellApp" And, if you remove Your Phone and People from that app, I supposedly believe it will lose its function.
I used the ESD Decrypter from Feartamixg - Extracted the Pro install.wim and I was able to then load up the source image. This is great, I was looking for this. I used the above ESD Decrypter - Extracted my install.wim and was able to select the source.