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; } } }

Quicken access to pull down lists slow

steve87@

For the past few weeks, whenever Quicken has to access a pull down list, it takes 20-30 seconds. It has gotten worse with each "upgrade" (so called) to the point where it is unusable. I have been a Quicken user for 35 years and this is the worst piece of garbage I have used in those 35 years. It is taking me a half hour or more to download transactions and enter the categories for each. It used to take about 5 minutes. I have done a file "repair" - no change. My file is on a Samsung SSD, and copying a 1GB file to the drive takes about 2 seconds. My quicken database is about 300K. I can copy the entire file in under 1 second. It seems that Quicken is causing Microsoft Defender to react every time it opens a pulldown list, the Antimalware Service Executable takes up 25% of the CPU resources while attempting to open a pull down list. If I temporarily stop the Antimalware Service Executable it gets a little better but that is an unacceptable solution.

Find more posts tagged with

Windows

Comments

Rocket J Squirrel

QWin writes to disk after just about everything you do. I agree that Antimalware takes over the CPU when QWin is running. I gave up and exempted it from Defender. Other suggestions here:

https://community.quicken.com/discussion/7915476/faq-are-there-any-windows-settings-that-can-improve-quicken-s-performance

steve87@

I've read both of those articles previously.

Background is that I was a road warrior for 25 years, and I never wanted to take Quicken with me on a laptop, so I always ran (and still run) Quicken via RDP (RDCMan) from my laptop to a machine that never leaves my house. It turns out that the slow problem DOES NOT occur on a local console, only on a RDP connection from my laptop. In this case the connection is a Gb switched Ethernet LAN. I have made some adjustments to the RDCMan "Remote Desktop" settings and that SEEMS to have resolved the absolutely awful performance. It is now acceptable. I changed the screen size from "Client" to a fixed 1920x1080 and changed the pixel size from 24 to 32 bits. The "host" computer in this case was running with a 2K monitor and I was using it in a 1K window, with scaling in effect. With the number of times that Quicken paints and re-paints the screen, particularly when opening a pull down, it took forever for the RDCman client to catch up with the remote computer. Thus slow performance. The clue was watching two buttons in Quicken flash a dozen times before the image stabilized.