PSFExtractor worked fine for extract files, however CABARC didn't work with long filenames. If you want to repack CAB then you should put the files in a folder with shorter path, eg. D:\test. Currently all tools except Dism++ rely on PSFExtractor to extract CAB+PSF. It wasn't designed to handle baseless PSFs, only express. Baseless CAB/PSFs aren't necessary for installing updates.
Or manually repack CAB+PSF: Rename CAB and PSF file with the same name, eg. Windows10.0-KB5006746-x64.cab and Windows10.0-KB5006746-x64.psf. Put them in a folder with shorter path name, eg. D:\test. Otherwise CABARC will fail. Run PSFExtractor.exe <filename>.cab (or simply drag the CAB file onto PSFExtractor.exe). PSFExtractor.exe is included with UUP converter, W10UI, etc. Make sure PSFExtractor.exe has a version number >=1.0.7.0. Now you have a folder with the same name. (optional) Delete express.psf.cix.xml and historycix.cab. Run cmd or PowerShell from that folder (or cd to the folder) and execute Code: PATH\TO\cabarc.exe -r -p -m LZX:21 n ..\<new filename>.cab * CABARC is Microsoft Cabinet Tool and is included in Cabinet SDK and IEAK, etc. Both the folder and the new CAB will work with dism. Note that the method will only work with less than 65535 files as it's the limit of CAB format. Microsoft themself pack multiple CABs inside another CAB when the number of files exceeds limit. However we can't do that.
Yes both cab/psf must have the same file name, or keep the original hashed UUP name (without adding _282)
Okay, I remember seeing something about not using 22000.1 for something specific in one of the MDL threads and forgot what that applied to.
A question: Win 11 Updates in .msu format contain both .cab and .psf files in them and we can integrate them using dism command, can we create a cab file like those .msi files and integrate Win 11 updates? I mean instead of using PSFX_repack, we just create a cab and put .psf and .cab into it(plus some other config maybe)
Afaik, that is what repack_psfx is made for, if it was that simple it wouldn't be needed. Why not just use W10UI? ps, it's .MSU
Typo, thanks. I just wanted to suggest a faster solution for it, W10UI is perfect, but what if it can be faster using this way? It was created before we saw a .msu, maybe now we know more? It looks like onepackage.AggregatedMetadata.cab have some good information inside of it to make this achieveable, if you like and have time, extract cab, psf, ssu cab and onepackage.AggregatedMetadata.cab from msu and repack them in another cab, and see if you can install update with dism