Windows 7 SP1 Cannot Integrate Update KB4537820 - Monthly Rollup

I am using the NTLite (v1.9.0.7304) update downloader feature, and have tried both a fresh, genuine copy (en_windows_7_ultimate_with_sp1_x64_dvd_u_677332.iso) and a copy of that ISO slipstreamed with updates to April of 2019 and I experience the same error.



Both times it was the same update that caused the error: KB4537820 - Monthly Rollup. It hits 99% before getting the error, followed by an "Aborted - Package integration [2096]" error.



I have attached the two preset files that were from my attempts. I am not trying to make any modifications other than slipstream updates.
 

Attachments

Last edited:

abbodi86

Member
Officially, ESU updates cannot be integrated offline

unless you use Audit+Sysprep, or unofficial bypass workaround that suppress the ESU check
 
Officially, ESU updates cannot be integrated offline

unless you use Audit+Sysprep, or unofficial bypass workaround that suppress the ESU check
thanks for the reply. I came to a similar conclusion after reading more information about that particular update.

nuhi Would it be feasible to add a feature that can identify when an update is not compatible with the given version? The Microsoft website specified which versions of Windows 7 are compatible with ESU updates. This would prevent accidental and time consuming user error when slipstreaming new updates.
 

nuhi

NTLite developer
Staff member
trentfromrid, yes, thinking about what to do, split the lists, keep only the newest or simply stop supporting it.
Btw when I tested it, it integrated just fine; must be doing something wrong and need to retest - tried from Win10 and Win7 (updated).
 
trentfromrid, yes, thinking about what to do, split the lists, keep only the newest or simply stop supporting it.
Btw when I tested it, it integrated just fine; must be doing something wrong and need to retest - tried from Win10 and Win7 (updated).
nuhi have you tried Windows 7 Ultimate? The MS website says that ESU updates are only supported on Professional and Enterprise editions, so I would expect integration to fail on other editions.
 

garlin

Active Member
Here's my conjecture about ESU offline integration, which I can't test (for reasons explained in a minute). A licensed (or bypassed) base host will pass the new servicing stack checks to allow integration to finish. This image may install correctly, but the new box cannot be further updated unless it gets licensed or bypassed.

The problem of testing this theory is you need a ESU license, and FAQ clearly states re-imaging consumes one of your activation instances. If your volume reseller is kind enough to reset this activation (justification - reimage), then no problem. But if your reseller isn't kind, then to test this theory you'll be eating up activations. Ugh. $$ in order to follow this testing path.

Of course, you can try the bypass. This is free, but could be blocked some point in the future (which you'd have to monitor progress). If you're being kind to willing users, this update list should have a giant "unsupported" sticker.
 

garlin

Active Member
trentfromrid, correct that MSFT's website omits any mention but it's been confirmed by many news sites.

I tested the bypass (maybe not correctly), and tried to live install the same IE11 cumulative as a test case. It installed, but on reboot it complained and reverted my change, but still kept it listed. Bypass could work, but it's kinda untested in working out the kinks.

Just need a volunteer with enough enthusiasm to figure it out :p
 

ege914

Active Member
just a reminder, are you integrating or enabling netfx3.5 too?
if yes, let me tell u
u can't enable netfx 3.5 and integrate other updates at the same time. (at least it is for me)
to overcome that, i always enable netfx3.5 first and integrate other updates and do changes on iso later. (so 2 steps)

this way i have no integration problem at updates. since i use abbodi's scripts to multiarch or multilang those scripts already enable netfx3.5 for me so i have no problem so far.
 

garlin

Active Member
What kind of netfx3.5 issues? I have other integration nightmares, mostly with RDP.

My problem is the build blows up on first WU check and wants to re-install 3552 & 3229, and the last feature rollup. I might have the problem solved, and testing a few fixes before posting a write-up.
 
Last edited:

nuhi

NTLite developer
Staff member
Those with this issue, are you using Windows 7 host that has servicing stack updated to the ESU requirement, but actually don't have ESU?
Have you tried to integrate the update manually with DISM?
Have you tried to integrate only the servicing stack and CU to the image with NTLite, nothing else done?

Thanks.
 

ege914

Active Member
i'm on windows 10 pro latest build
i did not try to update manually with dism because i don't even understand which update is causing problem since its different with everybody i don't think its about esu at all
only ss and cu is integrated without problem
 

Attachments

nuhi

NTLite developer
Staff member
Will be trying trentfromrid's preset tomorrow, I see it's also from Win10.

trentfromrid, why adding all those obsolete IE11 updates? I believe those are covered by the latest rollup update.
 

garlin

Active Member
I agree on IE11, 5319 is the only one beside the last rollup that is useful to satisfy weird WU issues.
 

nuhi

NTLite developer
Staff member
Looking at ntlite_dism.log
First it was about WU service not turned on.
Turned it on and retried, then

2020-03-13 11:23:01, Info CSI 00000001 ESU: Offline is not supported HRESULT_FROM_WIN32(1625).
Completion status: HRESULT_FROM_WIN32(ERROR_ADVANCED_INSTALLER_FAILED)

Meaning, there is nothing we can (legally) do, I'll see about adding that message on the update list.

abbodi86, is it true that Win10 cannot integrate latest Win7 updates now?
Is it only supported on Win7 host with ESU functional or they support Win10 somehow as a host as well?
I thought it's allowed to integrate once, then WU would require ESU, and doing anything like that from updated Win7 would require ESU.
But that integration under Win10 is not allowed for initial images is unexpected.
 
Top