@MSMG , For Windows 10 LTSC 2019, 17763.1, do we remove components first and then integrate updates or integrate updates first then do the component removal?
The only reason for adding component removal support for Images with CU integrated for V1903/v1909/v2004/v20H2 images was due to the Microsoft's change in Windows Update which made the removed components to return when updated with a new CU. But with the v1809/LTSC 2019 that's not the case, the removed components won't get returned back, It's very difficult to update the component removal for every new CU. Will think of adding the support for W10 v1809/LTSC 2019 with CU integrated, but it will take some time,Till then use the 17763.1 base image and remove the components and then add the new CU.
The only reason for adding component removal support for Images with CU integrated for V1903/v1909/v2004/v20H2 images was due to the Microsoft's change in Windows Update which made the removed components to return when updated with a new CU. But with the v1809/LTSC 2019 that's not the case, the removed components won't get returned back, It's very difficult to update the component removal for every new CU. Will think of adding the support for W10 v1809/LTSC 2019 with CU integrated, but it will take some time,Till then use the 17763.1 base image and remove the components and then add the new CU.
The .NET Framework 3.5 source files inside <DVD\Source\sxs> folder contains the language resources files for only the image in the <DVD\source\install.wim>. For other language integrated to the install.wim you need the .NET Framework 3.5 language resources files for the integrated language. For this the Toolkit provides the .NET Framework 3.5 pack with all the language resources files and do use this pack.
There is no need to update the toolkit to every new CU for 1809/LTSC 2019. But it will be good to update it to the version that is availlable from Microsoft site: 10.0.17763.316
I didn't mean it! Which registry key must be mounted to set the default registry value for all users in the install.wim image? Why duplicate? As far as I know, the key itself will be automatically copied from the policy branch or I was wrong! Code: [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows Defender] "DisableAntiSpyware"=dword:00000001 [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Policies\Microsoft\Windows Defender] "DisableAntiSpyware"=dword:00000001
@MSMG To remove windows components using packing list, do I use removepkgslist.txt or removeappslist.txt? and is this the correct format for the toolkit? Code: AdobeFlashForWindows InternetExplorer FirstLogonAnimation GameExplorer SpeechRecognition WindowsMediaPlayer WindowsPhotoViewer WinSAT AssignedAccess CEIP_SQM FaceRecognition KernelDebugging LocationService PicturePassword PinEnrollment UnifiedTelemetryClient WiFiNetworkManager WindowsErrorReporting WindowsInsiderHub HomeGroup MultiPointConnector RemoteAssistance DeviceLockdown EaseOfAccessThemes EasyTransfer FileHistory SecurityCenter StepsRecorder SystemRestore WindowsBackup WindowsFirewall WindowsSubsystemForLinux WindowsToGo Wordpad AADBrokerPlugin AssignedAccessLockApp BioEnrollment CBSPreview ContentDeliveryManager Cortana ECApp EdgeDevToolsClient MapControl NarratorQuickStart OneDrive ParentalControls PeopleExperienceHost PPIProjection QuickAssist RetailDemoContent SecureAssessmentBrowser SettingSync SkypeORTC SmartScreen Win32WebViewHost WindowsDefender WindowsMixedReality WindowsReaderPDF XboxGameCallableUI 3DViewer AdvertisingXaml Alarms BingWeather Camera CommunicationsApps DesktopAppInstaller FeedbackHub GetHelp Getstarted HEIFImageExtension Maps Messaging MixedRealityPortal OfficeHub OfficeOneNote OneConnect Paint3D People Print3D ScreenSketch SkypeApp SolitaireCollection SoundRecorder StickyNotes VP9VideoExtensions WalletService WebMediaExtensions WebpImageExtensions WindowsStore XboxApp XboxIdentityProvider YourPhone ZuneMusic ZuneVideo
Not really screwed up, as the x64 CU integrates fine, no problems. Also, the July CU works fine, only the August CU's (both) have this issue. It's even on MS own "known issues" list, as quoted. It may have something to do with the component removal, this file: chxinputrouter.dll can be a part of something that I removed by means of the packages.txt file: Code: ToolKitHelper:FirstLogonAnimation ToolKitHelper:SnippingTool ToolKitHelper:AssignedAccess ToolKitHelper:CEIP_SQM ToolKitHelper:KernelDebugging ToolKitHelper:UnifiedTelemetryClient ToolKitHelper:WindowsInsiderHub ToolKitHelper:MultiPointConnector ToolKitHelper:EaseOfAccessThemes ToolKitHelper:SecurityCenter ToolKitHelper:DeviceLockdown ToolKitHelper:AADBrokerPlugin ToolKitHelper:AssignedAccessLockApp ToolKitHelper:CBSPreview ToolKitHelper:ContentDeliveryManager ToolKitHelper:Cortana ToolKitHelper:ECApp ToolKitHelper:NarratorQuickStart ToolKitHelper:ParentalControls ToolKitHelper:PeopleExperienceHost ToolKitHelper:QuickAssist ToolKitHelper:RetailDemoContent ToolKitHelper:SmartScreen ToolKitHelper:WindowsDefender ToolKitHelper:WindowsReaderPDF ToolKitHelper:XboxGameCallableUI Now that MSMG could integrate the x86 CU without problems, I have to look for the component on this list that causes the error. Cheers.