Why aren't all accounts appearing in the update summary?

Question

I have four institutions with accounts set up in my update.  Lately some do not appear in the update summary window after the update.  The two that do may or may not have new transactions.  The two that DON'T appear may or may not have new transactions.  If the accounts don't show up in the summary but have new transactions, they will appear with flags in the register to denote there are new transactions.  Why all of a sudden should a bank account fail to appear in the update summary?

GeoffG · Answer

One other possibility is if you recently needed to reauthorize an account (prompted when first opening Quicken) as required by your bank, the included for OSU checkbox option seems to drop off. Check to see if the banks in question are checked in the OSU settings.

Jim_Harman · Answer

You should be able to correct the problem of the One Step Update (OSU) result details not being displayed with the following procedure. Note this will not correct any other problems, it just fixes the problem with the OSU results not being displayed.

* Do a OSU and then Exit Quicken
* In Windows explorer, navigate to C:\ProgramData\Quicken\Inet. If you don't see the C:\ProgramData folder, it is hidden by default. In Windows 11 Windows Explorer, click on View then Show and select Hidden items to show the hidden folders. You should also select File name extensions under Show to see the ".dat" part of the file if that is not already selected.
* In the Inet folder, open the folder that matches the name of your active QDF file and look for the runtime.dat file. If there is no such folder, it may be because you have renamed your Quicken file at some point. In that case, search the Inet folder to find the runtime.dat file that has a time and date that matches your recent OSU. For me the folder is QDATA, which is (or was 25 years ago) the default Quicken file name.
* Once you have found the correct runtime.dat file, rename it to runtime-old.dat or something similar. Quicken will create a new runtime.dat to replace the damaged one.

Good luck! Please let us know if you were able to find the correct runtime.dat file and if renaming it fixed the problem.

NotACPA · Answer

A non-answer that I won't otherwise respond to.