I started this discussion to share information about a Vmware Player 12 bug I discovered yesterday and how I solved it. I want to share it since there is no other discussion on this issue, I'm probably one of the few people who saw it.
When I was running Vmware Player 12 for the first time yesterday I experienced slightly higher system interrupt, it went from 4-5% until 8% in my task manager, and I experienced short freezes of my Windows 10 machine. Sometimes it froze for 2 seconds, sometimes for 15 seconds, it was scary.
PC configuration is:
- 4790K overclocked to 4.8 Ghz (all virtualization options in bios enabled)
- 16 GB od DDR3, 2400 Mhz
- Gigabyte G1 Sniper M5 motherboard
- lots of storage options SSD and older storage
- Windows 10 Home edition x64 all the updates installed, apart from the creators update which came out yesterday
- GeForce 980ti overclocked
So it is a fairly powerful machine, and at first I thought that my overclock was messing up. I entered Gigabyte Easytune and I saw some strange numbers (impossible ones), cpu moving towards 6 or 8 Ghz, RAM was going towards 3000 mhz, so something strange was going on.
I started to turn off, and turn on the couple of VMs I had so I was sure that Vmware Player was causing this, and only in situations when I was downloading something (other VMs for most of the time), the speed of the connection is about 70 Mbits/s. When I wasn't downloading anything there were almost no system interrupts. Tried restarting the machine it didn't help.
Since I connected that this happens when I have at least one VM running and there is some network activity (I get internet through the Ethernet connection of the motherboard) I figured that I should fiddle with the network settings.
Tried many things disabling the Antivirus, Firewall, and in the end I found some forgotten VPN service (the service which comes as a Windows 10 service), which I haven't used for a long time. It was listening for incoming connections. I deleted it and everything went back to normal.
So Vmware Player 12 doesn't like Win 10 incoming VPN service. Maybe this is the case only with the killer network hardware, or with any networking hardware, I wouldn't know. But this is how I solved one annoying bug.
