Solved Cannot Join Insider inside a W11 Hyper-V VM

cereberus · Feb 1, 2024

I have installed Windows 11 without any issue in a Hyper-V VM as I have done many times.
Logged in with MS account.

Secure boot on, tpm emulation on, 4 processor cores.

My laptop is fully W11 capable (11th gen processor - 500+gb spare space etc.

I go to join the insider programme, as I have done many times and I get this error message

I have never had this before - I cannot see any reason for it at all!
Looks like a bug to me!

EDIT: I attached vhdx file as native boot OS and was ablle to join as an Insider (Beta in this case).

Then when I opened vhdx file in Hyper-V, it worked fine as Beta Insider.

Bree · Feb 1, 2024

cereberus said:
I have never had this before - I cannot see any reason for it at all!

It may be the RAM, check that the VM has at least 4GB assigned.

cereberus · Feb 1, 2024

Bree said:
It may be the RAM, check that the VM has at least 4GB assigned.

Sorry forgot to mention that I assigned 6GB fixed as well.

What gets me is it installed W11 without any complaint.

If i change the no of cores, ram size, tpm, secure boot etc to not meet w11 requirements, I get the can't install message as expected.

Definitely something weird going on. I get the message before I even select the insider version, so its not version related.

It is not a major issue to native boot vhdx file and join from there but more faffing around (I also have to add nvme drivers to iso before I create vhdx file to native boot it).

Perhaps "they" really are out to get me - LOL.

Bree · Feb 1, 2024

cereberus said:
Perhaps "they" really are out to get me - LOL.

Well, I'm sorry but I can't test any of this for myself. I am not now nor have I ever been an Insider. All my insider machines got enrolled using the OfflineInsiderEnroll script

jimbo45 · Feb 2, 2024

Hi there
what was the reason for windows failing to install the insider version on Hyper-V.

TPM emulation , and sec boot all work properly. Is the Virtual CPU for the guest(s) failing because not supported. You may be able to fiddle around with the Host CPU topography in the VM definition if it's a CPU problem. Ram is fine - but is there sufficient disk space -- I know it's bonkers but to upgrade to a new build 40GB free must be available.

Another suggestion -- install the guest via dism /Apply-Image -- that seems to work on even quite limited hardware,

cheers
jimbo

spapakons · Feb 2, 2024

I don't know about Hyper-V, but in VMWare to install Windows 11 you must first encrypt the virtual machine. This will enable TPM 2.0 It is not enough to select TPM from the settings. I don't remember the exact process, but I remember mentioning to encrypt the virtual machine. Or you can just bypass compatibility check and force Windows 11 installation irrespective of the configuration.

cereberus · Feb 2, 2024

jimbo45 said:
Hi there
what was the reason for windows failing to install the insider version on Hyper-V.

TPM emulation , and sec boot all work properly. Is the Virtual CPU for the guest(s) failing because not supported. You may be able to fiddle around with the Host CPU topography in the VM definition if it's a CPU problem. Ram is fine - but is there sufficient disk space -- I know it's bonkers but to upgrade to a new build 40GB free must be available.

Another suggestion -- install the guest via dism /Apply-Image -- that seems to work on even quite limited hardware,

cheers
jimbo

Read my posts properly - there was no issue on installing standard Windows 11. The issue was joining the Insider Programme AFTER installation.

cereberus · Feb 2, 2024

spapakons said:
I don't know about Hyper-V, but in VMWare to install Windows 11 you must first encrypt the virtual machine. This will enable TPM 2.0 It is not enough to select TPM from the settings. I don't remember the exact process, but I remember mentioning to encrypt the virtual machine. Or you can just bypass compatibility check and force Windows 11 installation irrespective of the configuration.

Again - this is not my issue. As I stated clearly, I have installed W11 release version with no issue, but I cannot join the insider version afterwards.

spapakons · Feb 2, 2024

Windows Insider won't let you join if un unsupported computer is detected. So you must encrypt the virtual machine and do whatevr is required to make it Windows 11 compliant. So it is relevant to your issue.

Jabiru · Feb 2, 2024

I've installed Win 11 from the insider ISO onto a Hyper-V VM successfully several times. Here's the config I use....

Secure boot enabled
Template MS Windows
Enabled TPM Support
32GB RAM available
4 virtual CPUs
60GB of HD space available

Are you actually a registered member of the insider program? Is the image you are trying to use an activaed copy?

I believe you must download the Insider version from their website at: The Windows Insider Program

Check: Getting started with the Windows Insider Program

Jabiru

cereberus · Feb 2, 2024

spapakons said:
Windows Insider won't let you join if un unsupported computer is detected. So you must encrypt the virtual machine and do whatevr is required to make it Windows 11 compliant. So it is relevant to your issue.

but I could not have installed w11 if it was unsupported!!!!!

cereberus · Feb 2, 2024

Jabiru said:
I've installed Win 11 from the insider ISO onto a Hyper-V VM successfully several times. Here's the config I use....

Secure boot enabled
Template MS Windows
Enabled TPM Support
32GB RAM available
4 virtual CPUs
60GB of HD space available

Are you actually a registered member of the insider program? Is the image you are trying to use an activaed copy?

I believe you must download the Insider version from their website at: The Windows Insider Program

Check: Getting started with the Windows Insider Program

Jabiru

Will people blooming read my post properly - I clean installed Windows 11 RTM successfully in my VM so the VM is W11 compatible but it complains when I go to JOIN the Insider.

IT HAS NEVER done that before!

spapakons · Feb 2, 2024

The message in the photo is clear: "unsupported computer". Find out what settings you need to change to make it Windows 11 compliant. When nothing seems to work, back to the drawing board, meaning you have to delete this virtual machine and start over. You will spend less time starting over than trying to fix it.

Things to consider: GPT hard disk partition style, UEFI mode installation, Secure Boot enabled, TPM enabled and virtual machine encrypted, RAM allocated at least 4GB, CPU Intel 8th generation or higher or Ryzen 2nd generation or higher.

PS: Are you running the regular release of Windows 11 and you are trying to switch to an Insider's version? In this case you can download the Insider's version ISO from UPP Dump and then bypass compatibility check to manually upgrade to it.

cereberus · Feb 2, 2024

spapakons said:
The message in the photo is clear: "unsupported computer". Find out what settings you need to change to make it Windows 11 compliant. When nothing seems to work, back to the drawing board, meaning you have to delete this virtual machine and start over. You will spend less time starting over than trying to fix it.

Things to consider: GPT hard disk partition style, UEFI mode installation, Secure Boot enabled, TPM enabled and virtual machine encrypted, RAM allocated at least 4GB, CPU Intel 8th generation or higher or Ryzen 2nd generation or higher.

PS: Are you running the regular release of Windows 11 and you are trying to switch to an Insider's version? In this case you can download the Insider's version ISO from UPP Dump and then bypass compatibility check to manually upgrade to it.

Wrong - How many times do I have to explain situation. I really think you guys are not understanding what I am saying.

I can install release version in Hyper-V meeting all the requirements for Windows 11.

So it is complete bollards that when I try and join Insider it complains I do not meet Win 11 requirements when I have just met the requirements to install W11 in the first place.

How hard is it to understand this?

I know how to do all the ways to bypass it the checks but it is fecking stupid that it complains about joining Insider when release verion installs without any issues.

I sorted the issue in a few minutes by native booting from vhdx file, then joining Insider.

Tell me why trying to join the Insider Programme complains about not meeting W11 requirements when I have clearly met the W11 requirements to install W11 RTM in the first place.

There is clearly a bug - I do not need advice how to get around the issue - I sorted that in 10 minutes.

spapakons · Feb 3, 2024

Don't forget to report the bug from Feedback and to mark the thread solved.

cereberus · Feb 3, 2024

spapakons said:
Don't forget to report the bug from Feedback and to mark the thread solved.

I have reported it.

LesFerch · Apr 3, 2024

cereberus said:
but I could not have installed w11 if it was unsupported!!!!!

I have exactly the same issue with VMWare (Workstation Player 17). My computer meets Windows 11 requirements, but it won't let me join the VM to the Insider program.

Would it have killed them to display the specific deficiency that it thinks it's detected?

spapakons · Apr 4, 2024

What if you download the Insider's build you want from UPP Dump and manually upgrade? Maybe this will work.

jimbo45 · Apr 4, 2024

I have just installed the DEV version of W11 Enterprise on to a physical machine via WU, and had no problem with insider program. I then created a VM of the CANARY version of W11 PRO, No problem connecting that to the windows insider

So I have HOST with windows insider at DEV and the VM at CANARY.

Current HOST windows is

So I assume the problem is now fixed (at least on newer HOST builds).

OT - but it does seem that HYPER-V at least on Enterprise release works very well -- I'd still like a bit better dynamic USB re-direction -- compared with KVM/QEMU which makes it easy to dynamically attach and detach USB devices (any type) - so when using HYPER-V you need to know in advance (or at least before powering on the VM) what devices you want to have on it.

cheers
jimbo

SlicEnDicE · Apr 4, 2024

You people really have to learn how to read information or get better glasses.

I am sorry for your issues cereberus, I have not used Hyper-V in a while. I'll do that at some point...I'll let you know my findings once there...

My suspicion is that VMs are not allowed to join IP programme, because it produces false/irrelevant information for MS, so it is blocked. I could be wrong though...

One thing you could try though, is to enable nested virtualization for your Hyper-V machine...Virtualization support missing could be a showstopper...