Updading ISOs of XP/7/8.x was (and still is) a great thing to do and a great way to save time. It started to make less sense with W10, but since 1809 or so it is completely pointless for 99.9% of scenarios. So unless you have a REAL REASON, I suggest you to employ better your time.
Thanks, so it's ok to use the LTSC base ISO without the updates, but I'm not quite sure if Windows get better stability/performance after installing all the updates. Usually I let windows updates and defender disabled, just firewall running
I'm afraid you didn't get what I'm saying. I said that updating the ISO is stupid, not the OS. Just install the OS then run WU. To have it updated. It's the PC that is meant to work to simplify your life, not you that have to work to simplify PC's life. Preupdating W7 (for example) makes (a lot of) sense, because the great part of the updates are not cumulative, hence WU takes hours to install a ton of updates over another ton of updates, with many reboots in the middle. If you have 15 PCs pre-updating the W7 ISO spares you dozen of hours of work (and reboots) On the other hand, W10 updates are cumulative, so WU installs a single update (plus sometimes a single .net update), and usually need a single reboot, no matter if your W10 ISO is 2 years old or 30 days old. So where's the gain in pre-updating? In recent W10 is even worse, practically any update installed on top of xxxxx.yyy, first downgrades to xxxxx.1, then upgrades to xxxxx.zzz. In short updating say 19041.1 to 19044.1889 takes less time than going from 19044.1826 (July update) to 19044.1889 (August update). You work an hour or so to complicate the work of WU, not to simplify it.
Officially there is not even an IoT Enterprise 2021 LTSC ISO, so that will go fine, at the OP "download section" you can find all ISO links. And updates you can find at the OP "Updates overview" section and create your uptodate ISO when desired.
on another known board they show IoT Enterprise LTSC 22622.450 is this a manipulated build, I say its a fake am I right?
Thanks, perfectly clear! I thought it's a better practice to leave WU disabled and do the updates manually, perhaps avoid some of them too
yes you right the basic principle of LTSC is to have always the same build number (19044.xx) until end of support
As usual your too liberal usage of derogatory terms has nothing to do with reality. Is not that anything you don't like, don't understand or don't approve becomes automatically a frankenbuild. Frankenbuild implies that a relevant section of executables, libraries and other pieces of two or more IT products are combined together to reach a definite result. Say Win98 lite, back in the days, used the W95's explorer files to have a lighter/faster OS while retaining the W98 improved stability and wide HW support. Although I haven't tried the mentioned build, is clear that there isn't anything like that here. Possibly not a single OS file is deleted/hacked/replaced. Just LTSC certificates are added, and the right activation key is used. That's all
It doesn't officially exist in so many ways, it's a mixed build thus a frankenbuild, this was always been the consensus on MDL and still is.
Yours is as much not a real LTSC as the "22622 LTSC" when you use a part of the mums manually ONLY to SHOW the word LTSC combined with an unusual major build nr.
Wrong. The certificates/key pairs controls the kernel policy (according to what MS (not the user) decided to control) that is a major differentiator between various different editions. A LTSC build not released/endorsed by MS is still technically a LTSC not a pointless label on top of something else. A bit less of self centerism would help here. MDL is not made by you and yourself. And even if the that was object of a large poll, still wold mean nothing. Technical things are either wrong or right, is not that a wrong thing, if backed by 99% of users, becomes magically right
I extracted the enablement package and installed microsoft-windows-22h2enablement-package~31bf3856ad364e35~amd64~~10.0.19041.1799.mum microsoft-windows-22h2enablement-payload-package~31bf3856ad364e35~amd64~~10.0.19041.1799.mum via dism that installed the 22h2 enablement and 1889 installed via windows update i did not have to manually install it
I am a typical user of windows with an above average knowledge regarding its general usage so my technical knowledge/experience is not that deep & asking this just out of curiosity. Say someone install/add some sort of official certificate/enable some hidden policy in LTSC that allows it to do/achieve something which a 100% official LTSC version can't then isn't it obvious that it is possible only by addition of certain files which are not supposed to be there in the first place & thus can be considered as "combination" of two products(LTSC files & non-LTSC files not supposed to be there even if they appear via official MS channel after enabling/adding some policy in LTSC).
Can we even classify franken builds as true or false? It is either an official build or a modified/franken build on which updates may or may not install(kind of like how a kms activated windows pc at home receiving all the updates does not make it same as a genuine retail license activated windows).