One Step Update is STILL BROKEN after more than a year of user reports of CC-800 errors......

JeffWeems

This is for Quicken Classic for Windows. One Step Update was an important useful time saving feature of Quicken that I used for many years—but I had to give up using One Step Update. I now am forced by the CC-800 bug to update transactions one account at a time.

Because One Step Update always results in CC-800 errors, and then Quicken users have to go through the intensive time-consuming process to deactivate and reactivate all their accounts, users may have resorted to simply updating accounts one at a time. That's what I've been doing. But today I ACCIDENTALLY used One Step Update, and of course all my accounts got the CC-800 error and will need to be deactivated and reactivated again :( I have about 30 accounts in Quicken. You can see how One Step Update broke all of them this evening in the image below.

Please DO NOT send me the useless question/suggestion of whether I've recently restored from a Quicken backup file. I have NOT, and you KNOW that is not what is causing the CC-800 error in question here. Google's Gemini AI gives a perfectly good summary of what's happening

In Quicken for Windows, the CC-800 error is primarily caused by issues with Express Web Connect (and Express Web Connect+) connections, which occur when local data fails to sync with Quicken’s cloud services. This error, often appearing after crashes or during One Step Update, indicates a breakdown in communication between the local data file and the Quicken server. Key Details Regarding CC-800 Errors:

• Primary Connection Type: Express Web Connect / Express Web Connect+.
• Root Cause: A mismatch or communication breakdown between the local Quicken desktop file and the Quicken Cloud Services, which manage these connection types.
• Trigger Events: Often triggered by bank connectivity issues, software updates, or when the Quicken application crashes during a One Step Update (OSU) process.
• Symptoms: One Step Update fails for specific or all accounts, even if transactions technically download.
• Fixes: The most common resolution is to deactivate all accounts with the problematic institution and reactivate them, or by resetting the Quicken Cloud data. 

Quicken staff and management have scrubbed all mention of this One Step Update problem (on Classic for Windows) from the Support site and they've buried this issue that all Quicken Windows Classic users are faced with. There's no mention of an ETA or any work being done to address this known bug during the last year or more. This One Step Update bug should be THE FIRST THING LISTED ON THE KNOWN ISSUES LIST on the support site(s).

If Quicken Inc isn't going to fix the One Step Update CC-800 bug(s) you should remove the One Step Update command and options from the menu bar in Quicken classic! Just admit that One Step Update doesn't work reliably and you don't plan to fix it.

RalphC

One Step Update works perfectly for me. I'm not receiving any CC-800 errors, so it's likely not a Quicken issue.

kdzavo

Works fine for me too. I'm sure I would be frustrated too if it didn't work for me, but I hope Quicken doesn't remove the option. All that would accomplish would be to force everyone to update one account at a time.

MarcColety

Works fine, no one is going to remove an option that works for most people.

Chuck56

Works fine almost 100% of time for me, with my limited number of accounts….. When it doesn't, it is almost always due to an issue I created. I will admit though, I don't have anywhere near as many credit card and other accounts as you (I have 7), so my use is not as complex and taxing on both the desktop application/database and the quicken and financial services online systems. OSU is a very valuable tool for me and my needs. Can't imagine having to update each account individually.

Chuck56

@JeffWeems

Just a long shot, but it might be worth eliminating the possibility that the root cause is an issue external to Quicken. When I was having issues with Quicken performance a while back (not the same error code as you), I tried all of Quicken Support/Community recommendations to fix my issue to no avail. Then I got to thinking that maybe it's not a Quicken issue, but something external, like outdated / corrupt network drivers and/or other config/system files in Win 11.

So, I upgraded all out-of-date system/network drivers. There were many significantly out of date. In my case, I downloaded a free copy of Driver Booster to do it.

Then, I performed a…..

Settings/windows update/advanced options/recovery/Fix problems using Windows Update

This reloaded win 11 without affecting data or apps.

This resolved my issue. Not saying this will resolve yours, but the Quicken issues could be a symptom of Windows OS problems that are not severe enough cause your OS to crash but may be affecting the performance of applications riding on it.

Just a thought.

Michael3442

@Chuck56 You say you used Driver Booster first to fix your issues and then reinstalled Win11. After that your issues were fixed. Before you reinstalled Win11, and after using Driver Booster, did you try to run Quicken to see if Driver Booster fixed the problem?

Chuck56

Yes, I checked Quicken to see if it rectified it and it did. I suspect it was a corrupt network driver. I then decided to reinstall win 11 just to make sure all OS/system files were ok also. Not just for Quicken but my other applications. Following the reinstall steps above did not affect my applications or data at all, it just refreshed Win11.

Chuck56

Just to clarify, my issues were performance issues, ie., slowness of the application, etc. I was not experiencing CC-800 errors. I only suggested the above to rule out the possibility that desktop elements (OS, drivers, system files) external to Quicken may be inadvertently causing the issue.