[DISCUSSION] Windows 10 Enterprise (N) LTSC 2019

This is the CU applicability list:

Code:

<mum2:customInformation Dependency="Language Pack" Version="10.0.17763.55" xmlns:mum2="urn:schemas-microsoft-com:asm.v3" PackageFormat="PSFX" />
    <parent buildCompare="EQ" integrate="separate" disposition="detect">
      <assemblyIdentity name="Microsoft-Windows-CoreCountrySpecificEdition" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-CoreEdition" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-CoreNEdition" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-EnterpriseEvalEdition" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-EnterpriseGEdition" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-EnterpriseNEvalEdition" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-EnterpriseSEdition" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-EnterpriseSEvalEdition" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-EnterpriseSNEdition" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-EnterpriseSNEvalEdition" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-ProfessionalEdition" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-ProfessionalNEdition" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-ServerDatacenterACorEdition" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-ServerDatacenterCorEdition" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-ServerDatacenterEdition" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-ServerDatacenterEvalCorEdition" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-ServerDatacenterEvalEdition" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-ServerDatacenterNanoEdition" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-ServerHyperCoreEdition" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-ServerSolutionEdition" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-ServerStandardACorEdition" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-ServerStandardCorEdition" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-ServerStandardEdition" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-ServerStandardEvalCorEdition" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-ServerStandardEvalEdition" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-ServerStandardNanoEdition" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-UtilityVMEdition" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-WinPE-Package" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="WinPE-HTA-Package" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="WinPE-LegacySetup-Package" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="WinPE-Rejuv-Package" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="WinPE-Scripting-Package" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="WinPE-Setup-Package" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="WinPE-SRT-Package" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />

 

As you can see, enterpriseS and SN are available on the other updates applicability lists:
CU: https://forums.mydigitallife.net/th...rprise-n-ltsc-2019.76325/page-60#post-1471421
It's missing at the Flash updates list.

 

Just tested an inplace upgrade to 17763.55 and yeah my documents folder is not deleted in the upgrade so they fixed that

 

yes thats why i was ready do update LTSC without adobe but it worked with dism command now i integrated all 3 updates with no issues and im going test it .

 

It didn't work on LTSC, the 2019 LTSC install doesn't even get the flash update offered on WU.

Re-check what sku you ran the command on.

 

Installed Updates via WUSA on a live system and Flash Sec was skipped hence missing in installed updates list.

 

Finally Flash update doesn't have LTSC listed in the applicability list.

 

yeah you are right .its integrate but on what windows update they are installed is not showing the adobe

 

It states "not applicable" when integrated.

 

no just i show you in the screen before is integrated and success.

 

And i showed it states the "not applicable to this image" error.

 

nop.

 

Yep: https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-329#post-1471380

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

offline integration into the .wim files (x86 and x64) worked fine for me, with no error messages.

-andy-

 

You need to login to view this posts content.

 

Would be interesting to check what:

Code:

dism /image:"d:\mount" /Get-Packages

shows and if it appears after install.

It didn't get installed on my LTSC install (notebook).

 

So now disk cleanup wipes out the whole "downloads" folder if you were so confident to put a check mark in all boxes...

Cheers.

 

yes i talked about that several weeks ago and I wasn't amused..........I can only imagine what stuff people will wipe out