I’m seeing the same thing. A thread dump of the offending thread in MCE Buddy using Sysinternals’ Process Explorer seems to show it is locked in some kind of network connection or DNS lookup (for something that won’t exist in DNS, like another process on localhost or another host on the internal LAN?). I get this unexplainedly high CPU usage in addition to “cannot connect to server”, and noted the details in another thread.
Thanks for reporting this. I’ve replicated the issue and isolated the root cause. It’s happening when the GUI client tries to determine of it’s running locally or on a remote machine (Windows ends up doing a DNS lookup for it’s hostname which is causing excessive CPU utilization). We’re working on a fix.
Edit: After sitting there watching the process for a few minutes, there seems to be a pattern. It spikes and holds for a min or min/half and the falls off to nothing for about 10 seconds. Then repeats that over and over. So it seems it is trying to do something, times out, then retries a few seconds later?
So that is clicking “Stack” in the “Threads” tab of the explorer which i assume is what you are referring to. This was from sitting idle and using ~16%
The path it monitors is located as part of Drivepool. D:/MCEBuddy where D is a drivepool instance. However the drives in the pool are all connected to the same machine so no, it isn’t across a network with monitoring.
Weird. Looks like it is parsing the config file for something, and then is doing something that maybe requires UAC or some sort of user input but can’t.
Could it be some sort of character set or encoding issue? @AustinWBest are you setup with an international keyboard, fileysystem options, or perhaps the file paths have “smart quote” characters in them or other non-US characters? Have the defaults been set? Just to rule out that it isn’t trying to get a selection from the user that can’t, since Windows can’t get console input in some cases (mainly drivers, but this may not be that situation).
It doesn’t cause a problem with my MCEBuddy, but often shows with apostrophes in them (“Cook’s Kitchen”, or “Rory O’Connell”) will get parsed with a single-close-quote rather than an apostophe (or vice versa), and they end up in different directories and filenames. It also affects the metadata too, but that’s minor.
Perhaps your folders on the drivepool are using a different character set encoding than the config file or something similarly weird is going on.
@Goose would have to dig into whether or not using DrivePool changes things (the APIs?) that MCEBuddy needs to use if that’s the source of the problem. I don’t use DrivePool, so no feedback there.
Check your History file, manual file and other MCEBuddy configuration files. One of them may be corrupted. Start with clearing the history and manual files (just delete them) and if that doesn’t fix it then you may need a clean install.