nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

OL-290-B for Vanguard

Jack Scripps

Got a different error yesterday for this institution, but this error received when I tried to update today. Tried several ways. One-step update. Direct update for that institution. No joy. Also, went to Vanguard website and all is in order there. Problem seems to be with Quicken.

Find more posts tagged with

Known Issues

Windows

Direct Connect

Comments

Sceptic

@Jack Scripps if this error occurred after updating to R70.20, here is a Quicken Alert for this error. Quicken is currently investigating this issue.

https://community.quicken.com/discussion/7977559/update-11-6-26-multiple-financial-institutions-ol-290-b-error

This is a current thread discussing the issue.

https://community.quicken.com/discussion/7977556/ol-290-b-error-multiple-financial-institutions-direct-connect

The suggested workaround is to revert back to R69.53. The instructions and link to the prior release is contained in the Quicken Alert.

cyberphile

This is what is in the CONNLOG.TXT log when I try to update my Vanguard accounts (which use Direct Connect):

==== Mini-OSU Start (20261108/10:14:41) ====
20261108 10:14:41: QFN: Beginning send to https://ofx-prod-brand.intuit.com/qw2800/fib.dll
20261108 10:14:41: QFN: End send to https://ofx-prod-brand.intuit.com/qw2800/fib.dll, netstatus 0
20261108 10:14:44: QFN: Beginning send to https://services.quicken.com/ofx-secure-plus/15103
20261108 10:14:44: ***QFN kQFFinished: returns 67119177
20261108 10:14:44: HTTP 404 Not Found
20261108 10:14:44: ***QFN ICInitiate: 67119177
20261108 10:14:44: QFN: End send to https://services.quicken.com/ofx-secure-plus/15103, netstatus 10
20261108 10:14:44:

==== Mini-OSU End (20261108/10:14:50) ====

It last worked Nov 6, 2026 at 8:40am Pacific time.

Quicken James

Hello @Jack Scripps & @cyberphile,

Thank you both for sharing your experience.

As @Sceptic provided, this is a known issue, and he provided the Quicken Alert.

Our team is currently investigating the issue and has suggested to revert back to the version R69.53. No ETA or further details are available at this time, and we will update the alert as more information becomes available.

We apologize for any inconvenience and appreciate your patience.

I hope this helps.

M@rk$%^&

Same issue as identified—OL-209-B error Vanguard. It would certainly seem that this would be tested PRIOR to update certification?

Jack Scripps

I am wondering whether or not to go back to R69.53 at this time. Two concerns: Loss or corruption of data already downloaded, or the possibility of duplicate data downloaded after the reversion to the earlier release of Quicken, and whether I should try first to deactivate the online connection for the one institution that is "broken" and then reconnect to it? The other institutions (4 or 5 of them) all seem to be working OK. Finally, since this is so widespread, I would think that the Quicken teams would be burning the midnight oil to fix it with another update?

tlsher

I see the same error for Vanguard and agree regarding testing.

This issue is not a lack of testing related to any particular release. Users with older releases of Quicken, as well as Mac users are experiencing similar errors.

Quicken James

Hi @Jack Scripps, @M@rk$%^&, @tlsher, @BK,

Thank you for providing the information and letting us know you are experiencing the issue.

As I have stated above, this is a known issue. Currently we are asking those receiving the OL-290-B error to revert back to the previous build, R69.53. Doing this should allow you to continue downloading from your bank while our teams look into a resolution for the newest build.

https://community.quicken.com/discussion/comment/20585391#Comment_20585391

We apologize for any inconvenience and appreciate your patience.

Thank you!

nerdindenial

I downgraded to Quicken 69.53 for Windows as instructed.
Now I get error OL-295-A.

@Quicken James,

In my extended family, we are on two separate releases of R69.xx and another on QMac. We are all experiencing connectivity issues with Vanguard. So suggesting to revert to R69.53 is only counter productive. I suggest that you review this Alert to recognize that this issue is not related to R70.20 or QWin, rather it is more widespread. I am confident that this will be fixed soon. Regards.

cyberphile

I tried setting up my Vanguard Investments accounts on a test machine that is running Quicken Deluxe Classic R69.26. During the connection creation I am getting an OL-295-A error just as @nerdindenial is getting. The CONNLOG.TXT file is reporting:

==== Mini-OSU Start (20261109/09:14:11) ====
20261109 09:14:11: QFN: Beginning send to https://services.quicken.com/ofx-secure-plus/15103
20261109 09:14:12: ***QFN kQFFinished: returns 67305876
20261109 09:14:12: We re sorry, but the application could not find an item on the server that it needs. Try again now, or wait and try later.
20261109 09:14:13: QFN: End send to https://services.quicken.com/ofx-secure-plus/15103, netstatus 15
20261109 09:14:14:

Notice that there is an error with the access to https://services.quicken.com/ofx-secure-plus/15103 just as there is in R70.20. This would imply a more systemic problem with Quicken's startup processing. So there is now the apparently same problem with R69.23, R69.53, and R70.20.

nerdindenial

After unsuccessful 69.53 downgrade I tried deactivating and reactivating but still get OL-295-A.

Quicken James

Hello.

Thank you for the information you provided. I am aware of the alert you provided, as it is a new one from this morning. This post is one for OL-290-B that we also have an alert for and affects multiple banks not just Vanguard. The steps provided are from our escalation team.

You are correct that at this point, reverting to R69.53 will not work, as you will get the new error OL-295-A for Vanguard. That error did not start trending until this morning, and when I responded here, it was not out yet.

Prior to this morning, users were able to revert back and the connection was successful, meaning there is also an issue with the release R70.20.

Thanks again.

Quicken James

Hello @cyberphile and @nerdindenial,

Thank you for providing that information.

We now with Vanguard have a known issue that started trending this morning where users are getting OL-295-A. Here is the Community Alert. We appreciate your patience while our teams work on a resolution.

Thanks again.

[Ticket #12671101/CTP-19232]

Robert Chiarulli

I have same issue when updating my Vanguard accounts.

user17881

11/10/2026. Still an issue this morning. Still got an error on OSU. So I tried to reset my Vanguard account, at which point Quicken froze. So I DEACTIVATED online access for the account, and then when I tried to re-establish the connection, received message: "We encountered an error while connecting to your bank. Quicken is having trouble connecting to Vanguard." [Edited - Readability]

skondolf

Not sure if I'm posting this in the correct location, but I wanted to mention that I, too, am having issues trying to connect to Vanguard, so I followed the instructions for reinstalling Quicken and using the previous 69.29 version. When I attempt to connect to Vanguard, I still get the connection error, but this time the error message is OL-295-A, and the text says that my financial institution's server is not currently accepting requests. I'm assuming Vanguard has shut down the server due to this issue and may be working on installing a fix.

Can anyone at Quicken confirm this? [Edited - Readability]

Quicken James

Hello @Robert Chiarulli, @user17881, & @skondolf,

Thank you for letting us know you are experiencing the same issue.

This is a known issue with Vanguard, and our team is working towards finding a resolution. Here is the Community Alert we have up for this. We appreciate your patience while our teams work to resolve it.

Thanks again.

[Ticket #12671101/CTP-19232]

AJH3

OMG, I have been using Quicken for decades and, unfortunately, there is almost always an issue with connecting to a major financial institution (credit card, bank, credit union, and/or investment) with every release. Certainly a more disciplined testing should be performed BEFORE these are released to the general public because issues like this OL-290-B one are frustrating and the half-baked "interim fixes" thrown out by Quicken usually end up creating larger issues for the customers, like data corruption or even data loss, which is even worse.
Quicken, can you start testing and re-testing BEFORE releases? My IT people always did that for software we developed for in-company use, and we never had such onerous issues.