LTSC Net Framework bug

It may be problems integrating .NET language packs in the right sequence.
The language packs don't contain the .NET Framework components that are required to run an app, so you must run the web or offline installer before you install a language pack. If you have already installed a language pack, uninstall it, install the .NET Framework, and then reinstall the language pack.
Click to expand...

Integrate in two passes.
Pass 1 - .NET frameworks + CU. Apply updates, but don't save to image.
Pass 2 - Add language packs. Apply updates, and save to ISO.
 
I've always wondered about this? My theory was opposite: If the language packs have to be there first, in order for some "sub-components" of the CU to update the language packs? Presumably a bug fix in CU contains updated translations?

For example (this is real): "If you are one of the hundreds of parachuting enthusiasts that bought our book 'Easy Skydiving in One Fell Swoop' please change line 19 on page 23 from 'state zip code' to ' pull ripcord'."
 
The normal rule for Windows is install language packs first, but .NET is backwards /shrug

Languages overview (Windows)
  • Install languages, then updates and apps. If you're adding languages to an image that already contains apps or updates (for example, servicing stack updates (SSU) or a latest cumulative update (LCU), reinstall the apps and updates.
    Important
    After you install a language pack, you have to reinstall the latest cumulative update (LCU). If you do not reinstall the LCU, you may encounter errors. If the LCU is already installed, Windows Update does not offer it again. You have to manually install the LCU.
Click to expand...

To install language packs (.NET)
Language packs are executable files that contain the localized resources (such as translated error messages and UI text) for supported languages. If you don't install a language pack, .NET Framework error messages and other text are displayed in English. Note that the web installer automatically installs the language pack that matches your operating system, but you can download additional language packs to your computer. The offline installers don't include any language packs.

Important
The language packs don't contain the .NET Framework components that are required to run an app, so you must run the web or offline installer before you install a language pack. If you have already installed a language pack, uninstall it, install the .NET Framework, and then reinstall the language pack.
Click to expand...
 
Follow-up for the archive records:

With KB5014630 (released Q2 2022, direct descendent/successor of KB5004752 / KB5010473), NTLite v2.3.5.8714, and on a Win10 21H2 build environment, using the same original Dell OEM WinSrv2016 ISO, and same NTLite Preset XML (Except the KB changes of most-recent CU, SSU, and DotNet CU), this problem solved itself.

I'm skeptical that the Build Environment (of 21H2) was the cure; one of the other factors.
 
Last edited:
You must log in or register to reply here.
Back
Top