Like I said the ability to scan the Store URL will be disabled in the Store but the Store itself will be working, you can think SmartScreen as a Compatibility rather than more as a dependency.
also, can bing, ie, skype, smartscreen amongst other components be disabled instead of removed during integration phase permanently? there a definite list of what can be removed during integration while not being affected by cumulative integration / live system updates? im tired of issues, just want things to work now. i hope microsoft crashes and burn for all they have caused
echo. [K] Windows Insider Hub The Windows Insider Hub is name of Feedback Hub now.Insider Hub is an old app for Windows 10. You may think this.I will be localize for Feedback Hub,Chinese name (zh-cn) is 反馈中心.
Yes, you can use some of the popular tweaking tool like O&O ShutUp10 to disable any re-enabled settings. As far as Apps they don't get restored, it's only the system apps or other components which are affected in v1903. For now v1809 is the best bet to use since it's working solid with removed components and WU. Just need more time to test v1903 to fix the issues.
This is not Feedback Hub App, it's the Windows Insider Build Flighting feature you do use it in Settings->Updates->Windows Insider.
Many thanks to MSMG for this toolkit, Great work I have one question, Arabic (ar -SA) language in 10.0.18362.1 (x64) is missing some files. Can you upload them please Thanks Advise Sorry for my bad English, I'm English newbie
Yes due to lack to good upload speed and storage space in MEGA site, I have only uploaded the WinPE language packs for W7, W81, W10 v1507/v1511/v1607 and W10 v1903. Only on request basis I do upload them, will upload the missing files for Arabic (ar -SA).
There is one amd64 package missing in RDP81 pack for Windows 7. Also had to rename files in IE11 pack (replace "_" with "~").
@MSMG Please release Toolkit with working RemovePkgsList, so modifying OS is easier and time saving, Thanks
Bug report for custom registry import for Toolkit version 9.4 : 1. There is no pre-made directory for OS and architecture causing CustomReg script to fail, similar to WHD folder structure (i had to look inside Toolkit.cmd to find what it needs as input) 2. There is no warning / info feedback for user to know where to place .reg files (should be made similarly as when user forgets to put .cab files in proper WHD folder and receives needed info) 3. After import, a list of processed .reg files is cut on first space in file name (example : "Take Ownership" is printed as "Take")
Thanks have uploaded the missing file now and it's may be due to the MEGA while downloading the files it changes the character '~' to '_' in filenames, better download them as zipped so that it won't rename the files.
Got it. What would be a good way to circumvent that right now? Removing Defender and using a 3rd party av? That's not a problem. But how do I avoid WU for driver downloads and other things that happen in background but are also necessary for the system to work properly?
Updated the ToolKit to v9.4.1 Spoiler: Changelog v9.4.1 + Updated ToolKit's Bin folder with Windows 10 20H1 Insider Preview WADK (v10.0.18970.1000) Tools. > Moved Custom Activation Tokens, Files, Recovery, Registry, Terminal Server, UxTheme feature folders to ToolKit's Custom Folder. + Fixed a Bug in the Feature "Remove Windows Component Using Package List", where the ToolKit couldn't process the Package List. + Fixed a Bug in the Feature "Import Custom Registry Setting from Registry File", where the import failed with filenames containing spaces.