The worst thing of all - NONE. All the buzz our new member creates of hotpatch costs nothing. He is happy to install "something" with "hotpatch" in name on Azure Stack HCI after some steps, but: 1) All the same steps can be done on any other Windows 24H2 SKU - server or client, - not just Azure Stack HCI - so that is NOT and update for hypervisor, targeted to patch VMs without reboots. Below I would show again that I can install it even on unactivated Evaluation Client SKU. So let us think it is a "hot" patch for VMs running on hotpatch-ready hypervisor? But: 2) Installation of this "hot" patch requires a reboot. No "hot" just "patch". 3) He invented few registry keys to install a patch,... that, wow, allowed to install strange Windows11.0-KB5039329-x64.cab. Great! But were that steps needed at all? Strange thing, installation of this patch on a clean installed Windows 11 system with LCU 26100.268 applied fail... one time, and succeeds if tried immediately after. Without any registry keys. On client! With a reboot: So what value is of Windows11.0-KB5039329-x64? As of now - none. This is not an update for Azure Stack HCI to host hotpatch VMs (as it installs on any OS) and it is not a "hot" patch as it requires a reboot. There is no point of discussing installation of Windows11.0-KB5039329-x64 without some new knowledge. Consider it a version of LCU 26100.793, strangely packed, untill we get some information on that.
Who is he and what registry keys are you talking about i do not know. This is not a windows pe. You will need to reboot/close your machine one time. Can not stay online forever
Sorry, if that wasn't clear. I was referring to the scripts that allowed "finally successful Azure Stack Hci with hot patch" by winosr25. That steps are NOT needed to install Windows11.0-KB5039329.msu All you need as prereq is 26100.268 (Windows11.0-KB5036908-x64.msu from WU/UUP or wim/psf from inside Windows11.0-KB5039329.msu) After that feel free to add Windows11.0-KB5039329-Hotpatch-x64.cab (from Windows11.0-KB5039329.msu) - it fails first time and succeeds second. On any 26100 OS. With a reboot, Not "HOT" and has nothing about "Azure Stack HCI". All other buzz on that CAB without some real samples of installing update without reboots is speculation with zero knowledge "I successfully installed Hot Patch for Azure Stack HCI", but not "hot" and can do same on Win11...
It is clear now. The registry key you are talking about is "importme.reg"? It is just for to enable explorer as gui. Not related with updates. I have not used it this time because i have full packages no need that. My dream was a hyperv server with gui. Maybe should try that too.
No, I mean the 3 registry keys, winosr25 recommends by powershell here to install KB5039329. (EnableVirtualizationBasedSecurity, HotPatchTableSize,Hotpatch Enrollment Package - have nothing to do with GUI) The last offical Hyper-V Server was 17763. xinso has provided us working script 17763.1_Hyper-V_Server_2019_Desktop_Experience that made it full UI. I have been using that for 1.5 years in production. Would love to see such a stable solution for HCI from him again. Master, please, please, please
Well, sure. As @alexiv notices, only some updates, which have "hotpatch" in name might not require reboot. Other LCUs are considered baseline and do reboot. As of now we can't install hotpatch without reboot. It is not hot.
I use Azure Stack HCI on physical hosts.. Enabling nested for client VMs on top of stack doesn't change anything.
There is no hotpatch registry key on server 26100.1 maybe later it comes after hotpatch update. Just install cab package and grab registry differences very easy. Registry keys will not be usefull to you also if it is successful as kibkalo said.