Windows 10 LTSC 21H2 updates procedure post-EOL (End Of Life)

16309

Member
Messages
77
Reaction score
24
November 11, 2025—KB5068781 (OS Builds 19044.6575 and 19045.6575) - this update doesnt show on Windows 10, version 21H2 update history, it only show up when i click on Windows 10 Extended Security Updates (ESU) program.

There is a note that says
Important: Use EKB KB5003791 to update to Windows 10, version 21H2 on supported editions.

What is the update procedure now, can KB5068781 onwards be integrated(or run as normal prior to capture) or do we need to do or add something beforehand and what is EKB KB5003791?

What about LTSC 1809?

Apologies for being on the ball on this especially as KB5068781 has only just been released but it gives nuhi garlin tistou77 time to look and see if any changes need to be made.
 
Last edited:
16309 have you managed to figure it out?

Tried fetching
2025-11 Cumulative Update for Windows 10 Version 21H2 for x64-based Systems (KB5068781)Windows 10 LTSB
from windows update catalog and it will fail at 99% with clean en-us_windows_10_enterprise_ltsc_2021_x64_dvd_d289cf96.iso

the article above states that
Windows 10 Long Term Servicing releases (LTSB/LTSC) have their own lifecycles and are NOT covered via the Windows 10 ESU program. For more information, see Microsoft Lifecycle, so there should be an LTSC applicable package, EOL for LTSC is 2027.
 
Last edited:
I did not paid for NTLite to give advises to follow Microsoft guides, but to give solutions.
That's a bold statement, are you saying NTLite should bypass ESU?

Windows 10 Long Term Servicing releases (LTSB/LTSC) have their own lifecycles and are NOT covered via the Windows 10 ESU program. For more information, see Microsoft Lifecycle, so there should be an LTSC applicable package, EOL for LTSC is 2027.
Exactly, I am confused by that as well, as soon as you or me get some info regarding that, it will be implemented.
Make sure to post here if you find it, I'll also look.

Have you, with the LTSC, tried integrating from the same OS version and allowing internet connection (for DISM) as described in the Microsoft's guide?
 
Exactly, I am confused by that as well

So was i and others will be too and thats why i asked. MS listing that update under "ESU" doesnt help.
Now people know about this our(this forums) experts can look decide if anything needs to be done and give absolute clarification on the matter.
 
16309 have you managed to figure it out?
No because i am having problems installing ltsc 2021 on my thinkpad and i never grab the latest updates on patch tuesday(incase they get replaced before the end of the month) so i wait till the end of the month to see if they have been replaced/any reports of a bad cu that has problems.
 
tried again from ltsb section of windows update catalog - goes again to 99% and fails with a 'corrupted image' message.
However at work packages downloaded via WU on 21h2 ltsc VDIs worked ok, haven't tried yet manual upgrade from the available cab.

Code:
2025-11-13 20:36:55, Info                  CBS    Failed to execute execution chain. [HRESULT = 0x80073713 - ERROR_ADVANCED_INSTALLER_FAILED]
2025-11-13 20:36:55, Error                 CBS    Failed to process single phase execution. [HRESULT = 0x80073713 - ERROR_ADVANCED_INSTALLER_FAILED]
2025-11-13 20:36:55, Info                  CBS    WER: Generating failure report for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~19041.6575.1.22, status: 0x80073713, failure source: Execute, start state: Staged, target state: Installed, client id: DISM Package Manager Provider
2025-11-13 20:36:55, Info                  CBS    Not able to query DisableWerReporting flag.  Assuming not set... [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2025-11-13 20:36:55, Info                  CBS    Added \\?\G:\Temp\NTLite_dism.log to WER report.
2025-11-13 20:36:55, Info                  CBS    FinalCommitPackagesState: Started persisting state of packages
2025-11-13 20:36:55, Info                  CBS    Reporting package change for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~19041.6575.1.22, current: Absent, pending: Default, start: Absent, applicable: Installed, target: Installed, limit: Installed, status: 0x0, failure source: Execute, reboot required: False, client id: DISM Package Manager Provider, initiated offline: True, execution sequence: 34, first merged sequence: 34, reboot reason: REBOOT_NOT_REQUIRED, RM App session: 0, RM App name: N/A, FileName in use: N/A, release type: Security Update, OC operation: False, download source: 0, download time (secs): 0, download status: 0x0 (S_OK), Express download: False, Download Size: 0
2025-11-13 20:36:55, Info                  CBS    Reporting package change completion for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~19041.6575.1.22, current: Staged, original: Absent, target: Installed, status: 0x80073713, failure source: Execute, failure details: "(null)", client id: DISM Package Manager Provider, initiated offline: True, execution sequence: 34, first merged sequence: 34, pending decision: InteractiveInstallFailed, primitive execution context: Interactive
2025-11-13 20:36:55, Info                  CBS    Cannot read value for the force canceled current transaction. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2025-11-13 20:36:55, Info                  CBS    CBS force canceled transaction status datapoint is invalid. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2025-11-13 20:36:55, Info                  CBS    The store corruption status report is incomplete. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2025-11-13 20:36:55, Info                  CBS    Execute time performance datapoint is invalid. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2025-11-13 20:36:55, Info                  CBS    FinalCommitPackagesState: Completed persisting state of packages
2025-11-13 20:36:55, Info                  DISM   DISM Package Manager: PID=28664 TID=5372  Error in operation: (null) (CBS HRESULT=0x80073713) - CCbsConUIHandler::Error
2025-11-13 20:36:55, Info                  CBS    Exec: Current execution did not succeed but is not a valid auto repair scenario, skip auto repair.
2025-11-13 20:36:55, Info                  CBS    Exec: Processing complete.  Session: 28664_41987234, Package: Package_for_RollupFix~31bf3856ad364e35~amd64~~19041.6575.1.22, Identifier: KB5068781 [HRESULT = 0x80073713 - ERROR_ADVANCED_INSTALLER_FAILED]
2025-11-13 20:36:55, Info                  CBS    Removing the pending hard reserve adjustment for Client: DISM Package Manager Provider, Session: 28664_41987234
2025-11-13 20:36:55, Error                 CBS    Failed to perform operation.  [HRESULT = 0x80073713 - ERROR_ADVANCED_INSTALLER_FAILED]
2025-11-13 20:36:55, Info                  CBS    Session: 28664_41987234 finalized. Reboot required: no [HRESULT = 0x80073713 - ERROR_ADVANCED_INSTALLER_FAILED]
2025-11-13 20:36:55, Error                 DISM   DISM Package Manager: PID=28664 TID=5372 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x80073713)
2025-11-13 20:36:55, Error                 DISM   DISM Package Manager: PID=28664 TID=5372 Failed processing package changes - CDISMPackageManager::ProcessChanges(hr:0x80073713)
2025-11-13 20:36:55, Error                 DISM   API: PID=7648 TID=30608 Failed to process package  changes - CAddPackageCommandObject::InternalExecute(hr:0x80073713)
2025-11-13 20:36:55, Info                  CBS    Deleting directory: \\?\G:\Temp\NLTmpMnt\Windows\CbsTemp\28664_41987234\
2025-11-13 20:36:55, Info                  CBS    Moving directory from \\?\G:\Temp\NLTmpMnt\Windows\CbsTemp\28664_41987234\ to \\?\G:\Temp\NLTmpMnt\Windows\CbsTemp\28664_41987234\{D89D9B5E-7D25-46BA-90D5-7757C00FE884}
2025-11-13 20:36:55, Info                  CBS    Failed to move \\?\G:\Temp\NLTmpMnt\Windows\CbsTemp\28664_41987234\ to temp directory \\?\G:\Temp\NLTmpMnt\Windows\CbsTemp\28664_41987234\{D89D9B5E-7D25-46BA-90D5-7757C00FE884} [HRESULT = 0x80070057 - E_INVALIDARG]
2025-11-13 20:36:55, Info                  CBS    Failed moving directory: \\?\G:\Temp\NLTmpMnt\Windows\CbsTemp\28664_41987234\ to temp, will delete in-place instead [HRESULT = 0x80070057 - E_INVALIDARG]
2025-11-13 20:36:56, Info                  CBS    Deletion of: \\?\G:\Temp\NLTmpMnt\Windows\CbsTemp\28664_41987234\ successful
(..)
2025-11-13 20:37:03, Info                  DPX    ProvideRequestedDataByFile failed, Response file Name: \\?\G:\NTLite\Cache\Updates\10.21H2.x64\windows10.0-kb5011048-x64.cab
2025-11-13 20:37:03, Info                  CBS    Failed to extract file TOC.xml from cabinet \\?\G:\NTLite\Cache\Updates\10.21H2.x64\windows10.0-kb5011048-x64.cab [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
(..)
2025-11-13 20:37:03, Info                  DPX    Ended DPX phase: Resume and Download Job
2025-11-13 20:37:03, Info                  DPX    Extraction of file: update.ses failed because it is not present in the container (\\?\G:\NTLite\Cache\Updates\10.21H2.x64\windows10.0-kb5011048-x64.cab).
2025-11-13 20:37:03, Info                  DPX    DpxException hr=0x80070002 code=0x020109
2025-11-13 20:37:03, Info                  CBS    Not able to add file to extract: update.ses [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2025-11-13 20:37:03, Warning               DISM   API: PID=7648 TID=30608 The image does not support checking for servicing stack reload. - CAddPackageCommandObject::InternalExecute
2025-11-13 20:37:03, Info                  CBS    Appl: detect Parent, Package: Package_for_KB5011048~31bf3856ad364e35~amd64~~10.0.1.8028, Parent: Microsoft-Windows-CoreCountrySpecificEdition~31bf3856ad364e35~amd64~~10.0.19041.1, Disposition = Detect, VersionComp: EQ, BuildComp: GE, RevisionComp: GE, Exist: present
2025-11-13 20:37:03, Info                  CBS    Appl: detectParent: no parent found, go absent
2025-11-13 20:37:03, Info                  CBS    Appl: detect Parent, Package: Package_for_KB5011048~31bf3856ad364e35~amd64~~10.0.1.8028, Parent: Microsoft-Windows-CoreEdition~31bf3856ad364e35~amd64~~10.0.19041.1, Disposition = Detect, VersionComp: EQ, BuildComp: GE, RevisionComp: GE, Exist: present
2025-11-13 20:37:03, Info                  CBS    Appl: detectParent: no parent found, go absent
2025-11-13 20:37:03, Info                  CBS    Appl: detect Parent, Package: Package_for_KB5011048~31bf3856ad364e35~amd64~~10.0.1.8028, Parent: Microsoft-Windows-CoreNEdition~31bf3856ad364e35~amd64~~10.0.19041.1, Disposition = Detect, VersionComp: EQ, BuildComp: GE, RevisionComp: GE, Exist: present
2025-11-13 20:37:03, Info                  CBS    Appl: detectParent: no parent found, go absent
2025-11-13 20:37:03, Info                  CBS    Appl: detect Parent, Package: Package_for_KB5011048~31bf3856ad364e35~amd64~~10.0.1.8028, Parent: Microsoft-Windows-EnterpriseEvalEdition~31bf3856ad364e35~amd64~~10.0.19041.1, Disposition = Detect, VersionComp: EQ, BuildComp: GE, RevisionComp: GE, Exist: present
2025-11-13 20:37:03, Info                  CBS    Appl: detectParent: no parent found, go absent
2025-11-13 20:37:03, Info                  CBS    Appl: detect Parent, Package: Package_for_KB5011048~31bf3856ad364e35~amd64~~10.0.1.8028, Parent: Microsoft-Windows-EnterpriseGEdition~31bf3856ad364e35~amd64~~10.0.19041.1, Disposition = Detect, VersionComp: EQ, BuildComp: GE, RevisionComp: GE, Exist: present
2025-11-13 20:37:03, Info                  CBS    Appl: detectParent: no parent found, go absent
2025-11-13 20:37:03, Info                  CBS    Appl: detect Parent, Package: Package_for_KB5011048~31bf3856ad364e35~amd64~~10.0.1.8028, Parent: Microsoft-Windows-EnterpriseGNEdition~31bf3856ad364e35~amd64~~10.0.19041.1, Disposition = Detect, VersionComp: EQ, BuildComp: GE, RevisionComp: GE, Exist: present
2025-11-13 20:37:03, Info                  CBS    Appl: detectParent: no parent found, go absent
2025-11-13 20:37:03, Info                  CBS    Appl: detect Parent, Package: Package_for_KB5011048~31bf3856ad364e35~amd64~~10.0.1.8028, Parent: Microsoft-Windows-EnterpriseNEvalEdition~31bf3856ad364e35~amd64~~10.0.19041.1, Disposition = Detect, VersionComp: EQ, BuildComp: GE, RevisionComp: GE, Exist: present
2025-11-13 20:37:03, Info                  CBS    Appl: detectParent: no parent found, go absent
2025-11-13 20:37:03, Info                  CBS    Appl: detect Parent, Package: Package_for_KB5011048~31bf3856ad364e35~amd64~~10.0.1.8028, Parent: Microsoft-Windows-EnterpriseSEdition~31bf3856ad364e35~amd64~~10.0.19041.1, Disposition = Detect, VersionComp: EQ, BuildComp: GE, RevisionComp: GE, Exist: present
2025-11-13 20:37:03, Info                  CBS    Appl: detectParent: parent found: Microsoft-Windows-EnterpriseSEdition~31bf3856ad364e35~amd64~~10.0.19041.1288, state: Installed
2025-11-13 20:37:03, Info                  CBS    Appl: Evaluating package applicability for package Package_for_KB5011048~31bf3856ad364e35~amd64~~10.0.1.8028, applicable state: Installed
2025-11-13 20:37:03, Info                  CBS    External EvaluateApplicability, package: Package_for_KB5011048~31bf3856ad364e35~amd64~~10.0.1.8028, package applicable State: Installed, highest update applicable state: Installed, resulting applicable state:Installed
2025-11-13 20:37:03, Info                  DISM   DISM Package Manager: PID=28664 TID=5372 Initiating Changes on Package with values: 4, 7 - CDISMPackage::Internal_ChangePackageState
2025-11-13 20:37:03, Info                  DISM   DISM Package Manager: PID=28664 TID=5372 CBS session options=0x0! - CDISMPackageManager::Internal_Finalize
2025-11-13 20:37:03, Info                  CBS    Real pend will be used if required
2025-11-13 20:37:03, Error                 CBS    The image has been damaged by an offline servicing failure and no further servicing is allowed. [HRESULT = 0x800f0830 - CBS_E_IMAGE_UNSERVICEABLE]
2025-11-13 20:37:03, Info                  CBS    FinalCommitPackagesState: Started persisting state of packages
2025-11-13 20:37:03, Info                  CBS    FinalCommitPackagesState: Completed persisting state of packages
2025-11-13 20:37:03, Info                  DISM   DISM Package Manager: PID=28664 TID=5372  Error in operation: (null) (CBS HRESULT=0x800f0830) - CCbsConUIHandler::Error
2025-11-13 20:37:03, Info                  CBS    Exec: Current execution did not succeed but is not a valid auto repair scenario, skip auto repair.
2025-11-13 20:37:03, Info                  CBS    Exec: Processing complete.  Session: 28664_43528093, Package: Package_for_KB5011048~31bf3856ad364e35~amd64~~10.0.1.8028, Identifier: KB5011048 [HRESULT = 0x800f0830 - CBS_E_IMAGE_UNSERVICEABLE]
2025-11-13 20:37:03, Error                 CBS    Failed to perform operation.  [HRESULT = 0x800f0830 - CBS_E_IMAGE_UNSERVICEABLE]
2025-11-13 20:37:03, Info                  CBS    Session: 28664_43528093 finalized. Reboot required: no [HRESULT = 0x800f0830 - CBS_E_IMAGE_UNSERVICEABLE]
2025-11-13 20:37:03, Error                 DISM   DISM Package Manager: PID=28664 TID=5372 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800f0830)
2025-11-13 20:37:04, Error                 DISM   DISM Package Manager: PID=28664 TID=5372 Discard this Windows image and try the operation again on a new Windows image. - GetCbsErrorMsg
2025-11-13 20:37:04, Error                 DISM   DISM Package Manager: PID=28664 TID=5372 Failed processing package changes - CDISMPackageManager::ProcessChanges(hr:0x800f0830)
2025-11-13 20:37:04, Error                 DISM   DISM Package Manager: PID=28664 TID=5372 Discard this Windows image and try the operation again on a new Windows image. - GetCbsErrorMsg
2025-11-13 20:37:04, Error                 DISM   API: PID=7648 TID=30608 Failed to process package  changes - CAddPackageCommandObject::InternalExecute(hr:0x800f0830)
2025-11-13 20:37:04, Info                  CBS    Deleting directory: \\?\G:\Temp\NLTmpMnt\Windows\CbsTemp\28664_43528093\
2025-11-13 20:37:04, Info                  CBS    Moving directory from \\?\G:\Temp\NLTmpMnt\Windows\CbsTemp\28664_43528093\ to \\?\G:\Temp\NLTmpMnt\Windows\CbsTemp\28664_43528093\{FC9D9E3C-FA15-43A2-8FC8-09C8ED6436FB}
2025-11-13 20:37:04, Info                  CBS    Failed to move \\?\G:\Temp\NLTmpMnt\Windows\CbsTemp\28664_43528093\ to temp directory \\?\G:\Temp\NLTmpMnt\Windows\CbsTemp\28664_43528093\{FC9D9E3C-FA15-43A2-8FC8-09C8ED6436FB} [HRESULT = 0x80070057 - E_INVALIDARG]
2025-11-13 20:37:04, Info                  CBS    Failed moving directory: \\?\G:\Temp\NLTmpMnt\Windows\CbsTemp\28664_43528093\ to temp, will delete in-place instead [HRESULT = 0x80070057 - E_INVALIDARG]
2025-11-13 20:37:04, Info                  CBS    Deletion of: \\?\G:\Temp\NLTmpMnt\Windows\CbsTemp\28664_43528093\ successful
 
tried again from ltsb section of windows update catalog - goes again to 99% and fails with a 'corrupted image' message.
However at work packages downloaded via WU on 21h2 ltsc VDIs worked ok, haven't tried yet manual upgrade from the available cab.
garlin might be related to this post.
 
Hi everyone, I tried to install the latest update KB 5071546 on a new ISO Windows 10 2021 LTSC AFTER installing the following updates:

1)
ssu-19041.3562-x64_de23c91f483b2e609cec3e4a995639d13205f867.msu

(As specified by Microsoft for offline updates)

2)
kb5062682

(Dynamic Update for Windows 10, versions 21H2 and 22H2)

3)
KB5072542

(Secure Operating System Dynamic Update for Windows 10, versions 21H2 and 22H2)

But creating the new ISO fails as shown below:

ntlite.PNG

Has anyone had the same problem with Windows 10 2021 LTSC?
 
Hi everyone, I tried to install the latest update KB5071546 on a new ISO Windows 10 2021 LTSC AFTER installing the following updates:

You cannot integrate (install) ESU updates to offline image

because ESU validation can't be executed offline
otherwise, anyone could change EditionID in install.wim image registry to EnterpriseS, and bypass the validation
 
You cannot integrate (install) ESU updates to offline image

because ESU validation can't be executed offline
otherwise, anyone could change EditionID in install.wim image registry to EnterpriseS, and bypass the validation
So not even possible with active ESU on the Win10 host?
In that case I'll block/warn it in the UI when image is a target.
Thanks for the info.
 
Looks like MS will not correct this to allow for LTSC integration, despite being an supported edition.
VDIs with 10 21h2 LTSC will still apply it live from windows update without any ESU.
 
So not even possible with active ESU on the Win10 host?
In that case I'll block/warn it in the UI when image is a target.
Thanks for the info.

No, that's only for updates for the host itself

since Win7, ESU update = no offline integration, no matter what

in Win10, they only exempted WinPE from this condition (i.e. you can add ESU to boot.wim)

the only free way for LTSC 2021 is to install the update live in Audit mode, and capture new install.wim
however, you must do that for each new LCU
 
Back
Top