This can happen when some (language) feature is installed/enabled after the CU is installed/integrated. Addition: I noticed the "installed Updates" showing dates from march, when integrating updates to a windows image it's best to start with a clean base wim, not containing any previously integrated updates and better to use W10UI for the best integration experience.
@Enthousiast Ah..ok Btw.... To my knowlegde are those updates intergrated in this version >> Windows 10 Enterprise LTSC 1809 -- 17763.316 It's updated until Feb2019 Correct? Code: Windows 10 version 1809 updated feb2019 en_windows_10_enterprise_ltsc_2019_x86_dvd_892869c9.iso 88af607f1e752761577d21f2b7aa98692809bf66 nl_windows_10_enterprise_ltsc_2019_x86_dvd_7de5cbe9.iso 56A4E9E77605276E0DB6D25F17F69EDE089C92BA It Includes >> Net Framework 4.7 2018-11 Update for Windows 10 Version 1809 for x86-based Systems (KB4470788) Security Update for Adobe Flash Player-Wi 10-1809 -x86 (KB4537759) after installing this version, WU added these updates >> (back in April...) 2020-02 Cumulative Update for .NET Framework-3.5-4.8 -Win10-1809 (KB4538156) = windows10.0-kb4537490-x86 ( Net Framework 4.7.03190) 2020-02 Security Update for Adobe Flash Player-Wi 10-1809 -x86 (KB4537759) 2020-04 Servicing Stack Update for Windows 10 Version 1809 for x86-based Systems (KB4549947) 2020-04 Cumulative Update for Windows 10 Version 1809 for x86-based Systems (KB4550969) I used this as a base image for updating. By clean base image, u mean the 17763.1 version? I see no real problem in using the 17763.316 as a base. Pls correct me if wrong PS: Is it possible to remove those 2 packages from the WIM, then it's also a clean base like 17763.1 (not used this one so no idea there) Thx for the info and keep up the good work
@Enthousiast Ok , understood. Can u confirm that those 2 updates the only differents is between 17763..1/.316 KB4537759 KB4470788 I'll try anyway later on Thx for the help us usual.
All 1809 updates are listed here: https://forums.mydigitallife.net/th...-17763-xxx-pc-rs5.77945/page-216#post-1490183
Not true. This re-installation of an already installed updates has happened to me also, although I did not do anything to my OS during the two days. I think it's just the morons at Microsoft could not even identify if their POS update had been installed or not. Shame on these idiots. I don't understand how someone was not fired for stupidity like this.
Kinda two different situations, and still it can be caused by a fod install or update, i can honestly say, it never occurred on my many tests for my releases.
Hi, I need some help activating my Win10 enterprise LTSC Evaluation. I got the ISO from the MS website, but the usual activation method like entering the key, changing the kms and activating via cmd didn't work. I've seen a lot on this forum and I'm getting a bit confused. I've never played with Enterprise LTSC editions before, so a helping hand would be great. I've tried to use the default key for Win 10 Enterprise LTSC edition, from MS website, but it didn't work for. Where did I fail? I also don't want to run any 3rd party tools to make this work, if possible. Thanks.
Also, among all of it is the sentence "LTSC Evaluation can't be activated". Which means, since you managed to find the thread, you might as well read OP. Good luck.
No but in most, if not all, cases something caused it, it doesn't normally re-offer updates out of the blue.
Hi, Windows 10 Enterprise (N) LTSC 2019 iso linked on this thread, are already the Volume License version that can be KMS activated just after installation without any modification or patches ?