Listen. I had a Smart car, with sequential semi automated gears, the fully automatic one was an optional The point is that fully automated gears aren't different from manual ones, all the mechanical and electrical parts were there. The only changed thing was an activation key in the control unit. So assume I add that key (something that is really possible) and I got the automated gears, would that be sufficient to label that car as "frankencar"? I don't think so.
I don't know much about cars in general so not able to understand this analogy as you meant to convey but from what I understand the "mechanical & electrical parts" getting changed should be sufficient to label the car as "frankencarr" & isn't that what happens if certain exe/dll files on a specific windows version gets altered by a few bits to let them achieve something which they couldn't earlier because of "entering a secret activation code" in windows.
That's exactly my point. If No one is changing exe/or dlls there is no reason to call it frankensomething. Which is our case.
I didn't modify files in my iso i just left the store in and added the oem license certificate from LTSC 2019. Since i didn't modify anything my build is not fraken
But how come exe & dll remain unchanged if some "additional feature/capability" not present earlier is now available & if there is no "additional feature/capability" other than cosmetic changes in UI then what's even the point in doing any "modification". In original LTSC there is no MS store while in current windows version with store if you added license certificate from LTSC 2019 & it didn't result in any changes/addition to system files other than a cosmetic change of now showing LTSC in about version then what's the point or you should call it a "modified version UI" in regular win 10(kind of like how some ppl modify windows system dll for some custom icons for certain file types).
I created an ltsc iso with a script that was shared on these forums Since the iso's from uupdump are not official they are Franken?
Would be better if you had a vague idea about how the windows installation works.. All the available components are inside the WinSxS folder aka the component store, then the files are hardlinked to the windows dir. Remove an hard link, and your file although being still on your HDD is not available anymore. That's the way any optional feature appears and disappears since Vista. In win server almost any feature is controlled that way. In win 8.x the media center "magically" appears after you paste the right key in the right field, and so on. I hate to repeat what I wrote just few messages ago. A change in the license changes the product policies, take Windows 10 Pro, turn in to server, and your SMB limit will go from 20 to 65536 or more. Cortana will be disabled and so on. So go to the blackboard and write 100 times "product policies are not cosmetic changes" (although product policies may lead also to cosmetic changes) No, indeed, it's not installed. But you can install it later (or before the installation), exactly like you can remove it from Pro or Enterprise (before or after installing them). There is no crack or protection circumvention involved. It's a program. You can have it or not depending your will, just like a browser or an email client. Would you call frankenbuild a custom ISO that preinstalls Vivaldi or Norton AV? Acer / Lenovo /Dell / Whatever do that all the time, and we can call their installation images bloated, but no one has ever called them frankenbuilds.
I thought windows downloads additional stuff to winsxs folder as its size keep increasing over time & activating new features means certain additional stuff being downloaded to this folder. I guess "homebrew" is a better wording than "frankenbuild" for such modifications as they are modifications to a program to make them do things they are not supposed to do.
I have no idea regarding this, I was only curious about definition of frankenbuild & how it is not applicable in case windows version acquire additional capabilities because no system file is changed/modified.
winsxs grows because the monthly updates, do a reset base and it will be "slim" again In general, no. But when you do a dism /restoreimage a corrupt package may be redownloaded from MS servers Homebrew is better than frankenbuild, but still a bit misleading and derogatory. You hear homebrew and you instantly think to a stereotypical nerd that works in the basement doing weird things, while custom images are used everyday in large and medium sized companies, by their IT personnel using tools provided by MS to ease their work.
In the context of MDL and Windows ISO/Installation, Homebrew word is used to describe if someone has integrated updates and/or made some settings changes/installed-removed apps in Windows ISO. And Frankenbuild word is used to describe if someone changes build number/edition/license files in a way that is not suggested to do by MS. This can be ISO or installation. In another sentence, MS has properly documented how to make homebrew ISO's but doesn't support the Frankenbuild ways and might be against it in many scenarios. @acer-5100 if you think this is not correct terminology then please suggest the alternative words and how to differentiate between these two things.
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.