Don't use regisrty tweak when Group Policy stuck. Instead Reset it, as I said before. To fix the GPO you MUST reset a certain policy only through the GPO Editor (gpedit.msc). Find the correspondent policy, then switch it 2 times : Open policy window -> (•) Enabled -> (•) Not configured -> Apply Then Reboot or use cmd to update all GPO: gpupdate /force That's why I always stick to the rule do not touch policies through the registry and operate with them manually (GPO Editor) or using LGPO.exe utility (from MS). Some policies may stuck if they were switched over registry. Mostly people are not informed about this. Instead GPO Editor or LGPO.exe commands (i.e. for backup/restore your policies) always give a reliable results.
Sorry if I seem like hijacking this post, but even I had decided to stay with 1809 before I found that softwares like the latest version of adobe bridge have started to kill all windows versions upto 1809 by refusing to install in windows versions prior to 1903. It seems one or the other day everyone has to update to the current version of Windows which is ridiculous.
@MSMG - I have a question: What going on with GPO files during removal of big components (i.e. like Defender, Edge, etc.) that have their own policies in the OS? Is a process of removing correspondent policy files (.ADMX and .ADML) belongs to the stock (standard) scenario, or you applying some additional commands to clean them (smth. like to delete leftovers or so)? Thanks.
@MSMG does toolkit v10.6 support 20H2 build 572 ,,? will be there any new version of the toolkit soon ?? thank you
Bug in 10.6. Used the original image 19041.208 ru-ru. Deleting a UnifiedTelemetryClient deletes the file acmigration.dll from Windows/System32. When checking the sfc / scannow, this file is restored. Author, please correct it.
I have always wondered why people use sfc /scannow on hacked images or debloated live OS? Becuase M$ have only one placebo for every challenge / cancer of their code? This command is about restoring all bad things we trying to avoid so hard. I used this only once - to understand: never launch this again. Same as auto-diagnosys. My main Win8.1 OS is alive and updated about 7 years. Everything you should be interested in is working functions you use and reading topics how to fix things manually if they appears broken. No bloatware | no telemetry = no auto-diagnosys | no sfc /scannow
And still it was always the thing that differentiated MSMG toolkit from other hard cut chopping tools, to still try to have an integer install.
^ yes i totally agree, the user needs to have a good idea before leaving, simply removing any component and then complaining hmm this is not working properly! it's just a matter of reasoning and as i already said a good notion of how the operating system works ... i'm sure of this because that's how i learned (and i still learn every time i use the MSMG Toolkit) it wasn't easy today in one day I can say that the systems modified by me never had a blue screen or anything like that but I know that there is still a long way to go to achieve this dreamed of perfection if only my two cents is possible
The first threshold of entry into the world of custom builds (LIVE or ISO) - is to forget about sfc /scannow And do not use any auto-diagnosys (disable it completely, incl. services, schedules, etc.)
yes i believe we still have a long way to go and i say more by the floor of the carriage (M$FT) everything changes every 6 months just see the 20H2 version how many changes and more I think it is practically impossible for a user to keep up with this pace that will get crazy or paranoid lol; in this way as I said the other day it is more rational to stay with W8.1 until 2023 and as an alternative to use the W10 LTSC at least for now ...
Thanks for checking Activity History with vanilla image, do check if it needs net connectivity to show the page. Will release a test version once the fix is complete for v1809/1903-9/2004-9 left-over entries, do tryout and let me know the result.
First you need to use the 19042.508 + the required CU supported by Toolkit component remover to use component removal. Do try with next release and see if it works properly.
I've finished my first draft of the script to re-integrate Windows Defender. It is a first draft so it is far from perfect. I welcome any feedback. Now all I need is (hopefully)...
Before removing any component do check if it depends on other components. [20] Smart Screen | Depends on: Windows Defender [32] Windows Store | Depends on: Smart Screen To set the Settings->Apps->Apps and features->Choose where to get apps from, you need SmartScreen and the SmartScreen is partly controlled by Windows Defender