Discover Bank

How does one roll the version of Quicken back to 49.29?

I just tried the method from MintUserNew and it worked for my Discover Card, but not for my Discover Bank savings account. Someone above said that trying to reconnect to "Discover Bank" was a no-go and they were right. I could not find another name to use for Discover bank, so that means I can download my credit card transactions, but not my savings account transactions. This result suggests to me that there is still some sort of working relationship between Discover and Quicken and that the inability to download Discover Bank account data is strictly a Quicken problem. Applying Occam's Razor to this problem, it seems clear to me that whatever changes Quicken made going from R49.29 to the next version are responsible for the loss of connectivity to Discover Bank. I'm also thinking that unless that gets fixed first, the next iteration from R50.16 will simply re-introduce the problem and I'll need to go thru the process for addressing the Discover Card issue all over again.

This is pretty sad, Quicken.

This "known issue" needs to be re-escalated++

C'mon folks. Get this fixed!!

Anyone tried installing QW27.1.49.29MPatch.EXE on another system, adding Discover accounts, and the exporting the data?

Then importing that data back into my main 1.50.xx quicken system? Is it possible?

@bmchollan Looking at the release notes for the releases after 49.29 nothing is labeled as fixing security vulnerabilities. So I guess you just have to decide if you trust Quicken's documentation of what's included in each patch.

Thanks! Yes, I tried. Downgrading to a prior version worked for me so I'm just going to wait now for it to get fixed I guess.

I currently maintain 3 Quicken files, two of which contain a Discover debit account and a savings account. What's interesting is that I'm only experiencing this problem in 1 of the 2 files. The other file continues to update the Discover Bank accounts via Express Web Connect (not EWC+). I have not yet been forced into an update to EWC+ in that file. I have no idea what's different between the two setups but there does appear to be some inconsistency.

Rick11 - That's exactly what Discover told me as well. I'd feel a lot better about Quicken if they would just be transparent about this. So very disappointing! This product is going downhill month by month.

Even though Discover doesn't SUPPORT the Quicken-Discover interface, doesn't mean Discover doesn't provide some interface that Quicken can work with. Now if Discover says we don't support ANY programmatic data exchange, then Quicken (and us) is/are out of luck.

For those that are interested:

Intuit sold Quicken in April of 2016 to H.I.G. Capital, a Miami-based private equity firm. Then in September 2021, five and a half years after being acquired by H.I.G, they sold Quicken to Aquiline Capital Partners.

Somewhere along the way, it became more about profit and less about quality. Quicken has been laden with software issue for several years now, (most of time, Quicken Support will not admit they have an issue), and when they do, it takes them months on end at best to resolve it.

I am frustrated and I don't have the time or patience to wait them out while they do basically nothing to resolve their issues and the fact that they do not provide any transparency.

I am asking on this open community forum, does anyone have a decent alternative software that they have tried. If so, please share your experience.

I just determined that a couple of my previous comments had been deleted from this forum, so I'll resurrect a couple of the salient points that I think will inform the ongoing discussion of the relationship between Discover and Quicken.

In an extended conversation with a Discover representative, the individual first stated that there was no relationship between Discover and Quicken, but their comments subtly changed when they said that downloading transactions could be performed by using Web Express Connect. I think that the Discover people have been interpreting the question incorrectly. I think they assume we're asking if Quicken is a part of the Discover business (think financial subsidiary.) Seen in that light, the answer that they give makes sense - Quicken is not owned by Discover or Discover's owner. It was apparent to me by the end of the conversation that Discover and Quicken DO have an agreement about downloading transactions. It was also clear to me that the issue here (some some sort of handshake between databases) is something that only the Quicken people can fix.

So this whole thing is kinda a mess.

From my understanding the issue that started it all, was in May sometime where automatic downloads (OSU) weren't downloading transactions (but no errors). Apparently Quicken Tech support is NOT aware of this issue (I've spent an hour with them so far). If you deactivate the Discover connection, you won't be able to reactivate (CC-501 errors). However, if you rollback Quicken and then reactivate, you can, apparently (unofficially) get the Credit cards to work, but not banking. Quicken Tech support is also unaware of the CC-501 errors AND the rollback/update issue as well.

So I have NO idea what the Community Alert is for Discover when none of the 3 items above are "known" issues (according to the Tech Support rep I'm working with).