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

OSU makes whole PC unresponsive during updates in Windows 11

spalt

As we all know Quicken has never been a very good app in terms of performance or responsiveness, but now after upgrading to Windows 11 I am finding when the OSU process is running, my entire PC becomes unresponsive for the few minutes it takes to finish. MS Teams — can't send messages. Chrome — can't type in the address bar. The list goes on. What the heck is going on?!

I also find this hilarious…. hmm which one of these things is not like the other 🤔😂

Find more posts tagged with

Comments

Snorkle

I have been running quicken on windows 11 for about 4 years and have never experienced what you are reporting. OSU does tend to be slower than I would like from time to time but not to the detriment of system performance. I just ran task manager and monitored the cpu usage of qw.exe and it was using at most 1%. My PC has 32GB of RAM and has an Intel 11th gen i5 processor with SSD storage. Before upgrading my PC hardware I was running windows 10 with only 16GB RAM, an older processor (can't recall the model) and a conventional hard drive. That machine did not run much of anything very well. BTW my internet download data rate is about 690 Mbps.

spalt

interesting. i have a i7 w/ 32gb RAM and a 500gb SSD. this is a dell laptop managed by company's IT dept and they have been very wary to upgrade to windows 11 which is why I got it just a few weeks ago. my quicken file is 336mb with tens of thousands of transaction so that probably doesn't help matters….

https://community.quicken.com/discussion/comment/20452889#Comment_20452889

Snorkle

Hmm. Not a hardware problem then😊. My quicken file has about 30K transactions and is about 140MB.

jtemplin

And x64 isn't the performance magic wand folks think it is. Not the issue.

spalt

https://community.quicken.com/discussion/comment/20452899#Comment_20452899

i wouldn't be so sure. the fact they haven't switched over after all this time suggests… well… a lot of things. my point is it's a bit funny that on my system with hundreds of processes running, only a very tiny subset is still x86, and quicken is one of them.

jtemplin

https://community.quicken.com/discussion/comment/20452903#Comment_20452903

Windows developer here for a product with an old 32-bit code base much like Quicken. There are other threads here which discuss the difficulties of migrating an old code base to 64-bit, so I won't rehash those. You can search for "64-bit" to read those threads.

But to summarize, it is highly unlikely (I think more like never) Quicken will ever get ported to 64-bit; it would require rewriting too much old code/libraries that don't have 64-bit equivalents. That's the reason they "haven't switched over after all this time". The cost to benefit ratio is too low given desktop financial software is going the way of the dodo.

There are plenty of Windows apps that are 32-bit and will remain 32-bit for similar reasons. And they work just fine.

Your performance problems lie elsewhere.