One Step Update hanging up for 37 minutes (last attempt) with no update

Oldschool1962
Oldschool1962 Quicken Windows Subscription Member ✭✭

Understand there's a known issue but the fact the Task Manager needed to be used to exit the update seems to be very concerning. What's even more concerning is that scheduled transactions are being arbitrarily changed, by the system, while also finding transactions months from now have been reconciled. The system also has rescheduled payments as far out as 2037. Another issue with scheduled transactions is, they seem to be deleted from the list, appear as needing to be scheduled and also restarted weeks and months outside the scheduled auto entry date. We use 186 days for auto entry and have been for years without issue. It appears that whatever programing changes/updates are made, they mess the system up.

I also cannot access one step update settings without initiating a download and then needing to use the task manager to stop the function given the reason described at the very beginning of this message. Can't even perform a simple task of reconciling accounts without issues.

Addendum: Started a second one step update before starting this post and it continues to run. This "update" has been running for almost 55 minutes and actually has allowed one (1) account to be "updated" out of the seven (7) that will typically be downloaded on a daily basis. The update also does not have the "update cloud" that typically appears under the accounts list and status in the box.

Addendum: It's now more than an hour and simply can't waste any more time on the day waiting for the program to function properly. Maybe, another version can be offered to people who don't have the finances to have, let alone run their stock portfolio's in quicken. Maybe a simple banking program that allows for users to just run their finances so they can make ends meet without losing time on a day because the updates that revolve around market and portfolio management mean very little to them.

Comments

This discussion has been closed.