Man, this is frustrating and weird. What I don't understand is why the first search below works in the web client, but not Windows Client, is the search logic not the same? There doesnt seem to be any consistency in the search logic. reminderOrder:* -reminderDoneTime:*Does not work for me. reminderOrder:*does, ok -reminderDoneTime:*Returns nothing on it's own, and returns nothing when used with the full string... hmm... It seems the problem is that reminderDoneTime cannot accept a wildcard (*) The other two reminder search parameters (reminderTime does not accept a wild card either) seem to accept the wildcard just fine. Using the steps here: http://codeforemen.com/evernote-tip-filter-for-incomplete-reminders/ I was able to look at some of the reminder fields. One thing I do not understand about what he did there was that he built his search logic around the fact that after a completed reminder is unchecked (made incomplete), the reminderDoneTime is set to 00001231T000000Z. So what? I don't want to have to make reminders, check them, then uncheck them. <code> <note-attributes><reminder-order>20150529T135946Z</reminder-order><reminder-time>20150530T130000Z</reminder-time><reminder-done-time>20150529T135950Z</reminder-done-time></note-attributes> What works for me:For incomplete reminders, with or without a due date. reminderOrder:* -reminderDoneTime:2015 -reminderDoneTime:2014 -reminderDoneTime:2013 -reminderDoneTime:2012Is what I finally had to go with... back to the year I started using Evernote. =\ Edit:It seems reminderTime does not accept a wildcard either. This has to be a bug... right?Edit2Ok, maybe not a bug, but still annoying. The reason ANY and Wildcards do not work is because even a reminder without a date has a value in those fields.<reminder-order>20150529T141906Z</reminder-order><reminder-time>00001231T000000Z</reminder-time><reminder-done-time>00001231T000000Z</reminder-done-time>Not sure... how this helps. But at least the search above works for me... I guess. Certainly not intuitive at all. Although this does not appear to work on Android, and I haven't yet tried in IOS.... /sigh.