Q: What are requirements for 19044 LTSC reconstruction? A: In sxs folder - binaries not shown. Code: Microsoft-Windows-Branding-EnterpriseS-Package~31bf3856ad364e35~amd64~~10.0.19041.1.cat Microsoft-Windows-Branding-EnterpriseS-Package~31bf3856ad364e35~amd64~~10.0.19041.1.mum Microsoft-Windows-Editions-EnterpriseS-Package~31bf3856ad364e35~amd64~~10.0.19041.1.cat Microsoft-Windows-Editions-EnterpriseS-Package~31bf3856ad364e35~amd64~~10.0.19041.1.mum Microsoft-Windows-EditionSpecific-EnterpriseS-Package~31bf3856ad364e35~amd64~~10.0.19041.1.cat Microsoft-Windows-EditionSpecific-EnterpriseS-Package~31bf3856ad364e35~amd64~~10.0.19041.1.mum Microsoft-Windows-EnterpriseS-SPP-Components-Package~31bf3856ad364e35~amd64~~10.0.19041.1.cat Microsoft-Windows-EnterpriseS-SPP-Components-Package~31bf3856ad364e35~amd64~~10.0.19041.1.mum Microsoft-Windows-EnterpriseSEdition~31bf3856ad364e35~amd64~~10.0.19041.1.cat Microsoft-Windows-EnterpriseSEdition~31bf3856ad364e35~amd64~~10.0.19041.1.mum Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseS-Default-Package~31bf3856ad364e35~amd64~~10.0.19041.1.cat Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseS-Default-Package~31bf3856ad364e35~amd64~~10.0.19041.1.mum Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseS-License-Package~31bf3856ad364e35~amd64~~10.0.19041.1.cat Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseS-License-Package~31bf3856ad364e35~amd64~~10.0.19041.1.mum Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseS-Package~31bf3856ad364e35~amd64~~10.0.19041.1.cat Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseS-Package~31bf3856ad364e35~amd64~~10.0.19041.1.mum Microsoft-Windows-Security-SPP-Component-SKU-IoTEnterpriseS-License-Package~31bf3856ad364e35~amd64~~10.0.19041.1.cat Microsoft-Windows-Security-SPP-Component-SKU-IoTEnterpriseS-License-Package~31bf3856ad364e35~amd64~~10.0.19041.1.mum Microsoft-Windows-Shell32-OEMDefaultAssociations-Legacy-Package~31bf3856ad364e35~amd64~~10.0.19041.1.cat Microsoft-Windows-Shell32-OEMDefaultAssociations-Legacy-Package~31bf3856ad364e35~amd64~~10.0.19041.1.mum Microsoft-Windows-win32calc-Package~31bf3856ad364e35~amd64~~10.0.19041.1.cat Microsoft-Windows-win32calc-Package~31bf3856ad364e35~amd64~~10.0.19041.1.mum
Hi my dear friend @SunLion First of all, I hope you, all our colleagues of MDL and all your friends and family are well and healthy now and always... Could you share the files that you use on your method? I use pt-BR language iso too... Thanks in advanced. Best Regards @JeepWillys58
I noticed some changes on LTSC 2019 sku From install.wim Code: DefaultPpd-EnterpriseS-ppdlic.xrm-ms EnterpriseS-OEM-DM-1-pl-rtm.xrm-ms EnterpriseS-OEM-DM-1-ul-oob-rtm.xrm-ms EnterpriseS-OEM-DM-1-ul-phn-rtm.xrm-ms EnterpriseS-OEM-DM-1-ul-store-rtm.xrm-ms EnterpriseS-OEM-NONSLP-1-pl-rtm.xrm-ms EnterpriseS-OEM-NONSLP-1-ul-oob-rtm.xrm-ms EnterpriseS-OEM-NONSLP-1-ul-phn-rtm.xrm-ms EnterpriseS-OEM-NONSLP-1-ul-store-rtm.xrm-ms EnterpriseS-ppdlic.xrm-ms EnterpriseS-Volume-CSVLK-1-pl-rtm.xrm-ms EnterpriseS-Volume-CSVLK-1-ul-oob-rtm.xrm-ms EnterpriseS-Volume-CSVLK-1-ul-phn-rtm.xrm-ms EnterpriseS-Volume-CSVLK-1-ul-store-rtm.xrm-ms EnterpriseS-Volume-CSVLK-2-pl-rtm.xrm-ms EnterpriseS-Volume-CSVLK-2-ul-oob-rtm.xrm-ms EnterpriseS-Volume-CSVLK-2-ul-phn-rtm.xrm-ms EnterpriseS-Volume-CSVLK-2-ul-store-rtm.xrm-ms EnterpriseS-Volume-CSVLK-3-pl-rtm.xrm-ms EnterpriseS-Volume-CSVLK-3-ul-oob-rtm.xrm-ms EnterpriseS-Volume-CSVLK-3-ul-phn-rtm.xrm-ms EnterpriseS-Volume-CSVLK-3-ul-store-rtm.xrm-ms EnterpriseS-Volume-CSVLK-4-pl-rtm.xrm-ms EnterpriseS-Volume-CSVLK-4-ul-oob-rtm.xrm-ms EnterpriseS-Volume-CSVLK-4-ul-phn-rtm.xrm-ms EnterpriseS-Volume-CSVLK-4-ul-store-rtm.xrm-ms EnterpriseS-Volume-CSVLK-5-pl-rtm.xrm-ms EnterpriseS-Volume-CSVLK-5-ul-oob-rtm.xrm-ms EnterpriseS-Volume-CSVLK-5-ul-phn-rtm.xrm-ms EnterpriseS-Volume-CSVLK-5-ul-store-rtm.xrm-ms EnterpriseS-Volume-CSVLK-6-pl-rtm.xrm-ms EnterpriseS-Volume-CSVLK-6-ul-oob-rtm.xrm-ms EnterpriseS-Volume-CSVLK-6-ul-phn-rtm.xrm-ms EnterpriseS-Volume-CSVLK-6-ul-store-rtm.xrm-ms EnterpriseS-Volume-GVLK-1-ul-oob-rtm.xrm-ms EnterpriseS-Volume-GVLK-1-ul-rtm.xrm-ms EnterpriseS-Volume-MAK-1-pl-rtm.xrm-ms EnterpriseS-Volume-MAK-1-ul-oob-rtm.xrm-ms EnterpriseS-Volume-MAK-1-ul-phn-rtm.xrm-ms EnterpriseS-Volume-MAK-1-ul-store-rtm.xrm-ms After installing Code: DefaultPpd-EnterpriseS-ppdlic.xrm-ms EnterpriseS-OEM-DM-1-pl-rtm.xrm-ms EnterpriseS-OEM-DM-1-ul-oob-rtm.xrm-ms EnterpriseS-OEM-DM-1-ul-phn-rtm.xrm-ms EnterpriseS-OEM-DM-1-ul-store-rtm.xrm-ms EnterpriseS-OEM-DM-2-pl-rtm.xrm-ms EnterpriseS-OEM-DM-2-ul-oob-rtm.xrm-ms EnterpriseS-OEM-DM-2-ul-phn-rtm.xrm-ms EnterpriseS-OEM-DM-2-ul-store-rtm.xrm-ms EnterpriseS-OEM-NONSLP-1-pl-rtm.xrm-ms EnterpriseS-OEM-NONSLP-1-ul-oob-rtm.xrm-ms EnterpriseS-OEM-NONSLP-1-ul-phn-rtm.xrm-ms EnterpriseS-OEM-NONSLP-1-ul-store-rtm.xrm-ms EnterpriseS-OEM-NONSLP-2-pl-rtm.xrm-ms EnterpriseS-OEM-NONSLP-2-ul-oob-rtm.xrm-ms EnterpriseS-OEM-NONSLP-2-ul-phn-rtm.xrm-ms EnterpriseS-OEM-NONSLP-2-ul-store-rtm.xrm-ms EnterpriseS-ppdlic.xrm-ms EnterpriseS-Volume-CSVLK-1-pl-rtm.xrm-ms EnterpriseS-Volume-CSVLK-1-ul-oob-rtm.xrm-ms EnterpriseS-Volume-CSVLK-1-ul-phn-rtm.xrm-ms EnterpriseS-Volume-CSVLK-1-ul-store-rtm.xrm-ms EnterpriseS-Volume-CSVLK-2-pl-rtm.xrm-ms EnterpriseS-Volume-CSVLK-2-ul-oob-rtm.xrm-ms EnterpriseS-Volume-CSVLK-2-ul-phn-rtm.xrm-ms EnterpriseS-Volume-CSVLK-2-ul-store-rtm.xrm-ms EnterpriseS-Volume-CSVLK-3-pl-rtm.xrm-ms EnterpriseS-Volume-CSVLK-3-ul-oob-rtm.xrm-ms EnterpriseS-Volume-CSVLK-3-ul-phn-rtm.xrm-ms EnterpriseS-Volume-CSVLK-3-ul-store-rtm.xrm-ms EnterpriseS-Volume-CSVLK-4-pl-rtm.xrm-ms EnterpriseS-Volume-CSVLK-4-ul-oob-rtm.xrm-ms EnterpriseS-Volume-CSVLK-4-ul-phn-rtm.xrm-ms EnterpriseS-Volume-CSVLK-4-ul-store-rtm.xrm-ms EnterpriseS-Volume-CSVLK-5-pl-rtm.xrm-ms EnterpriseS-Volume-CSVLK-5-ul-oob-rtm.xrm-ms EnterpriseS-Volume-CSVLK-5-ul-phn-rtm.xrm-ms EnterpriseS-Volume-CSVLK-5-ul-store-rtm.xrm-ms EnterpriseS-Volume-CSVLK-6-pl-rtm.xrm-ms EnterpriseS-Volume-CSVLK-6-ul-oob-rtm.xrm-ms EnterpriseS-Volume-CSVLK-6-ul-phn-rtm.xrm-ms EnterpriseS-Volume-CSVLK-6-ul-store-rtm.xrm-ms EnterpriseS-Volume-GVLK-1-ul-oob-rtm.xrm-ms EnterpriseS-Volume-GVLK-1-ul-rtm.xrm-ms EnterpriseS-Volume-MAK-1-pl-rtm.xrm-ms EnterpriseS-Volume-MAK-1-ul-oob-rtm.xrm-ms EnterpriseS-Volume-MAK-1-ul-phn-rtm.xrm-ms EnterpriseS-Volume-MAK-1-ul-store-rtm.xrm-ms These were added after installing Code: EnterpriseS-OEM-DM-2-pl-rtm.xrm-ms EnterpriseS-OEM-DM-2-ul-oob-rtm.xrm-ms EnterpriseS-OEM-DM-2-ul-phn-rtm.xrm-ms EnterpriseS-OEM-DM-2-ul-store-rtm.xrm-ms EnterpriseS-OEM-NONSLP-2-pl-rtm.xrm-ms EnterpriseS-OEM-NONSLP-2-ul-oob-rtm.xrm-ms EnterpriseS-OEM-NONSLP-2-ul-phn-rtm.xrm-ms EnterpriseS-OEM-NONSLP-2-ul-store-rtm.xrm-ms
17763.2091 Windows10.0-KB5005394-x64_PSFX.cab Package_393_for_KB5005394~31bf3856ad364e35~amd64~~10.0.1.0 Code: EnterpriseS-OEM-DM-2-pl-rtm.xrm-ms EnterpriseS-OEM-DM-2-ul-oob-rtm.xrm-ms EnterpriseS-OEM-DM-2-ul-phn-rtm.xrm-ms EnterpriseS-OEM-DM-2-ul-store-rtm.xrm-ms EnterpriseS-OEM-NONSLP-2-pl-rtm.xrm-ms EnterpriseS-OEM-NONSLP-2-ul-oob-rtm.xrm-ms EnterpriseS-OEM-NONSLP-2-ul-phn-rtm.xrm-ms EnterpriseS-OEM-NONSLP-2-ul-store-rtm.xrm-ms Package_580_for_KB5005394~31bf3856ad364e35~amd64~~10.0.1.0 Code: pkeyconfig.xrm-ms pkeyconfig-downlevel.xrm-ms Package_4695_for_KB5005394~31bf3856ad364e35~amd64~~10.0.1.0 Code: csvlk-pack-Volume-CSVLK-10-pl-rtm.xrm-ms csvlk-pack-Volume-CSVLK-10-ul-oob-rtm.xrm-ms csvlk-pack-Volume-CSVLK-10-ul-phn-rtm.xrm-ms csvlk-pack-Volume-CSVLK-10-ul-store-rtm.xrm-ms csvlk-pack-Volume-CSVLK-11-pl-rtm.xrm-ms csvlk-pack-Volume-CSVLK-11-ul-oob-rtm.xrm-ms csvlk-pack-Volume-CSVLK-11-ul-phn-rtm.xrm-ms csvlk-pack-Volume-CSVLK-11-ul-store-rtm.xrm-ms csvlk-pack-Volume-CSVLK-12-pl-rtm.xrm-ms csvlk-pack-Volume-CSVLK-12-ul-oob-rtm.xrm-ms csvlk-pack-Volume-CSVLK-12-ul-phn-rtm.xrm-ms csvlk-pack-Volume-CSVLK-12-ul-store-rtm.xrm-ms csvlk-pack-Volume-CSVLK-13-pl-rtm.xrm-ms csvlk-pack-Volume-CSVLK-13-ul-oob-rtm.xrm-ms csvlk-pack-Volume-CSVLK-13-ul-phn-rtm.xrm-ms csvlk-pack-Volume-CSVLK-13-ul-store-rtm.xrm-ms
Fact: From 18362 forward, new update technology and PSFX update patch need complete source files. The Quick-Switch "EnterpriseS" is NOT recognized by updates. Therefore, the updates actually update Pro, NOT EnterpriseS. Down the track when Pro reaches End of Service, what? Game over. Maybe I am wrong. Time will tell. (But I have been playing Quick-Switch for a long time... Every time when it reached End of Service, I have to make custom update to keep it alive, or disable Windows Update.)
I finally succeeded with ServerTurbine 2022. Would prepare reconstruction files today New challenge is to reconstruct Hyper-V Server (ServerHyperCore), problem is we lack some files (branding, etc, which I don't want to take from 17763)
Together, we stand; seperated, we fall. Or Together, both stand; seperated, the stronger stands, the weaker falls. Or Helping each other, both get stronger. Taking without giving, is like a one-way ticket, no return. This is why a return ticket is cheaper.
Master is too strict to me. I am happy to share ServerTurbine (2019 or 2022) - just PM me, as rules don't allow to post self-made builds. I was able to reconstruct ServerTurbine 2022 (fully and clean) would provide files after some sleep. I have tried to reconstruct ServerTurbineCor but failed as neither updates, nor full version in Azure has files like License.rtf, Upgradematrix.xml, EditionMatrix.xml and ServerTurbineCor.xml for Core Miss five WinSxS folders: Spoiler amd64_microsoft-windows-e..ns-serverturbinecor amd64_microsoft-windows-l..lt-serverturbinecor amd64_microsoft-windows-l..me-serverturbinecor x86_microsoft-windows-l..lt-serverturbinecor x86_microsoft-windows-l..me-serverturbinecor And I am quite sure that until these folders appear in one of PSFX in future updates, no-one would be able to show working ServerTurbineCor 2022 Pushing files from full ServerTurbine fail the hash check. And I am not yet able to unpack binary files in \f and \r SxS folders, like amd64_microsoft-windows-l..me-serverturbinecor_31bf3856ad364e35_10.0.20348.112_none_571b7cbaedc034c9\f\license.rtf They are some way encoded, and SXSEpnd doesnt unpack them. Btw, can you explain please, why you consider Hyper-V Server (ServerHyperCore) an abandoned SKU? On TechReady last week they showed Hyper-V Server 2022 in work.
Q: And I am not yet able to unpack binary files in \f and \r SxS folders, like amd64_microsoft-windows-l..me-serverturbinecor_31bf3856ad364e35_10.0.20348.112_none_571b7cbaedc034c9\f\license.rtf A: Extract the updated package --> Remove f & n & b --> original update package Q: Btw, can you explain please, why you consider Hyper-V Server (ServerHyperCore) an abandoned SKU? On TechReady last week they showed Hyper-V Server 2022 in work. A: a. Because of Code: <Phase seq="1"> <package id="Microsoft-Windows-ServerStandardCorEdition~31bf3856ad364e35~amd64~~10.0.20348.1" name="Windows ServerStandardCor Edition" targetState="Installed" options="0"/> <package id="Microsoft-Windows-ServerStandardEvalCorEdition~31bf3856ad364e35~amd64~~10.0.20348.1" name="Windows ServerStandardEvalCor Edition" targetState="Staged" options="9"/> <package id="Microsoft-Windows-ServerDatacenterCorEdition~31bf3856ad364e35~amd64~~10.0.20348.1" name="Windows ServerDatacenterCor Edition" targetState="Staged" options="9"/> <package id="Microsoft-Windows-ServerDatacenterEvalCorEdition~31bf3856ad364e35~amd64~~10.0.20348.1" name="Windows ServerDatacenterEvalCor Edition" targetState="Staged" options="9"/> <package id="Microsoft-Windows-ServerStandardACorEdition~31bf3856ad364e35~amd64~~10.0.20348.1" name="Windows ServerStandardACor Edition" targetState="Staged" options="9"/> <package id="Microsoft-Windows-ServerDatacenterACorEdition~31bf3856ad364e35~amd64~~10.0.20348.1" name="Windows ServerDatacenterACor Edition" targetState="Staged" options="9"/> <package id="Microsoft-Windows-ServerAzureStackHCICorEdition~31bf3856ad364e35~amd64~~10.0.20348.1" name="Windows ServerAzureStackHCICor Edition" targetState="Staged" options="9"/> <package id="Microsoft-Windows-ServerTurbineCorEdition~31bf3856ad364e35~amd64~~10.0.20348.1" name="Windows ServerTurbineCor Edition" targetState="Staged" options="9"/> </Phase> b. I don't know about it.
1. Mount 20348.112 ServerTurbine install.wim (or open vhd if you have it) 2. Extract target updated package 3. Uncompress extracted package cab to folder 4. Delete folder\f, n, r 5. Compress folder to cab
If I extract Microsoft-Windows-Editions-ServerTurbine-Package from full ServerTurbine, it has files only for full. In installed OS in WinSxS the folders are with encoded files in \f and \r folders only. So no ServerTurbineCor files in CAB, nor in WinSxS The Microsoft-Windows-Editions-ServerTurbineCor-Package is from PSF updates, with only encoded \f \r files. No clean.
If you PM me, so I can reply, I would send VHDs and/or WIMs Have working WIM for 2022 full (finished with that), want to do 2022 Core Have a working VHD for 2019 (core only), wan't yet able to make a good WIM. But time to sleep a bit
Only Core --> AzureStackHCI Desktop Experience --> ServerTurbine Have a good dream! (Don't mind what I said if it offended you. I am just telling the truth. No offensive intention. No reason for me to harm you. NOT my personality.)