Thanks. I created 2 files xml 1.xml -> ok <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <servicing> <package action="stage"> <assemblyIdentity name="Microsoft-Windows-EnterpriseSEdition" version="10.0.19041.1237" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" /> <source location="Windows10.0-KB5005565-x64-baseless\Microsoft-Windows-EnterpriseSEdition~31bf3856ad364e35~amd64~~10.0.19041.1237.mum" /> </package> </servicing> </unattend> 2.xml -> same error <unattend xmlns="urn:schemas-microsoft-com:unattend"> <servicing> <package action="remove"> <assemblyIdentity name="Microsoft-Windows-ProfessionalEdition" version="10.0.19041.1237" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" /> </package> <package action="install"> <assemblyIdentity name="Microsoft-Windows-EnterpriseSEdition" version="10.0.19041.1237" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" /> </package> </servicing> </unattend>
It happens when you don't run a resetbase after installing KB5005565. You have two choices: 1. If you don't have pending packages try to run dism /image:"your_work_folder_path" /cleanup-image /startcomponentcleanup /resetbase on your image and apply 2.xml again, or 2. You have to remove 19041.1 ProfessionalEdition as well. In this case your 2.xml should look like this below, if you skip resetbase: Code: <unattend xmlns="urn:schemas-microsoft-com:unattend"> <servicing> <package action="install"> <assemblyIdentity name="Microsoft-Windows-EnterpriseSEdition" version="10.0.19041.1237" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" /> </package> <package action="remove"> <assemblyIdentity name="Microsoft-Windows-ProfessionalEdition" version="10.0.19041.1" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" /> </package> <package action="remove"> <assemblyIdentity name="Microsoft-Windows-ProfessionalEdition" version="10.0.19041.1237" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" /> </package> </servicing> </unattend> One of these should do the job.
Q: Is updated image reconstruction possible for Windows Update? If yes, a very good reconstruction. If no, not bad for a custom image if you can do custom update for it.
Unexpected answer. Not a right or full but useful for reconstruction. The most needed language files are License.rtf They are not in any original langpack, and in LCUs it's not that simple.. I found that a fresh copy of License and dozen of other mui files are in fresh (current 19041.1233, release each two month - local experience pack mul_windows_10_version_2004_or_20h2_8c_local_experience_packs_lxps_updated_september_2021_x86_x64_arm64_dvd_79e83212.iso)
LXP has the same MUI files for most System binaries, including Explorer, win32calc, etc I was shocked to find that You would need to create folders in SXS to put missing files if LCU isnt working Can't understand how these files are neutral (in ru-ru folder)
19044.1200 Windows 10 Enterprise LTSC reconstruction Code: Converting 19044.1200 Windows 10 Pro to IoT Enterprise LTSC amd64 xx-XX Mounting image Creating IoTEnterpriseS Adding xx-XX language pack Current Edition : IoTEnterpriseS (OEM) Removing Store Resetting base Unmounting image 19044.1200 Windows 10 IoT Enterprise LTSC amd64 xx-XX has been successfully created Press any key to continue . . .
Q: Where is the ProductName from? Code: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion] "CompositionEditionID"="EnterpriseS" "EditionID"="EnterpriseS" "ProductName"="Windows 10 Enterprise LTSC 2021"