I’ve been writing about the bugs in Quicken for years and I’ve been complaining to Inuit about it. For many of the bugs, they refuse to acknowledge they exist. For others they simply don’t care. Don’t expect any of these to be fixed… ever.
Here’s a short list of bugs and problems I’ve experienced with Quicken 2016 in just the first couple of days of use:
I canceled a repeating online payment. It will never send the instruction and complains that I have a pending instruction to send every time I exit the app (pictured).
No audio (happened before the upgrade and still no sound).
Every time you contact support, they claim your file is corrupt and want you to do a file repair, which never fixes the problem, though that, itself, is both a customer service problem and a serious bug that their software continuously corrupts the data file. This has been a problem for at least a decade (possibly more).
Redraw routines are incredibly inefficient with too many redraws happening — readily apparent and an actual problem when remoting in to your PC. Also a problem when moving the app window around the desktop. It’s very choppy even on high end desktops with high end graphics cards. This is something a 20 year old PC should handle easily.
Non standard text entries — When you click in it, it auto-selects the text. This has been a problem for decades. They seem to think it’s a feature, but to power Windows users, it ALWAYS interferes with our way of doing things. It’s impossible to get used to it because 99% of all other apps do it right (by not doing this).
[Update 2016-02-16] I changed a password to a credit card, now Quicken can’t connect and asks for the pw every time, instead of storing it in Quicken’s password locker with all the others.
- Linking bills to online crashes 100% of the time on first attempt of each bill.
- App hangs with high CPU% when trying to update online transactions frequently (not all the time). Must forcibly kill app.
Thank you for sharing this article. See the image below?
You’ll find actual working versions of them at the top and bottom of this article. Please click the appropriate buttons in it to let your friends know about this article.
I’ve reported on many Quicken bugs over the years and have reported them all to Intuit multiple times. I’d be embarrassed to admit how many hours I’ve spent on the phone, walking them through their own bugs. It’s all been 100% fruitless. They don’t care or can’t comprehend that their precious product isn’t perfect. So, I will now only report it on their website and blog about it here, hoping that maybe they’ll feel just a tiny shred of embarrassment. And, of course, for your benefit to know that it’s not just you experiencing this bug. It is a real thing.
So, what’s the bug THIS time?
If you download your transactions from your bank, and one of them is a deposit, then you attempt to change the name of the deposit from say, “DEPOSIT” (which the bank gave it) to the actual payer, say “John Smith”, Quicken will CHANGE THE TRANSACTION DATE to a date in the future, saying “It’s too late to make a payment to John Smith”. Here’s an actual screen shot:
Forget that this is a deposit of only a penny (that’s a whole other blog post!) The point is that this IS a deposit and I want to change the name from “DEPOSIT” to “Verizon Wireless”, who is the one that sent me the check. Quicken 2014 insists that I must be setting up a payment and refuses to keep the actual transaction date that’s already there.
I even accepted the transaction as “DEPOSIT”, hoping that after it was already in the registry, that I could change the payee to the right name and it still exhibits the same bug.
I know of no solution. As a work around, I just put “Verizon Wireless” in the memo field instead, leaving the bank’s choice of “DEPOSIT” in the payee field, which is NOT the right solution. So, no solution, only a less than desired work around.
See these images?
You’ll find an actual working versions of them at the top and bottom of this article. Please click the appropriate buttons in it to let your friends know about this article.
Check back later for updates too!