SactoMurph

Agree with everything Ricardo said, except my CPU loads are even higher and fan usage is quite loud (due to Dell desktop heating up), which is almost *never* an issue when using other software on my PC.

PinkElephant, thank you for the prompt (immediate!) reply, but no, this is not at all normal. As I mentioned, this has been going on, noticeably, for several weeks. As I did not mention, one of visible symptoms is that my CPU fan runs incessantly when Evernote instances are running in the background. My fan almost NEVER runs unless I am using a high-end rendering app. Recently, the fan activity has been constant, until the Evernote background processes are terminated manually and/or the Evernote app is uninstalled. Only then does the fan activity cease. With my level of technical knowledge, I can't say at a micro level what is causing this behavior, but at a macro level, it is obvious: something in the current Evernote release is doing it, and it is not normal.

What the other posters describe is exactly the issue I've been having for at least the past two weeks (Evernote Windows 10.52.8). When Evernote is launched -- and even when it is just running in the background -- Windows Task Manager shows at least 8 instances of the program as active, with one or more of them using >35% CPU capacity, and hundreds of megabytes of memory. I followed the various suggestions in this forum to the letter: backup of my data, followed by removal via Revo Uninstaller, followed by reboot and reinstallation; unchecking the option to retain data upon exit, etc. None of these addressed the issue; each subsequent use of the Windows app resulted in exactly the same behavior. At this point, I am accessing my notes on my PC via the web app, which is a suitable workaround in the short term. However, if the problem with the Windows app is not fixed in short order, I will absolutely look to transfer my data to another note-taking app, of which there is no shortage. I like Evernote (have been a paying member since 2009) and appreciate its functionality, but am rightly concerned when new, real problems are created by updates. That tells me that the back-end code has become unwieldy, and raises issues about the long-term integrity of my data.