Hi, I share some tweaks that I use and can be added to this tool Add Take Ownership on context menu Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\Classes\*\shell\takeownership] @="Take Ownership" "HasLUAShield"="" "NoWorkingDirectory"="" [HKEY_LOCAL_MACHINE\Classes\*\shell\takeownership\command] @="cmd.exe /c takeown /f \"%1\" && icacls \"%1\" /grant administrators:F" "IsolatedCommand"="cmd.exe /c takeown /f \"%1\" && icacls \"%1\" /grant administrators:F" [HKEY_LOCAL_MACHINE\Classes\exefile\shell\takeownership] @="Take Ownership" "HasLUAShield"="" "NoWorkingDirectory"="" [HKEY_LOCAL_MACHINE\Classes\exefile\shell\takeownership\command] @="cmd.exe /c takeown /f \"%1\" && icacls \"%1\" /grant administrators:F" "IsolatedCommand"="cmd.exe /c takeown /f \"%1\" && icacls \"%1\" /grant administrators:F" [HKEY_LOCAL_MACHINE\Classes\dllfile\shell\takeownership] @="Take Ownership" "HasLUAShield"="" "NoWorkingDirectory"="" [HKEY_LOCAL_MACHINE\Classes\dllfile\shell\takeownership\command] @="cmd.exe /c takeown /f \"%1\" && icacls \"%1\" /grant administrators:F" "IsolatedCommand"="cmd.exe /c takeown /f \"%1\" && icacls \"%1\" /grant administrators:F" [HKEY_LOCAL_MACHINE\Classes\Directory\shell\takeownership] @="Take Ownership" "HasLUAShield"="" "NoWorkingDirectory"="" [HKEY_LOCAL_MACHINE\Classes\Directory\shell\takeownership\command] @="cmd.exe /c takeown /f \"%1\" /r /d y && icacls \"%1\" /grant administrators:F /t" "IsolatedCommand"="cmd.exe /c takeown /f \"%1\" /r /d y && icacls \"%1\" /grant administrators:F /t" Disable Admin Share Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\ControlSet001\services\LanmanServer\Parameters] "AutoShareWks"=dword:00000000 "AutoShareServer"=dword:00000000 Disable Auto Run Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\Microsoft\Windows\CurrentVersion\Policies\Explorer] "NoDriveTypeAutoRun"=dword:00000255 Enable Folder Search Menu to Context menu aka Clasic search Code: Windows Registry Editor Version 5.00 ; Re-Enable Folder Search Menu after SP1 ; howtogeek.com [HKEY_LOCAL_MACHINE\Classes\Directory\shell\find] "LegacyDisable"=- [HKEY_LOCAL_MACHINE\Classes\Drive\shell\find] "LegacyDisable"=-
Did you integrate .NET FX35 prior to component removal, if yes then it will fail to remove some components.
Thanks, I will be adding the new method for W7-W10 TH1/TH2/RS1/RS2/RS3, SRV 2008R2-SRV2016/SRV too but it will take some time.
Did you integrate .NET FX35 before component removal, if yes then it will break the removal of some components and it's been a known issue from long time and that's why it's integrated at last. SFC /SCANNOW fix is only for the components which uses the ToolKit Helper for component removal and rest are using still the old method. And for HomeGroup Control Panel Shortcut, will check and fix it.
I have tested the ToolKit with English (en-GB/en-US) source and it's working properly without any issues. Also, The components Xbox Callable UI, People Experience Host, Windows Defender, SmartScreen removal uses the new method to remove the component and right now it only works for English (en-GB/en-US) source ISO's. Did you used the Start.cmd to run the ToolKit? Do wait for the next version which will be uploaded in a while with the Start.cmd fix for x64 systems.
Until I do add the new method to remove OneDrive, can't do anything to keep the Sync. All components will be made to use the new method one by one and it will take some time. Windows Content Delivery Manager was previously in Cortana section then moved to Telemetry section, but actually for W10 RS3 there's no Telemetry components to remove and only the Windows Content Delivery Manager is left in it. So just skip the Telemetry part when removing.
Don't know why it's giving errors, I need to test zh-CN image myself to see what's wrong. And the description bug might be due to the text in Chinese not able to display properly
I did tested the ToolKit multiple times with removing all the components for W10 RS3 x86/x64 Images but didn't encounter errors while removing the components.
May be as I did tested with multiple editions without the Enterprise, will check with the Enterprise edition too and see for any bugs.
When removing some components like Windows Defender there are few registry keys which differ for each languages, but I could narrow down the changes to only 1 key and still in the process to identify by what content it changes, will do find it and add support for all languages. And, for Some Editions like CoreSingleLanguage, N Editions, some keys don't exists at all and I have fixed them.