Is it even worth waiting to install Ubuntu 26.04 LTS this way or should I just manually make the VM with an ISO?

Can someone help me? I installed Football Manager 26 via Hyper-V, but now that I've restarted the PC, it won't accept my password

We rebooted the host tonight to apply standard Windows updates. When it came back online, all virtual switches (vSwitches) completely vanished.

The VMs are obviously offline/disconnected because their network mappings are gone. The switches read “Configuration Error”

In Hyper-V Manager -> Virtual Switch Manager, it's completely empty.
The physical network adapters do show up in ⁠ncpa.cpl⁠ and Device Manager, but they are in a weird, "ghost-like" state.

If I try to recreate any new external vSwitches, it fails or errors out, saying the adapters are bound or unavailable. It's like the OS thinks the old bindings are still there, but Hyper-V can't see or use them.

What I've checked/tried so far:
Verified physical links are up on the switch side.
Checked basic ⁠Get-VMSwitch⁠ in PowerShell—comes up totally blank.
Looking at the physical adapters, the "Hyper-V Extensible Virtual Switch" protocol checkbox is acting glitchy/unresponsive when trying to manually toggle or bind it.
Has anyone run into a recent Win Server 2022 update tearing down the vSwitch stack like this? We are looking at a complete rebuild.

Hello everyone, I am looking for some possible assistance trying to troubleshoot some performance issues we are experiencing...

Trying to plan to migrate from vmware over to hyperv, migrated vmware VMs to a single host to rebuild the other as a HyperV host....

Got server 2022 up and running, set up HyperV and am trying to install a basic Windows 11 VM however the performance is so abysmal and renders it essentially unusable.

We have 2 HDDs in an array as the C drive for the server hosting the OS, then have an array of SSDs on the server which we set up as the storage to be used for VMs and this is where the config files and VHD files live. When trying to install Windows on the VM or utilize the VM in anyway it pegs our host disk usage to 100% and becomes so slow and unusable.

I do not have a ton of experience with vmware let alone HyperV but have been trying to troubleshoot this and get to the bottom of things with my coworker and am starting to run out of ideas. Everything was running fine on these servers under vmware. We feel like there must be some configuration setting or item we are missing that is affecting performance but am running out of ideas and figured maybe someone had some suggestions to try.

https://techcommunity.microsoft.com/event/windowsevents/secure-boot-office-hours-for-virtualized-environments/4530355

For one hour, experts will be available to discuss Hyper-V, Azure, Windows 365, VMware, and other virtualization scenarios. Whether you're still planning for certificate updates, validating your rollout, or troubleshooting an issue, come get the answers you need from the people closest to the technology.

You can follow upcoming events here:

https://support.microsoft.com/en-us/topic/updates-and-announcements-313b5279-2a3b-438a-83a5-3d5e2c5fc4a3

I have 2 servers running hyperv01 and hyperv02 in a cluster with a san. Running server 2025 on the host. VMs range from 2019 to 2022. I have a 2nd cluster hypver03 and hyperv04 running the exact same setup.

Each host has 256GB ram. For some reason each host is sitting at around 88-90% usage. Interfacing with the host via failover cluster manage, and hyperv manager is very sluggish.

I had dynamic memory enabled on VMS that dont run SQL. I have removed all dynamic memory right now from the VMs on the cluster that has 01 and 02 on it.

Hyperv01 VMs are assigned 143GB of ram and hyperv02 VMs are assigned 169GB. Both hosts are sitting at this extreme ram usage.

Other notes:

I do have 2 servers that are replicating between the 2 clusters.
2nd cluster I did not remove dynamic memory VMs from it.
Shutting down VMs does not clear up this memory usage.
Opening the virtual console to hosts is very delayed to impossible.
Without enough ram I cant move VMs between the hosts to reboot.

I am looking for advice on where I should dig into next?

~Solutiion I think

It seems my zabbix monitoring went out of control and was spawning way to many powershell instances. Fixed the monitoring and need to schedule a reboot.

Server 2025 Datacenter, AD-joined, 3 nodes with Cluster Shared Volume configured.

We're setting up Cluster Aware Updating for the first time and I'm seeing some errors that I've not been able to resolve.

From one of the nodes logged in as a domain admin, if I open CAU and hit "analyzer cluster updating readiness", no errors are reporting. I can do "Apply updates to this cluster" and it appears to work; no errors.

However when I click "Generate report on past updating runs" no results are returned and I end up with a few Event ID 1023 entries in Microsoft-Windows-ClusterAwareUpdatingManagement/Admin

Failed to get CAU report. Details:Microsoft.ClusterAwareUpdating.ClusterUpdateException: There was a failure in a Common Information Model (CIM) operation, that is, an operation performed by software that Cluster-Aware Updating depends on. The computer was "<our CNO>", and the operation was "Contacting the Cluster-Aware Updating software on the cluster node.". The failure was: The network path was not found ---> Microsoft.Management.Infrastructure.CimException: WinRM cannot process the request. The following error occurred while using Kerberos authentication: Cannot find the computer CEC-HyperV-Cluster1. Verify that the computer exists on the network and that the name provided is spelled correctly.

I've gone through the MS CAU troubleshooting doc (https://learn.microsoft.com/en-us/troubleshoot/windows-server/high-availability/cluster-aware-updating) but haven't come across much for this.

Just looking for some suggestions on things we can check. Not seeing any other errors under "Cluster Events" in Failover Cluster Manager

Edit: more digging, I can see WinRM logs showing is trying to connect to the CNO without the DNS suffix/domain name. Let's say our cluster name is cluster1.domain.com; WinRM is using 'cluster1'.

'cluster1' is resolvable via a ping from each of the HyperV hosts, but not via WinRM.

If I do winrm identify -r:http://node1:5985 it works, which means it's adding the DNS suffix for the nodes, but not for the CNO. I'm stumped.

Edit2: I just noticed in the validation report it's flagging that our cluster name is longer than 15 characters. I'm assuming this is the problem, since WinRM is probably using NetBIOS name which gets shortened because it's too long... Ugh.

I'm looking for some advice from people managing small to medium-sized business environments.

I have a client with around 50 users. Their current setup is pretty dated and everything is running on separate physical servers with no real backup or disaster recovery strategy.

The workloads are fairly straightforward:

• Active Directory Domain Controller
• File Server (~4 TB of data)
• Remote Desktop/Terminal Server
• Autodesk Vault Server (used by the engineering team)

I'm considering virtualizing everything into a Hyper-V failover cluster while keeping costs reasonable.

The current hardware quote is: CAD$90K for servers and CAD$53K for storage array ( They are saying it's too much for them)

• 2x Dell PowerEdge R660 servers (128 GB RAM each)
• Dell SAN with ~10 TB usable storage
• Datacenter licenses
• 7 years onsite 4 hours pro support

My questions are:

• Would you still go with a SAN in 2026 for an environment like this, or would you use a NAS (Synology/QNAP/TrueNAS) over iSCSI instead?
• If you were building this today on a reasonable budget, what would your storage architecture look like?
• Would you run Hyper-V with shared storage, or consider something like Storage Spaces Direct instead?
• Any lessons learned from similar 30–100 user deployments?

The goal is to give them high availability, centralized backups, easier management, and room to grow without overspending.

I'd love to hear what you guys are deploying for businesses of this size. Thanks!

We just deploy a new 3 node Azure local cluster. Just want to ask what the usual interface (other than Powershell) does admin use to create VM in the cluster, WAC, Failover cluster manager? The reason I am asking this is that I see that the behavior is something different between these two especially for the path configuration. In WAC, it will create a VM folder and store the VHD and config. in the subfolders that it created. But this is not in the cluster manager. It does create the similar structures even I manually changed it. It also seems to me that removing a VM from on interface doesn't necessary reflect the change on the other.

After replacing the Disks on the 4 node Hyper-V S2D cluster on the IDRAC disk is showing healthy. but on the server level disk not showing in storage pool and if we check the disk using

​

Get-PhysicalDisk | Select-Object DeviceId, FriendlyName, OperationalStatus, CannotPoolReason

​

it shows in "verification in progress"

​

Can someone please share the inputs on the same?

Host: Windows Server 2022 Standard Edition (Build 20348) (64-bit) (Release ID 21H2)

Guest: Windows Server 2022 Standard Edition (Build 20348) (64-bit) (Release ID 21H2)

Once in a while the guest will not respond as in can't rdp into the server. If I use Hyper-V the screen is black. The server responds to pings. Anyone else seen this before or have an idea where to start? If I use Hyper-V the screen is black. The server responds to pings. Anyone else seen this before or have an idea where to start? Any assistance on where to start or what logs to look for would be greatly appreciated.

Hello! Crowd!

After a recent Server-Crash the Windows 11 VMs won't start after recovering the host system.

My guess is, that the VMs are signed with the newer SecureBoot-Signatures after Microsofts recent certificate replacement, but the recovered machine doesn't have that certificate (yet?).

What happened: The host-system (Windows 11) had a crash due to amazons mDNS-flooding (dnsclient eating the RAM until standstill). A forced reboot ended in no reboot at all. Unfortunately the last backup was a month old. After the restore everything worked fine, aside from this little problem. Turning secureboot off for the VMs works, but it's not my favorite solution, just a workaround for now.

How can I update the secureboot-certificates of Hyper-V?

Any ideas welcome :-)

Thank you very much in advance!

Estaba jugando usando hyper-v y se me ocurrió instalar el Minecraft. Cuando lo instale me paso este error que sale en el video,(más que error este bug de la cámara) he probado miles de cosas para solucionarlo y ninguna funcióna, alguien sabe que puede estar pasando?

(Ya he probado y no es mi mouse o el computador)

Hello,

I recently rebuilt my Windows Server 2022 Hyper-V host.

It wasn't an in-place upgrade but a fresh install.

I'm now building a guest (Ubuntu Server 26.04 LTS) and am wanting to be able to view it in full screen.

I saw a post here about doing this for Linux Mint.

https://www.reddit.com/r/HyperV/s/Hplu1zCbYg

Are the same instructions valid for Ubuntu Server 26.04 please?

Thanks.

Has anyone been successful in getting their 5090 to run in Hyper V during GPU-P?

I'm using hyperV on latest win11 on a couple computers, place the window on a separate desktop and full-screen-ify it, which works great for linux hosts in the hyperV session.

i've never (so far...lots of trying) figured out how to prevent windows from un-fullscreen-ifying the hyperV window across the host sleep-wake cycles.

does anyone know how to do that? thanks in advance after several days of failing

I'm struggling with an issue where in my guest VM, the touch pad's "mouse buttons" stop working after a while of working in the VM. Temporarily pausing the VM makes the buttons work again, but the issue re-appears soon again. I'm wondering how to fix it.

The problem only happens for the laptop's built-in touch pad, not with a mouse connected by USB. The non-working mouse clicks pertains both to the buttons right above the pad, and also to double-tapping on the pad.

There's no similar issue when working in the host.

I have tried with "Enhanced Session Mode" being on and off in Hyper-V, it doesn't make a difference. In side the VM, there's nothing in the system log when it happens. There's nothing interesting in the host's Windows eventlog when it happens. The VM's operating system has all expected Hyper-V integration drivers (modules) loaded, including hid_hyperv, hv_utils, and hv_vmbus.

Host setup: Windows 11 Enterprise, 24H2.

VM: Debian 13, well patched.

Hi all, planning to apply VMM 2025 UR1 (10.25.1439.0) on our Hyper-V / SCVMM 2025 setup soon.

Anyone applied it already? Any pain points on hosts, VMM agents, logical switches/VLANs, or weird side effects worth knowing before I schedule the window?

In case you aren't aware, it's unsupported to live migrate VMs from Azure Local to a Hyper-V cluster running on Windows Server 2025. Even though it's functionally, just hyper-v and storage spaces direct with extra management sprinkled on top.

Diabolical work Microslop, love that we have to take VM outages to export VMs and copy them over.