[Solved] After performing remove first and then integration, caused the integration to fail (v2.3.8.8850)
- Thread starter devilink
- Start date
The normal rules for correct order of execution haven't changed.
Always integrate updates & optional packages BEFORE removing components. Windows updates are written to replace specific files, and applying them in reverse order will cause problems with missing files or the registry.
The only recent change is Store Apps (Appx) are now integrated after Windows component removals. This is allowed because Apps are replaced as complete packages, and they don't interfere with Windows system files.
Do you have a preset, where you think NTLite isn't applying the correct rules?
Always integrate updates & optional packages BEFORE removing components. Windows updates are written to replace specific files, and applying them in reverse order will cause problems with missing files or the registry.
The only recent change is Store Apps (Appx) are now integrated after Windows component removals. This is allowed because Apps are replaced as complete packages, and they don't interfere with Windows system files.
Do you have a preset, where you think NTLite isn't applying the correct rules?
Checking your preset:
Since my image is (en-US), adding the (zh-CN) LXP will add new language features to this ISO.
My list of updated Apps:
NTLite skipped WindowsCamera because it was for the wrong build. With this updated list of packages, NTLite had no problems.
- There are bug fixes in v2.3.8.8889+ for Appx integration.
- It is unnecessary to integrate all old versions of .NET.Native.Framework, .NET.Native.Runtime, and UI.Xaml.
Only add the most recent versions. - Your source image is W10 21H2 (zh-CN), adding the Chinese Language Experience Pack (LXP) will make no improvements.
LXP's are for local Windows editions which are missing other languages.
Since my image is (en-US), adding the (zh-CN) LXP will add new language features to this ISO.
My list of updated Apps:
Code:
Microsoft.Advertising.Xaml_10.1811.1.0_x64__8wekyb3d8bbwe.appx
Microsoft.DesktopAppInstaller_2022.728.1939.0_neutral_~_8wekyb3d8bbwe.msixbundle
Microsoft.HEIFImageExtension_1.0.43012.0_x64__8wekyb3d8bbwe.appx
Microsoft.LanguageExperiencePackzh-CN_19041.51.153.0_neutral__8wekyb3d8bbwe.Appx
Microsoft.NET.Native.Framework.2.2_2.2.29512.0_x64__8wekyb3d8bbwe.appx
Microsoft.NET.Native.Runtime.2.2_2.2.28604.0_x64__8wekyb3d8bbwe.appx
Microsoft.UI.Xaml.2.8_8.2208.12001.0_x64__8wekyb3d8bbwe.appx
Microsoft.VCLibs.140.00.UWPDesktop_14.0.30704.0_x64__8wekyb3d8bbwe.appx
Microsoft.VCLibs.140.00_14.0.30704.0_x64__8wekyb3d8bbwe.appx
Microsoft.VP9VideoExtensions_1.0.51171.0_x64__8wekyb3d8bbwe.appx
Microsoft.WebpImageExtension_1.0.52351.0_x64__8wekyb3d8bbwe.appx
Microsoft.WindowsAlarms_2022.2206.27.0_neutral_~_8wekyb3d8bbwe.msixbundle
Microsoft.WindowsCamera_2022.2207.29.0_neutral_~_8wekyb3d8bbwe.msixbundle
microsoft.windowscommunicationsapps_16005.14326.20970.0_neutral_~_8wekyb3d8bbwe.appxbundle
Microsoft.WindowsSoundRecorder_2021.2207.43.0_neutral_~_8wekyb3d8bbwe.appxbundle
Microsoft.WindowsStore_22207.1401.1.0_neutral_~_8wekyb3d8bbwe.msixbundle
Microsoft.WinJS.2.0_1.0.9600.17018_neutral__8wekyb3d8bbwe.Appx
Microsoft.Xbox.TCUI_1.24.10001.0_neutral_~_8wekyb3d8bbwe.appxbundle
Microsoft.XboxApp_48.89.25001.0_neutral_~_8wekyb3d8bbwe.appxbundle
Microsoft.XboxDevices_300.2202.25001.0_neutral_~_8wekyb3d8bbwe.appxbundle
Microsoft.XboxGameOverlay_1.54.4001.0_neutral_~_8wekyb3d8bbwe.appxbundle
Microsoft.XboxGamingOverlay_5.822.6271.0_neutral_~_8wekyb3d8bbwe.appxbundle
Microsoft.XboxIdentityProvider_12.90.14001.0_neutral_~_8wekyb3d8bbwe.appxbundle
Microsoft.XboxSpeechToTextOverlay_1.21.13002.0_neutral_~_8wekyb3d8bbwe.appxbundleNTLite skipped WindowsCamera because it was for the wrong build. With this updated list of packages, NTLite had no problems.
