ok no wonder i couldnt customize things like accent colors on new users. so now, should i set accent color registry settings on the system hku default or users\default\ntuser.dat?
I have used a Windows 10 Enterprise LTSB 2016 DefaultLayouts.xml to remove 3rd Party Apps links but for Store and Edge it's not working, Will check with LayoutModification.xml and see if it works. Yes as you said one way is to use the Beyond Compare to find the necessary list of files/folder/registry settings for component removal using the available like NTLite / WinReducer. and the other way is to use the package mum file to know which files/folders are copied to where, what registry entries are written to where with which registry permissions.. this will help to make the list of tasks to be done for component removal.
I don't know what's the new registry keys to set the Accent Colors in Windows 10 RS2 but here's few tweaks related to Color setting. Code: ; Change LogonUI and Startscreen Default Background Color [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Accent] "StartColor"=dword:ff9b5200 "AccentColor"=dword:ff9b5200 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Accent] "DefaultStartColor"=dword:ff9b5200 ; Disable Automatically Pick an Accent Color from my Background [HKEY_CURRENT_USER\Control Panel\Desktop] "AutoColorization"=dword:00000000 ; Set Accent Color [HKEY_CURRENT_USER\Software\Microsoft\Windows\DWM] "ColorizationColor"=dword:c40078d7 "ColorizationAfterglow"=dword:c40078d7 [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Accent] "AccentPalette"=hex(3):A6,D8,FF,00,76,B9,ED,00,42,9C,E3,00,00,78,D7,00,00,\ 5A,9E,00,00,42,75,00,00,26,42,00,F7,63,0C,00 "StartColorMenu"=dword:ff9e5a00 "AccentColorMenu"=dword:ffd77800 ; Enable Show Color on Start, Taskbar and Action Center [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Themes\Personalize] "ColorPrevalence"=dword:00000001 ; Enable Colored Window Title Bar and Taskbar [HKEY_CURRENT_USER\Software\Microsoft\Windows\DWM] "ColorPrevalence"=dword:00000001 ; Use Accent Color instead of Default Wallpaper in Windows LogOn / LogOff Screen ; dword:00000000 = Use default Windows Wallpaper ; dword:00000001 = Use Accent Color [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\System] "DisableLogonBackgroundImage"=dword:00000001 ; Set Inactive Title Bars Color [HKEY_CURRENT_USER\Software\Microsoft\Windows\DWM] "AccentColorInactive"=dword:ffc0c0c0 ; Add More Windows Title Colors [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Themes\Accents\0\Theme0] "Color"=dword:00918b73 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Themes\Accents\0\Theme1] "Color"=dword:00a68e5e [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Themes\Accents\1\Theme0] "Color"=dword:00a44817 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Themes\Accents\1\Theme1] "Color"=dword:00a44817 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Themes\Accents\2\Theme0] "Color"=dword:00618a28 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Themes\Accents\2\Theme1] "Color"=dword:00bab4ab [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Themes\Accents\3\Theme0] "Color"=dword:0085bd37 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Themes\Accents\3\Theme1] "Color"=dword:0085bd37 Note: For some Editions like Pro VL/Enterprise it needs the OS to be activated to get the tweaks work.
I am not sure that works... Components are interconnected and 2 different components may require the same DLL file and/registry keys. I think with NTLite some files are set not to be restore-able. For example, GameMode.dll removed with NTLite results in SFC detecting that the file is missing, but also reports something like 'the file is not meant/needed for replacement' - I do not remember the exact wording. I think there may be an attribute that can be set for removed files that makes SFC avoid detecting them as 'needed'. The tile thing is not a big deal when it comes to personal use, but when you deploy on other PC's people tend to get worried when they see something is corrupt.
I changed the related section in ToolKit-v7.4.cmd as follows an saved it.. if "%RemoveStoreApp%"=="0" ( choice /C YN /N /M "Warning Removing All Default Metro Apps Except Store, Continue... ['Y'es/'N'o] : " if errorlevel 2 goto :Stop ) if "%RemoveStoreApp%"=="1" ( choice /C YN /N /M "Removing All Default Metro Apps, Continue... ['Y'es/'N'o] : " if errorlevel 2 goto :Stop ) It works okay now.. Thank you MSMG
FYI, if someone wants a list of more not-so-useful packages, you should head over here - https://forums.mydigitallife.net/threads/repo-windows-10-telemetry-repository.63874/ - these are Telemetry-related and MOST are already on MSMG Toolkit list, while some others are not. I've been experimenting with removal of other items and hopefully something useful can come out of that...
GameMode.dll is packages without mum. I wrote for you example here: https://forums.mydigitallife.net/threads/msmg-toolkit.50572/page-145#post-1349217 I wrote here: https://forums.mydigitallife.net/threads/msmg-toolkit.50572/page-151#post-1352228 this: Example 2: GameMode.dll package: Microsoft-Xbox-GameMode-Component-Package~31bf3856ad364e35~amd64~~10.0.15063.0 REMOVE: reghive components: \DerivedData\Components\amd64_microsoft-xbox-gamemode-component_31bf3856ad364e35_10.0.15063.0_none_8852639f9b0346bf \DerivedData\Components\wow64_microsoft-xbox-gamemode-component_31bf3856ad364e35_10.0.15063.0_none_92a70df1cf6408ba \DerivedData\VersionedIndex\10.0.15063.0 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-xbox-gamemode-component_31bf3856ad364e35_none_49e57636e0bf3801 \DerivedData\VersionedIndex\10.0.15063.0 (WinBuild.160101.0800)\ComponentFamilies\wow64_microsoft-xbox-gamemode-component_31bf3856ad364e35_none_543a2089151ff9fc reghive software: \Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-xbox-gamemode-component_31bf3856ad364e35_none_49e57636e0bf3801 \Microsoft\Windows\CurrentVersion\SideBySide\Winners\wow64_microsoft-xbox-gamemode-component_31bf3856ad364e35_none_543a2089151ff9fc files: \Windows\WinSxS\Manifests\amd64_microsoft-xbox-gamemode-component_31bf3856ad364e35_10.0.15063.0_none_8852639f9b0346bf.manifest \Windows\WinSxS\Manifests\wow64_microsoft-xbox-gamemode-component_31bf3856ad364e35_10.0.15063.0_none_92a70df1cf6408ba.manifest \Windows\System32\gamemode.dll \Windows\SysWOW64\gamemode.dll folders: \Windows\WinSxS\amd64_microsoft-xbox-gamemode-component_31bf3856ad364e35_10.0.15063.0_none_8852639f9b0346bf\ \Windows\WinSxS\wow64_microsoft-xbox-gamemode-component_31bf3856ad364e35_10.0.15063.0_none_92a70df1cf6408ba\ ... and sfc and ScanHealth are OK.
I just checked this code in the CMD file and it's exactly as you have it listed here... did I miss something???
Then I fail because I did the same thing for some other package and SFC would not even complete... BUT I wanted to say that these packages are safe to remove with the Toolkit: Microsoft-Windows-Security-AADBrokerPlugin-Package Microsoft-OneCore-AccountsControl-API-Package Microsoft-Windows-AppReadiness-Package Microsoft-Windows-Client-AssignedAccess-Package
I noticed CCleaner + CCEnhancer cleans WinSAT AVI and MP4 files and then SFC ScanNow fails, but repairs/replaces the missing files successfully.
That's the interesting thing -> I didn't touched the Media Player components and the same error occurs with an untouched CU Iso.
You are right. I lost the overview in this thread . Thanks for your response. But I thought there was another guy with the same symptoms...hm...
Thank for this, but I want to apply it for newly added users. Should it go on %windir%/system32/config/default or c:\users\default\ntuser.dat maybe the answer is the first because, the latter is what ive been applying the registry setting on to no avail.
That's called Component Protection/Splitting to have a working system without any issues in retained components and Yes it requires some method to make SFC not to throw errors at removed components.