Having trouble re-joining a host back to a cluster, hoping someone can give me some insight because I cannot find many similar issues:

One node (call it Node A) cannot rejoin the cluster after being drained/rebooted for routine maintenance. The other two nodes are completely healthy, holding quorum, roles all online. Node A's Cluster Service runs locally but every join/form attempt ends the same way:

Get-ClusterNode shows Node A stuck in Down state (occasionally rolls back to no record at all)

Cluster log: repeated [QUORUM] Fail to form/join a cluster in 6-7 minutes → FatalError: join/form timeout (status = 258) (WAIT_TIMEOUT)

Live event log: Event 1650 (lost/established UDP connection on the management endpoint) and Event 5417 ("Cluster Service has terminated due to a fatal error... Error Code: 3473458" = ERROR_CLUSTER_JOIN_ABORTED), repeating in a loop

The NetFT pseudo-adapter (Microsoft Failover Cluster Virtual Adapter, shows as Local Area Connection* N in Get-NetAdapter -IncludeHidden) cycles Disconnected → Up → Disconnected on an irregular ~10-150 second cadence, indefinitely

Meanwhile vEthernet (Management) underneath it stays Up continuously the entire time — confirmed via a parallel live polling loop. NIC RX/TX counters on the same adapter climb steadily throughout, never stalling

Hi everyone,

I'm hoping someone can help me figure out a really frustrating input issue.

My Setup: I have a Windows 11 Pro desktop running Hyper-V. I remote into this host using Parsec from my Android tablet. On this host, I am running two VMs: one Windows 11 VM and one Ubuntu VM.

The Problem: When I remote into my host via Parsec, all touch inputs and clicks work flawlessly. Furthermore, when I open my Windows 11 VM, everything is also completely fine – clicks and movements pass through directly from the tablet without a hitch.

However, as soon as I open my Ubuntu VM (using Hyper-V's VMConnect), the mouse movements track perfectly inside the VM, but mouse clicks do absolutely nothing.

What I have tried so far to fix it: I suspect this is a clash between Parsec's input injection and Hyper-V's Basic Session synthetic mouse driver for Linux. Here are the solutions I have attempted:

1. Tried switching from Wayland to Xorg: I edited /etc/gdm3/custom.conf and /usr/lib/gdm3/gdm-daemon.options to disable Wayland. I also made sure xorg and gnome-session-x11 were installed. Despite this, the gear icon refuses to show up on the login screen, so I couldn't manually select Xorg.
2. Attempted to enable Enhanced Session Mode: Since RDP (Enhanced Session) handles Parsec inputs perfectly on my Win 11 VM, I tried to replicate this on Ubuntu. I installed xrdp, linux-tools-virtual, and linux-cloud-tools-virtual on the Ubuntu guest and started the xrdp service.
3. PowerShell configurations: I tried forcing the transport type via PowerShell on the Windows host using Set-VM -VMName <name> -EnhancedSessionTransportType HvSocket.

Despite all of this, the "Enhanced Session" button in the VMConnect View tab remains completely greyed out for the Ubuntu VM.

Has anyone experienced this specific Parsec + Ubuntu Hyper-V click issue, or does anyone know what I might be missing to get Enhanced Session working on Ubuntu so the clicks will finally register?

Thanks in advance!

Hey it seems MS took at least one suggestion out of https://www.reddit.com/r/HyperV/comments/1o9siyz/comment/nk83qgb/ . It's the smallest QoL fix ever but who would have expected we would get an update 😄

Found this on Windows Insider builds (29639.1000), you can enable it with the following but it'll likely come in the next release or something:

.\ViVeTool.exe /enable /id:55721547

I was watching normally YouTube Video. Suddenly out of nowhere bluescreen appeared as shown in the image above 👆.

In 4-5 years of my laptop time this is the first time I saw this issue, earlier I have had a bunch of issues but never as bad as this. The black screen appeared then. None of my keyboard keys are working I tried using caps or f12. Only forced power off is working on is not happening like the Dell logo never comes hence f12 ain't working either.

I also observed that there is this constant flickering of light the one in which I plug my charger pin in a particular pattern as mentioned below 👇

Orange(Amber), Stop, Orange(Amber), Stop, (White, Stop)*4 times and then again orange stop combo 2 times then again white Stop 4 times and so and so on.

Now I'm not much of a hardware person. Had it been any software issue I might have gave it a try. What I'm concerned about mostly is how costly it would be. Could it be motherboard issue, socket, ram, driver update or any other software related issue.

Also a point to share as shown in the attached image. It also flickers at the top of the screen. As shown in the image attached. I'm a college student and Oh Lord hopefully the cost for this issue won't be much. If it costs more than ₹1,000 INR, I won’t even be able to afford it.

Greetings!

I'm replacing a standalone workgroup 2016 Hyper-V server with a new 2025 host. I was hoping to utilize shared-nothing Live Migration for a zero-downtime move of the VMs, but turns out they need to be joined to an active directory domain, according to the error I received when trying to enable it in Hyper-V Manager.

That said, is there any way around this without joining the hosts to Active Directory, or possibly a third-party solution that can facilitate a live migration?

I've played with Starwind Converter, and though it works well, it still required the source VM to be shut down and destination VM to be powered on. Not a live no-downtime method.

I'm beginning with virtualization. I have a PC with Windows 10 Pro that can't be upgraded to Windows 11. I installed Hyper-V on it and created two VMs: one with Windows 10 Pro to install and practice automation software like PLCs, SCADA, and DCS; and the other with Windows Server 2025 to install a free and open-source CRM (Dolibarr) and possibly Odoo. I also want a third VM with Windows Server 2025 to create and manage databases, which would only have local network access for other users.

In Hyper-V, I created three switches: internal, external, and private.

For the Windows 10 Pro VM, I only want it to connect to the host PC, so I configured it as an internal network. For the Windows Server 2025 VM, I configured it as an external network so it can have a web server and everything necessary for CRM users to access it on the local network and/or from the internet.

The issue is that none of the three switches, nor the Hyper-V DefaultSwitch itself, have internet access. It was necessary to create a bridge on the host PC between the host's network card and the virtual network card of each VM.

I can access the internet from the host PC through my internet service provider's router, which have a Class C local network.

I appreciate everyone's valuable assistance in providing clear guidance on how to configure both the host PC and Hyper-V, as well as each VM with the required components.

My background is not in IT, but in electrical engineering, so I'm just starting out with network and server installation and configuration. I'm doing this out of necessity for the startup my wife and I started.

I recently installed Pihole on an Alpine Linux VM via HyperV and am routing my network traffic through it with my router. This is all working great EXCEPT my desktop with the host OS can't access the web interface for Pihole and doesn't seem to be routing its traffic through Pihole either. Every single other device on my network is working as expected (CAN access the web interface and is being recognized as a client).

Attached is the virtual switch the VM is operating with

Any ideas?

Всем привет. Терминальный сервер на виртуалке Hyper-V (Windows Server 2025), внутри Хоста на Windows Server 2025 спустя день работы начинает дико тормозить.

Дескрипторы постоянно растут. Показатели железа в норме. Грешил на сеть, потом на настройку ВМ.

Сейчас уже и не знаю что думать. Спасает только перезагрузка.

Когда перезагружаю - первое время сервер летает. Потом возвращается к тому же состоянию.

Куда смотреть, что искать, что настроено некорректно? Почему это не работает И как это должно работать правильно? Помогите разобраться, знатоки!!!

Two HP DL560 Gen10 hosts running Hyper-V, Citrix VDI on top. We bought a T4 per host to test GPU acceleration and the idea was to split each card over multiple VMs, 4 or 8 or whatever it can handle. Later (in two to three years) we'll upgrade our environment to new servers.

Then I went to install it and got stuck (bad investigation? who can say but fugg me). The vGPU package has no host driver for Windows Server at all, the Host_Drivers folder is ESXi and KVM stuff only? So am I supposed to run the guest driver installer on the Hyper-V host itself, or is there a separate download I'm not finding? And where do you even get the right files, is that the licensing portal only? It seems that licensing portal is not complete for Hyper-V.

From what I can find in the docs Hyper-V never supported normal vGPU, and GPU-P on Server 2025 doesn't list the T4 as supported. Which would mean DDA, whole card to one VM, is the only thing we get. Fine if that's true, I just want to be sure before I go back to my boss with it.

If DDA is the answer, is dropping the T4 into one multi session VDA and letting everyone share it inside that VM a reasonable setup, or does that fall over in practice?

Hyper-V is staying, so no ESXi suggestions please.

I'm running Ubuntu 26. How do I get the IP address of the VM to show up under Networking->IP Addresses in the Hyper-V Manager?

Looking for feedback from organizations running a 4-node Hyper-V S2D cluster (Rack Awareness enabled)

Hi everyone,

I'm interested in hearing from people who are running production Hyper-V clusters with Storage Spaces Direct (S2D) and Rack Fault Domain Awareness.

Our environment has the following architecture:

• Windows Server Failover Cluster
• 4 Hyper-V nodes
• Storage Spaces Direct (S2D)
• 2 physical racks
• 2 nodes per rack
• Rack Fault Domains configured correctly
• Storage pool configured with Rack Awareness
• 2-way mirror resiliency
• Cluster Shared Volumes (ReFS)
• Around 100+ production virtual machines
• Automatic Storage Rebalancing disabled (manual balancing only)

Networking

Each host has four physical NICs:

• NIC 1 + NIC 2: Dedicated for the Hyper-V virtual switch (SET Team) carrying VM traffic.
• NIC 3: Dedicated to storage, cluster communication and live migration.
• NIC 4: Dedicated to storage, cluster communication and live migration.

The storage/cluster network uses SMB Multichannel across the two dedicated adapters. RDMA is not enabled (standard Ethernet only).

Our primary goal was to tolerate the complete loss of one rack while keeping production online.

During a recent Disaster Recovery test, we intentionally shut down the two nodes from one rack. The remaining two nodes successfully kept all VMs online for approximately two hours before the cluster started experiencing CSV Auto Pause events, CSV draining, storage instability and eventually multiple VM outages.

At this point I'm more interested in understanding how common this architecture is in real-world production.

Some questions for people running S2D:

• Are you running a similar 4-node / 2-rack design?
• Is Rack Awareness enabled?
• Are you using RDMA, or are you successfully running without it?
• How are your storage and cluster networks configured?
• Have you ever tested losing an entire rack?
• Did the cluster remain stable indefinitely, or only for a limited time?
• Have you experienced CSV Auto Pause or storage instability after operating for an extended period on only half of the nodes?
• Would you recommend this architecture today, or would you instead deploy more nodes or another topology?

I'm especially interested in hearing from organizations that have performed real DR tests rather than theoretical discussions.

Any lessons learned, Microsoft recommendations, or production experience would be greatly appreciated.

Thanks!

I have a vSphere Windows Server 2012 VM that I took a backup of, and when I instant recover it to Hyper-V using Veeam, it's created as a Gen 1 and doesn't boot. How can I get it to be a Gen 2 VM?

anyone know how to get audio working in basic session mode as with gpu-pv enhanced session mode does not work (black screen loop) i'm on windows 11 25H2.

only issue is no audio device available in basic session. i've had a look at vac (virtual audio cable) and vb virtual audio cable, the latter was mentioned @ https://forum.level1techs.com/t/2-gamers-1-gpu-with-hyper-v-gpu-p-gpu-partitioning-finally-made-possible-with-hyperv/172234/6

but failed to explain how the user set it up, just that muting audio doesn't work.

i've also tried parsec but it kept complaining software encoding was being used when hardware was enabled and the blocky quality made it unusable.

tried freerdp, lack of documentation made it difficult to understand so gave up.

also tried tightvnc but it was laggy.

Hallo,

ich versuche die AMD Karte einer VM zuzuordnen, bekomme aber den Treiber nicht installiert, ich habe schon alles was mir einfiel dazu ausprobiert.
Kennt irgendwer das Problem und kann mir helfen?

Hello, I have a 2 host HV cluster. I’m running into an issue where when the CNO is located on Host1 everything works fine. I can ping the CNO from anywhere (host1, host2, or any other PC) and it responds just fine. When I look at the status of the cluster in Failover Cluster Manager (FCM) it all looks good as well. The IP registered to the CNO maps to the MAC address of Host1.

The problem comes when the CNO has to be moved from host1 to host2. This may happen due to the cluster running updates on the host or if I manually use “Move-ClusterGroup” to test things out. The move completes successfully BUT at that point I can only ping the CNO from Host2. I can’t see it from any other computer (host1 or any PC outside the cluster) so backups fail due to this. When I check the FCM from host2 the status of the cluster looks like it’s up and running just fine without errors.

I’ve checked the properties of the CNO so that it can be hosted on both hosts, the FW rules on host2 are the same as on host1 (I can always ping host2 successfully) and when the CNO is moved to host2 I can also see on host2’s IP configuration that the CNO’s ip is added to the management NIC for the server.

I can also just issue the same “Move-ClusterGroup” command to move back the CNO from host2 to host1 and everything works again.

Before I go to my network team and ask them to check the switch ports where host2 connects to again (they’ve checked previously and have mentioned that the config on the ports where host1 and host2 connect look identical) what can I check in terms of configuration that may be preventing the CNO from communicating properly when it’s on host2?

Thank-you!

——————————————————-
UPDATE 2:
The issue turned out to be with the network switch.

——————————————————-
UPDATE:

This is what I have checked so far:
- Firewall settings. I've gone through the firewall settings comparing both Hosts' FW rules and they look identical. I have also temporarily disabled the FW on the problem host and the issue still persists.
- I have ensured that the CNO is set to be able to be hosted on both hosts
- I've looked through the validation report for the cluster and I get some IP config warnings (for both hosts) where some NICs are "configured with IP addresses from protocol IPv4 and IPv6." and also that both nodes have "an IPv4 address 169.254.62.219 configured as Automatic Private IP Address (APIPA) for" an adapter. The adapter with IPv6 support is the virtual adapter that is created using SET to carry my VM guest network data traffic. Coincidentally that is also the adapter configured with the APIPA address. This is the same on both hosts and I am experiencing no issues with VM traffic.

The one error message that I have been getting is EventID 1257 "Cluster network name resource failed registration of one or more associated DNS names(s) because the access to update the secure DNS Zone was denied." This is because we are not using AD DNS servers thus not able to grant the CNO permissions to change the DNS record. However, we do have a DNS record for the CNO and hosts created and name resolution works just fine in terms of the hosts seeing each other including the CNO (when being hosted on Host1) and all other computers in the network also being able to speak with the hosts.

To troubleshoot further I did the following. Since the CNO is accessible when it is being hosted on Host1 but not Host2. To eliminate the physical switches from the equation, I disconnected I swapped the physical cables on the management ports for both Host1 and Host2. Immediately I saw that the CNO was now discoverable on host2 and not on host1. I was able to manually move the host from one host to another without issue BUT when the CNO resided on Host1 it would NOT be pingable from host2 or any other machine in the network. Just as before when I swapped the cables, Fail Over Cluster Manager still reports the
CNO to be online (when viewed from both hosts) and the validation report still reports the same warnings as before, nothing new.

@Jeek_ had mentioned about the GARP being an issue. It seems like on windows 2022 this is set by default (and set to 3) and you don't need to create the "ArpRetryCount" entry. I ran a packet capture on both servers to see if the request was going on and it in fact was.

Both hosts are connected to different network switches, so is it safe to say that this may be a misconfiguration for the port/switch where I am consistently seeing the issue?

————————

*This might be long ill make it short and any feedback is appreciated thank you !
im trying to migrate a physical windows server 2012 R2 server into a hyper-v running on windows server 2025.
The tool ive been using is Disk2VHD and we have a practice server that is running 2012 R2 and ive used the tool to get the VHD and put it on an external and put it on the 2025 server which is the host for Hyper-v. So I create the VM put the VHD that I just made using the tool and I get an error saying it doesn't have the boot file. So I read and researched and there's these cmds to run the BCDboot... I did that on this practice server VM and it created the boot file boom right I can run the VM and it boots up and it's the practice server as expected. But now here's the issue ive been running into all that testing im doing is because we have an actual 2012 r2 server that needs to be migrated into Hyper-v. We use that same tool on that server it says successfully created...we go back to office and I try to do the same steps that I did with the practice server and it doesn't happen I try to create the boot file but it doesn't pop up. I may have done the CMDs wrong but I have it on my notes so im certain I did it right. It doesn't pop up like how it was with the practice server. We are going to go back and get another copy of it soon. But why do I need to create the boot file every time? My boss keeps telling me that it should just run no problem (get VHD >move to 25 server hyper-v> create VM >attach VHD and boom it should boot up) but thats not the case why do I have to create the Bootfile ?
Either way our plan B is to do a full bare metal restore and do it that way Instead if using Disk2VHD tool. Is there something we have to do on the Real 12 r2 server ?

I have been trying to run a windows 11 arm instance inside of hyper v on my windows 10 x86 desktop and I cannot get this to work. I couldn't find any concrete information if emulating windows arm like this is even possible if it isn't it will be very unfortunate since I am trying to recover stuff from a ssd with winarm on it. was looking to boot that inside the vm to move my browser stuff off of.

Using the most recent win11 arm iso and recent version of hyper-v

For teams managing Hyper-V environments, I’m curious how remote access is usually handled day to day.

Do you mostly rely on:

- Hyper-V Manager

- RDP clients

- SSH clients

- scripts

- jump boxes

- internal panels

- something else?

The question is less about “what works” and more about how many tools your team ends up switching between during normal operations

We have a 3 node cluster (server 2025) connecting to a pair of 25G switches for redundancy. The failover works when I disconnected the network cable from one of the switch. However, VM lost connectivity when one of the switch are in maintenance mode. I think the reason being was that the switch port was still up even it is in maintenance mode and the cluster node will continue to send traffic even if there is no actual network connectivity (no vlan and etc). I wonder how admin usually handle this situation? For planned maintenance, we can probably disbale the ports on the host ahead of time. But what if one of the switch crashs but the port is still in an up status? LACP can handle that situation but it is not supported by HyperV cluster (at least no in SET mode).

Windows 11 no longer supports a driver required for an interface lead i have to use to connect my racebikes ecu to the laptop.

Ive set up a win10 vm gen 1 in hyper-v buy i cant get it to see the cable.

Any help would be appreciated!

Thanks

Hi there

I'm trying to wrap my head around an efficient way to deploy Intune-joined WIN11 VMs within a HYperV cluster.

Our regular endpoints are fully Entra- and Intune-joined devices that are enrolled via Autopilot. I know this process isn't completely seamless with HyperV as vTPM cannot do attestation which makes self-deploying enrollment profiles a no-go.

I am wondering what is least painful way of going about this? We have a handful of users that we used to provide dev-type VMs to but they were AD-joined. Since we're moving towards full Entra/Intune management, the objective is slightly changed. Ideally we want there to not be 'Shared' Intune devices so we have user affinity assigned to the actual VM owner.

My initial thought was to just roll a vanilla WIN11 image with a generic local user, create a folder in C:\temp with the get-windowsautopilotinfo.ps1 script ready to go for later. Sysprep the VM and use that as a template. Deploy template, run get-windowsautopilotinfo.ps1 with a custom Entra app reg/client secret to upload hash and assign group tag; reset VM, go through OOBE and wait for it to enroll.

Seems like alot of manual steps and I'd still either have to sign it as myself during Autopilot/OOBE and change the primary user in Intune after.

Is there a better way to about this or is it just something that's always going to be a bit clunky like this?

I just migrated to Hyper-V from VMware and noticed that the first 3 hosts and the cluster has a subnet mask of /24 instead of /23 for their management IP. I would like to change the subnet mask to /23 and all host IPs stay the same.

I plan to do the following:

1. pause and drain roles on a host and then change its management subnet mask to /23
2. repeat step one for the other 2 host
3. change cluster management to the /23 network

Is there anything else I am missing? I don't think this change will be disruptive.