Quicken Community is moving to Single Sign On! Starting 1/22/21, you'll sign in to the community with your Quicken ID. For more information: http://bit.ly/CommunitySSO

Build Causing Crash on Account Updates

Unfortunately, Quicken updated itself to R20.15 this evening and now it is impossible to update any accounts either individually or by One Step Update. When I try to update, the program begins to open a Quicken sign-in page, but then immediately crashes. I have tried to sign out and sign in as a new user (which worked to fix this problem on an earlier revision) but that also causes an immediate crash. So, right now I am unable to update any of my brokerage accounts and Quicken is basically useless!!! Why does Quicken development always seem to be "one step forward, five steps back"? Very frustrating.

Bottom line, does anyone know the "fix" for this problem and if not, how can i revert to the previous build, which I think was 19.50.

Thanks for any help.


  • Sherlock
    Sherlock SuperUser ✭✭✭✭✭
    If you haven't already, I suggest you perform a clean uninstall, install and update.  You may want to review: https://www.quicken.com/support/using-qcleanui-uninstall-quicken.

    If you would like to revert to an earlier patch release, you should perform a clean uninstall, install while disconnected from the internet, update by applying the appropriate Mondo Patch, and you should restore a data file saved prior to updating from the earlier patch release.   To update Quicken, I recommend you download and apply the appropriate Mondo Patch: https://www.quicken.com/support/patching-updates-windows or http://www.quicknperlwiz.com/quickenpatches.html

    To prevent Quicken from automatically applying an update, I suggest you set Windows UAC settings appropriately.
  • UKR
    UKR SuperUser ✭✭✭✭✭
    After following @Sherlock 's advice about reinstalling Quicken repair your data file (as follows) or restore it from a Manual or Automatic backup taken before your software update.


    Validate your Quicken data file. It may have become damaged over time or if you ever had crashes, hang-ups or loops while running Quicken. Repeated crashes may eventually render a data file broken beyond the repair capabilities built into Quicken.

    Please run this exact procedure, skipping no steps:

    - Make a copy of your data file: Click File / File Operations / Copy.  Do not change any Copy Option settings. Save file under a new name in same folder as current Quicken data file.  (The Copy process appears to be performing a record-by-record copy of the data file and not just a simple binary image copy. This has been reported as recovering some otherwise not repairable files)
    - If Quicken reports an error creating the Copy file and you are using Q 2019 repeat the Copy process, but press and hold SHIFT and CTRL as you click File / File Operations / Copy. When prompted "Ignore errors that prevent file copy?" click "Yes".  Note: This may cause some data loss.
    - Open the copied file in Quicken.

    - Click File / File Operations / Validate and Repair. Click "Validate File" and "Rebuild investing lots", check to make sure the copied file is being validated. If you suspect that a damaged Quotes Price History causes your problems, also select "Correct investing price history" functions "Delete" or "Repair and Rebuild".  Click OK. Let it run.

    - Fix any errors logged as not repaired by Quicken.

    - Click File / File Operations. Press and hold SHIFT+CTRL as you click Validate and Repair. The next popup should show "Supervalidate" somewhere in header or text. Click "Supervalidate File", check to make sure the copied file is being validated, click OK. Let it run. It might run for a while.
    - Again fix any errors logged as not repaired by Quicken.

    - Now close and restart Quicken using this new file and try your failing action again. If it works, keep using the new file and abandon the old one.

    - If that doesn't resolve the issue, you may have no recourse but to restore your Quicken data file from a Manual or Automatic Backup taken prior to the problem first occurring, if necessary going back to older backups until you find a file that does not exhibit these symptoms.

This discussion has been closed.