I've been running Parallels since Version 7. I'm now on 13.1.1 (43120) on a MacBook Pro running High Sierra, and I'm encountering what I believe to be a new bug:
When I start MacOS, my CPU gets pegged at 100% utilization. When I check Activity Monitor, I see a process called "Windows 10" that's taking up 100% CPU indefinitely.
This is weird because Parallels isn't running. Neither Parallels Desktop nor Parallels Toolbox start (nor should they, since I don't have them configured to run at login). My Windows VM does not appear in a separate space, as it always does when running properly - there is actually no visible UI for the VM, just the process and its horrendous CPU consumption.
Waiting doesn't address the problem. The only two ways to stop this are:
1) Actually starting Parallels and the virtual machine, and then shutting it down; or
2) Killing the Windows 10 process.
This has now occurred to me several times in a row. And I can't seem to stop it, since I can't determine why - or even *how* - Windows 10 is running in the first place.
Any ideas?
When I start MacOS, my CPU gets pegged at 100% utilization. When I check Activity Monitor, I see a process called "Windows 10" that's taking up 100% CPU indefinitely.
This is weird because Parallels isn't running. Neither Parallels Desktop nor Parallels Toolbox start (nor should they, since I don't have them configured to run at login). My Windows VM does not appear in a separate space, as it always does when running properly - there is actually no visible UI for the VM, just the process and its horrendous CPU consumption.
Waiting doesn't address the problem. The only two ways to stop this are:
1) Actually starting Parallels and the virtual machine, and then shutting it down; or
2) Killing the Windows 10 process.
This has now occurred to me several times in a row. And I can't seem to stop it, since I can't determine why - or even *how* - Windows 10 is running in the first place.
Any ideas?
