Unable to integrate the latest LCU PSF and LCU CAB files on Windows 11 x64

Status
Not open for further replies.

Windows 10 User

Active Member
When I try to integrate the latest LCU CAB (KB5008353) file on Windows 11 x64, NTLite says the latest LCU PSF (KB5008353) file is missing (also, it doesn't even show up when I try to integrate it).

Can anybody tell me if one should download and install/integrate the latest SSU, LCU PSF and LCU CAB files to have a recent image, what's the difference between the LCU PSF and LCU CAB files and how are they related to SSU? Also, what's the difference between the LCU MSU file and the LCU PSF and LCU CAB ones and does the first (LCU MSU) also include the SSU? Why are Windows 11 updates called "Windows 10.0-KBX"?

EDIT: It looks like NTLite wants the Windows 10.0-KB5008353-x64_6554d11a PSF file when I can only find the Windows10.0-KB5008353-x64_bf2d40da PSF file.
 

Attachments

  • Captura de Ecrã (2).png
    Captura de Ecrã (2).png
    177 KB
  • Captura de Ecrã (3).png
    Captura de Ecrã (3).png
    119.5 KB
Last edited:

garlin

Moderator
Staff member
W11 releases identify as "W10" images, even though they're build 22000. For reasons never explained.
Using deployment tools with Windows 11 images

Therefore W11 updates are Windows 10.0-KB*

KB5009566 is Jan 2022's LCU
KB5008353 is Insider Preview update (not LCU)

LCU MSU packages are all-in-one, expanding to SSU CAB + CU CAB (expands to CAB + PSF). NTLite is happy.
Not having a MSU, requires downloading SSU + update CAB + update PSF.

Google your missing file.
 

Windows 10 User

Active Member
W11 releases identify as "W10" images, even though they're build 22000. For reasons never explained.
Using deployment tools with Windows 11 images

Therefore W11 updates are Windows 10.0-KB*

KB5009566 is Jan 2022's LCU
KB5008353 is Insider Preview update (not LCU)

LCU MSU packages are all-in-one, expanding to SSU CAB + CU CAB (expands to CAB + PSF). NTLite is happy.
Not having a MSU, requires downloading SSU + update CAB + update PSF.

Google your missing file.

Thanks, but like I said, I found CU CAB and CU PSF so they can't form CU CAB. So, CU CAB and CU PSF don't have SSU?

I did but didn't find it and it isn't the latest one, anyway. Shouldn't NTLite recognize Insider Preview updates?

Also, what are PSFX files?
 
Last edited:

garlin

Moderator
Staff member
CU CAB now includes the SSU, for redundancy. Unpack it using 7-Zip to see what's inside.

When NTLite handles updates, it doesn't care about labels. They're all updates to a target OS. But you should be careful in talking about different update types to avoid confusion.
  • LCU is the official monthly rollup update.
  • Preview CU are next month's update, available for early access. Most users avoid them because a different KB CU will replace the preview version in 4-5 weeks.
  • Insider Preview updates are early access of both new features and fixes. Some fixes will end in a different KB CU, or separate feature update. You can't refer to them as "CU" because that term is reserved for monthly updates.
NTLite doesn't care, they're all packages. It tries to unpack them and apply them.

Even with compression, WU downloads costs MS $millions in network charges. W10 introduced a new PSF format which applies differential changes against previous copies of files to save space. To work, you need the original and apply the "diff" to create a new file.

Back to your problem. Just rename both files to KB5008353-x64.cab & KB5008353-x64.psf
 
Last edited:

Windows 10 User

Active Member
CU CAB now includes the SSU, for redundancy. Unpack it using 7-Zip to see what's inside.

When NTLite handles updates, it doesn't care about labels. They're all updates to a target OS. But you should be careful in talking about different update types to avoid confusion.
  • LCU is the official monthly rollup update.
  • Preview CU are next month's update, available for early access. Most users avoid them because a different KB CU will replace the preview version in 4-5 weeks.
  • Insider Preview updates are early access of both new features and fixes. Some fixes will end in a different KB CU, or separate feature update. You can't refer to them as "CU" because that term is reserved for monthly updates.
NTLite doesn't care, they're all packages. It tries to unpack them and apply them.

Even with compression, WU downloads costs MS $millions in network charges. W10 introduced a new PSF format which applies differential changes against previous copies of files to save space. To work, you need the original and apply the "diff" to create a new file.

Back to your problem. Just rename both files to KB5008353-x64.cab & KB5008353-x64.psf

Thanks, but here there's a LCU MSU and a separate SSU CAB when you said the LCU MSU included the LCU CAB, the SSU CAB and the LCU PSF and I've seen a separate SSU CAB with a separate CU CAB when you said the latter already included the former and I've also seen a separate CU CAB and a CU PSF as well when you said the former already included the latter.

Also, what are these updates, OOB, DU Critical Update and General Package?

To 10.0-KB5008353-x64_6554d11a, you mean.

Sorry to bother you again but this is very confusing for me.
 
Last edited:

garlin

Moderator
Staff member
You're trying to overthink. Download the LCU (MSU) from Catalog, and you're done.
Download LCU 2022-01 Cumulative Update for Windows 11 for x64-based Systems (KB5009566)
unzip windows10.0-kb5009566-x64_6ed15753e97e34603a2978f412fb60c4eb77c1aa.msu

MSU expands to SSU + KB5009566 CAB + KB5009566 PSF:
01/05/2022 06:32 AM 4,602,729 DesktopDeployment.cab
01/05/2022 04:01 AM 3,688,338 DesktopDeployment_x86.cab
01/06/2022 12:12 AM 17,911 onepackage.AggregatedMetadata.cab
10/30/2021 01:20 PM 14,699,687 SSU-22000.345-x64.cab
01/05/2022 06:59 PM 53,425,642 Windows10.0-KB5009566-x64.cab
01/05/2022 06:57 PM 161,496,897 Windows10.0-KB5009566-x64.psf
01/06/2022 12:18 AM 758,228 WSUSSCAN.cab

There is no extra copy of SSU inside KB5009566 CAB, but we can check W10's handling.

Download 2022-01 Cumulative Update for Windows 10 Version 21H2 for x64-based Systems (KB5009543)
MSU expands to SSU + KB5009543 CAB
01/08/2022 04:27 AM 15,318,363 SSU-19041.1371-x64.cab
01/08/2022 04:40 AM 420 Windows10.0-KB5009543-x64-pkgProperties.txt
01/08/2022 04:33 AM 666,318,422 Windows10.0-KB5009543-x64.cab
01/08/2022 04:40 AM 728 Windows10.0-KB5009543-x64_uup.xml
01/08/2022 04:41 AM 972,262 WSUSSCAN.cab
...inside Windows10.0-KB5009543-x64.cab:
01/08/2022 04:27 AM 15,318,363 SSU-19041.1371-x64.cab
01/08/2022 04:28 AM 202 toc.xml
01/08/2022 04:28 AM 8,819 update.cat
01/08/2022 04:28 AM 421,548 update.mum
01/08/2022 04:27 AM 650,697,678 Windows10.0-KB5009543-x64.cab
...inside that Windows10.0-KB5009543-x64.cab:
1/07/2022 11:12 PM 93 cabinet.cablist.ini
1/07/2022 11:12 PM 98,808,009 Cab_1_for_KB5009543_PSFX.cab
1/07/2022 11:08 PM 563,004,122 Cab_2_for_KB5009543_PSFX.cab
1/07/2022 10:25 PM 8,819 update.cat
1/07/2022 10:23 PM 421,548 update.mum

Why does this happen? I'm not MSFT, but it's prolly a hack to update SSU & CU in correct order when SSU is out of date.
None of this matters. The MSU is the correct package for any LCU.

If you're digging around MDL, that level of discussion is very advanced and you should keep questions over there. That community is focused on hard-core hacking, and NTLite forum is middle of the road. Eventually some of their work makes it over here.

DU is Dynamic Update, which means you patch WinPE Setup to download any SSU or CU updates which are newer than your image's before starting install. It's entirely optional, and designed for places with strict security requirements (up-to-date patches). DU absolutely requires the latest SSU update since a downloaded update may be newer than your image's SSU level.

DU is not worth the time if you prefer to update your own image.

Did you rename KB5008353? I know both files work, they extract in PSFExtractor just fine (renamed).
 
Last edited:

Windows 10 User

Active Member
You're trying to overthink. Download the LCU (MSU) from Catalog, and you're done.
Download LCU 2022-01 Cumulative Update for Windows 11 for x64-based Systems (KB5009566)
unzip windows10.0-kb5009566-x64_6ed15753e97e34603a2978f412fb60c4eb77c1aa.msu

MSU expands to SSU + KB5009566 CAB + KB5009566 PSF:


There is no extra copy of SSU inside KB5009566 CAB, but we can check W10's handling.

Download 2022-01 Cumulative Update for Windows 10 Version 21H2 for x64-based Systems (KB5009543)
MSU expands to SSU + KB5009543 CAB

...inside Windows10.0-KB5009543-x64.cab:

...inside that Windows10.0-KB5009543-x64.cab:


Why does this happen? I'm not MSFT, but it's prolly a hack to update SSU & CU in correct order when SSU is out of date.
None of this matters. The MSU is the correct package for any LCU.

If you're digging around MDL, that level of discussion is very advanced and you should keep questions over there. That community is focused on hard-core hacking, and NTLite forum is middle of the road. Eventually some of their work makes it over here.

DU is Dynamic Update, which means you patch WinPE Setup to download any SSU or CU updates which are newer than your image's before starting install. It's entirely optional, and designed for places with strict security requirements (up-to-date patches). DU absolutely requires the latest SSU update since a downloaded update may be newer than your image's SSU level.

DU is not worth the time if you prefer to update your own image.

Did you rename KB5008353? I know both files work, they extract in PSFExtractor just fine (renamed).

No, I didn't rename it.
 
Last edited:

garlin

Moderator
Staff member
FOLLOW THE INSTRUCTIONS.

ren Windows10.0-KB5008353-x64_6554d11a.cab Windows10.0-KB5008353-x64.cab
ren Windows10.0-KB5008353-x64_bf2d40da.psf Windows10.0-KB5008353-x64.psf
copy both to Updates folder
NTLite pick KB5008353 CAB from folder
 

Windows 10 User

Active Member
FOLLOW THE INSTRUCTIONS.

ren Windows10.0-KB5008353-x64_6554d11a.cab Windows10.0-KB5008353-x64.cab
ren Windows10.0-KB5008353-x64_bf2d40da.psf Windows10.0-KB5008353-x64.psf
copy both to Updates folder
NTLite pick KB5008353 CAB from folder

After renaming it, the PSF still doesn't show up, although the CAB is listed on NTLite now. Will I have any problems?

I don't get it why one has to change the updates' names in order for NTLite to recognize them and why it recognized it after changing the names to "Windows10.0-KB5008353-x64" when it stated the name should be "10.0-KB5008353-x64_6554d11a".
 
Last edited:

abbodi86

Active Member
Because the cab and psf files must have the same name

due unpleasant changes in UUP dump site, now all downloaded files have their sha1 hash first 8 characters appended to file name
thus, you need to rename them after downloading
 

Windows 10 User

Active Member
Because the cab and psf files must have the same name

due unpleasant changes in UUP dump site, now all downloaded files have their sha1 hash first 8 characters appended to file name
thus, you need to rename them after downloading

I used PSFX_Repack to combine the CAB with the PSF to form a new CAB ending in psfx. I don't even need to rename them after downloading. After that I just have to integrate the new CAB with NTLite.

nuhi's working on a regex fix to handle this renaming problem.

Does that mean one won't have to use PSFX_Repack to combine the CAB with the PSF?
 
Last edited:

garlin

Moderator
Staff member
Repacking two files which work fine in NTLite into a new CAB (which NTLite needs to unpack), just because you don't want to rename them?
How often are you dealing with CAB/PSF pairs? Rename the files until it's fixed.
 

Windows 10 User

Active Member
Repacking two files which work fine in NTLite into a new CAB (which NTLite needs to unpack), just because you don't want to rename them?
How often are you dealing with CAB/PSF pairs? Rename the files until it's fixed.

I did rename them but like I said the PSF still wasn't listed unlike the CAB.

Very often since some updates come in CAB/PSF formats and they're often more up-to-date then Microsoft Update Catalog MSU format ones.
 

garlin

Moderator
Staff member
NTLite lists updates, not individual files. When a CAB or CAB/PSF is accepted, you're done.

They're not more "up-to-date", you're downloading Preview updates which is not the same release branch as LCU. Those are the exact files abbodi is talking about. Preview updates as released never get promoted into normal distribution.
 

Windows 10 User

Active Member
NTLite lists updates, not individual files. When a CAB or CAB/PSF is accepted, you're done.

They're not more "up-to-date", you're downloading Preview updates which is not the same release branch as LCU. Those are the exact files abbodi is talking about. Preview updates as released never get promoted into normal distribution.

So the PSF is actually used by NTLite since the CAB is now listed?
 
Last edited:

nuhi

NTLite developer
Staff member
CAB+PSF instructions:

Download both CAB and PSF from the UUP dump site.
When saving the filename, copy the name of the link and use that with right-click save, do not just save it as a non-descriptive hash name.

After downloading both files (CAB and PSF).
Copy CAB filename (F2 for rename, select all without extension) and rename the accompanying PSF file to be the same (with its own PSF extension intact).
Add that CAB to the Updates page, done, it will state in its Status/Type that it's CAB + PSF combo.

Or even simpler, copy the filename from the error box when trying to add the CAB file and rename the PSF to it.

Next version will allow for a different suffix, meaning if you cannot follow the above for some reason, and have something like:
Windows10.0-KB5010795-arm64_b75ebe1a.cab
Windows10.0-KB5010795-arm64_e014b3e5.psf
It will autocombine those without renaming. It's not a "fix", it's a convenience upgrade.
 

Windows 10 User

Active Member
CAB+PSF instructions:

Download both CAB and PSF from the UUP dump site.
When saving the filename, copy the name of the link and use that with right-click save, do not just save it as a non-descriptive hash name.

After downloading both files (CAB and PSF).
Copy CAB filename (F2 for rename, select all without extension) and rename the accompanying PSF file to be the same (with its own PSF extension intact).
Add that CAB to the Updates page, done, it will state in its Status/Type that it's CAB + PSF combo.

Or even simpler, copy the filename from the error box when trying to add the CAB file and rename the PSF to it.

Next version will allow for a different suffix, meaning if you cannot follow the above for some reason, and have something like:
Windows10.0-KB5010795-arm64_b75ebe1a.cab
Windows10.0-KB5010795-arm64_e014b3e5.psf
It will autocombine those without renaming. It's not a "fix", it's a convenience upgrade.

Thanks, I no longer have this issue on the latest version so I don't have to use PSFX_Repack or rename the CAB/PSF.

W11 releases identify as "W10" images, even though they're build 22000. For reasons never explained.
Using deployment tools with Windows 11 images

Therefore W11 updates are Windows 10.0-KB*

KB5009566 is Jan 2022's LCU
KB5008353 is Insider Preview update (not LCU)

LCU MSU packages are all-in-one, expanding to SSU CAB + CU CAB (expands to CAB + PSF). NTLite is happy.
Not having a MSU, requires downloading SSU + update CAB + update PSF.

Google your missing file.

Weird, LCU MSU already includes SSU (and CAB + PSF) but here the SSU is listed separately.

Also, are all Insider Preview updates called "Preview" or just some Microsoft Update Catalog/Windows Update ones?
 
Status
Not open for further replies.
Top