You mentioned a broad and vague definition for franknbuild. According to that definition an ISO that comes with Vivaldi as default browser instead of its ugly bad copy Edge, is surely not backed by MS, at the same time is surely not a frankenbuild. Franknbuilds are, practically not existent in 2022, there are unofficial SKUs, reconstructed SKUs and alike that are both "non existent in nature" but also built with 100% of original and untouched files. An hypotetical frankenbuild could be Win Server 2008R2 x86. Given its easy to turn W7 x86 to Server, but such server would miss most of the server tools, so you had to grab the needed files from (Vista based) Server 2008 x86. Vista has no DISM, its packages are managed differently than W7 and later, so you had to copy the files manually, add regs and so on... In short you may end with a working OS, but you had to stitch and glue together pieces from two different generations. So frankenbuild would apply well to describe the thing.
Not really, MS acknowledges the need to pre-integrate 3rd party apps in Windows images and allows to do it through Sysprep/setupcomplete. But again, we need to keep in mind that throughout history, whenever there is a need to use a word for a new thing, we either use already existing words or make new ones. Hence a word can have multiple meanings in different contexts. There is a need to differentiate between standard homebrew/custom images and where users claim it's a Win 11 RTM LTSC, Win 10 Starter 21H2, etc (unofficial changes regarding build number/edition/license files). We can't use one word to describe these two things.
Considering the nonsense this mostly comes with, e.g. making W11 LTSC while giving 0 fu*ks about how long-term support is going to work, TBH Franknbuild seems to be aptly named.
Who are you to decide? How much time you spent testing it? What are the policy differences between a pro and a ltsc version? As a general rule is better to open the mouth when one has an idea about the discussed matter. And looks like you have no idea of what you're talking about.
I have already explained what frankenbuild means, if you read what I wrote you have no need to ask. BTW.. the short answer is "obviously it isn't"
I rather stop the discussion instead of going down the rabbit hole of personal insults. You can call it whatever name you prefer, and I'll call it whatever name I see fit.
As usual. When facts, real experiences are asked, trying to derail the discussion, is the only option.
How to install 22H2 on LTSC? I tried with enablement package (classic way with MSU) and also tried with Command Prompt to add CAB packages with DISM, none of them works. Maybe I missed some info here in thread. Currently using LTSC (non-IoT) build 19044.1865 in VMware.
the short answer is "You can not install 22H2 on LTSC", for long answer read this thread a few pages before
I did. i already shared what files to install if u want to since enterprise ltsc is not in the update.mum for 22h2 installing the other mums via dism from the eablement cab will get u 22h2 on ltsc microsoft-windows-22h2enablement-package~31bf3856ad364e35~amd64~~10.0.19041.1799.mum microsoft-windows-22h2enablement-payload-package~31bf3856ad364e35~amd64~~10.0.19041.1799.mum
Come on man, it's pointless It's a non-sense to install 22H2 on a long-term OS. It looks like a schizophrenic decision that you install long-term operating system with short-term updates in mind. If you want 22H2, just install normal 'enterprise' without LTSC.
the updates for LTSC and STSC are exactly the same the update to 1889 came through window update just fine
Perhaps it is kind for you to create a separate topic so that when someone asks you about the possible problems and errors encountered for doing the upgrade,you can answer them easily.Thank you.
the 22h2 enablement is installed and the cumulative updates still come through windows update. do not have to manually install them
I'm interested in this mechanism. Can you provide some links where it's explained? I searched by myself but cannot find anything relevant enough about this, just a bunch of non-technical articles... Thanks.
Like I said the enablement package is (for now) irrelevant. No advantages, no harm. That said, when the support for regular 19044 (Pro / Home /Enterprise) ends, any further update could be potentially restricted to LTSC and to 19044 only . Given there is no precedent scenario (1809 didn't have fake updates to major number) we can't rule out any option.