When integrating WU updates using MSMG toolkit, there are 4 options to choose from. #1. Integrate to Windows Setup Boot Image #2. Integrate to Windows Setup Install Image #3. Integrate to Windows Setup Install & Recovery Image #4 Integrate to Windows Setup boot, Install & Recovery Image. When I select Option #2, will this option work if I intend to install windows on my pc via USB or VM?
SFC scan error by following Windows 10 RS5/19H1/Server 2019/Server v1809/v1903 Usage Order by MSMG. Is Intro's method for no sfc scan errors for component removal and WU integration on LTSC 2019 17763.1 the only way possible? I also integrated win32 so could the sfc scan error be related to that? Code: ToolKitHelper:AdobeFlashForWindows ToolKitHelper:InternetExplorer ToolKitHelper:FirstLogonAnimation ToolKitHelper:GameExplorer ToolKitHelper:WindowsMediaPlayer ToolKitHelper:WinSAT ToolKitHelper:AssignedAccess ToolKitHelper:CEIP_SQM ToolKitHelper:FaceRecognition ToolKitHelper:KernelDebugging ToolKitHelper:LocationService ToolKitHelper:UnifiedTelemetryClient ToolKitHelper:WindowsErrorReporting ToolKitHelper:HomeGroup ToolKitHelper:MultiPointConnector ToolKitHelper:RemoteAssistance ToolKitHelper:DeviceLockdown ToolKitHelper:EaseOfAccessThemes ToolKitHelper:SystemRestore ToolKitHelper:WindowsSubsystemForLinux ToolKitHelper:WindowsToGo ToolKitHelper:AADBrokerPlugin ToolKitHelper:AssignedAccessLockApp ToolKitHelper:BioEnrollment ToolKitHelper:CBSPreview ToolKitHelper:ContentDeliveryManager ToolKitHelper:ECApp ToolKitHelper:EdgeDevToolsClient ToolKitHelper:Edge ToolKitHelper:LockApp ToolKitHelper:MapControl ToolKitHelper:NarratorQuickStart ToolKitHelper:OneDrive ToolKitHelper:ParentalControls ToolKitHelper:PeopleExperienceHost ToolKitHelper:PPIProjection ToolKitHelper:RetailDemoContent ToolKitHelper:SecureAssessmentBrowser ToolKitHelper:SettingSync ToolKitHelper:SkypeORTC2 ToolKitHelper:SmartScreen ToolKitHelper:WindowsDefender ToolKitHelper:WindowsMixedReality ToolKitHelper:WindowsReaderPDF ToolKitHelper:XboxGameCallableUI
Why do you guys integrate win32 calculator in LTSC? Why don't you guys ever read previous pages and investigate? It's so simple, just read for f**ks sake. It has been explained countless times that LTSC already contains the win32 calculator, it has got no metro apps. I really need a vacation.
Yes System Apps and Advanced Components removal will be available in future versions. right know the CU restores the removed components and yet to work on that.
Normal command prompt cannot modify certain registry keys and it needs special permissions, use NSudo to run the script.
Both versions are supported now for v1903, the support was added since 18362.1 was only available through UUP.
Remove All Apps won't remove the C:\Program Files\WindowsApps folder since the VC runtime and framework appx are retained.
RemoveAppsList.txt is for removing the Apps using the DISM. RemovePkgList.txt is for removing the packages with DISM and also with recent versions the support for removing ToolKitHelper.exe Components are added.
What component did you removed and which source OS are you using? Do post the package list contents you are using.
It's the Win32Calc since it is from 14393 build and the LTSC already contains an Win32Calc, it will give error. Integrating updates post component removal works.
Thank you for the update. Looking forward to the ability to remove advanced components like cortana and defender. I know the CU's put them back on currently.
Would be so nice to see. For me, and for most of us, I think having system removal [and hopefully being able to do so in batches than one by one] as well as some advanced windows components is most important. I don't even add .NET 3.5 anymore, a lot of software have moved on. By not adding .NET 3.5 I also think it reduces the risk of having 'dirty' images after finalizing. So to say, nice of priority can be on [removals] while [additions] could come later
I know. But still, if I integrate it, my start menu is broken. I'll stick with the ugly metro calculator app.
I'm sorry, I don't understand your answer You mean we cannot cleanup an image after integration of .NET 3.5 ?