nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

"Check for Updates" says up to date when it isn't and "One Step Update" doesn't see new updates

bdantes

Subject line pretty much says it all.

I was on R53.3 from Dec 2023 of Quicken Windows Home and Business. I finally got suspicious that I hadn't seen any updates pop up in One Step Update in a long time. "Check for Updates" similarly reported that R53.3 was the latest version. I went and searched on the Quicken website and found release notes:

https://info.quicken.com/win/windows-release-notes

discovering that I was 25 releases behind! I had to manually download the latest 61.20 release and install it over the older release.

Quicken support refuses to believe they have a server side bug — despite the banking transactions downloading fine, or the same problem occurring in a fresh file.

So if you're reading this, you may want to check your version against the reported release notes to make sure you ACTUALLY have the latest version.

And PLEASE, if you are able to replicate this issue , note it in a response here and let Quicken support know.

Find more posts tagged with

Windows

Update

One Step Update

Comments

NotACPA

Please do HELP, About Quicken and tell us the "Subscription Valid thru" date.

Also, do you use One Step Update to download from your FIs into Q? Because you should have been notified thru that process that updates were available.

And I have a tough time believing it's a "server side bug" either … since I regularly get notified of updates. There's something else going on.

bdantes

Thanks for the response, but honestly it read a little bit like, "Are you an idiot and don't have an active subscription?" :-P From your signature, I see I've been using Quicken as long as you have. :-) I am a former software engineer myself and definitely know Quicken well.

My subscription is valid through April 30 of this year. I already stated that I use One Step Update, and Help → A Check for Updates also failed to see the new update.

I believe this is not a general problem either — but I still strongly believe it's a server-side bug, perhaps with the way my subscription is stored on Quicken's end. But given that I can repeat the problem with a fresh file, and the One Step Update always picked up the new releases prior to R53.3, I don't see how the problem could be on my end.

RalphC

I'm not experiencing that issue and never have. There seems to be only one report of this issue so it can't be a systemic Quicken issue.

retird

@bdantes my One Step Update worked this morning. Have you restored from a backup dated before you updated the software to see if the backup vewrsion would work?

bdantes

@RalphC While I agree that there may be something triggering this bug that is specific to my subscription, there may be other users subject to that same trigger. This is a quiet bug — it took me quite awhile to finally get suspicious and double check the Quicken web site to see if there truly had been no releases. It's not like the version check gives any errors — it just kept happily reporting that R53.3 was the latest. Just because something isn't happening to all or even a large number of users doesn't mean that it isn't systemic. I also had never experienced an issue like this for years of using Quicken until I did.

@retird As I have stated twice, this problem also happened with a fresh Quicken file, thus ruling out the possibility that my client-side data was somehow at fault. I fail to see how anything client-side could ever cause the software to report that it was up to date when it wasn't, unless Quicken is caching some data on the user's machine independent of the data file that causes this problem (but if Quicken is relying on some kind of cached client-side data for a version check, that makes even less sense — the whole point is to contact their server to check for updates). Even if it were a client-side network issue, such as a firewall, one would expect the software update check to fail with some kind of error, not silently fail by reporting false success.

Triage unequivocally points to a Quicken server-side bug of some kind, even if only affecting a small number of users who have in their subscription triggering this whatever is/was doing it on mine.

The only thing I could do is manually reinstall Quicken. I'm waiting for the next release after R61.20 to see if updates start working again.

bdantes

R61.21 just dropped today (not in the release notes yet) and it showed up properly in One Step Update again. So hopefully this problem doesn't recur.

retird

@bdantes the release notes for R61.21:

Release R61.21 (US Versions, February 2025)

FIXED - An issue where selecting a Tax Line Item incorrectly assigned it to a different tax form.

bdantes

@retird Yes, I’m aware of what the release notes said in the One Step Update. I was referring to the release notes posted on the website at the link I gave in the original post - those haven’t been updated yet.

bdantes

And just for the record, that release notes web page above https://info.quicken.com/win/2025-release-notes still hasn't been updated with the R61.21 hot fix release as of this writing (5 days later). So I guess even that is unreliable as a "source of truth" of what the latest release actually is.