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.