No, the option to enable or disable access to your microphone is independent of whether you have metro apps deleted. It's in your privacy menu in the control panel. I recommend removing everything you want to remove.
toolkit problem on rs4: 1) mount 2) integrate driver 3) integrate whd 4) 1) rm all 4) 3) rm all 4) 3) advanced) edge, ie, defender, people, smartscreen in this order 5) disable features ( manual script).... 6) cleanup 7) umount 8) rebuild unattend.xml gives error: windows setup could not configurate windows to run this computers hardware works fine on vanilla.
The gap between vanilla and your configuration is pretty huge, it would be helpful if you could narrow it down a little, see which step actually breaks things. On a related note, I am just learning about unattended setup. Is there an app that creates these xml files based on your options?
Here you are referring to using autounattend.xml right, I do test the toolkit serviced image by installing it with autounattend.xml and all my setup has been successful so far. Either test again skipping Disable features or do the disable features before removing defender, peoplexperincehost, smartscreen.
@MSMG Thank you so much for keeping your ToolKit updated throughout the years! Since I like to be an early adopter when it comes to new software releases, I've just built a new ISO for 1803. I knew the order of making changes was always really important, so I decided to follow your supplied Readme.txt to the letter. Basically I removed -every- AppX and (advanced) component that is removable (except IE UI) - I like to keep my install very lean, and integrated the latest CU/ .NET 3.5 / Win32Calc. Furthermore I disabled most of the Windows Features just before committing the changes with the ToolKit. My experience: FLAWLESS! No issues whatsoever when testing the slimmed down ISO in a VM. I read reports about unrepairable "sfc /scannow" results when removing Windows Defender/Telemetry, but to my surprise no issues on my end. Though a few repairable items were found, see below. Perhaps this info is useful. Thanks again, and keep up the great work! Now off to searching for newly added Windows Services that can be disabled without breaking important features (currently up to 148(!!) services disabled on an already ToolKit slimmed down 1709... I can't believe they keep adding more useless stuff with every release *sigh*) A few tiny notes on the Readme.txt: - "The ToolKitHelper.exe requires Microsoft .NET Framework 4.7.1." - it works fine with .NET 4.7.2 as well, so probably should read "4.7.1 or higher" - TH2-RS4 guide, step E reads for Windows Update Integration: " <Updates\w10\<Architecture>> folder (E.g <Packs\Updates\w10\x64>)." - this should of course read: E.g. <Updates\w10\x64> Code: 2018-05-13 07:35:54, Info CSI 0000568c [SR] Verify complete 2018-05-13 07:35:54, Info CSI 0000568d [SR] Repairing 5 components 2018-05-13 07:35:54, Info CSI 0000568e [SR] Beginning Verify and Repair transaction 2018-05-13 07:35:54, Info CSI 0000568f [SR] Repairing corrupted file \??\C:\Windows\System32\en-US\\OneDriveSettingSyncProvider.dll.mui from store 2018-05-13 07:35:54, Info CSI 00005690@2018/5/13:14:35:54.912 CSIPERF - FileMapsCreated 115ms 2018-05-13 07:35:54, Info CSI 00005691 CSIPERF - FilePI Commit 116ms 2018-05-13 07:35:54, Info CSI 00005692@2018/5/13:14:35:54.912 Primitive installers committed for repair 2018-05-13 07:35:54, Info CSI 00005693 [SR] Repairing corrupted file \??\C:\Windows\SysWOW64\en-US\\OneDriveSettingSyncProvider.dll.mui from store 2018-05-13 07:35:54, Info CSI 00005694@2018/5/13:14:35:54.990 Primitive installers committed for repair 2018-05-13 07:35:55, Info CSI 00005695 [SR] Repairing corrupted file \??\C:\Windows\System32\\OneDriveSettingSyncProvider.dll from store 2018-05-13 07:35:55, Info CSI 00005696@2018/5/13:14:35:55.084 Primitive installers committed for repair 2018-05-13 07:35:55, Info CSI 00005697 [SR] Repairing corrupted file \??\C:\Windows\System32\\usbceip.dll from store 2018-05-13 07:35:55, Info CSI 00005698@2018/5/13:14:35:55.162 Primitive installers committed for repair 2018-05-13 07:35:55, Info CSI 00005699 [SR] Repairing corrupted file \??\C:\Windows\SysWOW64\\OneDriveSettingSyncProvider.dll from store 2018-05-13 07:35:55, Info CSI 0000569a@2018/5/13:14:35:55.241 Primitive installers committed for repair 2018-05-13 07:35:55, Info CSI 0000569b [SR] Repair complete
there are settings and i still have microsoft store so the apps downloaded from there will need smartscreen they should be there
You must download the local experience pack yourself. It doesn't download otherwise. I checked on my PC, and it said GET which means I don't own it, and it isn't installed.
Since we are using a combination of DISM method and the manual method the SFC will show some files are changed/corrupted. Once I do update the ToolKit to completely use the manual method, then the SFC problem can be solved. Made changes to the Readme.txt to reflect the below noted typo errors and suggestions.
The smartscreen is not required for Store App but there's a option in smartscreen to whether scan for windows store url while downloading apps from it.
I used the toolkit from the beginning again and made same modifications without removing edge browser yet still no smartscreen filter settings either in control panel or settings i know there is settings in edge itself but i want the normal settings those in a pic i shared in my last reply so it appears that removing defender by the toolkit removes smartscreen all along with it, in that case i don't understand what's the point of 4-3-2-O smartscreen removal existing in first place !!
@MSMG ToolKit 8.6 W10 Pro x64 1803 en-us The integration of the metro skin for the WMPlayer lasts a very very long time (20-30 min).
It's better to have separate option for those who wish to remove smartscreen without removing defender. As for the microphone issues in RS4 I have none with onboard Realtek codec. The microphone works an the settings are available in the system settings UI. My process usually looks like this: - run toolkit - integrate CU manually - intagrate classic calculator and directx ( I never integrate .net in toolkit as it caused issues for me before even if done in apropriate order. I just let WU download and install it) - remove all apps including store - remove all windows components - remove all advanced components except IE and photo viewer and classic windows search - enable registry tweaks expect forcing latest .net framework for all programs - do some custom registry tweaks (like blocking onedrive setup along with ms c2r office) - cleanup with resetbase enabled, save and rebuild the image The only thing I observed is missing battery performace options slider and profiles whch I need to then setup manually, however, it may be not related to the toolkit. As for the inability to search for drivers though WU for me that is a desired behaviour, so I would like the option of removing telemetry along with this behaviour to stay, at least as an option. @MSMG Keep up the good work! Thanks PS. It could be a good idea to add the option for integration of classic windows sticky notes app.