Windows 10: DISM.exe failed about wrong setup order in LTSC 2019 x641809 cause hr: 0x800f0800nothing...

I'm new configuring the LTSC 2019 without Internet, trying to deal with server setup practice.1.Things well known below:1.1-"control-program - windows...fuction-.net3.5" can't be turn on by one click on win7/win8/win10/win11, so we need a Image from another successed windows 10 can be found from web1.2-the online method Windows Updatewuserv, dont work with LTSCLTSC is the version who try avoid windows update automaticly or frequently checked and installed,so the less , necessary patch can be found with the setup as a part of "function installation pack group" and the "component-like patc

:)

 

Office 2019

Only supported on Win10. Sorry, 8.1 users, only 4 years old, gotta go.

Microsoft Office 2019 will only work on Windows 10

https://blogs.technet.microsoft.com...-to-office-and-windows-servicing-and-support/

Spoiler Office 2019
Last year at Ignite, we announced Office 2019 – the next perpetual version of Office that includes apps (including Word, Excel, PowerPoint, and Outlook, and Skype for Business) and servers (including Exchange, SharePoint, and Skype for Business). Today we’re pleased to share the following updates:

• Office 2019 will ship in H2 of 2018. Previews of the new apps and servers will start shipping in the second quarter of 2018.
• Office 2019 apps will be supported on:
  • Any supported Windows 10 SAC release
  • Windows 10 Enterprise LTSC 2018
  • The next LTSC release of Windows Server
• The Office 2019 client apps will be released with Click-to-Run installation technology only. We will not provide MSI as a deployment methodology for Office 2019 clients. We will continue to provide MSI for Office Server products.

 

Windows 10 LTSC 2021 License Downgrade to 2019 LTSC

Does the Windows 10 LTSC 2021 has the license downgrade right to Windows 10 LTSC 2019?

 

Dism Online Cleanup-Image RestoreHealth fails

I tried Dism Online Cleanup-Image RestoreHealth after Windows update locked up the boot

DISM failed. No operation was performed: dism.log errors

2019-01-11 18:44:25, Info DISM DISM Package Manager: PID=15128 TID=15148 Error in operation: (null) (CBS HRESULT=0x80072ee6) - CCbsConUIHandler::Error

2019-01-11 18:44:25, Error DISM DISM Package Manager: PID=15128 TID=15144 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x80072ee6)

2019-01-11 18:44:25, Error DISM DISM Package Manager: PID=15128 TID=15144 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x80072ee6)

2019-01-11 18:44:25, Error DISM DISM Package Manager: PID=15128 TID=15144 Failed to restore the image health. - CPackageManagerCLIHandler:rocessCmdLine_CleanupImage(hr:0x80072ee6)

2019-01-11 18:44:25, Error DISM DISM Package Manager: PID=15128 TID=15144 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x80072ee6)

2019-01-11 18:44:25, Info DISM DISM Package Manager: PID=15128 TID=15144 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine

2019-01-11 18:44:25, Error DISM DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=80072EE6

NB this is an Asus X750JB laptop with Microsoft Windows 10 Pro Version 10.0.17134 Build 17134, originally bought as Windows 7, upgraded to 8, 8.1 then 10. Now with a SanDisk SDSSDA240G. As such, the boot sequence in the BIOS seems to be legacy rather than
UEFI.

Any ideas how to fix this?