Hyper-V: vmms. exe is creating two temp files in the System32 folder . . . I use Hyper-V, with a Server 2012R2 guest VM that I use for development and testing So it appears that vmms exe being the culprit fits the facts This feels like a bug in vmms, rather than any kind of intentional or desired behavior vmms exe lives in C:\Windows\System32, so that could explain why the files are being written in that location
Virtual Machine management service memory leak, server 2016 Wondering if anyone has any ideas what might cause this? One of my Hyper-v hosts seems to have a problem with the Virtual Machine Management service The memory usage for that service just continually climbs, it starts off at a hundred MB but increases by about 2 GB a day I got an alert yesterday that memory usage was high and the service was using 90GB! There also seems to be other issues