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
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.