@MSMG One thing I noticed after removing provisional apps is that using MSMG the Store has no entry in Apps and Features and is unusable. But, manual removing of apps using dism or NTlite is working properly.
@ MSMG Hi I like to know if someday is possible remove UWP Settings on Windows 10, or how to turn back Settings in Win32 thanks in advance
Host OS: Windows 10 v1709 x64 en-us 16299.19, KIS18, VC++ 2012-2013, .Net3.5-4.7. - Extract the ToolKit to a folder path which doesn't contain a space, without any modification (D:\Downloads\ToolKit-v7.9). - Extract original VLSC ISO SW_DVD5_Win_Pro_Ent_Edu_N_10_1709_64BIT_English_MLF_X21-50143 into DVD folder. - Double click the Start.cmd and choose Yes when asked. - Select the Source. - Select one index - 5 Proffesional. - Mount Install. No mount Boot and Windows RE. - Remove selected ones Apps (Xbox, Print 3D) or not remove nothing. - Remove Apps associations. - Remove All Windows Components. Xbox Game and People Exp. Host does not removes!!! Unauthorized Use of ToolKitHelper Utility Error. - Remove All Advanced Windows Components, but Defender, SmartScreen and Xbox does not removes again!!! Error. ... and that is all. Maybe some component of the system is needed in the ToolkitHelper? Visual C++ or something else?
Well, you cannot remove settings but can hide its pages using group policy which is what I'd do after removing xbox crap. As for the latter question, I think it's not possible as the control panel is now being used as a placeholder and won't be there in RSX build when MS fully transfers all the settings to UWP app, may be
What does that file have to do with MSMG ToolKit? What about the fact of the store and photos apps being in english and not in my language and aren't opening when I click them?
ok I know how to use gpedit.msc, but sorry I send my question to MSMG so I stay waiting for some answer right dude
Since you are using Windows 10 v1709 x64 en-us 16299.19 as Host OS, so there's no need for .Net Framework 4.6 to be installed as it comes built-in with 4.7, so .Net Framework is not an issue. I did tested the ToolKit extracting to C:\Downloads\ToolKit-v7.9 and still the ToolKit Helper is working here. The steps you are doing is correct but still it's not working for you, anyway do like this - Right click on ToolKit.cmd and choose edit to open with Notepad. - Search for the below text, make sure it's "%InstallMount%" and not "%InstallMount%\%%i" Code: :: Removing Microsoft Windows People Experience Host if "%WindowsComponent%"=="PeopleExperienceHost" ( echo.------------------------------------------------------------------------------- echo.Removing Windows People Experience Host Package... echo.------------------------------------------------------------------------------- %ToolKitHelper% "%InstallMount%" PeopleExperienceHost ) - Now modifiy it like this Code: :: Removing Microsoft Windows People Experience Host if "%WindowsComponent%"=="PeopleExperienceHost" ( echo.------------------------------------------------------------------------------- echo.Removing Windows People Experience Host Package... echo.------------------------------------------------------------------------------- echo.ToolKitHelper=%ToolKitHelper% %ToolKitHelper% "%InstallMount%" PeopleExperienceHost ) - Save the file. - Run the ToolKit and select a single index for servicing. - Goto Remove Windows Componetns and Choose People Experience Host. - The ToolKit will show the path of ToolKitHelper.exe while removing the components. - Do tell me know what it shows.
When you remove a metro app using the DISM it will remove the entries from C:\ProgramData\Microsoft\Windows\AppxProvisioning.xml C:\Users\Default\AppData\Local\Microsoft\Windows\Shell\DefaultLayouts.xml Some Apps like Defender it will remove from the above said XML files and also from other few XML files from Windows folder too, the ToolKit uses the DISM to remove the Apps and so it's related, even for components which uses ToolKitHelper.exe also it uses the above said XML files for removing the App. In your previous post, you said you were using SW_DVD5_Win_Pro_Ent_Edu_N_10_1709_64BIT_English_MLF_X21-50143.iso and hence the apps are in english. If you want them to be in your language either use a ISO of your language or integrate a language pack and then integrate the metro app again to update the app language resources or wait for the WU/Store to update the app language resources. The Photos App not working I haven't checked about it and the Store App, it has been already discussed here that it's not working as it's missing some dependent packages. And today I chekced with the Store App manifest.xml file and here's the dependency packages Code: <Dependencies> <TargetDeviceFamily Name="Windows.Universal" MinVersion="10.0.10586.0" MaxVersionTested="10.0.15063.0"/> <TargetDeviceFamily Name="Windows.Holographic" MinVersion="10.0.14393.0" MaxVersionTested="10.0.14393.0"/> <PackageDependency Name="Microsoft.VCLibs.140.00" MinVersion="14.0.24123.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US"/> <PackageDependency Name="Microsoft.NET.Native.Framework.1.3" MinVersion="1.3.24201.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US"/> <PackageDependency Name="Microsoft.NET.Native.Runtime.1.4" MinVersion="1.4.24201.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US"/> </Dependencies> And for Photos App the dependency packages are Code: <Dependencies> <TargetDeviceFamily Name="Windows.Desktop" MinVersion="10.0.10586.0" MaxVersionTested="10.0.15063.0" /> <TargetDeviceFamily Name="Windows.Team" MinVersion="10.0.10586.0" MaxVersionTested="10.0.14393.0" /> <PackageDependency Name="Microsoft.VCLibs.140.00" MinVersion="14.0.24123.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US" /> <PackageDependency Name="Microsoft.NET.Native.Framework.1.3" MinVersion="1.3.24201.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US" /> <PackageDependency Name="Microsoft.NET.Native.Runtime.1.4" MinVersion="1.4.24201.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US" /> </Dependencies>
What @BladeGod said is correct the Settings App is required for Core Metro Services, StartMenu, if you remove it will break the StartMenu and other features of Windows Shell. You can customize the Settings App by hiding the requried componet like I have done for Defender, the Settings App will one day fully replace the classic control panel and there won't be control panel no more in future. If you still want to remove everything metro related then you may need to write down your own control panel, StartMenu and even a desktop shell.
I only want to remove the live tiles and the Windows Defender Security Center from Start Menu after I disabled it in systems in which I installed an untouched Windows 10 Creators Update/Fall Creators Update version or updated to Fall Creators Update after I installed a MSMG ToolKit Windows 10 Creators Update version. Besides that, I also have the other problem of not being able to open the photos and store apps and the fact that they are in english and not in my language.
@MSMG What I meant by manual removing using dism is removing packages one by one by mounting the wim. And yes, MSMG also uses dism but for some reason, it breaks the store app but the former doesn't. I guess you got my point.
I'm sorry I haven't searched enough for the report Good luck, if you need any help, don't hesitate, I'm a C# software developper
Ok other than removing the apps using the DISM, just some tweaks are applied, don't know what's causing it?
Quick question to everyone - has anyone been able to remove all of the Hyper-V stuff using MSMG and still be able to install? I removed the Hyper-V stuff, and now I get an error on install that says "Windows is having trouble accessing the required files for installation." I'm not using a virtual machine either, I booted it on my laptop on a USB drive. All of my changes work if I don't remove Hyper-V stuff, so I'm 100% sure that's causing the problem. Not a huge problem, and I could just leave Hyper-V alone, but I still think it's a little bizarre. Has anyone seen this before? I'm using Windows 10 Enterprise 1706 as a base. EDIT: Turns out that this wasn't caused by removing Hyper-V at all. There's a bug in the toolkit right now that may break images if you try to rename the sources inside of the .wim.