From Feb 20, 2025, of course Vanguard is issue, but other non-Vanguard One Step updates failing

Been "fine" through Feb 19.
All these One Step Update issues started from Feb 20, starting with Vanguard OL-295-A. Then other updates.
What's happening here all of sudden for non-Vanguard One Step updates?
Anyone seeing issues with non-Vanguard accounts?
Up to date with latest updates for Quicken Classic Deluxe for windows.
Thanks!
Comments
-
One more to add:
Quicken Classic for Windows Premier R61.20
0 -
Same!
0 -
Hello All,
We appreciate you bring these errors to our attention!
First, please be aware that the issue with Vanguard is a known issue and has been escalated internally, though we do not have an ETA on resolution at this time. While the investigation remains ongoing, please refer to this Community Alert for any and all available updates.
As for the other errors you are receiving in yellow with multiple financial institutions—our teams are looking into this and working on getting it resolved. However, our development team also believes that this is a problem in the runtime.dat file, and recommends the following steps below to correct this issue.
First, please run One Step Update. If the issue persists, follow these steps:
1. Rename the runtime.dat file found at C:\ProgramData\Quicken\Inet\FILENAME\. (For example, add a 1 at the start of the file name, so that it reads 1runtime.dat.)
2. Run a One Step Update (OSU) again to confirm the issue is resolved.
Note - The Program Data folder is hidden by default. If you need instructions on unhiding the folder, you can find instructions on Microsoft's support site.
Please let us know how it goes!
-Quicken Anja
Make sure to sign up for the email digest to see a round up of your top posts.0 -
I am experiencing the OL-295-A problem with Vanguard for about a week. I have not occured any other issues regarding updates for my accounts inin Quicken Classic Deluxe. I contacted Vanguard this morning. They were going to write a repair ticket. they wanted me to upload log files to their IT department. I did not know how to do this. After an hour of research, I was able to loctae and save the log files. Re contacting Vanguard was a waste of time. They would not put me in contact with their IT department. They referred to it as internal research. The stated it was a third party issue and hung up. Do not waste your time contacting Vanguard.
3 -
yes, Vanguard customer service has been diminishing for years. They do not care about its customers. Yet, We are Paying Quicken for our tracking services and Quicken is responsible for fixing this issue. Otherwise, why use Quicken anymore?
1 -
Howdy All. Had a voice chat with Vanguard today (2/25/25). I ensured they opened a ticket and dispositioned with note to reach back out to me when resolved.
2 -
Thanks for sharing!
-Quicken Jasmine
Make sure to sign up for the email digest to see a round-up of your top posts.
0 -
This is starting to worry me. I brought this up to both Vanguard and Quicken on 2/21. Quicken agent contacted their server folks and they confirmed a problem with Vanguard on 2/21. I was given a case number to identify if "fixed". Seems like the communication could be a little better as to what might be causing this. If first identified on 19th per something I read on the feed, I am not sure why my call-in on 2/21 seemed to be brand new "news" to both sides!? Not inspiring. If all Quicken users have lost there access to Vanguard, that would seem to be a very BIG deal!? Temporary outages is one thing, but flying blind for a week is not something one would expect with such minimal response?
1 -
Well—Followed your steps—After Inet—-No Filename shown!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
0 -
Thanks for letting us know, I have send this information to my team!
-Quicken Jasmine
Make sure to sign up for the email digest to see a round-up of your top posts.
0 -
Hello All,
We are actively investigating this issue further and would like you to try these steps again, now with an additional final step:
- 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.)
- 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)
We appreciate your help and will update you as soon as we have more information!
-Quicken Jasmine
Make sure to sign up for the email digest to see a round-up of your top posts.
0 -
I want to share my feedback about the above mentioned workaround. As you can see from the screenshot below, i have attempted several times to do this workaround. Initially they worked from Feb 26. But lately in all of March the result is not good. I'm continuing to get these errors, CC-502, "… is reporting connection issues", "… is blocking transaction download".
Prior to Feb 20, OSU has been reliable. Sure there was glitch here and there, but not like what is happening right now.
What is happening lately?
Please help!
0 -
Thank you for coming to share this information, I have forwarded this along to my team.
-Quicken Jasmine
Make sure to sign up for the email digest to see a round-up of your top posts.
0 -
Ever since the February update, I lost connection to Capital One and Vanguard. Of course Vanguard was a known issue. I had to deactivate & reactivate all my other accounts. Now crashes when downloading transactions
0