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

Crashes once updating to R67.7

jmaino

I updated to R67.7 yesterday, and started to experience random crashes during investment register/transaction entry or managing the Security List on at-least 3 occurrences within a few hours.

I downgraded back to R66.23 and have not experienced a crash since, with the same data-file. No reboots of Windows occurred in between, so it appears to be related to R67.7 in this case.

I also experienced what appears to be a GUI issue; my investment transaction was entered and showed on the screen, but the GUI did not show me, nor did it permit me to scroll down to a new, empty transaction. I could scroll upwards through transactions, but it was stuck in a state where it would not show nor allow another new entry to be made below the one last entered. Closing and restarting Quicken cleaned things up so that I could enter new transactions.

I will try R66.28 next to help further determine where a change was made that started this.

Is anyone else experiencing similar? I'm looking for suggestions on how to best isolate so that I can provide additional detail/bug report with useful info to the development team.

Thanks

Find more posts tagged with

Windows

crashing

Comments

Quicken Carlos

Hi @jmaino,

Thanks for your reply and for following up.

Due to the nature of this issue, the next step is to escalate it. The previous escalation with our Technical Support team was not completed because the uninstall and reinstall process resolved the issue at that time.
I recommend contacting Quicken Support once more for further assistance. They can guide you through additional troubleshooting steps in real time or escalate the case if necessary.

Phone support is available Monday through Friday, from 5:00 AM PT to 5:00 PM PT.

When contacting support, it may also be helpful to mention that:

The issue previously appeared resolved after reinstalling Quicken
The problem has since returned
You may also ask for the escalation ticket number.

I hope this helps!

jmaino

It just crashed again for me - on both machines - following the same sequence.

Entering a new short option position, creating a new security. However, this time, the wildly large number that showed-up in the register Share Bal column was positive on one machine, and negative on the other. But, both crashed when trying to get that number corrected.

I think I'm going to have to go back to R66.28 at this time.

jmaino

I'm now on R67.10 and sadly, I'm still seeing crashes - and I'm seeing them while doing the same things on multiple machines (not sharing a datafile - separate copies of the same datafile) so it does not appear to be a single installation/machine issue. I've uninstalled/deleted/re-installed Quicken on both.

In this most-recent crash (again, no Fatal reporting dialog showed up), I entered a new short option position in a new manually created security - and while I entered 100 shares short (1 option contract in my case), after doing so, the share balance that was shown in the register was an extremely large positive number (in the millions or 10's of millions) - but a different large number on both machines. This was a brand new Security that Q never knew about prior to this, so there were definitely no shares known of prior to the entry.

I took 2 different paths on the two machines - and both crashed.

On 1 machine, I went to the security list, and simply deselected the "Download Quotes" button on the newly added security that had the errant Share Bal displayed. I don't recall if it did so immediately, or only after I pressed "Done", but it then crashed.

On the 2nd machine, I went back to the register entry, pressed the "Edit" button and made no changes but then pressed the "Enter/Done" button. I got the "ring" sound, but then this 2nd machine also crashed.

On both machines, once restarting Quicken, the "Share Bal" column now correctly shows -100 in the register, while making no changes.

So, the data does appear to be in the database correctly in both instances (at -100) .

I'll add that this does not happen for all securities that I create/follow the above path - but the fact that it occurred on 2 different machines both entering the same security is somewhat curious (to me, at least).

On both machines, I had made separate entries prior to the crash earlier today - and had no issues.

(Is something that was changed between R66.2x and R67.x mis-treating a signed number as unsigned in the GUI? I'll pay closer attention over the next several days to see if this only occurs on short positions now that I'm of the belief that I'll continue to experience the crashes unless fixed, or I revert to R66.28 again)

foot

I will wait to see how the brave @jmaino's reinstallation works before I volunteer to go to that much trouble!

Quicken Carlos

@jmaino,
Thanks for your reply and for the update!

I appreciate you following the troubleshooting steps provided by the agent. I understand that you’ll need a few days of entering new transactions before you can fully confirm whether the issue is resolved.

I look forward to your reply!

jmaino

@Quicken Carlos
Thanks - I did so. Agent had me uninstall Quicken, delete the Quicken subdirs under Program Files (x86) and ProgramData, and reinstall Quicken. I won't know for several days, after entering new transactions, if this solves the issue - but will report back no later than mid-week next week on status.

Quicken Carlos

Hi @jmaino and @foot,

Thanks for your replies and for trying the steps above.

At this point, due to the nature of the issue, I recommend contacting Quicken Support for further assistance. They can guide you through additional troubleshooting steps in real time or escalate the case if necessary.

Phone support is available Monday through Friday, from 5:00 AM PT to 5:00 PM PT.

I hope this helps!

foot

I am also seeing frequent crashes. Has happened while entering transactions, and when entering passwords for One Step Update. No error pop-up - the Quicken window simply disappears. Version R67.7, Build 27.1.67.7 on Windows 11 Pro version 29H2 build 25200.8457

I ran "Validate File", which reported 100s of invalid transactions, for "ACCT_d4b", dated 0/0/1900. It reported these had been deleted and/or repaired. ACCT_d4b is not the name of any real account, as far as I know. There were a few errors associated with transactions on accounts I did recognize.

I hoped running Validate File might fix the problem, but I have just had another crash (app just disappears, no error pop-up) while entering a bond purchase transaction.

jmaino

…. and I just experienced this one more time (but again, this time, no Crash dialog appeared). But, perhaps we're narrowing down to something that describes a process to better reproduce.

In this instance, I was entering 4 transactions that had occurred yesterday, but I had inadvertently used today's date for all 4 of them. I went back to edit the first of these 4 (in the register, not via the "Edit" dialog), and upon pressing enter after altering the date, the crash occurred.

I reverted back to R66.28 again, and upon restarting Quicken, all (including the first that I had tried to change before the crash) still carried today's date. So the change I attempted to make did not become sticky in the database before the crash.

Hoping this helps.

jmaino

@Quicken Laura Thanks, but, unfortunately that did not resolve things for me.

I just had another crash while entering an investment transaction - however, this time, it did bring-up the Crash report dialog (unlike all other times prior), and I submitted the details of the crash moments ago.

Quicken Laura

Hi @jmaino,

Thank you for the detailed information; this is very helpful, especially your testing across versions. The fact that the same data file is stable on R66.23/R66.28 but crashes on R67.7 does suggest this may be related to a change introduced in the newer release.

Regarding the Administrator message, you’re correct. Quicken typically discourages running in admin mode. We suggested it only as a troubleshooting step to observe any difference in behavior.

As a next step, it may still be worth running Validate and Repair or restoring a backup from before the update while remaining on R67.7, just to confirm whether the issue is due to any subtle file inconsistencies.

To validate the file:

Go to File
Select Validate and Repair File
Choose Validate File
Click OK

We appreciate your continued testing. Please keep us posted on any additional findings.

jmaino

Hi @Quicken Carlos - no, I never received that screen regarding Quicken unexpectedly quitting the last time it was run. In the cases where I saw crashes with R67.7, the tool would simply exit/close/disappear, and restarting would bring it up as normal again, until the next crash. There are no pending updates on my computer, and when I saw crashes in R67.7 vs none when subsequently downgrading to R66.2x, I performed no reboots either. Only changing the version of Quicken being used.

I've again updated to R67.7 and am trying to run in Administrator mode as you recommended, but received this dialog when doing so, saying that Quicken does not support running as Admin - so, I'm not quite certain this is what you expected when making that recommendation:

qadmin.gif

My user has Admin priveleges and datafile is stored locally.

There are no issues with simple navigation - my issues always seemed to occur during or after the entry of new investment transactions - so will have to wait into this week to know more. I'll report again on additional details and finding once I have something new to enter.

Quicken Carlos

Hi @jmaino,

Thanks for reaching out to the Quicken Community and for bringing this to our attention.

There are several scenarios where Quicken may crash. To better understand the issue, I have a few questions:

Is the error you’re seeing the same as the one shown in the image below?

If so, does the same behavior occur after restoring a backup?
Are there any pending updates on your computer?

I also recommend trying to run Quicken as an administrator:

Right-click the Quicken icon
Select Run as administrator

Then, try navigating to the Investing transactions to see if the crash still occurs. If it works without crashing, you won’t need to run Quicken as an administrator every time.

I look forward to your reply!

jmaino

R66.28 is stable for me - no crashes. Whatever I've experienced, it's only once upgrading to R67.7