version means? What version you are referring to here precisely?Maybe a contribution, as i understand you can't skip versions, which may be why the delta error message appears.
I don't have any system running on 20H1/H2 ATM, all upgraded to 21H1. so can't try.What if you instead use KB5000802 for 20H2 and not 20H1 for updating?
Because MSFT released a newer version of 21H1 EP in the last PT, so I added that too here.Another thing is what is the reason for updating with EP 21H1 when already using live installation 19043.844?
If you look closely at the bottom of the SS, in the NTL status bar, it's already written process aborted. so I don't think it's about any pending restart, & furthermore, IDK whether this kind of feature is there & possible in NTL live OS modification i.e. to resume the process from there where it left followed by a rebootEP 21H1 is a pending installation, so a restart is required on a live installation.
afaik 21H1 is build on 20H2 witch is build on 20H1 and you're getting the error from trying to integrate the LCU KB5000802 for 20H1 on 21H1 instead of the LCU KB5000802 for 20H2 to 21H1. Even they have same size MS separate the LCU's on Update-Catalog.version means? What version you are referring to here precisely?
Only thing i experienced is that when try to run my preset over the monthly updated image after restart, then suddenly when NTL is processing removals the Windows disc cleannup tool starts and after running/ closing it NTL suddenly asks for a restart and hereafter i can start the process again without errors and fullfill the intended mofications as it does not appear that NTL has saved the modifications that had been made until now, when it interrupted with restart in the middle of the process before the point where All changes are directly saved.If you look closely at the bottom of the SS, in the NTL status bar, it's already written process aborted. so I don't think it's about any pending restart, & furthermore, IDK whether this kind of feature is there & possible in NTL live OS modification i.e. to resume the process from there where it left followed by a reboot
Hi nuhiThis also depends on what was removed in an earlier session, on that host's installation image or live, and most importantly was Servicing Stack compatibility always on.
If you can dig up the preset(s) which made that Host, it would be helpful in finding the cause.
But if you deleted something manually, or touched WinSxS folder, then anything is possible.
Thanks.
Hi nuhiThanks for the report.
Mine worked fine (my preset + that CU), will test your preset tomorrow with it and let you know if confirmed.
what do you mean by lite image? I only use unmodified vanilla/stock Win 19041.1. ISO image for all of my recent 20xx ISO branch modification as always since December 2019 till now as that's the base ISO for all 20h1.20h2 & 21h1 branchUnfortunately I cannot replicate the issue.
First problem was that your (original) preset already has KB5000842, so naturally when I tried to add it later it was denied as existing.
Windows didn't complain installing it.
Then I redid it all with the previous one, KB5001649, and tried to install KB5000842 after installation.
Again no error.
Am I missing something?
Integrating to a lite image is not supported nor recommended.
There are two points here, first yes I tested what you reported here on 19041.1, even got the FODs and all, I'm not dismissive as I have nothing to lose by finding a bug. But cannot replicate.what do you mean by lite image? I only use unmodified vanilla/stock Win 19041.1. ISO image for all of my recent 20xx ISO branch modification as always since December 2019 till now as that's the base ISO for all 20h1.20h2 & 21h1 branch
I can understand the first one somehow but did you check my last update here that I posted today?
Just Use that stock 19041.1 & add the preset that I posted in my last /earlier post here with all the updates that I added over there listed in preset & other settings applied, hopefully, you'll get that error too.
nuhi ok, I get it that you can't replicate this same error using the same ISO+same preset+same updatesThere are two points here, first yes I tested what you reported here on 19041.1, even got the FODs and all, I'm not dismissive as I have nothing to lose by finding a bug. But cannot replicate.
Second point, you said:
"so I tried to make (again) a new 21H!.906 (19043.906) ISO on the top of stock 20H1.1 (19041.1) Win10 ISO, adding the latest 2021-03 Cumulative Update Preview for Windows 10 Version 20H2 for x64-based Systems (KB5000842) & again, NTL showed the same error in this newest version as well"
And in the screenshot it states "Integrating", so how can I misunderstand that you're integrating to a lite image? Remember, this is a separate point, just saying that is not supported and is expected to break.
When making images, be it updating, always start fresh + preset and replaced update, cleaner and works.
Lite image means a slimmed down windows setup (install.wim) image.But what do you mean by Lite image? You mentioned this term earlier as well in your comment & I've also asked this same Q specifically in my earlier comment.
Ok, got it, thanks KasualLite image means a slimmed down windows setup (install.wim) image.
At least 1 component has been removed.
nuhiI use 19041.1 as base as well, for my images, and when I was testing yours of course.
I'm sure you're doing something extra to your image if it denies updates after installation, I just need the info what it is so I can replicate the issue.
Try what you told me in this topic, integrate previous version CU and try to install latest when it's installed, let me know how it goes.
If it fails, and you used only NTLite, not even your own REG files integrated with it, then please attach that new preset and I give it another try.
Thanks for your patience.