There is not 1904x Starter. Official 15063.0 Windows 10 Starter https://forums.mydigitallife.net/threads/windows-editions-reconstruction-project.80939/
Actually i'm a newbie. I'm interested in Reconstruction. You can actually teach me on Private Message or Discord. So the people you don't want to know can't find out. I promise I will not share your Discord address with anyone else. You don't have to share your Discord address. But I think it would be safer than other people. You can tell me when you're available.
[FYI] Code: Converting 19041.1 Windows 10 Pro to IoT Enterprise LTSC amd64 en-US Mounting image Creating IoTEnterpriseS Adding en-US language pack Removing Store Adding SSU Adding 21H2Enablement Adding LCU Current Edition : IoTEnterpriseS (OEM) Resetting base Unmounting image 19044.1202 Windows 10 IoT Enterprise LTSC amd64 en-US has been successfully created Press any key to continue . . . Code: WIM Information: --------------------- GUID:{511213BF-FD3F-3DDA-6457-AE9980160AE8} Image Count:1 Compression:LZX Part Number:1/1 Attributes:0x8 RP_FIX Image Index: 1 ------------------- Name:Windows 10 IoT Enterprise LTSC 2021 Description:Windows 10 IoT Enterprise LTSC 2021 Flags:IoTEnterpriseS Files:85364 Folders:25189 Expanded Size:12174 MB WIM XML Information: --------------------------- <WIM> <IMAGE INDEX="1"> <DIRCOUNT>25189</DIRCOUNT> <FILECOUNT>85364</FILECOUNT> <TOTALBYTES>12766277839</TOTALBYTES> <HARDLINKBYTES>5766219317</HARDLINKBYTES> <CREATIONTIME> <HIGHPART>0x01D5ACF0</HIGHPART> <LOWPART>0x608D2670</LOWPART> </CREATIONTIME> <LASTMODIFICATIONTIME> <HIGHPART>0x01D7BE9B</HIGHPART> <LOWPART>0xAD892921</LOWPART> </LASTMODIFICATIONTIME> <WIMBOOT>0</WIMBOOT> <WINDOWS> <ARCH>9</ARCH> <PRODUCTNAME>Microsoft® Windows® Operating System</PRODUCTNAME> <EDITIONID>IoTEnterpriseS</EDITIONID> <INSTALLATIONTYPE>Client</INSTALLATIONTYPE> <SERVICINGDATA> <GDRDUREVISION>0</GDRDUREVISION> <PKEYCONFIGVERSION>10.0.19041.1202;2016-01-01T00:00:00Z</PKEYCONFIGVERSION> <IMAGESTATE>IMAGE_STATE_GENERALIZE_RESEAL_TO_OOBE</IMAGESTATE> </SERVICINGDATA> <PRODUCTTYPE>WinNT</PRODUCTTYPE> <PRODUCTSUITE>Terminal Server</PRODUCTSUITE> <LANGUAGES> <LANGUAGE>en-US</LANGUAGE> <DEFAULT>en-US</DEFAULT> </LANGUAGES> <VERSION> <MAJOR>10</MAJOR> <MINOR>0</MINOR> <BUILD>19044</BUILD> <SPBUILD>1202</SPBUILD> <SPLEVEL>0</SPLEVEL> <BRANCH>vb_release</BRANCH> </VERSION> <SYSTEMROOT>WINDOWS</SYSTEMROOT> </WINDOWS> <NAME>Windows 10 IoT Enterprise LTSC 2021</NAME> <DESCRIPTION>Windows 10 IoT Enterprise LTSC 2021</DESCRIPTION> <FLAGS>IoTEnterpriseS</FLAGS> <DISPLAYNAME>Windows 10 IoT Enterprise LTSC</DISPLAYNAME> <DISPLAYDESCRIPTION>Windows 10 IoT Enterprise LTSC</DISPLAYDESCRIPTION> </IMAGE> <TOTALBYTES>3288224818</TOTALBYTES> </WIM>
No problem. Unfortunately my English is not specific, I often confuse American English and British English.
Q: Is amd64 mum\cat compatible with arm64? A: No. We can use arm64 mum\cat of a package to fake another package only. e.g. There is not available arm64 Win32Calc. But we still need a fake one for working update. We 1. rename Microsoft-Windows-Branding-EnterpriseS-Package~31bf3856ad364e35~arm64~~10.0.19041.1.mum\cat as Microsoft-Windows-win32calc-Package~31bf3856ad364e35~arm64~~10.0.19041.1.mum\cat 2. modify content of the mum from Code: <?xml version="1.0" encoding="utf-8" standalone="yes"?> <assembly xmlns="urn:schemas-microsoft-com:asm.v3" manifestVersion="1.0" copyright="Copyright (c) Microsoft Corporation. All Rights Reserved."> <assemblyIdentity name="Microsoft-Windows-win32calc-Package" version="10.0.19041.1" processorArchitecture="arm64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> <package identifier="win32calc-Package" releaseType="Feature Pack"> <parent integrate="delegate"> <assemblyIdentity name="Microsoft-Windows-Foundation-Package" version="10.0.19041.1" processorArchitecture="arm64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </parent> <update description="Install Win32 Calculator" displayName="Win32 Calculator" name="win32calc"> <component> <assemblyIdentity name="Microsoft-Windows-win32calc-Deployment" version="10.0.19041.1" processorArchitecture="arm64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" /> </component> </update> </package> </assembly> to Code: <?xml version="1.0" encoding="utf-8" standalone="yes"?> <assembly xmlns="urn:schemas-microsoft-com:asm.v3" manifestVersion="1.0" copyright="Copyright (c) Microsoft Corporation. All Rights Reserved."> <assemblyIdentity name="Microsoft-Windows-win32calc-Package" version="10.0.19041.1" processorArchitecture="arm64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> <package identifier="win32calc-Package" releaseType="Feature Pack"> <parent integrate="delegate"> <assemblyIdentity name="Microsoft-Windows-Foundation-Package" version="10.0.19041.1" processorArchitecture="arm64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </parent> </package> </assembly> In this way, there is correct Win32Calc registry item even though there is not real Win32Calc binariy files, Windows Update recongnizes it, and, since it has not Win32Calc definition in the mum, it will update whole system and skip Win32Calc language pack. One day, when there is official arm64 Win32Calc, you revert the mum, and it is FULL 19044 21H2 LTSC arm64. Code: Converting 19041.1 Windows 10 Pro to IoT Enterprise LTSC arm64 xx-XX Mounting image Creating IoTEnterpriseS Adding xx-XX language pack Current Edition : IoTEnterpriseS (OEM) Removing Store Resetting base Unmounting image 19041.1 Windows 10 IoT Enterprise LTSC arm64 xx-XX has been successfully created Press any key to continue . . . 19044.1200 Code: WIM Information: --------------------- GUID:{7B893D06-CD32-4BCB-88D5-B0AF74B79FEA} Image Count:1 Compression:LZX Part Number:1/1 Attributes:0x8 RP_FIX Image Index: 1 ------------------- Name:Windows 10 IoT Enterprise LTSC 2021 Description:Windows 10 IoT Enterprise LTSC 2021 Flags:IoTEnterpriseS Files:92235 Folders:28879 Expanded Size:13019 MB WIM XML Information: --------------------------- <WIM> <TOTALBYTES>3377652724</TOTALBYTES> <IMAGE INDEX="1"> <DIRCOUNT>28879</DIRCOUNT> <FILECOUNT>92235</FILECOUNT> <TOTALBYTES>13652456603</TOTALBYTES> <HARDLINKBYTES>6294643066</HARDLINKBYTES> <CREATIONTIME> <HIGHPART>0x01D5AD20</HIGHPART> <LOWPART>0x41288DEC</LOWPART> </CREATIONTIME> <LASTMODIFICATIONTIME> <HIGHPART>0x01D7BF37</HIGHPART> <LOWPART>0x7D8E5016</LOWPART> </LASTMODIFICATIONTIME> <WIMBOOT>0</WIMBOOT> <WINDOWS> <ARCH>12</ARCH> <PRODUCTNAME>Microsoft® Windows® Operating System</PRODUCTNAME> <EDITIONID>IoTEnterpriseS</EDITIONID> <INSTALLATIONTYPE>Client</INSTALLATIONTYPE> <SERVICINGDATA> <GDRDUREVISION>0</GDRDUREVISION> <PKEYCONFIGVERSION>10.0.19041.1200;2016-01-01T00:00:00Z</PKEYCONFIGVERSION> <IMAGESTATE>IMAGE_STATE_GENERALIZE_RESEAL_TO_OOBE</IMAGESTATE> </SERVICINGDATA> <PRODUCTTYPE>WinNT</PRODUCTTYPE> <PRODUCTSUITE>Terminal Server</PRODUCTSUITE> <LANGUAGES> <LANGUAGE>xx-XX</LANGUAGE> <FALLBACK LANGUAGE="xx-XX">en-US</FALLBACK> <DEFAULT>xx-XX</DEFAULT> </LANGUAGES> <VERSION> <MAJOR>10</MAJOR> <MINOR>0</MINOR> <BUILD>19044</BUILD> <SPBUILD>1200</SPBUILD> <SPLEVEL>0</SPLEVEL> <BRANCH>vb_release</BRANCH> </VERSION> <SYSTEMROOT>WINDOWS</SYSTEMROOT> </WINDOWS> <NAME>Windows 10 IoT Enterprise LTSC 2021</NAME> <DESCRIPTION>Windows 10 IoT Enterprise LTSC 2021</DESCRIPTION> <FLAGS>IoTEnterpriseS</FLAGS> <DISPLAYNAME>Windows 10 IoT Enterprise LTSC</DISPLAYNAME> <DISPLAYDESCRIPTION>Windows 10 IoT Enterprise LTSC</DISPLAYDESCRIPTION> </IMAGE> </WIM> Beautiful
You have to learn using Mr. SuperBubble's package extraction tool. [VBScript] Aunty Mel's Cheap And Nasty SxS Package Extractor (Updated 2013/11/09) https://forums.mydigitallife.net/th...s-package-extractor-updated-2013-09-30.48325/
Has anyone tried to install Windows 11 User Experience Desktop Package on latest Server IP? In theory it should bring new 11 UI to Server. Recreating Server Insider Preview for ARM64 might not be impossible too, but updates won't work because it is a unexisting build.
I'm afraid that Server's Product policy won't allow it. And, ServerARM64 has key only. Code: <Phase seq="1"> <package id="Microsoft-Windows-ServerWebEdition~31bf3856ad364e35~amd64~~10.0.22463.1000" name="Windows Server Web Edition" targetState="Installed" options="0"/> <package id="Microsoft-Windows-ServerDatacenterEdition~31bf3856ad364e35~amd64~~10.0.22463.1000" name="Windows ServerDatacenter Edition" targetState="Staged" options="9"/> <package id="Microsoft-Windows-ServerDatacenterEvalEdition~31bf3856ad364e35~amd64~~10.0.22463.1000" name="Windows ServerDatacenterEval Edition" targetState="Staged" options="9"/> <package id="Microsoft-Windows-ServerStandardEdition~31bf3856ad364e35~amd64~~10.0.22463.1000" name="Windows ServerStandard Edition" targetState="Staged" options="9"/> <package id="Microsoft-Windows-ServerStandardEvalEdition~31bf3856ad364e35~amd64~~10.0.22463.1000" name="Windows ServerStandardEval Edition" targetState="Staged" options="9"/> <package id="Microsoft-Windows-ServerTurbineEdition~31bf3856ad364e35~amd64~~10.0.22463.1000" name="Windows ServerTurbine Edition" targetState="Staged" options="9"/> </Phase>