Why integrating updates in one step is different from integration in two?

ddlnegocios

New Member
Hello, just bought a License and this is my first post here.

I'm creating a fully updated Windows 10 Enterprise LTSB 2016 X64 pt-BR edition. Right now I have all updates I need that are available, so Windows Update doesn't offer new updates. Just for knowing, this is list (10 updates):

1 - .NET Framework 3.5
2 - KB4346087 Atualizações de microcódigo da Intel
3 - KB4486129 .NET Framework 4.8
4 - KB4486148 Pacote de Idioma pt-BR .NET Framework 4.8
5 - KB4577586 Remoção do Adobe Flash Player
6 - KB4589210 Atualizações de microcódigo intel
7 - KB5012170 Atualização de segurança para DBX de Inicialização Segura
8 - KB5017396 Service Stack Update
9 - KB5020873 Atualização Framework 4.8
10 - KB5021235 Atualização Cumulativa Mês 12/2022

Well, in the process of integrating updates, I observed two different situations:

1) If I ask Nlite to integrate all updates ONCE (in one step) and then make a fresh install Windows, only Cumulative Update (KB5021235) keeps being offered by Windows Update.

But check this out...

2) If I separate integration in two parts, first adding and processing first the 9 updates considering the list above; second loading install.wim again and adding the Cumulative Update and making fresh install of Windows, Windows Update says that system is fully updated (this is what I want).

So, are there any explanation for this?
 

nuhi

NTLite developer
Staff member
Hello,

there is a need to re-apply cumulative update when integrating, due to some updates requiring that (shares versions with the cumulative update, but usually being older than).
Will check your list and correct the all-in-one step, so it triggers that special step in this case as well.

Thanks, nice find.
 

ddlnegocios

New Member
Hello,

there is a need to re-apply cumulative update when integrating, due to some updates requiring that (shares versions with the cumulative update, but usually being older than).
Will check your list and correct the all-in-one step, so it triggers that special step in this case as well.

Thanks, nice find.
You're right! I found something that might help you. I was browsing on the Forum of MyDigitalLife and I there's a tool named Windows NT 10.0 Updates Installer (it adds updates to the SO, only). In description says one of its capabilities:

# Enable .NET Framework 3.5 if available source detected, and reinstall Cumulative updates afterwards.

Well, it looks like to be something due Framework 3.5. That's all I could figure out. I hope that somehow can help you.
 

ddlnegocios

New Member
Here's what I did:

Deleted .NET Framework 3.5 from the list and made integration of the others updates (including Cumulative Update). Then I did a fresh install of windows and checked for new ones. No updates were found.

So, it really seems to be something with .NF 3.5 when it's the list too.
 

nuhi

NTLite developer
Staff member
Thanks, will test tomorrow.
It should have done that already, I'm surprised it didn't, will fix and send you a test version.

(dealing over PMs)
 

ddlnegocios

New Member
2) If I separate integration in two parts, first adding and processing first the 9 updates considering the list above; second loading install.wim again and adding the Cumulative Update and making fresh install of Windows, Windows Update says that system is fully updated (this is what I want).
Well, I followed this option. It worked perfectly. But in the future it will be nice if the possibility of integration in one step works.
 

ddlnegocios

New Member
1) If I ask Nlite to integrate all updates ONCE (in one step) and then make a fresh install Windows, only Cumulative Update (KB5021235) keeps being offered by Windows Update.
Hi, back again... I'm testing it right now on new stable version of NTLite (9039)...

Launched install.wim file and I'm going to try Integrate all updates I said above (just changing CU to the latest version, JAN 2023) in One Step (all updates in one folder).

Let's see if it will works.

1674134877689.png
 
Last edited:
Top