The Windows Security App is a common interface for all security related stuffs like SmartScreen ,Firewall, Parental Controls, etc. If you remove any of them then their function will be blocked in this App, it doesn't mean you need them to run the Defender, only the first Tab is the Defender settings.
Hi Folks, Just using MSMG on Win10 20H2 right now. I delete components 1 by 1 because of the bug. My understanding is that it is not recommended to clean up after that, will it reinstall every deleted components ? Can I use my ISO even if it is not cleaned up ?
we do not recommend clearing the image. Updates won't come because the update is broken, the author knows. I did the tests. after removing the toolkit components, cumulative updates are not installed at all.
I've reached the point where I don't know what am I doing anymore. First, take this into account: I aim for a very slim install. I don't care about sfc, or updates at all. I remove A LOT of functionalities more once I end working with MSMG Toolkit and keep on working on the image with other tools. So, my first step is MSMG Toolkit. And I am lost. I start downloading an image from uupdump. Feature Update 19042.610. The updates are launched over the bare 19041.1 once the install is finished. As this inteferes with component removal, I try to integrate the updates into the wim image. First I tried manually using DISM and ended with two packages of every feature, one for the old and one for the new... and neither could be uninstalled. Cleanupt or resetbase did nothing. The I used MSMG Toolkit to integrate kb4577266, kb4579305 and kb4580364. It refused to install kb4562830 but I still went ahead to test it, applied changes and rebuilt image. DISM didn't showed double packages and those I wan't removed could be removed, I did resetbase... happiness at last... but... build version wasn't showing 19042.610 but 19041.610 "This doesn't look like a good omen", I feared. I used MSMG Toolkit to install the package it refused before, kb4562830, but this time it installed it. Applied, rebuilt, went to DISM to check. Now version build is OK, 19042.610 ... but here they are again, double invincible packages that laugh at my efforts with disdain. So... what am I doing? Why is this happening? What SHOULD I be doing instead? Different image version? Different download origin? Go back to Windows Millenium? Can someone please explain how are all of these facts connected and enlighten me with the wisdom I lack to achieve the grace of installing a working Windows 10 version before my life ends? Thank you.
Hello dear forum users! Sorry to be off-topic, help me find a tweak (reg file) that includes PhotoViewer for Windows 10.0.19042.610. Thanks.
I see that file C:\msmg10.8\Bin\XMLs\w10_CustomStartMenuLayout.xml, where do I need copy it to so the 4 > 6 option will import it?
XML was applied to image before removing components, in fact all the step's in Before using ToolKitHelper_1.0.4104.0: were used / applied.
The bug is SolitaireCollection in RemovePkgsList, it works with RemoveAppsList, but it doesnt matter if, win update is broken after
that's right, we are waiting for the author on this issue. The free ntlite removes components, and updates are installed and the sfc /scannow check passes. something with the toolkit utility. https://forums.mydigitallife.net/threads/msmg-toolkit.50572/page-864#post-1628712
It is not recommended to clean up image and it is installing the updates which will restore the deleted components and not the image clean up. Right now you cannot install the update for 19042, better wait for next release.
To integrate updates using Toolkit follow the below step Code: [E] - Integrate Windows Updates using [Integrate->Windows Updates->WHD Update Pack Menu] menu. Note: The Toolkit supports updates either in .msu/.cab format. Copy Windows Cumulative Update file to <WHD\w10\<Architecture>\Cumulative> folder (E.g. <WHD\w10\x64\Cumulative>). Copy Windows Defender Update files to <WHD\w10\<Architecture>\Defender> folder (E.g. <WHD\w10\x64\Defender>). Copy Windows Dynamic Update files to <WHD\w10\<Architecture>\Dynamic> folder (E.g. <WHD\w10\x64\Dynamic>). Copy Windows Enablement Update files to <WHD\w10\<Architecture>\Enablement> folder (E.g. <WHD\w10\x64\Enablement>). Copy Windows Flash Player Update file to <WHD\w10\<Architecture>\FlashPlayer> folder (E.g. <WHD\w10\x64\FlashPlayer>). Copy Windows .Net Cumulative Update file to <WHD\w10\<Architecture>\NetCumulative> folder (E.g. <WHD\w10\x64\NetCumulative>). Copy Windows Servicing Stack Update file to <WHD\w10\<Architecture>\ServicingStack> folder (E.g. <WHD\w10\x64\ServicingStack>). Copy Windows Setup Media Update files to <WHD\w10\<Architecture>\SetupMedia> folder (E.g. <WHD\w10\x64\SetupMedia>). Copy Windows WinPE Update files to <WHD\w10\<Architecture>\WinPE> folder (E.g. <WHD\w10\x64\WinPE>).
Open the file C:\msmg10.8\Bin\XMLs\w10_CustomStartMenuLayout.xml with notepad and copy the new start menu layout contents to it and save it. Now use 4->6
Ok you used the same image and I see you did performed the below steps with 19042 Enablement update integrated dism /image:C:\mount /cleanup-image /startcomponentcleanup dism /image:C:\mount /cleanup-image /startcomponentcleanup /resetbase dism /image:C:\mount /cleanup-image /restorehealth But how you did it since integrating 19042 Enablement pack will creating a pending.xml which will not allow to perform the above steps. Did you used the Store ESD image from Microsoft which is sysprep image?
From what I've gathered it's not okay to clean up sources with a 19042.610 build on 10.8 atm? I used UUP dump if that matters to build my image.