I don't understand this? SKU selection list is empty as you can see. I've captured the wim by using this command since there is not an option that you can choose the wim flag via DISM. Obviously it must be Windows Foundation. This is the command I've tried: Code: wimlib-imagex.exe capture E:\ C:\Users\<My Username>\Desktop\Unstaged\install.wim "Windows Longhorn Client" "Windows Longhorn Client (22000.469.amd64fre.co_release.220118-1733) EDITIONS:CLOUDEDITION,CLOUDEDITIONN,CORE,CORECOUNTRYSPECIFIC,COREN,CORESINGLELANGUAGE,EDUCATION,EDUCATIONN,ENTERPRISE,ENTERPRISEEVAL,ENTERPRISEG,ENTERPRISEGN,ENTERPRISEN,ENTERPRISENEVAL,IOTENTERPRISE,PPIPRO,PROFESSIONAL,PROFESSIONALCOUNTRYSPECIFIC,PROFESSIONALEDUCATION,PROFESSIONALEDUCATIONN,PROFESSIONALN,PROFESSIONALSINGLELANGUAGE,PROFESSIONALWORKSTATION,PROFESSIONALWORKSTATIONN,SERVERRDSH" --flags="Windows Foundation"
Use the xml in page1 to install the edition code:1.xml Code: <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <servicing> <package action="install"> <assemblyIdentity name="Microsoft-Windows-EnterpriseGEdition" version="10.0.22000.1" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" /> <source location="Z:\EnterpriseG.mum" /> </package> </servicing> </unattend> code:2.xml Code: <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <servicing> <package action="install"> <assemblyIdentity name="Microsoft-Windows-Client-Languagepack-Package" version="10.0.22000.1" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="en-us" /> <source location="Z:\langpacks\en-us\update.mum" /> </package> </servicing> </unattend> hint: unstaged image applied to Z:\
To install language pack, just use dism add-package is much more convenient. Otherwise, 38 languages, you have to modify or make 38 xmls.
I don't know what I'm supposed to do to unstage an ISO. I'm trying to do all of this manually, but somehow I always getting an error. I actually need either an automated script or a detailed tutorial for that.
1.xml in the unstaged ISO has info like this Plus, even an untouched ISO of 14357 has pkeyconfig.xrm-ms and pidgenx.dll inside of the packages folder at the root of install.wim. Code: Index : 1 Name : Windows Longhorn Client Description : Windows Longhorn Client (14357.1000.amd64fre.rs1_release.160527-1700) EDITIONS:ENTERPRISE,CORE,COREARM,CORECONNECTED,CORECONNECTEDCOUNTRYSPECIFIC,CORECONNECTEDN,CORECONNECTEDSINGLELANGUAGE,CORECOUNTRYSPECIFIC,COREN,CORESINGLELANGUAGE,EDUCATION,EDUCATIONN,EMBEDDEDINDUSTRY,EMBEDDEDINDUSTRYA,EMBEDDEDINDUSTRYE,EMBEDDEDINDUSTRYEEVAL,EMBEDDEDINDUSTRYEVAL,ENTERPRISEEVAL,ENTERPRISEN,ENTERPRISENEVAL,ENTERPRISES,ENTERPRISESEVAL,ENTERPRISESN,ENTERPRISESNEVAL,ENTERPRISESUBSCRIPTION,ENTERPRISESUBSCRIPTIONN,PPIPRO,PROFESSIONAL,PROFESSIONALCOUNTRYSPECIFIC,PROFESSIONALEDUCATION,PROFESSIONALEDUCATIONN,PROFESSIONALN,PROFESSIONALS,PROFESSIONALSN,PROFESSIONALSINGLELANGUAGE,PROFESSIONALSTUDENT,PROFESSIONALSTUDENTN,PROFESSIONALWMC,PROFESSIONALWORKSTATION,PROFESSIONALWORKSTATIONN,STARTER,STARTERN
You use iso-boot to stage the unstaged.wim. I use two simple xmls to stage it --much faster and convenient
Master, can you tell me what a standard unstaged.wim looks like? I don't know if I'm doing it right? Code: <IMAGE INDEX="1"> <DIRCOUNT>13908</DIRCOUNT> <FILECOUNT>57736</FILECOUNT> <TOTALBYTES>6960624251</TOTALBYTES> <HARDLINKBYTES>82331269</HARDLINKBYTES> <CREATIONTIME> <HIGHPART>0x01D75A3A</HIGHPART> <LOWPART>0x45C417B7</LOWPART> </CREATIONTIME> <LASTMODIFICATIONTIME> <HIGHPART>0x01D835B3</HIGHPART> <LOWPART>0xE041C669</LOWPART> </LASTMODIFICATIONTIME> <WIMBOOT>0</WIMBOOT> <WINDOWS> <ARCH>9</ARCH> <PRODUCTNAME>Microsoft® Windows® Operating System</PRODUCTNAME> <SERVICINGDATA> <IMAGESTATE>IMAGE_STATE_GENERALIZE_RESEAL_TO_OOBE</IMAGESTATE> </SERVICINGDATA> <VERSION> <MAJOR>10</MAJOR> <MINOR>0</MINOR> <BUILD>22000</BUILD> <SPBUILD>1</SPBUILD> <SPLEVEL>0</SPLEVEL> </VERSION> <SYSTEMROOT>WINDOWS</SYSTEMROOT> </WINDOWS> <NAME>Windows 11 专业版</NAME> <DESCRIPTION>Windows 11 专业版</DESCRIPTION> <FLAGS>professional</FLAGS> <DISPLAYNAME></DISPLAYNAME> <DISPLAYDESCRIPTION></DISPLAYDESCRIPTION> </IMAGE> </WIM> Spoiler
Found a problem of making 22000.1 unstaged iso: The setup.exe will not launch legacy setup when running on a working system(not pe) Identification: the functions in autorun.dll has changed , the one in 22000 will not check if the iso is unstaged. Solution: replace autorun.dll with the one in older builds like 19100.1051.