@MSMG Could you add an option that “don't re-compress the winre.wim if not mounted” when apply and save images. usually windows images (such as Windows 7 SP1/Windows Server 2008 R2 MVS image), All images in install.wim have the same winre.wim(checked by hash code) . But after MSMG re-compressed all images' winre.wim don't have the same hash code which will enlarge the image size.
This was changed when adding support for random indexes, will be correcting it. Will add the option to skip rebuilding boot.wim/winre.wim if not mounted and also if winre.wim is selected then which install.wim index has to be chosen for mounting winre.wim and copy the same winre.wim to other mounted install.wim so that this will reduce the overall install.wim size.
Any reason you chose that guide and not Chris Titus'? Chris' seems to be a lot more detailed and properly done.
Yes did understood your query, the Toolkit was capable of removing Edge Chromium for Windows 10 v2004 and above with all four methods 1) Edge Chromium Integrated through standalone msu/cab installer. 2) Edge Chromium Integrated through Windows 10 v20H2 Enablement package. 3) Edge Chromium Integrated through system prepared images. 4) Edge Chromium Integrated through new CU embedded method. Now since the CU contains the Edge Chromium which is similar to system prepared images, the removal works in the same method.
It was chosen randomly and also it had the demo for selecting the source from custom install.esd. Ok have added the latest Chris Titus Tech video too. Also will be creating own demo videos for Toolkit add them in future.
Another method is to use wimlib instead of DISM for image re-compress. tested by wimlib-1.13.4 (released Apr 18, 2021): the command: wimlib-imagex.exe optimize winre.wim --compress=lzx will always make the winre.wim with the same hash.
That's it. I implemented this, in Custom 11.4 for anyone who wanted to use it, while waiting for your return. This is going to be very good. Welcome, Master!
I apologize a forgot to ask about this one in my previous post but, what is Lockscreen App? Does it remove the lockscreen or it is just a confusing naming related to other stuff? Also a question about Win32 Web View, is it something related to Edge, Internet Explorer or? Edit: Another one came to mind. If I delete Content Delivery Manager which is required for OOBE (Out of Box Experience), do I still have OOBE on the beginning of the installation, or is it removed entirely?
LockApp - Container-App for Apps and Messages to be displayed on the Lock screen. Win32WebView - Edge Classic Web View control used by developers. ContentDeliveryManager - Used to Install Suggested Apps, provide data for apps, display advertisements, needed for OOBE, Microsoft Account. removing this will not remove OOBE
@MSMG Have used the images I created with your ToolKit last night to produce the attached CBS logs. I gave more time for the background checks to complete, which in turn has produced more detailed logs. I hope these are useful to you.
I use the same ISO, except different? language (en-US), and after clean install, without touching it with MSMG, SFC /scannow found corrupt files. It is either Microsoft foult or UUP Dump?
@MSMG 1) Great news about removal System Apps - AsyncTextService, CredDialogHost, XGpuEjectDialog ! Please, add the next ones (may be in one of the next releases) to complete this satisfactory step with the removal of SysApps: • AccountsControl • CapturePicker • OOBENetworkCaptivePortal • OOBENetworkConnectionFlow Note: OOBENetwork is not the same as OOBE Security screens (OOBENetwork removal don't touch it at all) Also you may have a look at the Windows Capabilities to Disable: • MathRecognizer • OneCoreUAP.OneSync • OpenSSH.Client • Language.Handwriting ----- Removal all of these are completely safe and has been tested dozens of times (LTSC). 2) Don't forget include supported items to the Templates, as @graver.x correctly pointed out. 3) I know how to get rid of appearing CloudExperienceHost for the newly created account (for every new added user). In simple words it unbinds CloudExperienceHost from User Account. In this case anyone can remove it later on their own, after Windows installation on Live OS (ONLY). (Also this disables OOBE Security Screens. For tweaked OS they are nonsence) NTUSER.DAT file must be patched with a certain dependent tweaks inside. Integrating patched NTUSER.DAT into ISO is completely safe, has been tested and works flawlessly (LTSC). Disabling CloudExperienceHost depends on tweaks (Live OS or/and NTUSER.DAT): Spoiler: CloudExperienceHost - TWEAKS Code: :: GPO : Don't launch privacy settings experience on user logon reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\OOBE" /v "DisablePrivacyExperience" /t REG_DWORD /d 1 /f reg add "HKCU\Software\Policies\Microsoft\Windows\OOBE" /v "DisablePrivacyExperience" /t REG_DWORD /d 1 /f :: Scheduler : CloudExperienceHost [ CreateObjectTask ] schtasks /Change /TN "Microsoft\Windows\CloudExperienceHost\CreateObjectTask" /Disable :: CloudExperienceHost OOBE : Autologger reg delete "HKLM\SYSTEM\CurrentControlSet\Control\WMI\AutoLogger\CloudExperienceHostOobe" /f :: CloudExperienceHost : ETW Logging reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\CloudExperienceHost" /v "ETWLoggingEnabled" /t REG_DWORD /d 0 /f :: Online Speech Recognition (Cortana) reg add "HKCU\Software\Microsoft\Speech_OneCore\Settings\OnlineSpeechPrivacy" /v "HasAccepted" /t REG_DWORD /d 0 /f :: Improve Inking & Typing Recognition reg add "HKCU\Software\Microsoft\Input\TIPC" /v "Enabled" /t REG_DWORD /d 0 /f :: Camera on your Lock Screen reg add "HKCU\Software\Microsoft\Windows\CurrentVersion\Authentication\LogonUI\AccessPage\Camera" /v "CameraEnabled" /t REG_DWORD /d 0 /f :: Advertising ID for Relevant Ads reg delete "HKCU\Software\Microsoft\Windows\CurrentVersion\AdvertisingInfo" /v "Id" /f :: Relevant Ads for Current User reg add "HKCU\Software\Microsoft\Windows\CurrentVersion\AdvertisingInfo" /v "Enabled" /t REG_DWORD /d 0 /f :: Tailored experiences with diagnostic data reg add "HKCU\Software\Microsoft\Windows\CurrentVersion\Privacy" /v "TailoredExperiencesWithDiagnosticDataEnabled" /t REG_DWORD /d 0 /f :: Privacy Consent Presentation Version reg add "HKCU\Software\Microsoft\Windows\CurrentVersion\Privacy" /v "PrivacyConsentPresentationVersion" /t REG_DWORD /d 2 /f :: Values ("PrivacyConsentSettingsVersion"): [2] = Win10 before 19041 (2004); [3] = Win10 19041 and above reg add "HKCU\Software\Microsoft\Windows\CurrentVersion\Privacy" /v "PrivacyConsentSettingsVersion" /t REG_DWORD /d 2 /f :: Allow apps to access your location reg add "HKCU\Software\Microsoft\Windows\CurrentVersion\CapabilityAccessManager\ConsentStore\location" /v "Value" /t REG_SZ /d "Deny" /f :: Find my Device reg add "HKCU\Software\Microsoft\Settings\FindMyDevice" /v "LocationSyncEnabled" /t REG_DWORD /d 0 /f
1) CloudExperienceHost, OOBENetworkCaptivePortal, OOBENetworkConnectionFlow can be removed, I have worked on it need more testing, will be available in future versions. CloudExperienceHost is also associated with Autopilot and removing CloudExperienceHost needs the user to disconnect from internet when installing the OS. CapturePicker will break UWP screen capture functionality, need to check with AccountsControl. Will check with the Windows Capabilities. 2) Yes have updated the templates, it will be available from next version.
@MSMG According to my experience, CloudExperienceHost CAN'T be removed from the ISO, but on Live OS only (especially with much helpful NTUSER.DAT patching). CloudExperienceHost OOBE is a part of Login / Password screen during Windows installation (unfortunately). Or you know smth I don't. UWP screen capture is a garbage we don't want. But dependency should be noticed inside the MSMG Menu (as usual). AccountsControl is useless until we still have classic MMC manager. And other things (apps to remove, tweaks to disable on Live OS) also break modern AccountsControl (never used it and always ignored). As soon as CloudExperienceHost is removed, AccountsControl will stop functioning. So they have to go together. Moreover, modern AccountsControl has disandvantages, so it was never recommended, compared to the stable classic manager. Thanks a lot for you hardwork! I'm happy MSMG Toolkit now is so close to the All-in-One tool for cleaning ISO (at least for LTSC!)