One Step Update SUMMARY missing information

Hi @solostorm

I am seeing this same issue and I am running an earlier version.

When did this behavior first begin for you? I think it started within the last week for me. When you say "This includes not indicating some accounts which failed to complete downloads." how did you determine that some accounts fail the download process? Are you seeing an error code?

Frankx

For the accounts in question:

1. Account Register: Directly below the Account Name above and to the left of the Register, do you see the date and time of the last update and, if so, is it accurate or is it old? In addition, in that same line, does it show the connection method (Direct Connect, Express Web Connect or Express Web Connect+)?
2. Account List: In the Transaction Download and the Last Download columns, what does it show for the connection method and the date and time of the last download? (If you do not see these columns, click on the "Options" button below the list and check those options.)

I've never seen a runtime.dat file in my system that was not a Quicken file. Thanks for highlighting the Epson one. I would leave that one alone.

I certainly understand your concern about deleting any file(s) when you don't fully understand what they do and how that might impact your system. In fact, the first time I was told to do it I cringed and then first made a copy of it that I saved to a thumb drive….just in case.

Others have expressed similar concern about doing this. What some have suggested doing was to simply edit the name of the file to runtime_OLD.dat. Then they could leave the file there and if for some reason they wanted to undo the action they could simply delete the new runtime.dat file that Quicken created and then edit the "_OLD" out of the original file's name.

Also, it is not unusual to find multiple runtime.dat files in multiple locations. Most commonly, this occurs if there are multiple unique data files being used because each unique data file will have it's own unique runtime.dat file. If you have ever created a Quicken TEST file, that, too would have its own unique runtime.dat file. Even after you delete a Quicken data file that runtime.dat file will remain there.

If it will make you feel more comfortable, edit those 2 runtime.dat files in both of the Quicken paths to runtime_OLD.dat. Then you have an easy fallback should something go wrong with the creation of the new runtime.dat file(s).

@Ajay2020 - Great! As noted in my post in that thread I'd referenced, most of my accounts fixed the last update date/time on the first attempt to Reset or Deactivate/Reactivate the account but in one instance I needed to Deactivate/Reactivate 3X before the update date/time was resolved. I've seen others say they had experienced the same thing but all had said that eventually it all worked out well and was resolved. But I cannot recall anyone saying that they could not eventually resolve the issue entirely via the process in that referenced thread.

BTW, this is not an issue that you should be seeing frequently. For me, I last had to do it back in June 2023 (the data of the referenced discussion thread) and 15 months later I have not had a recurrence of this issue. I also have not seen others posting that they have had a recurrence after just a short time.