Windows Non Core Edition Activation
Norine Wiltshire
I've found some references, when looking for information on WAIK installs of Windows 8 of a varient called Windows 8 core, that can be installed off the professional edition disk. There's also a mention of it on Win Super Site that says
Paul Thurrott of WinSuperSite explicitly names Windows 8 Core in his giant comparison table of different Windows 8 editions (notice the plain "Windows 8" is absent from the table because it is referred to as "Core"):
It means the "Home" edition for all intents and purposes. Perhaps the best source for this is MSFT's own site (for Windows programmers). Search for "PRODUCT_CORE" here (which programmers rely on) and look at the "Meaning" column:
Note that it currently refers to it as "Windows 10 Home" but all other editions have their own qualifiers (e.g., search for "PRODUCT_PROFESSIONAL", "PRODUCT_ENTERPRISE", etc.) In fact, prior to the release of Windows 10, the "Meaning" column for "PRODUCT_CORE" (at the same link) referred to it as simply "Windows 8", which normally means the home edition by default (in the absence of the terms "Pro", "Professional" or "Enterprise").
How can you convert a Desktop Experience edition of Windows Server 2016 to a Core edition? For previous insider builds you use the powershell uninstall-windowsfeature cmdlet to remove features such as server-gui-shell and server-gui-mgmt-infra to convert a Desktop Experience edition to a Core edition, but these features no longer exist in the RTM version.
I'd like to start getting some Windows Server 2016 Core VMs up and running. As it is not yet available on MSDN i'm forced to use the evaluation ISO. This works fine in the long term (>180 days) if you want to use Desktop Experience editions, as you can change the evaluation edition to a licensed edition with a product key and dism.exe /online /set-edition:ServerDatacenter /productkey:00000-00000-00000-00000-00000 /accepteula but this wont work with the Core editions of Server 2016 as dism.exe /get-targeteditions doesnt list any options to change it to a non-evaluation edition. So right now i'm forced to either wait a few weeks for it to become available on MSDN, or convert a desktop experience edition to a core edition as i'd need these VMs to work past 180 days.
"Unlike some previous releases of Windows Server, you cannot convert between Server Core and Server with Desktop Experience after installation. If you install Server Core and later decide to use Server with Desktop Experience, you should do a fresh installation."
It took me one week to find a build where WSL2+Docker works to find out one day later the build expires, which of course breaks the WSL2 and thus also Docker. More information here Re: WSL 2 not working after installing 20262 - Microsoft Tech Community
Obviously bad timing
I have traced the setup and compared it with the setup on the GUI edition and it seems to be OK.
Then I have tried to trace the first Docker startup procedure with process monitor in the GUI edition and collect all the steps to replicate them in the Core edition, but without success.
I am ready to test whatever is necessary to make it working.
Because even if WSL2 will be in the end part of WS2022 LTSC (edition with GUI) I would rather want to have it working in the core edition, because of the resource saving potential.
While looking for the differences I have found out that the docker desktop process opens a lot of named pipes which are essential for everything to work together.
I was able to open some of the pipes by starting the dockerD.exe, but not all.
I am trying to activate windows server 2019 standard key from windows server 19 EVAL ISO But I am not able to activate the key. I have tried the above step as mention but luck. Please find the step which I have performed and the error screenshot. please help to fix the issue.
If you install Evaluation edition of Windows Server it will expect a Retail key when doing the straight conversion. For those of us with Volume license keys the upgrade path involves first using DISM ONLINE Set edition using a KMS key, Then on reboot use slmgr /ipk using your Volume key and then finally run slmgr /ato.
Trying to keep up with Microsoft's internal Windows Core OS (WCOS) project is no easy task. Even we find it challenging to keep up with all the different codenames, plans, and changes being made to Windows with Windows Core OS. So, to try and keep things in line, we've compiled this ultimate guide for Windows Core OS, CShell, and everything in between.
Windows Core OS is something we've been writing about since early 2017 and has been in the works for much longer. It's the future of Windows, which takes the shared code of OneCore and builds a modern, legacy-free OS on top of it. Windows Core OS, along with CShell, allows Microsoft to create new versions of Windows 10 quickly, and share standard components and features across different device types and WCOS versions quickly and easily.
To answer this question, we first have to explain what Windows Core OS isn't. Today, Windows 10 is several different operating systems across the many devices types it can run on. There's Windows 10 for desktops, Windows 10 for HoloLens, Windows 10 for IoT devices, Windows 10 for Surface Hub, Windows 10 for Xbox, and there was also a Windows 10 for phones. Although these are all Windows 10, they're all technically different operating systems that don't run very well on devices for which they are not designed. Windows 10 desktop, for example, would be a terrible experience on a phone, and vice versa.
All of these versions of Windows 10 do share universal elements, however, such as OneCore and OneCoreUAP which are layers of the operating system that you can find on all of these versions of Windows 10 that enable things like the Universal Windows Platform. But the rest of everything included in these operating systems are specific to that version of Windows. Not everything is interchangeable or shareable between them, as most of these features have to be rewritten each time by the teams working on these individual versions of the OS for them to function.
A great example of this is with the Start menu and Action Center on Windows 10 for desktop and Windows 10 Mobile. While Microsoft tried very hard to make these experiences seem the same, underneath, they were very different. Keen-eyed users would have likely noticed differences in features between the two Start experiences, and that's because for one feature to be available on both platforms, it needed to be built twice, not just once. Live tile folders are a perfect example of this, a feature that was first found on Mobile took over a year to appear on the desktop.
As it stands today, there's a lot of extra work and overhead that Microsoft needs to deal with every time it wants to build a version of Windows 10 for a new device type, such as foldables. Windows 10 as it exists on its own wouldn't be a good fit for foldable PCs. Microsoft could start building yet another version of Windows 10 for this category of devices, but then they'd have to rebuild many of the existing features you can find on other versions of Windows 10 already to ensure those features behave and operate correctly on this form factor. It's a waste of resources and effort.
That's where Windows Core OS comes in. With Windows Core OS, Microsoft is building a universal base for Windows that can be used across all these different devices. Instead of having to develop a new version of Windows 10 for every new device type that comes along, Microsoft can simply use Windows Core OS to start. They would then pull in features and functions it has already built for it, and create it as an OS for that device type. All that would be created with less overhead and fewer resources used.
Windows Core OS strips Windows down to the bare minimum. It doesn't include any legacy components or features, and sticks to UWP as a core for the operating system as it's lighter and already universal. From there, Microsoft can build out Windows Core OS with different components and features that it can then apply to devices where necessary. But this time, those components and features can be shared across the many different devices Windows Core OS will run on.
It's essentially a modular platform. Any feature or function Microsoft builds for it can then be applied to any Windows Core OS device that it wants. For example, let's imagine Microsoft builds out Win32 support as a component for Windows Core OS for desktop and laptop devices. Since that work has now already been done, Microsoft can also bring that Win32 component to HoloLens 2 or Surface Hub 2X running Windows Core OS, enabling that functionality on those experiences too.
The big selling point for Windows Core OS for Microsoft is that for the people working on Windows, it takes way less time and resources to build new Windows experiences when it's required. If Microsoft or any of its partners want to develop new device form factors running Windows, they no longer have to wait years for Microsoft to build up a version of Windows 10 that works for it. Using Windows Core OS, they can create new Windows experiences in a fraction of the time and way more efficiently.
The shared component idea extends to the UI as well, thanks to a universal shell Microsoft has been building called Composable Shell, also known as CShell for short. CShell is the other half of this universal idea for Windows Core OS, and allows Microsoft to build shell experiences that can be shared across devices, and even bundled up together where it makes sense. For example, any shell-facing feature like an Action Center, Start menu, or taskbar, can then be used across all CShell-powered devices without having to rewrite them to fit on different devices every single time.
Let's imagine Microsoft decides to finally build a Surface Phone running Windows Core OS. It'll feature a mobile experience primarily, but if you connected it to a Continuum dock, Microsoft could also bundle the actual desktop experience it built with CShell. So instead of getting a fake desktop experience as you did with Windows 10 Mobile, you'd boot into the real desktop experience Microsoft made for CShell, which runs on actual desktops. That's pretty cool.
93ddb68554