Forum Widgets
Latest Discussions
Windows Server 2025 Desktop Experience: Hyper-V cannot be installed
I have a lab with various Servers running Windows Server 2025. Some of them are installed without Desktop Experience, some with. Aside from Desktop Experience, the VMs and the operating are configured the same way using automated setup scripts. I exposed the VirtualizationExtensions for all VMs on the host using Set-VMProcessor -ExposeVirtualizationExtensions $true. Moreover, I configured all VMs to use static memory assignment. However, when I try to install Hyper-V on Windows Servers 2025 with Desktop Experience, I receive the error Hyper-V cannot be installed because virtualization support is not enabled in the BIOS. The issue occurs without any updates installed as well as with KB5050009 (2025-01 Cumulative Update for Microsoft server operating system 24H2 for x64 based Systems) installed. On machines without Desktop Experience, Hyper-V can be installed without any issues. As a side note, on VMs using Windows 11 24H2 on the same host, I can install Hyper-V without any issues.
ASCHI cluster different RAM amounts per node
is it a supported model for ASHCI to have 1 node in a cluster to have different amounts of RAM? i appreciate that you can specify preferred owners, and possible owners on VMs, to restrict/ allow VMs to go to specific hosts, and understand that under normal circumstances you probably wouldnt want to have hosts with different amounts of RAM to circumvent over provisioning and then getting into difficulties upon loosing hosts, but am looking at making one of my ASHCI hosts a SQL server, i dont want to remove it from the cluster due to impacting storage, but need to increase the RAM, and if i can do it to just a single host id prefer that.
Hyper-V can not be installed because virtualization support is not enabled in the BIOS
Win 2022 Datacenter as Hyper-V host Win 2022 Datacenter as Virtual Machine ... after latest Windows Updates (troublemaker KB5034439 who require resize of Recovery partition to be able to be installed successfully) ... on the VM ... is Unable to install Hyper-V Role because of the error "Hyper-V can not be installed because virtualization support is not enabled in BIOS". Very first error it was a different one and it was fixed by enabling extensions who was fixed via this commands /Hyper-V Host /Elevated PowerShell #List of VM Get-VM Get-VMProcessor -VMName <name> #Check Nested (Get-VMProcessor -VMName <name>).ExposeVirtualizationExtensions #Configure Nested Virtualization Set-VMProcessor -VMName <name> -ExposeVirtualizationExtensions $true #Disable Nested Virtualization Set-VMProcessor -VMName <name> -ExposeVirtualizationExtensions $false ... but the error "Hyper-V can not be installed because virtualization support is not enabled in the BIOS" is very tough and I not yet find any solution yet. I'm convinced that they (MS) disable Nested Support via latest Windows Update, but it is only my personal opinion. I even update firmware to the Bios of Host machine and triple check the Virtualization boxes to be enabled but since no one change it it is the same. Anyone having some idea how to Enabled Nested Virtualization on Hyper-V Host Machine ?
Hyper-V NIC Configuration Question
I am about to build a new Windows 2025 Standard Edition server with 2 Ethernet ports and Hyper-V. Should I configure the 2 NICs as a teamed NIC that is shared with Hyper-V, or dedicate one NIC to Windows Server 2025 and the other NIC to Hyper-V? Or is there another recommended configuration? Thank you.Windows Server 2019 VPN Issue
Hi Team, I'm having issues trying to set up VPN service on server 2019. I've followed this link as a guide just to simply setup vpn connection so that we can access out the network from outside https://www.youtube.com/watch?v=dNBCTLMXVOQ From the dashboard, everything looks ok Upon connecting from the windows 10 machine, this is what I get Hoping if someone can assist me with this issue. My only aim here is just to create a simple VPN connection from the server 2019 roleCreating a test environment similar to prod - how to license?
Hi, We want to create a test environment to avoid "system wide" settings deploy to production without testing them first (e.g. Kerberos Enforcement or Entra Sync Settings) We would use Windows Trial licenses and Entra Connect to connect to a Testtenant. How must we license this test environment to be compliant with MS licensing? Some say it's Trial and not production "you do not have to". Others say we need to license "like Prod". Can anyone (preferably a Microsoft employee) help with this question? BR StephanSCVMM/Hyper-V Manager/Powershell not able to apply Microsoft NDIS Capture virtual switch extension t
Hello all, As title implies, I cannot enable Microsoft NDIS Capture virtual switch extension on my new Server 2022 core Hyper-V hosts. We primarily manage VMs via SCVMM. Our server 2019 core hosts on the same hardware do NOT have this issue. I'm posting to: A) Understand what this extension really does, my understanding is it enables "packet capture" or "virtual port spanning" which my virtual environment DOES require, as we use DarkTrace v-sensors on all our hosts for IPS/IDS. We enable this by going into failover cluster manager and setting port mirroring to "source" for all our VMs and "destination" for all the v-sensors. I'm unsure if this will continue to work as intended if the NDIS capture extension isn't checked. B) See if anyone else has had this issue or resolved it. If I try to enable via Hyper-V manager, it simply states that "the selected extension isn't working correctly. Check the event logs for further information (There are no event logs to correlate). If this is a non-Microsoft extension, contact the vendor (it IS in fact, a microsoft extension. "Microsoft NDIS Packet Capture Filter Driver Company: Microsoft Version: 10.0.20348.1"). If I attempt to enable via powershell (enable-vmswitchextension -name "Microsoft NDIS Capture") it will start for a time, and then stop again. If I use SCVMM to apply the logical switch to the host, it will successfully apply the switch, but throw an error with the host being non-compliant. As follows: Warning (26846) Either the switch extension 'Microsoft NDIS Capture' with driver ID 'ea24cd6c-d17a-4348-9190-09f0d5be83dd' was not installed on the host, or VMM was unable to enumerate the extension's driver version and driver ID. The switch extension is required for this virtual switch. Obviously, the logical switch has that driver selected to be enabled, but the hosts cannot enable it for some reason. What's interesting is that "driver ID" that SCVMM is reporting (ea24cd6c-d17a-4348-9190-09f0d5be83dd) is NOT the driver ID that is present on the Host. Running "get-vmsystemswitchextension" on the host reports the following: Id : 430BDADD-BAB0-41AB-A369-94B67FA5BE0A Name : Microsoft NDIS Capture Vendor : Microsoft Version : 10.0.20348.1 ExtensionType : Monitoring CimSession : CimSession: . ComputerName : HOST-Q-02 IsDeleted : False Im at a loss here. Ideally, I can just get this enabled in case it is needed. Alternatively, if I can determine that the extension is NOT needed... Im "ok" with not having it enabled.... but you never know when my org will add something that needs it.ASHCI cluster with different RAM amounts
been looking through server requirements and things, and i cant see a definitive answer of whether i need to have the same amount of RAM per ASHCI host. i appreciate it may not be best practice due to failing over VMs within the cluster, and being in a position where you over provision RAM and could end up in a sticky situation, but given that you can not only set preferred owners, but also have the ability to set possible owners, you should be able to account for that. tldr: ASHCI cluster can i have have one node with 4TB of RAM and 5 nodes with 2TB of RAM
DNS record auto registered even the auto registration option was unchecked
Hello guys, I have an DC which have two NICs, A for Domain service and B for camera server. I don't want the IP address of NIC B registered in our DNS, so I uncheck the auto register option in the advance setting of NIC B. However, the IP address of it still keep registering t our DNS even I have manually deleted that option. I have checked the steps in the official article and it doesn't help. https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/unwanted-nic-registered-dns-mulithomed-dc Any suggestion is much appreciated.
