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).
An unofficial build is an unofficial build, but certificates are sort of passwords, not real components of the OS. Whatever if your problem is a certificate added to the ISO, turn your vision by 180 degrees. Take, say Win server 2022, it comes with two sets of certs (good to make it Standard or Datacenter), then remove the Datacenter certs, then make the ISO. Is that a "frankenbuild"? For sure is something not made by MS, nevertheless the server standard inside that ISO would be a 100% "Kosher" SKU. So where's the difference between removing and adding a certificate?
wsreset -i lets u install microsoft store on LTSC. my LTSC 2021 iso couldn't be fraken build just because i left microsoft store in?
Sure I I made the example of Win98 Lite, I can make many other Modified != Frankenbuild If MS thought that KMS activated windows were different than "genuine" ones they would block them, they would use a stronger protection method. Clearly for all means the two are exactly equivalent (at least outside corporations and professional use) In short, if that is not a MS concern why in the heck should be yours or mine?
What i meant to ask is, if this "activating password" allow a specific version to achieve/do something which it originally can't because now it has additional capabilities because of addition of new files then what would you call it if not frankenbuild. Say server standard turned to server datacentre because of which it can now concurrently open 50 RDP connections instead of 20 because now its RDP system file is identical to server datacentre edition(I don't know anything regarding this so just consider it as sort of hypothetical situation).
I have no issues with frankenbuilds, I am just curious regarding "its definition". Modified!=Frankenbuild is a pretty vague term & thus can't be used as a "standard definition/rule" on forums as per my opinion.
Since my LTSC 2021 iso was made with a script and i left microsoft store in and added the oem certifcate. my modified build gets updates without problems. a fraken build would give u errors when trying to install updates