It’s just Hyper-V itself deleting and recreating switches & vNICs. It’s the same root cause as that issue where your Ethernet adapter gets a “(2)” or “(3)” tacked on, like in this (3rd) issue: https://learn.microsoft.com/en-us/answers/questions/326293/h...