Investing Accounts Do But Banking Accounts Don't Update

SMBMD
SMBMD Quicken Windows Subscription Member

Since yesterday, One Step Update updates all my Investing accounts, but hangs on updating any Banking accounts. The Update function even hangs if I try to update an individual Banking account. Following another discussion, I logged out of my Quicken account and the logged back in, the only result of which I now get a "Processing Data" message instead of a "Waiting" message for all my Bankingon accounts. My Quicken operates in a Windows 10 environment.

Comments

  • Quicken Anja
    Quicken Anja Moderator mod

    Hello @SMBMD,

    Have you tried uninstalling/reinstalling Quicken? Please refer to the following support articles for instructions on uninstalling here and reinstalling here.

    However, after you have uninstalled and before you proceed with reinstalling, please open your Windows File Explorer and navigate to This PC > C: Drive > Program Files (x86) and delete the folder titled "Quicken" (doing so does not affect your data files). After you have deleted this folder, go ahead and try reinstalling.

    Let us know how it goes!

    -Quicken Anja
    Make sure to sign up for the email digest to see a round up of your top posts.

  • SMBMD
    SMBMD Quicken Windows Subscription Member

    Thanks for the suggestion, Anha, I did try this, but I have the same result - the Investing accounts but the Banking accounts don't. For each Banking account, the accompanying message is Processing Data; under Online Services, by Updating Data there is an arrow pointing down and the messaged Scheduled Transactions.

  • UKR
    UKR Quicken Windows Subscription SuperUser ✭✭✭✭✭

    How long do you wait before you get impatient and kill Quicken?
    Less than 30 minutes? More than 30 minutes?
    If OSU takes more than 30 minutes for an update process, it should time out and continue with the next bank.

    If you haven't done so already, please do the following actions:

    1. Even if you are on the latest software level already, download and install the latest Manual Patch file from https://www.quicken.com/support/update-and-patch-20182019-release-quicken-windows-subscription-product to ensure your Quicken software is up to date and correctly installed.
    2. Reboot Windows.
    3. Start Quicken. Do not run One Step Update.
    4. Run BOTH Validate and Supervalidate to attempt to repair your Quicken data file.
    5. If nothing helps, try to restore your Quicken data file from an Automatic or Manual backup taken just prior to the problems first occurring. https://www.quicken.com/support/how-backup-or-restore-your-quicken-data

    Validate and Supervalidate instructions
    First save a backup file prior to performing these steps
    Validate: 
    • Click File
    • Select Validate and Repair File...
    • Select Validate File
    • If the data file contains investment accounts also select "Rebuild investing lots".
    • 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
    • Review the Data Log. Anything interesting in there, worthwhile posting here?
    • Close Quicken (leave it closed for about 30 secs)
    • Reopen Quicken and see if the issue persists.

    Super Validate:
    • Click File
    • Press and hold both CTRL and Shift keys while you click Validate and Repair File...
    • Select Supervalidate File
    • Click OK
    • Review the Data Log. Anything interesting in there, worthwhile posting here?
    • Close Quicken (leave it closed for about 30 secs)
    • Reopen Quicken and see if the issue persists.

  • SMBMD
    SMBMD Quicken Windows Subscription Member

    The Supervalidate process worked!!! Thanks so much.

    Stan

  • Quicken Anja
    Quicken Anja Moderator mod

    @SMBMD Thanks for the update letting us know what worked! Glad to hear the issue has been resolved. 🙂

    -Quicken Anja
    Make sure to sign up for the email digest to see a round up of your top posts.

This discussion has been closed.