64 Bit Version (+1 Merged Vote)
Using Quicken Version R33.24 on HP Computer:
Running Windows 10 Home Version 21H1 - 64 bit
Processor Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz 3.19 GHz
Installed RAM 32.0 GB (31.9 GB usable)
Comments
-
Quicken will never have a 64 bit version. This has been discussed many times.
Quicken user since version 2 for DOS, now using QWin Biz & Personal Subscription (US) on Win10 Pro.
0 -
lopisis1 said:I have been using Quicken for well over 10 years.none of your points have anything to do with 64-bit software... or making Quicken run faster.- file size doesn't slow down Quicken - it is just slow
- file downloads also - it is just slow
- multitasking - DOS had multitasking...Quicken is just ... a collection of bits and pieces over the years - and it is now a slow kludge
-1 -
I agree the sluggishness and responsiveness of the UI are really really bad! I have reported these issues many times but never get any feedback. It feels like with each update the UI gets slower and slower and the redraw of the interface is very poor!1
-
Come on guys, it is long past time to up grade the code to 64-bit [removed - speculation/disruptive]1
-
It is time to bite the bullet and convert to 64 bit. I also use Quickbooks and they have just converted it to 64 bit and it is faster in every way. The backups are faster, the UI is faster, the interaction with banks (ie transaction downloading is faster) and they added more features (not fewer) to boot. I am tired of all of the excuses given ie, Look at the Mac update fiasco, there is not way to update the datebase, you will not have all of the features that we currently have etc. etc.I know this will not happen overnight. It would probably take 2 years or so do properly. If Quicken Inc. had started this process when they first bought the program from Intuit it would be done by now! It is not a matter of if but WHEN this will have to be done.0
-
I'm with you guys, I think they need to work on transitioning to 64. The interface is a little sluggish at times. Though their web interface is just fine. I'm sure they're just telling everyone to eventually just use the website.0
-
I have the suspicion that the core Quicken program is ancient and it just doesn't run snappy even on today's SSD's. Would there be any performance improvement moving to a 64 bit version?1
-
No, there would not be any performance improvement. My Quicken runs fine on my current Windows 11 computer.Quicken Subscription HBRP - Windows 10-2
-
Hello @Stuart Boyle,
Thank you for reaching out to the Community with your request.
I went ahead and merged your Idea to this active Idea thread regarding this topic.
Ideas are reviewed by our Development and Product teams to see what features people would like to have available in the future. Please, be sure to add your own vote as well by clicking the up arrow (see example below).
Thank you!
-Quicken Anja
Make sure to sign up for the email digest to see a round up of your top posts.0 -
Thanks for merging. I have upvoted this. With today's modern computer processing architecture and operating system capabilities, a rewrite to an application that can take advantage of these things is long overdue. Hopefully some of the legacy code can be refactored as part of this as well.0
-
And there is the core reason this is never going to happen.tom porterfield said:Hopefully some of the legacy code can be refactored as part of this as well.
The main "legacy code" that is known to be 32-bit and unsupported (as in they can't get a newer 64-bit version of) is the database. And the database is so core to Quicken, they would have to totally rewrite Quicken, and that isn't going to happen. Quicken Mac started a rewrite in 2007 which to the day isn't completely done.
What's more going to 64-bits doesn't actually provide any performance improvements in itself.
Performance problems have to do with bugs, or how the code is written. The only exception to this would be if the code was already written to take advantage of all the memory available and it was "memory restricted". The current code doesn't even use all of the memory it has available with 32-bits.
Signature:
This is my website: http://www.quicknperlwiz.com/0 -
BTW I got to log the original post:
What does using 32-bit/64-bit have to do with downloading transactions or multitasking?lopisis1 said:File downloads from financial institutions take forever and nothing else can be done until it is finished. In this day and age multitasking is essential.
This whole request seems to be based on a false assumption that they are connected in some way.
They aren't.
From what I see Express Web Connect accounts are done in parallel. Direct Connect are done serially, but that seems to be tied to the way the connection is made, the underline code must be using something that is "global" and such can't have multiple instances running at the same time.
But like I said this has nothing to do with 32-bits vs 64-bits.Signature:
This is my website: http://www.quicknperlwiz.com/0 -
> @Chris_QPW said:
> And there is the core reason this is never going to happen.
>
> The main "legacy code" that is known to be 32-bit and unsupported (as in they can't get a newer 64-bit version of) is the database. And the database is so core to Quicken, they would have to totally rewrite Quicken, and that isn't going to happen. Quicken Mac started a rewrite in 2007 which to the day isn't completely done.
>
> What's more going to 64-bits doesn't actually provide any performance improvements in itself.
> Performance problems have to do with bugs, or how the code is written. The only exception to this would be if the code was already written to take advantage of all the memory available and it was "memory restricted". The current code doesn't even use all of the memory it has available with 32-bits.
I honestly couldn't care less what they've tried in the past or what they need to do to modernize the application. I write computer software for a living, I understand a lot of the issues that can be faced with keeping an application current and modern.
Every time my license comes up for renewal I look around for alternatives. At some point the alternatives will be better than what Quicken is offering and I will leave. Quicken either needs to realize that at some point they will lose more customers and their money over this than what they are saving by doing nothing. You say it will never happen. I can promise you that it either will happen, or the product will die.2 -
I fully expect it to die, eventually.tom porterfield said:You say it will never happen. I can promise you that it either will happen, or the product will die.
EDIT. And I can tell you that some long-time users are betting that "eventually" isn't too long off. But they think that not for 64-bits, they think of that because of all the bugs and problems Quicken has.
Signature:
This is my website: http://www.quicknperlwiz.com/0 -
Quicken is more and more a very fragile house of cards.....
- legacy software that is so intertwined, that touching it causes all sorts of issues.- the entire financial downloading, protocols, 3rd parties, etc - makes it all the more heading toward the iceberg.And folks want Dark Mode and 64-bit - as if any of that really matters when Quicken crashes, introduces old bugs, can't even install like most other software programs, and the interface to outside 3rd party Intuit for proxy downloads from financial institutions, along with the financial institutions changing the game.... and don't even touch the Quicken Cloud and SYNC to Mobile App.1 -
Quicken has become sssooooo ssslllooowww that I will not renew unless there is a 64 bit version to try. Quicken user for 20 years with data entry (stock purchases) back to 1984 - 38 years. It takes quicken about 2 minutes for one transaction entry without splits, those take longer. The program "bounces" off my screen to where just the minimize, maximize and close buttons are barely visible. Quicken has become a complete bloatware aggravation to use. It will be easier for me to learn and create a database for transaction tracking. In addition to quicken I have always kept bank account registers in a spreadsheet, so these are not idle words to say it would be easier to work in a database, or simpler to work in a spreadsheet. Quicken should announce that a 64 bit version is "in production" and ask for beta testers to verify their work. I like the features we have, but the pain of using the program has become intolerable. Quicken, your users have told you what you need to do if you want to continue to succeed. Ignore customer complaints and they will go away - both the complaints and the customers. Quicken R44.38 Windows 10 Pro, 16 GB RAM, 1 TB SSD, NVIDIA GeForce 940MX w/ 2GB Video RAM, Intel Core i7-7500U CPU @ 2.70 GHz (4 CPU's), ~ 2.90 GHz. Also, my membership valid until May 21, 2023, so that is 189 days from today. So let's see the request for 64 bit beta testers by January 13, 2023 (two months for Quicken to have some strategic business meetings).0
-
@Sunrise_Mike a 64-bit version would do nothing to improve the speed of Quicken. Plenty of people on here have very large/old Quicken data files with no performance problems that you describe.Signature:
This is my website: http://www.quicknperlwiz.com/1 -
Wouldn't a 64 bit version only increase the addressable size of the program code? So I think unless the current version is around 4GB or bigger, would 64 bit version help? Now if a complete rewrite was done, I would bet Quicken would be faster. I was using Quicken back on DOS when living on the farm. If that code has just been added to and modified, well putting it nicely, it isn't going to be as efficient as a newly designed system. Reminds me of a program I once changed from a tape file for data, to an ISAM file and later to a Total database. What a mess that thing was to change just to keep up with state and federal regulations.
0 -
About the only thing it could do for increasing the performance is increase the amount of memory Quicken can allocate over 2GB (there is no limit on the size of the code). Note in some case machines this can be 3GB or maybe even 4GB, but never more than that in a 32-bit program (holding down Shift and selecting Help -> About Quicken will show how much it can allocate). The thing is that Quicken is already caching the information when it goes to use it. That is why opening an account the first time might be slower than opening it from then on. But try something open up the task manager and see how much memory it is using. Then open all your biggest accounts so that they are cached, and then do One Step Update and look at how much memory Quicken is using.Divemaster said:Wouldn't a 64 bit version only increase the addressable size of the program code? So I think unless the current version is around 4GB or bigger, would 64 bit version help? Now if a complete rewrite was done, I would bet Quicken would be faster. I was using Quicken back on DOS when living on the farm. If that code has just been added to and modified, well putting it nicely, it isn't going to be as efficient as a newly designed system. Reminds me of a program I once changed from a tape file for data, to an ISAM file and later to a Total database. What a mess that thing was to change just to keep up with state and federal regulations.
Here is mine.
And I want to note that the "Windows host processes" are just that processes and each process can allocate the 2GB.
So, even with caching everyone of my 20 accounts the main Quicken process is allocating less than 200MB.
Quicken's bottlenecks are not in the areas of where 64-bits will help.
They tend to be in four spots from what I can determine.- Network, and this can be the biggest time. If Quicken has problems with talking to its servers, it can hang for long periods of time.
- Corrupted data files.
- Badly designed GUI objects, like the investment account register is a hot mess of controls.
- Doing unnecessary refreshing/calculations. For instance, I think one of the reasons the investment accounts are so slow when they have a number of transactions (above even the terrible GUI controls) is that they seem to be recalculating all the information for the security lots for the whole register every time anything is updated in the register or even outside it when it is being displayed.
Yes, there are things that one might do to improve Quicken's performance but going to 64-bits isn't it.Signature:
This is my website: http://www.quicknperlwiz.com/2 -
I have the same issuse, but I am running on Intel i7 12th gen CPU with 64 DDR5 ram Windows 11. When I run Quicken, and I check the task manager, one core is usually running 100% 4.someting GHz.
0 -
Oh, I forgot, but my is slight faster, just slightly around one second most of the time, you almost can finish "one thousand and one". Once awhile, it takes almost one minutes. I got Quicken under one minute by changing the power setting in Windows 11 Pro to performance, and fans are running full power, like a hair dryer. I think Microsoft is no longer supported e-core and p-core for 64Wow. Quiken is running like installed in a i386 computer.
0 -
You should switch to the Mac version as it is faster and uses a modern database. It has most Quicken Windows features but not all. But what you get in speed and modern interface more than compensates for the old 32-bit Windows version. I switched to the Mac version as of Aug 2024 and never looked back.
Quicken Mac Premier Starting 8/2024
Quicken Windows 2000-2024
Successfully moved to Mac with thousands of transactions and stock/option trades. Quicken Mac handles large files a lot faster.
0 -
I absolutely REFUSE to pay for over-priced, proprietary, APPLE products (or Q's fawning of them). Particularly when they're feature-deficient in comparison to the Win counterparts.
You're welcome to waste your money any way that you want … but I won't slavishly follow.
Q user since February, 1990. DOS Version 4
Now running Quicken Windows Subscription, Business & Personal
Retired "Certified Information Systems Auditor" & Bank Audit VP0 -
Kind of ridiculous that they still don't compile for 64 bits.
At times it's extremely sluggish and everything on my modern computer slows down (Windows 11, Processor 13th Gen Intel(R) Core(TM) i7-1365U 1.80 GHz, Installed RAM 32.0 GB (31.6 GB usable).
This is long overdue.
0 -
Going to 64-bit isn't a magic bullet. There isn't anything in it that will magically speed up the current code just because you convert it to 64-bit, other than maybe a very marginal amount. The real performance gains would be found in rewriting core code that is currently performing badly. This just as possible in 32-bit as it is in 64-bit, actually more possible. It is pretty well known that there are core parts of Quicken that depend on code that aren't supported anymore and as such there isn't any 64-bit version them, and to change them out would require more work than Quicken Inc can muster.
Signature:
This is my website: http://www.quicknperlwiz.com/0 -
Sounds right, from what I remember (been retired from IT system software 21 years now). 64 bit just allows bigger address spaces to process more data, I think you would have to change code to take advantage of that ability? But then now days I would be considered a dinosaur in the IT world, so take that with a grain of salt.
0 -
That is correct, and frankly I don't see much opportunity to take advantage of that extra address space without changing some very core parts of Quicken, which would be beyond what they can do with the personal they have and without disrupting the current user base and taking years to do it like the rewrite of Quicken Mac is taking.
People might not realize it but Quicken is already caching each register that you open, and still, it has more memory than it needs for such processes with just the 32-bit address space. I can't imagine what more they could cache.
Every test I have done to try to locate performance bottlenecks suggests that the problems aren't where most people think they are. For instance, people point out how old the database is. It could certainly use updating to be more robust, but from what I can see it performs quite well. For instance, it does well when running reports. If you think about an investment report, it needs to retrieve even more data than what would be for a single investment register. But when people report problems with performance it is almost always in the investment register (while at the same time the reports are fine).
There are also performance problems that seem to be network/Internet related, 64-bit isn't going to affect that. Then there are the problems that some people report where everything seems to run slow. Given that the majority of people don't have this problem clearly that isn't related to 32-bit/64-bit. What it is exactly is never really been pinned down other than in some cases a corrupted data file.
And the last category I would have state is just general GUI performance. That one I think is related to the fact that Quicken has so many different GUI libraries/interfaces. And for that one has to realize why this condition exists in the first place. Quicken has a ton of features, and still people want more. Quicken Inc doesn't have the resources to add such features, work on the bugs, and still have time to re-write parts of Quicken in the newer GUI libraries. For instance, the Tax Planner, parts of the Lifetime Planner, and a good portion of the Business "forms" are within in a library that has been around since about the late 1990s.
Signature:
This is my website: http://www.quicknperlwiz.com/0 -
My perception is that Quicken's development staff is stretched pretty thin. In view of that, I think we need to be thoughtful in what we ask them to add/improve. 64-bit code looks to me like a "shiny new thing" (OK, not new) that isn't going to mean much in a practical sense.
2
