I only have raw es-ES, which is what I needed. It cost me a lot of time, since I had to analyze the errors to add necessary files.
"Why?" because since Windows Server 2016 NanoServer isn't supported for infrastructure server. Originally you could create a VM with Nano, or even install it on host. Now that is a container image only. You need manual reconstruction to create modern Nano. But internal packages are required.
25398.1~469 Code: <assemblyIdentity name="microsoft-windows-immersivecontrolpanel.appxmain" version="10.0.25398.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" /> 25398.531 Code: <assemblyIdentity name="microsoft-windows-immersivecontrolpanel.appxmain" version="10.0.25398.531" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" /> 25398.887 Code: <assemblyIdentity name="microsoft-windows-immersivecontrolpanel.appxmain" version="10.0.25398.887" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" /> If the neutral component is updated but the corresponding LP is not updated, this issue will occur.
Indeed, Nano server 2016 has also its own editions, somehow like if it is another product or family. It would be an amazing project to create a Nano server 2025. I can see two paths: - create dedicated packages like in Nano server 2016 - using windows server 2025 packages * * in this case, what are the differences with the core edition ?
Well, if you do understand, what "Container image" is, and what differs container image of Nano (let's now speak about Nano 2016) from infrastructure image of Nano (2016) - you see just few packages, needed to run as dedicated VM or bare-metal. With Container image now Nano is available as a regularly updated service in Azure. If the aim is to run it bare-metal or inside VM, you may add packages from 2016. But in current Nano image the list of roles is seriously cut from 2016. It is way more "nano" then "core". 10 times at least.
I reckon: Yarrak31 wants working solution (CUs) for tr-TR. You made for Yarrak31. Yarrak31 is happy. Other members, using different script, not happy. Final way: You provive your own 25398.1 script which is matched with your CUs as advised by xinso last night.
I had suggested zwl29107 a final way to solve it once for all. Wait patiently. If yes, you earned; If no, nothing lost.