I've noticed that the windows server kernel is faster then the regular one from Windows but I would rather not install the whole server OS just for that if I can avoid it. I've tried replacing the ntoskrnl.exe and disabling driver enforcement but it keeps blue screening so I was curious if someone had another method to accomplish this.
not kernel difference ! the faster performance are less service less application if you need low windows usage use ltsc 2021
Figure out how to activate Windows 11 Enterprise multi-session (formerly ServerRDSH) and it'll load the server kernel with all client features/software available. Among the other usual changes, that does mean you can use netsh to enable the alternate TCP congestion modes.
Enterprise Multi-Session (ServerRDSH) is treated as a Server SKU. Not the normal Enterprise, that is a Client one.
Interesting. So this is really server, despite the enterpise name? How does this differ from the workstation edition?
I activated it. How can I tell if it's using the server kernel? Also how can I enable the other nodes? Thanks in advance.
There is no difference, all Client and Server SKUs of the same branch use the same kernel. It's just licensing that differs.
Server kernel means very little (especially nowadays), it's mostly a value that informs installers about licensing What counts are the kernel policies enabled by a definite SKU Say RDSH advertises itself as server. But it has the maximum 20 smb connections like clients It has multi user support on RDP connections like servers And so on (it's a long string). Just check and compare yourself using the product policy editor/product policy viewer or similar utility
Interesting, after activating it, the SKU is blank so I have no way of knowing but I'll take your word for it. Also if the only thing special about this is the additional rdp sessions, why not just use anydesk or rdpwrap with a regular version?
Client SKUs are all consumer-oriented Editions like Home, Pro etc. On the ISO from MS, the only oddball is ServerRDSH, which is a Server SKU, license-wise. All others are Clients. There is only one kernel per branch. But, Server has fundamentally different product policies applied, which makes it behave differently. Speed differences might stem from kernel features that are inactive (or active) on Server vs. the Client OS.
In Very interesting, thanks for the info. Now the goal is to find out the different policies, so I can adjust them according on Client machines
You can't. Or, to say better, you can't fine tune the policies w/o loosing the activation. The policies are strictly regulated by the serial number and related certificates. BTW You can use my SKUwitch way to turn (almost) any windows in (almost) any windows, say you can have Win 11 LTSC, you can turn the clean Server 11 in win 11, you can turn almost anything in Hyper Core or Azure HCI (bot of them don't require activation), and so on.
Hey that's pretty cool! I'll have to check out that tool soon! I'm curious if it would work on Windows RT. Thanks very much for coding it. As for the activation, I just use hwid and it works.