Yeah. It was pointed out to me on another forum also, that the 21H2 version I downloaded may have been a preview release and some of those will install on non-complient hardware. I don't know how true that is.
Sorry I understand most of that. I was wondering about:
If I was starting from a blank disk how do I initialise the bootloader on the efi partition?
I was wondering about system backups because realising copying a vhdx file while in use probably wouldn't go too well, and not wanting to...
Can you explain this bit please? I'm still learning this stuff.
On a side note how do you backup your vhdx based systems? Just use a dedicated backup solution? Copy the vhdx file while off-line?
No, I'm not asking how to get it to install. I'm saying I can install using this "legit" iso into a gen 1 VM without any patching whatsoever and would like to know why?
Then I'm confused. I know about the workarounds and have tried some of the patching methods in VMware.
However this is an unpatched iso of 21H2 created from the uupdump site three days ago. I just installed it again in a new Gen 1 machine:
How is this possible then?
But was this possible only within a Hyper-V machine? Because I'm sure I couldn't get an earlier w11 iso to install in Vmware without enabling UEFI/TPM etc.
I've recently started using Hyper-V for running test environments after using VMware for years.
The other day I decided to try installing windows 11 on a VM. I created an iso of 21H2 (build 1042) using the uupdump.net site.
Being new to Hyper-V I created a Gen 1 machine. The W11 build installed...