Windows Quicken Classic - Hanging/OSU Freezing/CC-501 Errors

Me too….Been like this for two days. Tried the possible "fix" posted by boatnmaniac to do a manual patch install and file restore. No Luck!

15 minutes and still waiting for OSU to complete! UGH!

Bank of America failed for me too, with CC-501.

My version of Quicken for Windows is 2 versions back, so this isn't a symptom of the newest version.

But on retry - BofA succeeded.

All my other cards are working, too.

Puts me in a tough spot - I'm not going to convert Fidelity from DC to EWC+ without first upgrading Quicken version. But if the latest version of Quicken has broken most credit cards - then I'm not going to upgrade Quicken either! Not until the CC-501 reports settle down.

Updates usually take about a minute or so, but today are taking 5 minutes. I tried restarting the PC and only running Quicken by itself. Even with the time, 3 of my FI's didn't connect. What's up and can I go back to the previous Release?

Thanks…Mr Zipp

Version R64.30 Build 27.1.64.30 Windows 11 Home

It started yesterday and continued today after the update.

6:05 AM, OSU failing with CC-501 - Fidelity, Elan Financial Services, American Express. Yesterday, it was Chase.

6:43 AM, Noticed, now just Fidelity, Elan Financial Services throw CC-501 BUT it seems like transactions were posted OK in Quicken. American Express now working without CC-501.

11:36 AM, OSU working fine at this time. Also, updated to R64.30, no issues so far.

Mine hanged yesterday then worked late in the day and now it hangs again!

So OSU finally completed. All accounts failed. All CC-501 errors.

Thanks for the suggestion. I'm going to let it ride and see if it clears up later today. I did upgrade to 64.30 right before running OSU. Don't think it's related though.

thanks for all the great input. Eventually I updated and synced but after using task mgr to get out of Q n restart computer multiple times.

Could it be our version of windows 11

For what it's worth Quicken one step update worked fine for me this morning unlike yesterday. Well, fine is relative because I still receive a message about citibank that's been happening for several weeks. But I never have updated to the latest release. I am on Version R63.21 Build 27.1.63.21.

Still not working this morning. Ugh!

Talked to support and they said they are clueless about when it will be fixed. My thoughts: This is not you, you have done nothing wrong, and there is really nothing you can do to fix it. This is all Quicken and you are at the mercy of its engineers to fix it.

It is unhelpful when Quicken Anja, above, yesterday stated that it looked like the situation was stabilizing. Software is not a human being, who is in critical condition in a hospital, who is responding to treatment. Software does not stabilize. If it is broken, it will remain fully broken until it is fixed. When she said stabilize, it suggested that as volume of OSU requests went down with customers giving up (perhaps a clue?), OSU failures declined and people over time were able to eventually succeed. But they never fixed the problem and, this morning, as people updated their accounts, the failure of the Quicken engineers became abundantly clear. They fixed nothing. They are clueless.

Software that is working does not magically, suddenly break. If the software is working end to end, only a change somewhere in the long chain of software causes the failure. Updates to your Quicken software on your computer could be the problem. Updates to their backroom software could be the problem. Updates to security software could be the problem. Updates at service providers could be the problem. Etc., etc, etc. Failures like these are reflective a corporate change control problem. The process of how they design, test, and implement changes is inadequate and is failing repeatedly. And the corporate executives in charge of this process should be held accountable. There is no doubt that an audit of Quicken's IT department would expose massive failures and/or inadequacies in their change control process that would potentially result in firings or demotions.

In short, they not only need to figure this out, but they also need to figure this out long-term, and make appropriate management changes.

I was able to successfully update all my credit card and brokerage accounts using the one account at a time method. I had updated my Windows Quicken Premier to R64.30 prior to attempting account updates.

Chase, Citi, and Discover cards all updated without errors.

I then updated the Fidelity Visa card account and that went fine.

Updating the Fidelity Visa account started simultaneous updates of two Fidelity brokerage accounts that had been coverted to EWC+ last Saturday. Both brokerage accounts updated correctly.

Comparing the holdings and values of my Windows Quicken Fidelity broakerage accounts with Fidelity's online information everything is in agreement — well, there is some small discrepancy with what I think is probably due to CD pricing issues.

The R64.30 update did resolve a problem with Quicken erroneously saying one of the brokerage account cash balances was not in agreement with what Fidelity was reporting, although the amounts were actually the same.

So, I think my Quicken accounts are in pretty good shape.

Of course, not sure what caused what or what tomorrow will bring.