Patelco CU unable to download for over a month

robinsd
robinsd Quicken Windows Subscription Unconfirmed ✭✭

Hi,
I posted several weeks ago and the issue is still unresolved. I followed the advice given in the Quicken response to my issue after the CU support person insisted it was a Quicken issue and it was up to Q support to fix. Several maintenance releases have come out since then and as of today the issue remains. Q support closed my post before I could find time to respond.

Now the error message has morphed into OL-295-A.

I just tried turning 2FA on the account off and it's now possible again in spite of the website description of it as mandatory.

That, and choosing Patelco-WC as the institution name instead of just Patelco allowed me to finally download current data. Earlier I had followed the advice to reset all my accounts and then finally to remove all online info from all the Patelco accounts.

Now I will go back and re-enable 2FA for obvious reasons and will post a follow up afterwards.

Robert

Update: Turned 2FA back on and now Quicken simply updates my Patelco accounts without the old dialog boxes asking how to verify 2FA or the one that simply has a lock icon and no descriptive text.

I suppose Patelco is yet another victim of poorly skilled outsourcing. This is probably an indicator of other instabilities and vulnerabilities. Time to move to a professionally staffed CU. After 48 years of membership at Patelco I can no longer recommend them to friends and family. Wow! Now I need to get on social and warn all the people I've sent there over the years since 1976.

Comments

  • robinsd
    robinsd Quicken Windows Subscription Unconfirmed ✭✭

    Indeed, here you go:

    https://www.fastcompany.com/91150428/patelco-credit-union-security-breach-update-timeline-what-to-do-ransomware-attack

  • robinsd
    robinsd Quicken Windows Subscription Unconfirmed ✭✭

    I forgot to add that the next time I restarted Quicken following my turning 2FA back on that the transaction download failed exactly the same as previously. I might hazard a guess that there was some bad maintenance on their security infrastructure that finally bit them in the you-know-what in public last week. Problems are not fixed and are much worse than one could have imagined… apparently.

This discussion has been closed.