Evernote for Windows Issue [ version 10.16 ]

[Gary Lutz 2]

Recently upgraded to Evernote version 10.16 for Windows. The app was able to be launched from the desktop for a total of three times and then it stopped after that. When clicking on the Evernote icon on the desktop the cursor would show a spinning wheel for about a minute and then disappear. Nothing showing on the task bar as running. The only way I could see the application was inside the Task manager.  About 5 to 6 occurrences of Evernote running in background under Background Processes. Does not appear in Task Manager as an App running. I have tried uninstalling and reinstalling, redownloading the application but still results the same way. 

Hoping some one else may have encountered this issue and would mind sharing some way to resolve it.

As a backup plan, I have been using the Evernote totally as a Web service now to access my material.

[gazumped 11,808]

Hi. I'd recommend reaching out to Support.  And maybe Legacy for the moment? https://help.evernote.com/hc/en-us/articles/360052560314-Install-an-older-version-of-Evernote

[PinkElephant 8,346]

@Gary Lutz This is the completely normal behavior of the v10 client. EN uses a framework, practically a browser without a front end. The framework handles all interaction between the app and the surrounding computer.

Once you close the app, the framework stays open. It disappears when you quit the app instead of closing it. Quit means by the menu, close to hit the X.

Now you may have a bad install. Uninstall by using a helper like REVO uninstaller.

When it still does not work there is support.

[agsteele 2,997]

As noted by others, multiple Evernote processes is normal so not necessarily an indicator of the cause of your issue. Indeed, the old so-called Legacy version will also launch multiple processes.

As @PinkElephant indicates, a clean uninstall and reinstall may resolve the issue for you. Otherwise you have the option to open a support ticket.

[Gary Lutz 2]

Today, July 5th, the desktop functionality returned to normal. Still no reason why it presented the way it did. I only know that like the other folks who paid a comment, something was going on in the backend. The was no access to the front end ( User Interface) of the application while it was doing whatever it was doing in the background. I am only happy that it is working correctly now.