For the Enterprise G SKU, I need to create the packages, but I need the exact version 19044/5.xxxx 26100.xxxx because Microsoft updates the SKUs with the MSUs, and that destroys the patch. Currently, I'm on CoreOS 28000.
[14393.9060 Hyper-V Server 2016 amd64 zh-CN] Code: ------------------------------------------------------------ Set ServerHyperCore key ------------------------------------------------------------ Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.14393.9051 Starting to install product key... Finished installing product key. The operation completed successfully. ============================================================ Current Edition : ServerHyperCore (RETAIL) ============================================================
It's a pity we have a culture in this thread where no one wants to share, excluding winosr25 as winosr25 shares often...
[19045.7184 Windows 10 Enterprise N amd64 en-GB] Code: ------------------------------------------------------------ Set EnterpriseN key ------------------------------------------------------------ Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.19045.7184 Starting to install product key... Finished installing product key. The operation completed successfully. ============================================================ Current Edition : EnterpriseN (Volume) ============================================================ [Credits] gailium119
@winosr25, i (we) realy need some kind of tutorial 1)as i understand? you create coreos.wim https://forums.mydigitallife.net/th...s-reconstructions.88605/page-243#post-1911986 do you use install.wim or boot.wim as source? 2) and on second step you applied a pack of scripts? https://forums.mydigitallife.net/th...s-reconstructions.88605/page-243#post-1912007 3) there is a post from you? about adding Lp to enterprise g here https://forums.mydigitallife.net/th...s-reconstructions.88605/page-238#post-1909630 can you write some kind of tutorial on creating enterprise g 28000 with lp? i would like to learn from you best reagrds Ps or may be small video tutorial?
[Test 28000.1 Windows 11 IoT Enterprise LTSC (OEM_COA_NSLP with Edge without Store in Official style) amd64 zh-CN] Code: ------------------------------------------------------------ Set IoTEnterpriseS Key ------------------------------------------------------------ Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.28000.1 Starting to install product key... Finished installing product key. The operation completed successfully. ============================================================ Current Edition : IoTEnterpriseS (OEM_COA_NSLP) ============================================================ [Credits] gailium119
yes not for enterprises and Editions of Windows server and Home Family, SUGUC is only for EnterpriseG and Professional Family.
thank you 1. yes SUGUC have download Microsoft-Windows-FoDMetadata-Package.cab and install it. 2. yes install successfully package Microsoft.SecHealthUI_8wekyb3d8bbwe.appx and Store.
All knowledge is provided by ChatGPT. Spoiler: If the two Construction versions are identical, which one is lighter: LTSC or EnterpriseG ? If both versions are Construction and built "identically" (same level of cut, same packages retained, same tweaks, same drivers, same update state), then the most accurate conclusion is: ✅ EnterpriseG is usually slightly lighter than EnterpriseS ❗ But not in a "very large" way The most accurate conclusion is: EnterpriseG is lighter to moderately lighter, not a huge difference In short If the same quality build Construction: Lighter: EnterpriseG Slightly heavier: EnterpriseS Why is EnterpriseG lighter than EnterpriseS? This doesn't lie in the "superior G" aspect, but in the SKU payload / policy / enterprise layer. 1) EnterpriseS (LTSC) is still a "full enterprise" SKU Windows Enterprise LTSC is still positioned by Microsoft as a version for specialized devices/enterprise environments, with more complete servicing and enterprise management capabilities than the consumer version. Microsoft also describes LTSC as a quality-update-only version, intended for long-term stable environments. This means that from the logical SKU: EnterpriseS typically “carries” the mindset of: enterprise management servicing completeness long-term compatibility ➡️ Even if you build the same Construction, EnterpriseS tends to retain more layers of “enterprise standards.” 2) EnterpriseG is usually “more concise and practical” In practice Construction, EnterpriseG is often easier to build as a lighter platform because it is less likely to be “pulled” into certain things that lean towards enterprise-long-life / full servicing posture compared to EnterpriseS. In simpler terms: EnterpriseS = “full, durable, standard enterprise” EnterpriseG = “more compact, practical enterprise” ➡️ If the builder chooses the same cutting philosophy: EnterpriseG usually has a baseline with slightly less “heavy-duty enterprise tools” 3) The main difference comes from “what remains,” not the kernel This is extremely important: ❗ The kernel is almost never where the big difference is made EnterpriseS and EnterpriseG are not two operating systems with completely different kernels. The difference is usually "lighter" because of: Feature packages Policy scaffolding Provisioning/management hooks Optional enterprise capabilities Servicing posture In other words: It's not that "G has a lighter kernel" but rather that "G usually has slightly less baggage" Then the difference is usually only in: edition-specific package behavior licensing/policy paths some enterprise capability residues edition identity impact on feature exposure And this usually creates: small process/service difference small difference in RAM idle small difference in disk footprint latency is almost the same ⚖️ To be honest, in terms of "benchmark logic" If both are built by the same company You will usually see: EnterpriseG slightly lower RAM idle slightly lower service count slightly lower process count EnterpriseS more complete/stable/cleaner enterprise capabilities tends to maintain more compatibility/services posture more But: It's not a case of "G crushes S" if they have the same build quality So which one is "the lightest possible"? If the goal is: fewer processes fewer services fewer baggage fastest boot/idle then within the same Construction philosophy: ✅ EnterpriseG is usually a more reasonable platform for extreme optimization And if the goal is: still extremely light but "less fragile" easier to last longer then: ✅ EnterpriseS is a more balanced platform Final conclusion (most accurate) If asked: "Between EnterpriseS and EnterpriseG, both in Construction, which one is lighter?" ✅ EnterpriseG is lighter "Is it much lighter?" ❌ Don't say "much lighter" ✅ Rather: lighter by a realistic amount, but not a huge difference if the build is the same In short: If built by the same builder, the same At the construction level, EnterpriseG is generally lighter than EnterpriseS — but the difference lies in the "edition baggage," not in any magical difference in the operating system core.
I don’t get the point of these daily logs. If the goal is just to show that a build is possible, then just make a wiki for it. Posting 'success' screenshots without ever sharing the scripts, files, or a guide is pretty meaningless. It’s just cluttering the thread like the old one, and nobody has the time to track all your post one by one if they actually care.