Quicken is S L O W - Everyone affected Please chime in.

I respectfully disagree with the premise that “the problem is not with Quicken.” On my system, Quicken is the only application that exhibits profound performance issues. Other, far larger and more compute-intensive applications, such as Photoshop run great. Some of my Photoshop files, especially for panoramas, exceed 1GB in size. Other transaction- and I/O-intensive database applications also run just fine. It is only Quicken that moves like cold molasses.

I’m currently traveling and will install R51.12 when I get home.

I'm affected too!!!! updating to R51.12 now to see if it resolves, not looking too good…

@bboese that is the latest update for the Canada version. Other Canadians have said it seems to solve the issue but they also say it slows back down. Let us know after you run it for a few days if it is still faster. I hope it says fixed for you. Then they can fix the US version.

@Boatnmaniac You are correct that those Windows updates became available on the dates you posted. If you search the community the recent slowness issue pre-dates those releases. I appreciate you posting the Windows update dates. Not only are Win11 users talking slow but Win10 users are too.

As a precaution I have my computers set to NOT automatically install any Windows updates. Been that way for years. I didn't install those windows updates prior to my early posts here. Like with Quicken updates I wait for sometimes weeks or longer especially with major updates. This thread started on 6-5-2023 and many other threads before that.

I think we can agree that "something" is causing the slowness. All we, as Quicken customers, can do is post, send logs, troubleshoot our own stuff and etc. The resolve rest clearly with Quicken.

I think, my opinion, is that if an update by Windows is causing the issue then Quicken is no longer compatible and Quicken should interact with Microsoft and strive to get it fixed.

@retird - one of the critical business issues that Quicken has is that they operate the software on distributed platforms - meaning it operates on everyone's laptops/ computers - and there are literally thousands of permutations of how these computers are configured and how they may complete with other software packages placed on the computers. This was just the way it was in the 1980s when QUicken was first developed.

We can't expect Quicken to troubleshoot each and every computer in America. My point is unless EVERYONE is experiecing the SAME issue, the problem points to the individual's computer and NOT the software.

Therefore, when someone offers a suggestion on these boards - and we are all doing it blindly - best to take up that suggestion and try it.

You are assuming the root cause issue is with Quicken's software; I suspect the root cause issue is your computer, since not everyone is experiencing what you are experiencing.

Further, this issue has to be broken down into multiple issues.

a) the performance when simply entering transactions.

b) the performance when launching the software (since there is a call routine to the mother ship to confirm the account.

c) the performance when conducting OSU. This also requires a call routine to Quicken's data provider (Intuit) and if some of the FIs are now running EWC+, that is a separate, more intensive set of call routines that take longer. And each FI may have different server configurations which further adds variation to the performance any individual user may experience.

@Mark1104 the last item of your post "c" could easily point to at least one reason for OSU slowness. I have been considering that as possibly one of the "Elephants in the room" for some time. So Quicken startup may be slow but once loaded runs fine. Windows treats 32 bit software differently than 64 bit. Only other slowness here then is with OSU's. All these financial institutions I use involve the Intuit servers to transfer data and runs slow.

Try talking to Intuit tech support. I have tried numerous times when issues came up with Quicken or a financial institution where Quicken points the finger at the financial Institution and the finanial institution says it is Quicken. You can't talk to Intuit and Quicken IT tech support will tell you they have no phone number they can give you so you can talk to them. Financial institutions IT tell me they can't give you the number for Intuit either.

You might want to read about the changes Intuit instituted May 31, 2023 with it's platform and supported products. Did this have an effect?

I, or others here, have tried all suggestions here I think. None bare fruit. I think the only suggestion (guess) I did not personally do was Safe Mode as others did that.

The best suggestion offered here was to "Report a problem", sanitize the data file, and send to Quicken. Many did this and many more did not. I'll ask you the same thing. Please send Quicken the same thing we sent them and in the comments tell them you are not having the slowness problem. They can compare yours to ours and possibly aid in tracking down the cause. They are still working on this according to the last update (you have to go to the Alert section in the community and scroll down to find it) and they have no time frame to resolution.

I disagree with @mshiggins requarding the agreement of what @Mark1104 and @splasher say.

@retird

«All these financial institutions I use involve the Intuit servers to transfer data and runs slow.»

what makes you so sure? I am far from a networking expert, but it's my understanding that the security of EWC+ causes the data to travel quite directly from the FI to my computer. Permitting the transactions to travel through Intuit or Quicken would appear to compromise the secuty intended by the EWC+ approach.

Futher, I am not even aware that the 'direct connect' method involves Quicken servers - all the data comes from Intuit as the data provider is my understand. That creates another issue in determining 'root cause' - most moving parts of OSU are simply not in Quicken's control.

@mshiggins You might not personally care what’s in these files, but you can be proud that you are part of a shared, communal effort to solve the mystery that is Q’s ultra-slow performance.