uup-converter v106 - Extract multiple/any AggregatedMetadata.cab on fly when parsing Apps CompDB - Fix console ForceV2 check (for text coloring)
In Post #5911 from Dec 19, 2021 Last edited: May 22, 2024 you provided an amazing "EnterpriseS build 19041.1" package. I was wondering if you see any value in updating the package to "EnterpriseS build 22000.1" - Compatible with updates - Can be installed directly without updates - makes a usable IoTEnterpriseS edition after updating beyond LCU 22000.xxxx
uup-converter v106u - Fixed issue with "Creating Cumulative Update MSU" enhancement thanks to @Clusterhead and @TS2008 for testing
EnterpriseS 19041.1 licenses were available in the LCU (as reverse delta) does 22000 LCU have EnterpriseS licenses?
A crucial ingredient is missing from the 22000 EnterpriseS recipe. This helps explain many things I was confused about with other recipes I've seen. Thank you! [16 July 24 edit - Attempt #1] In response to @Enthousiast, please allow me to make a (probably still wrong) attempt to correct my statement: Unlike the "pure" 19041.1 EnterpriseS, the only 22000 EnterpriseS that exist at this time are either total Frankenstein's or LCU specific versions that can't be further updated since they are reconstructed curiosities made using dodgy recipe ingredients. In any event, I more-or-less understand the point that @abbodi1406 was making.
uup-converter v106z - One more fix/enhancement for "Creating Cumulative Update MSU" process thanks to @Clusterhead and @TS2008 for testing PSFX MSU Maker v5 - Unified code with uup-converter (except wimlib part) - Better support to handle multiple AggregatedMetadata cab files while v5 can now create MSU file(s) per each AggregatedMetadata.cab, however, it's best not to mix files because DesktopDeployment files can't coexist for different builds, and SSU extraction might fail without proper dpx.dll Spoiler Example: Code: ============================================================ 367848fb-48ba-4a1e-aac4-fc901c84fa60.AggregatedMetadata.cab ============================================================ Extracting: SSU-26100.268-x64.cab failed. Provide ready DesktopDeployment.cab or dpx.dll and try again ============================================================ 77610792-e463-4270-8175-62e4c395d96b.AggregatedMetadata.cab ============================================================ Extracting: SSU-22000.6-x64.cab Creating: DesktopDeployment.cab Creating: DesktopDeployment_x86.cab Creating: onepackage.AggregatedMetadata.cab Creating: Windows10.0-KB5005027-x64.msu Finished Press any key to exit. after manually adding dpx.dll 26100 to repo: Code: ============================================================ 367848fb-48ba-4a1e-aac4-fc901c84fa60.AggregatedMetadata.cab ============================================================ Extracting: SSU-26100.268-x64.cab Creating: DesktopDeployment.cab Creating: DesktopDeployment_x86.cab Creating: onepackage.AggregatedMetadata.cab Creating: Windows11.0-KB5039417-x64.msu ============================================================ 77610792-e463-4270-8175-62e4c395d96b.AggregatedMetadata.cab ============================================================ KB5005027 msu file already exist Finished Press any key to exit.
I could not get PSFX_Repack_6 to work ever. Tried version 2/3/6 always gives error. All the files inside folder it can not find any of them. How to get it work? I need that cab file much. Inside 1150 update "Windows11.0-KB5040435-x64.msu" there is a wim file "Windows11.0-KB5040435-x64.wim". There is no cab or esd file. Can be problem. Could not convert that wim to cab or esd i need Windows11.0-KB5040435-x64.cab with or without SSU-26100.998-x64.cab. if somebody succeded to use this software can upload somewhere cab version of 1150 update
Can I use W10UI and keep updating the same iso file, for example LTSC 26100.1 would be updated to 26100.1150 and the next time this 1150.iso would be updated to .1xxx and so on. OR I'd always have to use the iso that msft releases as a base when using W10UI ?
You can (but only if the pending flag is not triggered) but best is to start with the clean iso every month, that's how most of us here do it for many years.
PSFX_Repack does not support MSU WIM files (builds greater than 25330) you also don't need all those files to repack psfx updates, you are confusing PSFX_Repack with PSFX_MSU why do you need repacked Windows11.0-KB5040435-x64.cab?
Because msu file gives error while integrating on all my builds. I do not know if the update is problematic or not. I will try to integrate from cab file. Do you have a plan to support builds greater than 26100? I have put what it needs. Maybe can be update to read me file with exact file names. Main problem is it does not find files. It can be not support but it should say that it can found the files but not support the build for now.
Afaik, even UUP LCU is now offered as full MSU, MSU includes the CAB. Can you show us the full updates integration progress, including the list if used updates?
At clean 26100.1 install.wim dism gives this error. Code: DISM.exe /Online /Add-Package /PackagePath:D:\Windows11.0-KB5040435-x64.msu /English Deployment Image Servicing and Management tool Version: 10.0.26100.1 Image Version: 10.0.26100.1 Processing 1 of 1 - An error occurred - D:\Windows11.0-KB5040435-x64.msu Error: 0x80070570 Error: 1392 DISM failed. No operation was performed. For more information, review the log file. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log Sometimes it says "Unattend.xml file gives error" ı have not heard there is an unattend.xml file inside a msu before. Code: DISM.exe /Image:D:\a /Add-Package /PackagePath:D:\Windows11.0-KB5040435-x64.msu Deployment Image Servicing and Management tool Version: 10.0.26100.1 Image Version: 10.0.26100.1 Processing 1 of 1 - D:\Windows11.0-KB5040435-x64.msu: An error occurred applying the Unattend.xml file from the .msu package. For more information, review the log file. Error: 0x80070570 Error: 1392 Dosya veya dizin bozuk ve okunamaz durumda. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log I have tried 26100.560 / 26100.830 install.wims too. Some of them could be modified wims maybe can result error but strange to have so much errors.
I doubt it will make any difference the error means corrupted file (on your OS probably) or faulty harddisk