About PSFX LCU update to an updated build Fact: Original updated build --> install LCU --> Success Original updated build --> Extract a package --> Resetbase --> install the extracted package --> Resetbase --> install LCU --> Failure Q: What is the difference between them?
Dear friend, I'm sorry that you think that way, I'm no one's boss, I'm a simple apprentice who doesn't have a lot of free time, because I either work or I can't keep up and I have to obey the rules of my work in order to earn my living and of my family, I'm not able to stay here all the time, now for example I should be sleeping, because here it's 4 hours in the morning and I have to be at work in 4 hours. But if you think I don't make an effort, or that you can't help me, that's fine. I'm not going to lose my job, I'm supporting mine, to be there at all times, neither because of you nor because of anyone here. Have a nice weekend and have fun while I work. Best Regards
22000.1 Microsoft-Windows-Security-SPP-Component-SKU-Professional-License-Package~31bf3856ad364e35~amd64~~10.0.22000.1 22000.1 + 22000.100 LCU Microsoft-Windows-Security-SPP-Component-SKU-Professional-License-Package~31bf3856ad364e35~amd64~~10.0.22000.1 Microsoft-Windows-Security-SPP-Component-SKU-Professional-License-Package~31bf3856ad364e35~amd64~~10.0.22000.100 22000.1 + 22000.100 LCU + Resetbase Microsoft-Windows-Security-SPP-Component-SKU-Professional-License-Package~31bf3856ad364e35~amd64~~10.0.22000.100
e.g. amd64_microsoft-windows-s..aleducation-license_31bf3856ad364e35_10.0.22000.100_none_3342296d75888864 original PSFX Code: f r Baseless PSF (original PSFX installed) Code: f r ProfessionalEducation-OEM-DM-1-pl-rtm.xrm-ms ProfessionalEducation-OEM-DM-1-ul-oob-rtm.xrm-ms ProfessionalEducation-OEM-DM-1-ul-phn-rtm.xrm-ms ProfessionalEducation-OEM-DM-1-ul-store-rtm.xrm-ms ProfessionalEducation-OEM-NONSLP-1-pl-rtm.xrm-ms ProfessionalEducation-OEM-NONSLP-1-ul-oob-rtm.xrm-ms ProfessionalEducation-OEM-NONSLP-1-ul-phn-rtm.xrm-ms ProfessionalEducation-OEM-NONSLP-1-ul-store-rtm.xrm-ms ProfessionalEducation-ppdlic.xrm-ms ProfessionalEducation-Retail-1-pl-rtm.xrm-ms ProfessionalEducation-Retail-1-ul-oob-rtm.xrm-ms ProfessionalEducation-Retail-1-ul-phn-rtm.xrm-ms ProfessionalEducation-Retail-1-ul-store-rtm.xrm-ms ProfessionalEducation-Volume-GVLK-1-ul-oob-rtm.xrm-ms ProfessionalEducation-Volume-GVLK-1-ul-rtm.xrm-ms ProfessionalEducation-Volume-MAK-1-pl-rtm.xrm-ms ProfessionalEducation-Volume-MAK-1-ul-oob-rtm.xrm-ms ProfessionalEducation-Volume-MAK-1-ul-phn-rtm.xrm-ms ProfessionalEducation-Volume-MAK-1-ul-store-rtm.xrm-ms These xrm-ms files are made of some 22000.1+ some 22000.100. i.e. Some 22000.1 ones updated by 22000.100 (in f folder) have all been renewed without backup. Therefore, any reconstruction with such updated image is not possible to be accepted by upcoming LCU.
Q: What to do if 19044 21H2 official image is being resetbase? (we are talking about reconstruction of course) Two ways I can think of: 1. Patch the updated image reconstruction (not easy) 2. Use baseless cab+psf to update OFFLINE, in two ways: A. with whole repacked baseless LCU. B. with original LCU + baseless packages of b1. Branding b2. Editions b3. SPP b4. other SKU-specific
Wait 'till next Tuesday. My 19044 EnterpriseS has been up to date with plan B - original LCU + baseless packages. Only few baseless packages added to original LCU, and it can be used as classic LCU.
I used the 19044.1149 EnterpriseS made by the A plan you mentioned. After installation, I successfully updated it to 19044.1151 with windows10.0-kb5004296-x64.cab. Spoiler
Use 17763EnterpriseS to make fake 19044.1EnterpriseS, use PSFExtractor.exe to parse 19044.1149 baseless packages, install, and then remove 19044.1EnterpriseS. The serverturbine was made in the same way, but I couldn't figure out how to do it before.
1. Make 19041.1 with 17763.1 EditionSpecific package (Am I correct?) 2. Add 19041.1149 baseless LCU 3. Remove 19041.1 Got it. Thanks.
The extracted Microsoft-Windows-EditionSpecific-EnterpriseS-Package upgrade package will lose the f\r folder after installation, causing subsequent update failures, but you can copy the f\r folder to WinSxS, so that the upgrade will not be affected.