1. It's been working since 2019 up until the past month or so on KMS, 2. How to do HWID activation on a virtual machine?
First as I suggested many times, use Azure HCI, instead of rdsh. Its a way better SKU practically on everything. Second, looks like MS updated their RDSH certs, just replace them with original ones and activation will be OK
Thank you! Are certificates fixed only in 22H2 or in 21H2 too? When I clean installed 22H2, I found that ServerRdsh activated without issue with the original SKUs.
I have no idea, I just tested the ones on Win10 (which suffers the same loss of activation, after being updated
22621 activates fine: https://forums.mydigitallife.net/th...activation-script.79535/page-244#post-1740930
Depends on your definition of fine. Mine is offline permanent activation, w/o any kms emulator/massgravel/whatever
when its activated, how many connections will it allow ? Also is there a tutorial how to do Azure Stack HCI ?
#1 Go to the uupdump website and create the download stipt for W11 Professional, no additional images, no updates, whatever) #2 download the script and edit convertconfig.ini [Store_Apps] SkipApps = 1 #3 Create the image (you can skip the ISO creation), deploy the image with dism/imagex or (better for newbies winntsetup.exe), in a vhdx(*) You can use a real partition but a vhdx is way more practical and flexible. #4 until the vhdx is still mounted change the edition to ServerRDSH (using dism /set-edition) #5 unmount the vhdx and boot it in Hyper-V, you will get the old school OOBE, set keyboard/location and whatever to your liking, after that the system will reboot and will go straight to the desktop (user administrator, no password) That is. Create a new user (with admin rights!!!) using lusrmgr.msc, create a password for administrator, and possibly disable the the administrator user after logging in with the new user. No appx will be downloaded!!!, your Win 11 will be as clean as a Server or LTSC with zero hassle and a huge amount of spared time). If you need to, you can now switch the edition back to Pro (or Enterprise or whatever you like) using slmgr /ipk <serial-of-the-SKU-you-need> Depending on what you need to do leave it as a Hyper-V machine, or add it to your bootloader to boot it natively. (*) If you want to boot the vhdx natively is better that you set HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\FsDepends\Parameters\VirtualDiskExpandOnMount to 4 before the first boot, otherwise your vhd will be expanded to its maximum size on boot P.S. to be clear this works on any machine, no matter if the requirements are met or not