Jump to content


Level 2
  • Content Count

  • Joined

  • Last visited

Posts posted by 3k47

  1. Juggy, if you get your client to sync again and you find that the client is still slow and freezing up often, you might want to try my workaround which has solved the slow Windows client problem for many of us.  

    Instructions to implement the workaround that fixed the slow Windows client can be found here: http://www.evernote.com/l/ALrsBe2IrjdFfbGIOZYVpxRJAOUnjFZD2f4/

    Discussion relating to this problem and the workaround can be found in this thread: 



  2. FIXED (by a work around).

    I'm the OP on this thread, and I had the exact same problem you folks have been mentioning (and videoing), and my problem is completely fixed for now by a workaround.  The problem is somehow related to the client using the network in the background.  The solution is to create a windows firewall rule blocking evernote.exe while you are using evernote (typing, dropping in graphics, moving notes, whatever).  

    This completely eliminated the freezing for me.  Then when you are finished creating or modifying content, you can disable the firewall rule and let the client sync.  

    See my previous posts for details on how to set this up so it's a little more convenient to enable/disable the firewall rule (rather than having to open windows firewall each time, etc.).

    My workaround described earlier in this thread lets me just click a shortcut to block evernote (and allow me to use the client without freeze ups), and then allow me to unblock it instantly when done, and will even automatically unblock it after a set time (in case I forget).

    Still hoping Evernote decides to fix this properly someday.

    Here are the detailed instructions on how I got my Windows client working again: http://www.evernote.com/l/ALrsBe2IrjdFfbGIOZYVpxRJAOUnjFZD2f4/

    Hope it helps.  Cheers.

  3. For those of you who might be using my Windows Firewall blocking method, I've made one small change to the implementation.  Instead of having Task Scheduler disable the Evernote-blocking firewall rule every so often, I have it doing so only on user logon.  Then in the Block Evernote batch file, I've changed the code so it enables the firewall rule blocking Evernote's connection to the servers, then waits for 2 hrs, then automatically disables the firewall rule (and thus allows Evernote to sync again, in case I walk away from my computer and forget).  Note that the 2 hrs is a totally arbitrary length of time.  This blocking/waiting/unblocking sequence all takes place within the single batch file as follows:

    netsh advfirewall firewall set rule name="Block Evernote" new enable=yes
    timeout 7200
    netsh advfirewall firewall set rule name="Block Evernote" new enable=no

    Of course you still need to have the firewall rule "Block Evernote" created as I described in a previous post in this thread.  This new change has 3 advantages:

    1)  I always have 2 hours of typing/tagging/manipulating notes without freeze-ups before the client can start syncing again.  The previous implementation had the unblocking taking place every two hours after logon, and thus if I were unlucky enough to turn on the blocking to start typing right before an even multiple of two hours since the last time I logged on, the unblock script would run and I'd have to stop and run the blocking script again.

    2) While this batch file is waiting the 2 hrs (7200 seconds) a cmd window is left open on my screen reminding me that the Evernote client is blocked and I should unblock it before leaving my desk.  Of course I can minimize this window I need the screen space.

    3) Unblocking when I'm finished using the client is as easy as switching to the cmd window showing the 7200 second count down, and pressing any key.  This cancels the countdown and continues to the next line of the batch file, which is of course the line which turns off the blocking.

    Hope this is useful for someone else.  Cheers.

    • Like 1

  4. @gazumped How big a database in size and notes do you have?  I'm curious about the criteria under which this problem presents itself.  More to the point, I'm wondering how many notes/how much data I'd need to archive and remove from my account to eliminate this behavior.  My database is 74k notes across 34GB of data.

  5. FINALLY I have some relief on this issue.  After a bunch of experimentation I discovered that the primary source of my freezing is based on the Windows client connecting to Evernote's servers while I'm typing.  No combination of checking/unchecking advanced options under the Synchronization section, disabling context, disabling the search update feature, etc. would solve my freezing issue. I already have the client on fairly fast machines (with SSDs) and each machine was displaying the same problem. As a last-ditch effort I disconnected my Internet connection to the computer and found that essentially solved the problem.  Evidently telling the client (via Options/Synchronization) not to update instantly (or ever) doesn't actually stop it from syncing. Instead I created a firewall rule to block the windows client from connecting to the Evernote servers.  

    This presents obvious problems, as no one wants to have to go into Windows Firewall every time you type in Evernote.  Nevertheless, this was worth it for me, since the client was otherwise useless.  Then of course, if you forget to unblock the app your changes will not sync (and nor will anything else).  

    In order to speed up this process and remove the possibility of forgetting to re-enable syncing with the servers for the windows client, I created batch files which easily turn on and off the firewall rule, and I created a Windows Task Scheduler task to turn back on syncing to the client (by disabling the firewall rule) every 2 hrs or so, just in case I walk away from my computer.

    Here's the process:

    Create a windows firewall rule: Windows Firewall/Advanced Settings/Outbound Rules/New Rule.  Type of rule = Program.  Program path = the path to your evernote.exe file. Then choose "Block the connection." When does this rule apply? Check all three options.  Then for the name, make sure to name it "Block Evernote."  This gives you a firewall rule which can be turned on and off by batch files and by Task Scheduler

    Create two batch files, Block Evernote.bat and Unblock Evernote.bat.  I've attached what those batch files look like to this post (you'll need to change their extensions from .txt to .bat).

    Block Evernote.bat has one line in it, which is 'netsh advfirewall firewall set rule name="Block Evernote" new enable=yes'.  The unblock version is the same, but "enable=no".

    Next create shortcuts to these two batch files (in order to provide administrator privileges).  Once the shortcuts are created, you need to right-click each shortcut, go to Properties, click Advanced, and Run as Administrator checkbox (if you skip this step it won't work, because netsh needs admin privileges).

    Now double-clicking either of these shortcuts will enable or disable the window's client's ability to talk to the servers.  Use the Block one before you start typing in Evernote, and the Unblock when you are done.

    To make sure you don't forget to turn off the blocking, go to Windows Task Scheduler/Click "Task Scheduler Library" on upper left/"Create Basic Task..." on upper right.  Give it a name like "Unblock Evernote" and make sure you click "Run with highest privileges."  The Trigger should be at log on (or at startup should work also), and select that you want it to repeat every 2 hrs (or however often you like) for a duration of indefinitely.  In the Action, you would put Program/script = netsh, and Add arguments = advfirewall firewall set rule name="Block Evernote" new enable=no

    This is a lot of messing around, but totally worth it to me to be able to use the client again.  And this work-around, so far, has been very effective.

    Evernote, please look into fixing this issue more permanently.  This is simply poor coding.  The interface/database manipulations need to be decoupled from the background functions such as server access (and not executed serially).  And while you're at it, it wouldn't hurt to have the advanced options (which are supposed to stop the client from updating the note on the server every 5 words) actually work.

    Hope this helps someone else.  Good luck!

    Unblock Evernote.txt

    Block Evernote.txt

    • Like 2


    In the interest of cutting to the chase and helping any google-searchers to find the solution many of us are using, I'm posting that work-around here at the top of the thread.  To see my original problem and post, read below.

    The problem of regular freeze-ups while typing, inserting, or modifying notes via the windows client (which seems to present to users with very large databases) is somehow related to the client using the network in the background.  The solution is to create a windows firewall rule blocking evernote.exe while you are using evernote (typing, dropping in graphics, moving notes, whatever).  

    This completely eliminated the freezing for me.  Then when you are finished creating or modifying content, you can disable the firewall rule and let the client sync.  

    My workaround lets me just click a shortcut to block evernote (and allow me to use the client without freeze ups), and then allow me to unblock it instantly when done, and will even automatically unblock it after a set time (in case I forget).

    Still hoping Evernote decides to fix this properly someday.

    Here are the detailed instructions on how I got my Windows client working again: http://www.evernote.com/l/ALrsBe2IrjdFfbGIOZYVpxRJAOUnjFZD2f4/

    Hope it helps.  Cheers.



    Hello everyone.  Looking for some suggestions to speed up my windows client.  I'm wondering if anyone is experiencing the same issues I am, and if the community (or support) have any workarounds.

    Essentially, here's the situation:  My windows clients on all machines have become so slow they are virtually impossible to use.  Regular tasks like typing multiple sentences, changing notebooks on a note, adding tags to a note, or even scrolling through a list of notes has stops constantly at somewhat random intervals.  The gui freezes (and shows not responding) for sometimes 4 to 5 seconds at a time.  And this will typically happen every two or three sentences or so, whether the client is currently syncing or not.
    Before we start, know that the slow speed is universal through all of my windows computers (multiple decent speed desktops 1 to 2 years, surface book i7, surface pro, etc.) and has been the same across all of the last 5+ versions of the windows client.  All of my computers have SSDs (with the database, OS, and Windows client installed on the SSD) and reasonable performance.
    The problem I suspect the problem is linked to the enormous size of my database.  Since I run my business with 68+ employees and 6k+ customers off the system, my database is around 65K notes taking up around 40GB.  I realize that I am approaching the 100k note limit quickly (perhaps by the end of this year I'll need to remove some anyway), but I'm wondering if there might be a work around to not have to cut down the database and still have the clients workable.
    The slowness appears to be entirely related to CPU usage.  Monitoring my resources, the SSDs have no trouble keeping up under nearly all circumstances.  The CPU however is pegged every few seconds while the gui is being used.  (Or rather, since the client seems to be single-threaded, one core is pegged.) The application seems not be multi-threaded in any meaningful fashion, and I can only assume that some background table queries are taking place regularly based upon what I am typing.  I could certainly understand if searches were slow with a database my size, or even tagging (since the tag table must be loaded in memory each time a tag is typed, to search for a matching tag name).  But there seems to be no reason to have this sort of CPU stall out with things as simple as typing or scrolling through notes.  And when it stalls my GUI completely stops responding for 1 to 5 seconds.
    I have disabled all syncing (in case instant sync or background sync or similar was the problem), and this has not helped.  I realize that evernote maintains some kind of word token table for searching.  Perhaps this word token table is being searched at regular intervals based up words typed, in order to provide the [completely unused by me] context function?  Or perhaps the text I am typing right now is being tokenized at intervals (this should be extremely fast) and then inserted appropriately into the token table at the same intervals (which would probably be where the freezing occurs).  Even now as I type this very message in a new note in the windows client my cursor routinely freezes and cues up my keystrokes, only to insert them some seconds later.  I have very little experience in database driven applications (and am doing a lot of guessing here), but it seems like a simple decoupling of the interface from the background table queries, token insertion, and the like via multi-threading would easily solve this problem.  I realize that is likely low on the priority list of things to accomplish for Evernote, so what I'm really looking for here is a work-around.
    The first and most obvious solution would be for me to remove a large number of notes (and perhaps place them in a second evernote account).  This I am prepared to do, but it's not exactly Plan A.  This would be a pretty comfortable solution if we were able to have two accounts on Android devices which we could switch between.  I'd be happy to pay the money for a second premium account.  Then I would simply keep most of my older notes in the second (slower) account, and could access them easily (if more slowly) by switching accounts on either my windows clients (already possible) or my android devices (not possible as far as I can discover).  As there doesn't seem to be the ability to switch accounts on an android device (without deleting my 40GB account and re-downloading the other each time) this solution would mean I wouldn't have access to the older notes when I was away from my windows pcs.
    Does anyone have any suggestions of other work-arounds?  Can anyone think of any guesses as to what the background lookups/etc. causing the high CPU usage actually are, and how I might disable that functionality to be able to use the client again?  Can I disable context lookup, just in case that helps? I assume if the holdup is the insertion of tokens into the main search table at regular intervals, that is core functionality that I won't be able to disable from the GUI.
    I thought I would see what you all think before I spend hours and hours developing a plan on what data to make inaccessible on my mobile devices. :)
    Thanks in advance for your help, and Happy New Year!
    • Like 2
    • Thanks 3

  7. I don't know if this counts as a full workaround, but it has allowed me to search for notes due during a time range on the Windows client (though it has limited utility for saved searches, as seen below).  Perhaps others may find it useful.  Note that I have not tested this thoroughly, so YMMV.


    Searches using the "reminderTime:" syntax can include a specific (non-relative) date, and this seems to work on the Windows client.  For example, I could search for reminders due today by searching "remindertime:20140522".  Apparently this query is designed to return all notes with reminder time occurring May 22, 2014 or later.  


    Thus if I am trying to search for all notes due this week, I would enter the following in the search field:


    reminderTime:20140522 -reminderTime:20140529


    In the OP's case, for a search including notes with reminder times today and previous, that search (if performed May 22, 2014) would look something like


    reminderTime:19000101 -reminderTime:20140523  (All notes with reminder time between January 1, 1900 and May 22, 2014 inclusive)


    Obviously this is not very useful if you want to create a saved search showing what you need to do today (or should have already done by today), since it would require you to change the date(s) specified every day you use it.
    • Like 1
  • Create New...