Error 0x80092004 - [8196] installing KB4486153 into Windows Server 2019 1809 LTSC image


New Member
Been running into this trying to update/create a new image with current updates. Always starting from a fresh iso extract, download all updates and then try and integrate them. I keep running into error:

KB4486153 - Error 0x80092004 - [8196]

Doing a search here I see an old post but that's from 2020. Doing general google searches I see that this error apparently is common. Looking at my other non-ntlite server systems running I DO NOT see .net 4.8 as an update option (they are all running 4.7).

So a couple questions.
1) Should NTlite actually even be pulling this update for server 2019/1809LTSC?
2) if it should, how to fix the issue?

Just to be clear, I'm using the November 2022 windows server 2019 image as a base:

ea247e5cf4df3e5829bfaaf45d899933a2a67b1c700a02ee8141287a8520261c *en-us_windows_server_2019_x64_dvd_f9475476.iso

Below are the update packages as selected/pulled by NTlite 2023.3.9171
<Packages> <File>E:\NTLite\Cache\Updates\10.0.1809.x64\windows10.0-kb4504369-x64_38b8c4dff79633757ee50837a735d3df0e75fa65.msu</File> <File>E:\NTLite\Cache\Updates\10.0.1809.x64\windows10.0-kb5005112-x64_81d09dc6978520e1a6d44b3b15567667f83eba2c.msu</File> <File>E:\NTLite\Cache\Updates\10.0.1809.x64\windows10.0-kb4486154-x64_638d2ba625fff21772a2cb7fc759f645044c2ad9.msu</File> <File>E:\NTLite\Cache\Updates\10.0.1809.x64\windows10.0-kb4486155-x64_78eea67f76d827934139d7620291d5b9897d1b8d.msu</File> <File>E:\NTLite\Cache\Updates\10.0.1809.x64\windows10.0-kb4486156-x64_7027d060c4c961234f29a7d37030ff1827627d2d.msu</File> <File>E:\NTLite\Cache\Updates\10.0.1809.x64\windows10.0-kb4486157-x64_38a8e353f369d6b92128621501c01ee7c32b498a.msu</File> <File>E:\NTLite\Cache\Updates\10.0.1809.x64\windows10.0-kb4486158-x64_29f52ea3b7488069849cc3b34051a48dafdbf65d.msu</File> <File>E:\NTLite\Cache\Updates\10.0.1809.x64\windows10.0-kb4486159-x64_f04cdb2271ae99f5181cdfb77fbec489fb84ea4d.msu</File> <File>E:\NTLite\Cache\Updates\10.0.1809.x64\windows10.0-kb4486160-x64_c4da350c5c3ce40081d170b2e6797de3dce99d66.msu</File> <File>E:\NTLite\Cache\Updates\10.0.1809.x64\windows10.0-kb4486161-x64_6b1f402d5a3be0e6c3043a08cf7876f1ea5b5e3f.msu</File> <File>E:\NTLite\Cache\Updates\10.0.1809.x64\windows10.0-kb4486162-x64_f5f9b677e31256569819fd5c5a3a2126d25658e7.msu</File> <File>E:\NTLite\Cache\Updates\10.0.1809.x64\windows10.0-kb4486163-x64_4fa5a4d1d7f8651d4f626365fc354177ef9b53ce.msu</File> <File>E:\NTLite\Cache\Updates\10.0.1809.x64\windows10.0-kb4486164-x64_9a6b8150556e95928bfb60d37d349e8b8a973ced.msu</File> <File>E:\NTLite\Cache\Updates\10.0.1809.x64\windows10.0-kb4486165-x64_074ec9ac12249bdc4efca8371fef81f4cc507479.msu</File> <File>E:\NTLite\Cache\Updates\10.0.1809.x64\windows10.0-kb4486166-x64_bebb22d32a140814421a0867a0ea53ad8e1e5105.msu</File> <File>E:\NTLite\Cache\Updates\10.0.1809.x64\windows10.0-kb4486167-x64_0087edf77791f5c5798d14f1257ec5c25e7c927a.msu</File> <File>E:\NTLite\Cache\Updates\10.0.1809.x64\windows10.0-kb4486168-x64_e2ab8396f03736d8e5947175b12827b9128a0b2e.msu</File> <File>E:\NTLite\Cache\Updates\10.0.1809.x64\windows10.0-kb4486169-x64_be0ec56038f8856133d0457ce68a00c29c7a216a.msu</File> <File>E:\NTLite\Cache\Updates\10.0.1809.x64\windows10.0-kb4486170-x64_dffe35849ed27d8821449a41ac6a3641c41943e1.msu</File> <File>E:\NTLite\Cache\Updates\10.0.1809.x64\windows10.0-kb4486171-x64_d8b778df07a1ac1d6c3442150e881668a41a553c.msu</File> <File>E:\NTLite\Cache\Updates\10.0.1809.x64\windows10.0-kb4486172-x64_ee854aac90c5eb65968ccecaa3da66846b12e79c.msu</File> <File>E:\NTLite\Cache\Updates\10.0.1809.x64\windows10.0-kb4486173-x64_0051801d5a4bc04f49a2ea93b88899fd16580276.msu</File> <File>E:\NTLite\Cache\Updates\10.0.1809.x64\windows10.0-kb4486174-x64_1d125f32e8ebbcc1a25bf5f52f0d6e99d4608f1b.msu</File> <File>E:\NTLite\Cache\Updates\10.0.1809.x64\windows10.0-kb4486175-x64_64e33a924a4c459fc8307285faebf59e899cf0cd.msu</File> <File>E:\NTLite\Cache\Updates\10.0.1809.x64\windows10.0-kb4486176-x64_4ee5505d1c7b4eca118ab7dbdd037a55a42079d2.msu</File> <File>E:\NTLite\Cache\Updates\10.0.1809.x64\windows10.0-kb4494174-x64_10354a50b5c05f9bf3c4ca68d98e34daa47ec059.msu</File> <File>E:\NTLite\Cache\Updates\10.0.1809.x64\windows10.0-kb4503308-x64_1cf7ea2c2d4263e710babb4a8d56416388e1c78e.msu</File> <File>E:\NTLite\Cache\Updates\10.0.1809.x64\windows10.0-kb4584642-x64_d015746abf6392ff85470d444d8b5982c4b8a1a6.msu</File> <File>E:\NTLite\Cache\Updates\10.0.1809.x64\windows10.0-kb4589208-v2-x64_fa90a4bdc1da0f5758cdfa53c58187d9fc894fa0.msu</File> <File>E:\NTLite\Cache\Updates\10.0.1809.x64\</File> <File>E:\NTLite\Cache\Updates\10.0.1809.x64\windows10.0-kb5019181-x64_01173052877dc5762f73069a958c108afd1125be.msu</File> <File>E:\NTLite\Cache\Updates\10.0.1809.x64\windows10.0-kb5023702-x64_25c0d04726b1f92c46e76d371ca58875051506c5.msu</File> <File>E:\NTLite\Cache\Updates\10.0.1809.x64\</File> <File>E:\NTLite\Cache\Updates\10.0.1809.x64\windows10.0-kb4486153-x64_43ee33b302bfdba470542a128a9ee0b58faa5412.msu</File> <File>E:\NTLite\Cache\Updates\10.0.1809.x64\windows10.0-kb4502559-x64_bebab74d4ce25e6a356ed02e0b42f1dbf842ae70.msu</File> <File>E:\NTLite\Cache\Updates\10.0.1809.x64\windows10.0-kb4502564-x64_bdaf127522b14f41d2f66840c62b03d80a831e1e.msu</File> <File>E:\NTLite\Cache\Updates\10.0.1809.x64\windows10.0-kb5012170-x64_3d468c9eaeeabd42eba636d5429643c386b0beff.msu</File> <File>E:\NTLite\Cache\Updates\10.0.1809.x64\windows10.0-kb5022504-x64-ndp48_1febc9659953d8ffa0bd67ee7de672871fab3654.msu</File> </Packages>
Last edited:
there are 4 versions, which one ? Server Standard ? Server Standard (Desktop Experience) ? Server DataCenter ? Server DataCenter (Desktop Experience)?
All versions have the error.
Also tried against an older iso:

7b463563206dce275f2d3ff77ac36c430052fae161cd4f8b31f3dc7af1c3f418 *en_windows_server_2019_x64_dvd_3c2cf1202.iso

which also same errors on the same KB. Tried installing the KB manually and it also fails.
W10 1809 & Server 2019 released with .NET 4.7.2 native support. To add .NET 4.8, install KB4486153.

KB4486154 thru KB4486174 are optional .NET language packs. Don't bother installing them unless you're a developer, they don't provide any extra features to the end-user.

If we look on your updates list, there are superseded (replaced) KB's which can be removed.
  KB4504369 SSU Jun 2019 (superseded)
* KB5005112 SSU Aug 2021
* KB5005545 Setup Dynamic Update Aug 2021 (optional)
* KB5023702 Mar 2023 LCU
* KB4584642 Microsoft Edge
  KB4486153 NET 4.8 Jan 2020 (superseded)
  KB4502559 NET 4.7 Jun 2019
  KB4502564 NET 4.8 Jun 2019 (superseded)
* KB5022504 NET 4.8 Feb 2023
  KB4486153 NET 4.8 Feature
  KB5003171 May 2021 LCU (superseded)

  KB4494174 Intel Microcode
  KB4503308 Adobe Flash
* KB4589208 Intel Microcode
* KB5019181 Intel MMIO
* KB5012170 Secure Boot DBX

* marks what NTLite is currently suggesting for Server 2019 (Desktop Experience).

My recommendation:
- KB5005112 SSU Aug 2021
- KB5023702 Mar 2023 LCU
- KB4584642 Microsoft Edge
- KB4486153 NET 4.8 Feature
- KB4502559 NET 4.7 Jun 2019
- KB5022504 NET 4.8 Feb 2023
[whatever Intel CPU vulnerabilities and Adobe Flash removal you see fit]

Remove the other KB's, if you're in the habit of pulling from NTLite's Updates folder and not from using the Downloads Updater list.
Wouldn't say 'habit' of pulling/dragging the update folder to the image as I don't use ntlite often (every couple years).

Starting from a fresh install of NTlite 2023.3.9171, selecting all updates to be downloaded/verified against the server 2019 1809 image and pulling that directory over. In my opinion with ntlite defaults and selecting all updates it should not put the end user into a state where there is an error. i.e. It should either not download/ un-select superseded packages by default.

When I create the iso I apply updates to all 4 versions on the disc (so I can install what is needed, basically am just looking to update the iso with current patches. )

At least it was this way historically (the last time I used ntlite was about 3 years ago and then nlite before that).
Normally if updates are superseded, they should be pre-emptively skipped or fail integration. This depends on the order of evaluation.
An updates list by itself doesn't tell me what NTLite did (which is why we look at NTLite.log & NTLite_dism.log).

If NTLite failed to work on a cleaned-up list, that's a simpler case to troubleshoot than using a possibly bad list of updates.
Just to check my 'process' for updates.
  • I go to tools/download updates.
  • On this screen I select the top left most box 'Update Queue' which then selects all the updates.
  • Then I select download.
  • close out of the download update window
  • Then I got to the Integrate/Updates section and drag the folder that had the updates to it which then populates. Gives me a message that 1-2 updates are already applied to the image but populates the list.
  • then go finish/apply; select integrate updates
  • finally proceed.
I can try again and grab a fresh log.
You can just do Enqueue from Downloads Updater, and not load all existing updates from the Updates folder. Or pick specific ones instead of bulk loading the entire folder. You can multi-select from the Add Files folder picker.

NTLite never deletes any old files from Updates folder. Which is a good/bad thing if you're not purging it on a regular basis.
i'm creating a copy of the above named image, using JUST ntlite updater, just to see if i get the error.

.net 4.8 and all updates have been intergrated on ALL images without error code and all superceded are being skipped
Yeah, I'm re-running it here as well but am currently on my laptop so it's taking a bit. Basically all I did was use the above base image, select all the updates from ntlite, downloaded into an empty directory and then drag that directory over to the integrate/update section.