Jump to content
  • 4

New Evernote for Windows, v6.0 (6.0.6) GA

Stephane Lo


Today, we started rolling out Evernote v6.0 for Windows to the general public.
This is a big milestone for the team, and we couldn’t have gotten here without your continuous input and feedback.

Of course, this is not the end and there is still a lot to do. For instance, we’ve heard the recent comments on Saved Searches. This was an intentional change to simplify the overall experience. We understand it affected the workflow of many people and are bringing this feature in a hotfix release very soon while we continue exploring how to best evolve saved searches to be relevant for a wider audience.

In the meantime, now that v6.0 is officially released, let’s help as many people, new and old, find and enjoy this release. We’d greatly appreciate your support with the public launch of this release, on the blog and on social media!

As usual, please keep sending feedback, suggestions, and use cases our way. Many thanks.

**EDIT: the release is now updated with a 6.0.6 Hotfix**

You can download the updated v6.0.6 here


New in 6.0.6:

  • Fixed loss of tag structure on drag and drop of nested tags
  • Fixed bug with subscription expired message 
  • Fixed various crashes

Fixed in 6.0.5:

  • Saved Searches are back
    • Find your existing and new saved searches in the left sidebar below Tags
    • Create new saved searches from the left sidebar saved searches section or right-click on the search description
  • Fixed crash on switching Evernote account
  • Fixed crash when importing from OneNote 2016
  • Fixed ENScript exportNotes bug

If you’re updating from v6.0.3 beta:

  • Selecting a notebook or tag highlights it in the left side bar. Override this behavior in the settings
  • Added option to trash the original note when copying between Personal and Business.
  • And 30 smaller bugs.

If you're updating from v5.9.9 and below, check out the blog announcement and the release notes.

Link to comment
  • Replies 401
  • Created
  • Last Reply

Recommended Posts

  • Level 5*
49 minutes ago, kvitekp said:

Yeah, a little quirk in EM_SETTEXTMODE message implementation on Microsoft side -- it requires _empty_ text to be set into control before the setting is accepted. Just initialized control is not enough, one has to literally set empty text into it.


Link to comment


This topic is now archived and is closed to further replies.

  • Create New...