(It looks like the one I mentioned. Never mind.) As for Updates. you may need Wuyouzi067's MSU_to_esd_and_Modded_CU_202311242121.7z Good luck.
Did you check the script so quickly? Sorry, I was expecting the answer tomorrow. Thanks for taking the time to check the script, and I do believe I have Wuyouzi067's script at hand Just as a last question, is this frankenbuild script reliable? Just to be sure that there will be no instability or errors due to missing files.
You try it firstly and feedback if necessary. It's really old, I can't refresh my memory. Sorry. I recommend that you do it and try to trouble-shoot errors by yourself. Perhaps hassle, but you can get "independent" sooner. Once you can make it, you can apply it to any other builds. Then you can say: I did it my way. Happy. Then? Migrate it to xinso's 25398.1 script.
Microsoft-Windows-EditionSpecific-EnterpriseS-Package-amd64-10.0.22000.1.cab by @gailium119 https://forums.mydigitallife.net/th...struction-project.80939/page-368#post-1729535
Nice! xinso, the newly reconstructed AzureStackHCI updates from WU without problems and no flashes in menu? Would you show the list of packages? /get-packages for 26100.1?
Have you read the notes? Hotpatch is just an MSU, you can install it, but unless cluster is managed by Arc with Azure benefit, there would be a reboot after LCUs. Seems you just post attempts to do something without any checks )
scripts local -------------------1----------------------- $registryPath = "HKLM:\SYSTEM\CurrentControlSet\Control\DeviceGuard" $parameters = $parameters = @{ Path = $registryPath Name = "EnableVirtualizationBasedSecurity" Value = "0x1" Force = $True PropertyType = "DWORD" } New-ItemProperty @parameters ---------------------------------2---------------------------- $registryPath = "HKLM:\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management" $parameters = $parameters = @{ Path = $registryPath Name = "HotPatchTableSize" Value = "0x1000" Force = $True PropertyType = "DWORD" } New-ItemProperty @parameters -------------------------------------------3------------------------------------- $registryPath = "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Update\TargetingInfo\DynamicInstalled\Hotpatch.amd64" $nameParameters = $parameters = @{ Path = $registryPath Name = "Name" Value = "Hotpatch Enrollment Package" Force = $True } $versionParameters = $parameters = @{ Path = $registryPath Name = "Version" Value = "10.0.26100.793" Force = $True } New-Item $registryPath -Force New-ItemProperty @nameParameters New-ItemProperty @versionParameters ----------------------------------------------------------4---------------------------------------------- Dism /english /online /Add-Package /PackagePath:\Windows11.0-KB5039329-x64.msu /ScratchDir:e:\tmp
Have you been able to HOT PATCH OS? Not install the update, but install LCU on OS with HotPatch without a reboot requirement? On you screenshots we see ask for a reboot after hotfix install. That IS NOT a hotpatched system behavior. You just install something to some OS without understanding what is it and pretend that it works without testing HotPatch functionality. Right? Right!