The image has been damaged by an offline servicing failure (W10 21H1)

W

WWE_Fan69

New Member
Messages
18
Reaction score
0
Hi there, this is my first post here and I hope with your help we can get this problem sorted :-)

My current situation:
I have an original OEM Windows 10 Pro pack, it was sealed and so I know its brand new (the version is 21H1 x64) and I need it upgrading to the 22H2 version, but I am having a lot of "The image has been damaged by an offline servicing failure and no further servicing is allowed..

The updates this happens on are:
KB5023733 - Cumulative Update Preview 19041.2788.1.9
KB5003791 - Feature update to the windows 10 version 21H2
KB5011048- .NET Framework 4.8.1 10.0.1.8025
KB5015684- Feature update to the Windows 10 version 22H2 Enablement package
KB5012170- Security update for Secure Boot DBX 19041.1880.1.1
KB5022502- .NET Framework 3.5 and 4.8 Cumulative Update 10.0.4614.6

CAN I use any other ways to get these updates integrated please as this updated disk will bw used for a brand new built up PC for a client, so obviously I need this to be fixed and for it to not be a problem updating in the future.

Thanks all for your time,

Arty.
 
The preferred path is to download a non-OEM release from MS directly, and update it. You can use the browser User Agent trick, or Rufus USB tool to download a clean W10 22H2 ISO.

Start there, and apply the latest monthly CU, .NET 4.8 CU (installing 4.8.1 is optional) and Secure DBX. Make an USB image for your client, or burn the updated image to DVD. Most of the time, OEM images are stock Windows ISO's with extra vendor apps which are already out of date and newer versions are available from their website.

Servicing errors indicate they may have cleaned up the WinSxS components to save space, or your host system isn't running a current W10 or 11 release to work on other images.
 
garlin said:
The preferred path is to download a non-OEM release from MS directly, and update it. You can use the browser User Agent trick, or Rufus USB tool to download a clean W10 22H2 ISO.

Start there, and apply the latest monthly CU, .NET 4.8 CU (installing 4.8.1 is optional) and Secure DBX. Make an USB image for your client, or burn the updated image to DVD. Most of the time, OEM images are stock Windows ISO's with extra vendor apps which are already out of date and newer versions are available from their website.

Servicing errors indicate they may have cleaned up the WinSxS components to save space, or your host system isn't running a current W10 or 11 release to work on other images.
Click to expand...
Hi there and thanks for your reply.

We only use Windows OEM keys as I am a self-employed system builder, and as we have paid for the sealed OEM packages we would like to use these until we have used up our stock..

Is there any way I could download an updated OEM version of Windows 10 or can I just use Media Creator to make a Windows 10 22H2 image that'd accept the OEM product keys we have?

Failing that, is there ANY way at all of getting our current versions up to date?

Obviously, we could try to get the problematic updates auto installed on first user logon, but I was hoping to integrate as much as possible. Once we have an updated Windows installation we can proceed to add our own company customisations. I hope this has explained a bit better
:)


Ps. My host PC I am running nLite on is fully licensed Windows 10 Pro retail.
 
My understanding is OEM licenses only differ in that cannot be used for upgrades (requires clean install), and once activated, cannot be transferred to a new PC or upgraded motherboard (hardware locked). Otherwise, it's not actually a distinct Windows build.

Your OEM product key should activate on a generic Windows image of the same edition (Home/Pro). Windows keys since W10 are for the edition, and not a specific release build (works on both W10 & 11).

Reviewing your updates list, installing both enablement packages is unnecessary. You would only need the 22H2 Enablement, since it supersedes the 21H2 Enablement. Enablement turns on hidden features already installed in the latest monthly CU's.

KB5023733 Mar 2023 Preview CU
KB5003791 Enablement package 21H2
KB5011048 NET Framework 4.8.1 (optional)
KB5015684 Enablement package 22H2
KB5012170 Secure Boot DBX
KB5022502 NET 4.8 CU Feb 2023
 
Hi all, well Ive got an update for you all (no pun intended)
I am STILL getting the errors about image being damaged etc...
These are the exact steps I have performed and the order I Performed them in:

I used Windows Media Creation tool to make a Windows 10 x64 ISO.
When said ISO was finished, I extracted it into the root C: drive (C;\Win10)
I opened ,nLite, went to Add Image Directory and I selected the correct folder location (c:\Win10)
Right clicked the Install.esd, convery to WIM (replace ESD)
When this has completed, I mount the first image (Windows 10 Home or Core), and when this is mounted I click on Updates > Add >Latest Online Updates, I select all updates (before I started this, I uninstalled, then did a fresh install of nLite, just to rule out a bad update file) and click Download and wait while they all update, and successfully verify, I then click Enqueue.
I have not changed any settings, the update extraction is set to Standard, None selected for Clean Update Backup and Extra Options is not selected, I then click the Apply button, and proceed using the defaults (Save the Image, WIM adn no other options messed with) and click process.


I then get the Errors and warnings - Update Integration dialog box come up and it throws up 3 errors, these are listed below:

* Integrating: KB5023696 - Cumulative Update 19041.2728.1.7 - One or several parent features are disabled so the feature can not be enabled.

* Integrating: KB5023773 - Cumulative Update Preview 19041.2788.1.9 - One or several parent features are disabled so the feature can not be enabled.

* Integrating: KB5022502 - .NET Framework 3.5 and 4.8 Cumulative Update 10.0.4614.6 - Error 0x80092004 - [8196]

this is as far as I have gotten. Id appreciate any comments on how I can do this sucessfully.

Thanks again all,

Arty.
 
Can you attach the auto-saved preset file NTLite created? (Under the Preset folder and menu tab)
 
Hi, yes Im so sorry for the delay, I had deleted the failed attempts, so I have just recreated the above steps, and the contents of the file follows:



It wont accept my post when I paste the file in, it says Oops! We ran into some problems. Please try again later. More error details may be in the browser console.
 
Reviewing your preset:
Source image is W10 22H2 Home (Sep 2022).​
​
KB5020377 - Dynamic Update Nov 2022 (optional)​
KB5023696 - Mar 2023 CU​
KB5023773 - Mar 2023 Preview CU (pick the normal monthly or monthly preview, but not both)​
KB5011048 - NET 4.8.1​
KB5012170 - Secure Boot DBX​
KB5022498 - NET 4.8.1 CU Feb 2023​
KB5022502 - MET 4.8 CU Feb 2023​

Nothing really wrong here. Are you using a 3rd-party AV solution? If so, can you try disabling it while NTLite runs?
 
garlin said:
Reviewing your preset:
Source image is W10 22H2 Home (Sep 2022).​
​
KB5020377 - Dynamic Update Nov 2022 (optional)​
KB5023696 - Mar 2023 CU​
KB5023773 - Mar 2023 Preview CU (pick the normal monthly or monthly preview, but not both)​
KB5011048 - NET 4.8.1​
KB5012170 - Secure Boot DBX​
KB5022498 - NET 4.8.1 CU Feb 2023​
KB5022502 - MET 4.8 CU Feb 2023​

Nothing really wrong here. Are you using a 3rd-party AV solution? If so, can you try disabling it while NTLite runs?
Click to expand...

Thanks, I am now trying it again with your recommendation. I will update as soon as its finished. Thanks for all your patience with me :-)
 
So I am back yet again!!
This is really doing my head in, WHY wont it work??

I started with selecting KB5023696 Cumulative Update, but it errored out with KB5011048 - .NET Framework 4.8.1 10.0.1.8028 - The image has been damaged by an offline servicing failure, so I re-did my steps from scratch, but the first thing I did was enable .NET Framework 3.5 and a few other options, and when it came to the updates, I tried with KB5023773 - Cumulative Update Preview (and unselecting the other) and again it came up with the dreaded image damaged YET AGAIN!!!

For what its worth, here is the latest preset, weather it'll show anything is another matter.

Arty.
 

Attachments

What happens if you skip .NET 4.8.1 Framework and update, for now?
 
garlin said:
What happens if you skip .NET 4.8.1 Framework and update, for now?
Click to expand...
If I skip all .Net updates, it seems to work and not damage the image, but when trying to integrate either Cumulative Update (preview or otherwise) I get the following:

Integrating: KB5023773 - Cumulative Update Preview 19041.2788.1.9 - One or several parent features are disabled so the feature can not be enabled.

So Im sorta making progress. Next on the list is pinning down the rogue .NET that breaks the image :s
 
And I'm back!

I got to this: Integrating: KB5022498 - .NET Framework 3.5 and 4.8.1 Cumulative Update 10.0.9139.2 - Error 0x80092004 - [8196]
Cant find any specific info on it though..

So, the following updates throw up errors, even integrating singularly:

KB5023773 - Cumulative Update Preview
KB5023696 - Cumulative Update
KB5022498 - .NET Framework 3.5 & 4.8.1

as an interesting sidenote, no matter how many times I use nLites Check for updates, KB5020377 - Dynamic Update for Windows Setup is always in the list to be selected, and it always integrates it, but it still shows up like a bad penny lol
 
Error 0x80092004 points to data corruption. Are you running a 3rd-part security solution?
 
garlin said:
Error 0x80092004 points to data corruption. Are you running a 3rd-part security solution?
Click to expand...
Apart from standard Windows 10 security, I do use Norton 360, but that shouldn't really interfere with things, I guess I could try disabling auto-protect and trying that update again.. How would Norton affect 1 update and no others? I've done a chkdsk /f and I've done sfc /scannow which passes, and so does the dism /cleanup-image passes *shrug*

What I'll also try doing tomorrow when I'm at the pc again is downloading the updates through a different agent and see if the errors still exist.

Thank you very much for all your help and patience tonight :-)
 
I just tried replicating things here out of curiosity, since these threads keep popping up regarding updates and NET frameworks. To do this, I used an unmodified W10 21H2 image that only had "trim editions" done to it in NTLite. Then I used the "Latest online updates" feature of NTLite on that image and enqueued everything. This was very similar to what OP is trying to do and I got many of the exact same updates to install. Then I processed the image (using the latest version of NTLite and all relevant NTLite options at defaults). It finished without issues, except for 2 problems.

1) First, it gives an error when it's done processing which is the 0x80092004 error, but it is for KB5022502. After some Googling, I'm quite confident this is a Microsoft bug, because this issue persists outside of NTLite and there are multiple reports on that. Microsoft already had to fix and re-release KB5022498 which I'm assuming is the reason an update threw an error, because before Microsoft "fixed it" the issue used to be the other way around, where KB5022498 would not install if KB5022502 was already present. You can read about this problem here (link1, link2). I think the issue now is the reverse, where KB5022502 won't install if KB5022498 is present.

2) The second problem is the Dynamic Update for Windows setup (KB5020377) never gets recognized as being installed in the image. For troubleshooting purposes I decided to enqueue this again, by itself, and chose to integrate this update into all 4 parts of the image (WIM, WinRE, PE, Setup), but it still continued to show up as not being recognized by the Windows Updating feature of NTLite as being installed.

Note: I did all of this testing on a machine that has no antivirus/firewalls of any kind, on the computer or in the router, and I had even just installed Windows cleanly, so I have no doubt that the host machine is in a flawless state for testing/troubleshooting.
 
Hellbovine said:
2) The second problem is the Dynamic Update for Windows setup (KB5020377) never gets recognized as being installed in the image. For troubleshooting purposes I decided to enqueue this again, by itself, and chose to integrate this update into all 4 parts of the image (WIM, WinRE, PE, Setup), but it still continued to show up as not being recognized by the Windows Updating feature of NTLite as being installed.
Click to expand...
This has been discussed before.

DU is not a component update, it's a CAB archive which is extracted to the ISO image (replacing the existing files). Therefore it can never be reported, unless you have a database that cross-checks the DLL file versions.

The side effect is there's no revert for DU, other than starting over with a clean ISO image.
 
WWE_Fan69 said:
Apart from standard Windows 10 security, I do use Norton 360, but that shouldn't really interfere with things, I guess I could try disabling auto-protect and trying that update again.. How would Norton affect 1 update and no others? I've done a chkdsk /f and I've done sfc /scannow which passes, and so does the dism /cleanup-image passes *shrug*
Click to expand...
Most users aren't reporting your integration errors, so the root cause is likely specific to your PC.
Since your host's updates are recent, it leaves 3rd-party AV apps since NTLite is writing "protected" Windows files.
 
Latest preset say the NTlite mounted image is build 10.0.19045.2006 and updating to .2788 is KBkb5023773.
About .netframework you should only use this one as it was updated on 29/3-23 - more info here (scroll down and see known issues).The updated .netframework here.
NTL update section show more than one similar updates sometimes and can confuse with "missing" - but always version number - check only the latest version to integrate in build.
 
You must log in or register to reply here.
Back
Top