CC-601 Error - Fidelity Brokerage Accounts not updating.
I can't get my brokerage accounts at Fidelity to update. Quicken is throwing "CC-601 We cannot find an account with a non-zero balance or with any transactions in the last 12 months. Please check on your website and try again."
This has been happening since yesterday. I have tried the usual tricks - e.g., de-authorizing, reauthorizing, checked log-in credentials, deleted Quicken as a 3rd party app on the Fidelity website. Nothing seems to be working.
The re-authorization process appears to work smoothly. The accounts appear to be connected. However, when I hit the sync button the "CC-601" error appears.
It is impacting taxable and non-taxable brokerage accounts.
What am I missing?
Comments
-
Hi @gtgerbo,
Thank you for sharing what you’re experiencing.
We have received multiple reports regarding various issues associated with Fidelity. I would recommend contacting Quicken Support directly for further assistance. They can walk you through troubleshooting steps in real time and escalate the issue if necessary. The Quicken Support phone number can be found through this link here. Phone support is available from 5:00 am PT to 5:00 pm PT, Monday through Friday.
For additional updates, please refer to the active alert regarding this issue.
Please let me know if you have any other questions.
Quicken Laura
Make sure to sign up for the email digest to see a round up of your top posts.
-1 -
This is also happening to me. I have gone through all the deactivating and reactivating steps. This just started happening on Saturday 2/28. What is going on? Everything was working fine up until Saturday morning.
0 -
I'm having the same issue this morning (3/2/26).
0 -
Add my name to the list using a Mac, latest Version 8.5.0 (Build 805.60099.100). This started 3/1/26 for me.
0 -
Same problem here. I saw it on 3/2, but it might have been happening earlier when I wasn't attempting an OSU.
0 -
An update to my post…
I pursued Quicken Laura's suggestion and tried contacting Quicken Support directly for further assistance. According to Quicken Support, the issue had already been escalated. There is no ETA on when this will get resolved.
Wonderful.
1 -
@gtgerbo What's curious about this is that I downloaded from 7 accounts at Fidelity Investments on Saturday 2/28 and today 3/2 without problem.
I have 3 taxable and 3 retirement accounts in my main file and a taxable account for an organization in another file.
This suggests that it's something deeper than a simple programming issue … and thus might take a while to resolve.
Q user since February, 1990. DOS Version 4
Now running Quicken Windows Subscription, Business & Personal
Retired "Certified Information Systems Auditor" & Bank Audit VP0 -
Hi everyone,
Thank you for continuing to share your experiences and reports with us; we truly appreciate your patience.
We are aware that some customers attempting to connect accounts from Fidelity Investments in Quicken Classic are encountering FDP-101 or CC-601 (CP_SCRIPT_ERROR) errors. Our teams have identified this as a known issue and are actively investigating the root cause.
At this time, there is no additional action required on your part. We are working toward a resolution as quickly as possible and will provide updates as soon as more information becomes available.
To stay informed, please refer to the active alert:
We understand how important reliable account connectivity is and sincerely appreciate your patience while we work through this issue.
Quicken Laura
Make sure to sign up for the email digest to see a round up of your top posts.
-1 -
Also having the same problem all Fidelity accounts are cc601 unable to find non zero. I set up a new account in Quicken with one fidelity account. After doing and updating it also returns the error on a new set up. That explains why uploading a back up didn't work. Except giving me more work to do. Back to manual entry. Seems I've been doing that alot with Quicken
2 -
NotACPA This suggests that it's something deeper than a simple programming issue … and thus might take a while to resolve.
Agree.
I did not encounter any errors over the weekend or this week either.
0 -
I have had the same problem since Saturday. Interesting that several friends who use same version have had no problems.
@Laura, I have checked the active alert several times and don't see any additional information.
0 -
I have the same problem since Saturday. I've gone through the deactivate-reactivate routine. It didn't help.
0 -
I have the same problem with Everbank started 3/3/26
0 -
Same problem March 4, 2026.
0 -
Just add another CC-601 error to the pile. Got it on 3/1 or 3/2 when I tried to update the February transactions. January transactions downloaded fine. I haven't done anything other than read the messages here so I won't try the deactivate-reactivate since it apparently doesn't work.
0 -
Same with everyone here, started getting the same error at the same time a few days ago. Very frustrating… paying for this Quicken subscription to download accounts and then having to enter the transactions manually… why am I still using Quicken???
1 -
Hi everyone,
Thank you for sharing your experience with us. Our team is actively working on a resolution; however, we do not have an estimated time for the resolution just yet.
We understand how important it is to maintain a reliable connection and successfully update your accounts, and please know that resolving this issue is a priority for us.
We truly appreciate your patience and understanding while we work toward a solution. For the latest updates, please continue to refer to the alert linked in the previous post; any new information will be shared there as soon as it becomes available.
Thank you again for your continued patience.
Quicken Laura
Make sure to sign up for the email digest to see a round up of your top posts.
-2 -
I added a new Roth account and thought for sure it was something that I did, but now I find it's a general problem? I'm posting with hopes that I'll get notified when there is an update.
0 -
Add me to this list. I creted a test file and got cc-601.
With my old file no error message but no transactions
0 -
Can u pls go thru the exact steps you did in creating a test file? I don't want to have to go thru the long tedious process of restoring my account from a back up if my real account gets messed up by this Fidelity issue.
0 -
I am also not getting downloads on my existing Fidelity accounts but I am getting a different error
The Fix it button has me reauthorize my accounts but it does not fix it. I tried deleting my existing accounts and starting over and then I get the CC-601 error
0 -
Add me to the list of the CC601 errors with Fidelity. Multiple accounts that were working and it seemed to break with the last 2 Quicken software updates.
1 -
Add me too, same as the rest of you. Just wish that instead of a generic error code, they would have informed us that it was a known problem. Especially since I spent hours on my own and multiple backup copies thinking my file was corrupt.
1 -
Fidelity Investments and Fidelity VISA transactions suddenly stopped downloading via One Step Update on 2/20/26. OSU screen consistently shows complete and no errors listed. Daily mutual fund and stock prices populate fine. But still, new transactions listed on fidelity.com do not show in any of family's Brokerage, Roth, Trad IRA, 401k, and annuity accounts. Tools > Account List shows Express Web Connect+ and Last Download shows ‘Not Available.’ Each account’s Account Type is correct with Brokerage, Roth, etc. I’m using Premier Classic R 66.23, Build 27.1.66.23. Based on some related Q Community feedback, I tried to reset a couple accounts. Both did not show as a choice when I tried to reconnect them.
1 -
@Quicken Laura, @Quicken Kristina, @Quicken Alyssa
Do we need a Mac thread for this issue as well? The general error codes seem identical but the experiences are slightly different. There is a new Mac release today: Version 8.5.1 (Build 805.60122.100) and I'm just reporting back that upgrading to this release had no effect on my ability to sync with Fidelity. I disconnected and reconnected the Fidelity accounts after upgrading but the FDP-101/CC-601 error codes remain. I presume the underlying issue is platform agnostic.
The Fidelity Announcement Ticket #12266898/ CTP-16491 is the one I've been watching, so occasional updates to it are appreciated. A similar Ticket #12269329/ CTP-16510 was just created for what appears to be the same issue (same error codes at least) but involving banks.
0 -
Me too. Been trying to resolve this issue since March 2nd.
1 -
Same problem for several days. Finally just adding my name to the list.
0 -
A suggestion from a veteran software engineer…spend more time testing changes before releasing them to production. The Fidelity connection has had issues at least 5 times in the last 6 months resulting in failed connections and/or erroneous data updates. I have been a Quicken user for over 30 years. This is definitely the worst streak for Quicken reliability.
12 -
I have the same CC-601 problem.
1 -
Is there any update on an ETA for this issue? What is the current status? Is the problem understood yet and development is working on a fix or is the dev team still trying to understand what is happening? Can the dev team reproduce the issue?
I would also like to second the comment from jblevy01. You are putting out too many updates at a very fast pace with insufficient QA. The stability of the product has really fallen over the past few years. I too have been using Quicken for at least 30 years and it has gone from being a rock-solid product to incredibly unreliable.
10
Categories
- All Categories
- 52 Product Ideas
- 34 Announcements
- 243 Alerts, Online Banking & Known Product Issues
- 20 Product Alerts
- 515 Welcome to the Community!
- 680 Before you Buy
- 1.5K Product Ideas
- 55.5K Quicken Classic for Windows
- 16.8K Quicken Classic for Mac
- 1K Quicken Mobile
- 830 Quicken on the Web
- 126 Quicken LifeHub





