I'm not trying to disagree, but when I loaded up Process hacker and dug down into the threads tab of the explorer.exe process, I saw the Decor8 service running as one of the active threads of that process, and the CPU consumption matched exactly the symptom I saw with the CPU utilization. Maybe I'm using the wrong terminology, but the data was pretty evident. If it helps, I'd be willing to reinstall Decor8 again and send you a screenshot of what I found, if you think that it would help you track down the issue.