Windows 10 Hotfix Repository

By DISM or by W10UI_9.5?

DISM failed here: https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-597#post-1646690

 

With NTLite and no error

 

I am talking about manual dism usage, the msu is not handled correctly:

Code:

Microsoft Windows [Version 10.0.19042.844]
(c) 2020 Microsoft Corporation. All rights reserved.

C:\Windows\system32>Dism /mount-wim /wimfile:d:\W10UI\19041_Work_Test\sources\install.wim /index:1 /mountdir:c:\mount

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Mounting image
[==========================100.0%==========================]
The operation completed successfully.

C:\Windows\system32>
C:\Windows\system32>DISM /Image:"c:\Mount" /Add-Package /PackagePath:d:\W10UI\19041.1_Updates_x64_Test\windows10.0-kb4601382-x64_87d4ba1dac3ea12aee681b660c505607ae9b01f3.msu

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19041.1

Processing 1 of 1 - d:\W10UI\19041.1_Updates_x64_Test\windows10.0-kb4601382-x64_87d4ba1dac3ea12aee681b660c505607ae9b01f3.msu: An error occurred applying the Unattend.xml file from the .msu package.
For more information, review the log file.
 Error: 0x800f0823

Error: 0x800f0823

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

C:\Windows\system32>

Tools will probably first extract the combined cab and split them in two usable cabs (or apply it by using the update.mum), like W10UI_9.5 does.

 

Thanks for it ... maybe i mixing it .

 

And so with the latest CUs, no need to integrate SSU updates anymore

 

MSFT being the culprit for naming the combined ssu "ssu-19041.841-x64.cab" looks like "KB4598481" which actually is the jan. 21. 2021 released ssu version.

 

You cannot

either perform dism cleanup, then integrate kb4562830

or integrate kb4562830 and install the image in Audit mode + run dism cleanup + sysprep + capture new install.wim

UUP do not have combined CU (not yet anyway)

 

What if you added the January SSU first (KB4598481) before adding combo KB4601382.

 

Then it probably would work, considering the old 19041.504 SSU or higher is required for the LCU to be able to integrate/install.

Will test it asap

 

Since CR-edge on EP-20H2 (KB4562830) will cause pending state, it is not possible to perform cleanup unless doing it in audit mode and then capturing it as a new image.

The easiest way is to add all updates that don't cause a pending state first (eg SSU, Flash/Flash Eraser, NF 48, LCU) > Perform cleanup > Add all updates which will cause a pending state (eg NF 3.5, EP-20H2) > Next, If you add/enable NF 3.5 feature, you need to re-add NF 4.8 and LCU. So when you check for updates, WU will no longer offer to download and reinstall NF 4.8 and LCU.

 

That would be the same as "use W10UI_9.5"

 

I installed the 841 SSU and 844 LCU separatedly and was able to roll-back from 844 to 804. The 841 SSU remained installed. Since SSUs are generally uninstallable, will we be able to roll-back LCUs if they are enmeshed with SSUs?

 

LCU KB4601382 and SSU KB5000911 are still normal independent updates
they can be installed together or separately, or uninstalled separately

they just packed them together into unified cab, mainly for WSUS deployment, because WU already use UUP

SSUs are permanent
but because they changed CBS name to Package_for_ServicingStack,
when you install the next SSU 19041.860 (KB????), SSU 19041.841 (KB5000911) can be uninstalled

 

Does this apply to 1809 / LTSC as well (or just 2004 / 20H1+)?

 

You need to login to view this posts content.

 

It seems unnecessary for offline use, in the end the January SSU (KB4598481) was no longer needed and became redundant after the combo update package was installed. It's more ideal to expand the combo msu to get the combo cab and then expand the combo cab to get the actual SSU and LCU packages before adding them into the install.wim as W10UI does.

Yes for sure. Just use the W10UI for instant or use that package installation order, to add manually with dism or maybe in other tools like msmg toolkit, ntlite etc.

 

So, do we still need the latest SSU when integrating the LCU? I thought the latter already included the former.

 

If you manually download a LCU and run it, no, that is a 2 in 1 process now.

Things are a bit more complicated if you are integrating. Integrating you can use something like 7zip to extract the CU and SSU cab files and integrate like usual.

 

I'm talking about integrating. Do we need both or only the LCU now?

 

I think some have mentioned that attempting to DISM the new 2 in 1 CU fails. I used 7Zip to pull the CU and SSU cab files out of the msu and I could integrate them separately without issue.