Hyper-V 2022 - VMSS logs constantly about Hyper-V-VmSwitch

Copper Contributor

Hi guys,

any hyper-v gurus around? :cool: I have a new 2022 host which will be deployed to production soon. I've found by luck that vmms process (Virtual Machine Management service) constantly logs Verbose messages about "Ioctl Begin ioctlCode: 0xD15" and " Ioctl End ioctlCode: 0xD15, delta (100 ns): 80, ntStatus:  0x80000005(NT=Buffer Overflow)" with Event ID 0 and source Hyper-V-VmSwitch.

vmms01.pngI've looked around and had no luck finding the cause. It's happening even if I stop all the VMs and I even removed the vSwitch - there is no vSwitch on the host and it still logs like hell. The source is well know SID 1-5-18 (SECURITY_LOCAL_SYSTEM_RID)


Anyone saw this before or have any idea what could be the issue here?

Thanks for any ideas



7 Replies
Hi, if you get an answer I'd love to know, too!

Trying to figure out if there's some way to turn off auditing. I'm not concerned about any errors since it's just "Verbose", but still, it's flooding my event logs !
The same thing is happening to us.

I don't know if it could be because we are using SET-TEAM (Switch Embedded Teaming) on the network cards.

More information on this would be appreciated.

@festuc Any news on this?

Just ran into the same "issue", also with SET teaming on a Hyper-V 2022 cluster.

@aedii Nops :( anyone has give us any reply.


Hello, the same thing is happening to me. Although it's been a while, were you able to solve it?


Hi, nope didn't solve it. Consulted with some Hyper-V MPVs etc and it's happening all the time, it's like 1MB log file which is rotating, so it's not that big of a deal. Still a nughty bug I thing, but it seems nobody cares :)



Hi, thanks for your response.
I have managed to stop this problem. On my Hyper-V system it was causing network performance issues.


To solve it I reinstalled Hyper-V, the steps I followed:

  1. Shut down all VMs
  2. Remove the network adapter from each VM
  3. Delete the virtual switch
  4. Remove the Hyper-V role
  5. Reboot
  6. Add Hyper-V role
    1. I have a dedicated network adapter for VMs. Before installing Hyper-V, I disabled TCP IPv4 and IPv6 protocols on the adapter
    2. Select network adapter without connection sharing
    3. Select location of HV machines and disks
  7. Reboot
  8. All machines appeared in HV without the need to import them
  9. The Hyper-V-VmSwitch log shows a few messages but they stop and some correct information already appears

Greetings, I hope it helps you!