Capital One 360 Not Updating
Quicken, Windows, version R61.21, build 27.1.6.21
On updating it says: Capital One 360 is reporting connection issues. Associated accounts cannot update right now. We are investigating the issue.
It seems to have started a few days ago, but I thought it's been doing it longer. Is this a Quicken issue or a Capital One issue?
Comments
-
Hello @Tony Luers,
We appreciate you bringing this issue to our attention!
Our teams are actively investigating this issue further and would like you to try the steps provided below:
- Run One Step Update (OSU) first to see if the issue resolves.
- If the issue persists, rename the runtime.dat file located at: C:\ProgramData\Quicken\Inet\FILENAME\
- (For example, add a 1 at the beginning of the file name so it reads 1runtime.dat.)
- (For example, add a 1 at the beginning of the file name so it reads 1runtime.dat.)
- Run One Step Update again to check if the problem is resolved.
- Close and reboot Quicken to ensure changes take effect.
📌 Note: The ProgramData folder is hidden by default. If you need help accessing it, Microsoft's support site has instructions on how to unhide folders.
To assist in our investigation, please provide the following and let us know once you have done so:
- Logs (Help > Report a Problem)
- Screenshots (excluding personal data)
- A sanitized copy of your Quicken data file (with personal details removed)
Thank you!
(CTP-12393)-Quicken Anja
Make sure to sign up for the email digest to see a round up of your top posts.2 -
Quicken Anja
Thank you Anja!
That solved the problem.
I appreciate your help.
Tony
1 -
Thanks for the update! Glad to hear that worked for you. 🙂
-Quicken Anja
Make sure to sign up for the email digest to see a round up of your top posts.0 -
Classic Deluxe for Windows - V R61.21 Build 27.1.61.21
This did not work for me. Same error has been happening since 13 March, 2025.
0 -
Hello @Ray Hallman,
Thank you for adding to these steps and trying the previously provided instructions, though I am sorry to hear that it did not resolve the error for you.
As mentioned before, this is still being investigated, so since the instructions did not resolve the issue, please submit a Problem Report with log files, a screenshot, and a sanitized data file attached via Help > Report a Problem so we can get them added to the ticket.
Thank you!
-Quicken Anja
Make sure to sign up for the email digest to see a round up of your top posts.0 -
Only one of my Capital One accounts has been updating. This is going on for weeks now. I can't even get the account to update manually. It isn't even letting me set it up for online updates.
0 -
Hello @titanrx,
We appreciate you joining the discussion and sharing your experience.
After checking internally, I do not see any errors occurring for Capital One 360 on your account. Could you confirm if you’re seeing the same yellow box error as shown in the screenshot of the original post? Or are you encountering a different issue? If so, please provide more details on exactly what you’re experiencing, including any error codes or messages you receive.
Additionally, please navigate to Help > Report a Problem and submit a problem report with log files attached so we can further investigate.
Looking forward to your response! Thank you.
-Quicken Anja
Make sure to sign up for the email digest to see a round up of your top posts.0 -
Was having the same problem and the suggestion to rename the runtime.dat filename solved it for me. Had been going on the past week (and this is 3/19/2025).
1 -
Renaming solved my problem too. Thanks.
1 -
Hello @GregSBurns & @Chris Bergerson,
We appreciate you adding to this discussion and confirming that the instructions resolved the issue for you! Glad to hear that worked for you both.
Thank you!
-Quicken Anja
Make sure to sign up for the email digest to see a round up of your top posts.0 -
I suppose the question should be asked as to what happened, why, and why must we rename the runtime.dat file? What changed and is it Quicken or Capital One?
0 -
@Tony Luers We appreciate your questions! At this time, the exact cause of the issue is still being investigated. However, we do know that it is not originating from the financial institution as this error has occurred with multiple different financial institutions. Renaming the runtime.dat file is a troubleshooting step that has helped some users restore functionality, but we are continuing to look into the root cause on our end.
We’ll share updates as soon as we have more information. Thank you for your patience!
-Quicken Anja
Make sure to sign up for the email digest to see a round up of your top posts.1 -
Hi Quicken Anja - just adding my experiences to this thread. I was experiencing the same error message since the beginning of March. The accounts were still downloading transactions but the error message persisted. I followed your instructions to rename and the error message has gone away for me. Thanks for the help!
0 -
Quicken Anja
I appreciate the answer.
When you figure out the root cause, will there be an update sent out to fix it?
0 -
@Chameleon360 You're welcome! Glad to hear this resolved the error for you.
@Tony Luers If our development team determines that a fix requires a future update release, that would be the path forward. However, some issues can be resolved on our end without the need for a software update. While I don’t have those details at this time, I appreciate your patience as the team continues to investigate.
-Quicken Anja
Make sure to sign up for the email digest to see a round up of your top posts.0
