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
Having trouble with one-step update (updated title)
This discussion has been closed.
Answers
I don't know, only that it is scheduled to be a security nightmare in 2020, when updates stop.
Windows 10 Pro 32 & 64-Bit Build 21322.1000
also Windows 10 Pro 64-Bit Build 19042.804
Note: Product What's New in Quicken is grayed out.. Also Year is stuck on 2020 and Copyright Date is stuck 2018 in About Quicken.
View: https://community.quicken.com/discussion/7859218/work-with-copies-of-your-actual-quicken-data-files/p1?new=1
https://www.quicken.com/support/size-or-capacity-limitations-quicken-data-file
In any case, it has to slow some processes down, but to a crawl?
(Removed-Disruptive)
Any response?????
Our Teams began staged release of the R23.21 Hot Fix patch as of this morning (01/06/20).
The Hot Fix was released to 15K Quicken Windows 2020 (subscription) Users and is targeted at resolving two issues:
- Fixed: An issue in which One Step Update (OSU) would stop responding for some users.
- Fixed: An issue in which users who had chosen to auto-renew their subscription were being prompted to manually renew their subscription.
The Hot Fix staged release is currently on "Pause" while we listen for feedback from Users who have received the patch.If no new issues/concerns are reported the patch will be rolled to the next stage of Users. If you would prefer not to wait, the R23.21 Patch is also available from here, click on the "US Mondo Patch Update" link to download and install the latest version.
After installing the R23.21 release, please start a new thread to report any issues, errors or concerns experienced.
**Please Note: The R23.21 release has been created for Quicken 2020 (subscription) product versions and is not applicable for affected Quicken Windows 2017 Users. A new patch will be coming to resolve this behavior for Quicken Windows 2017 Users.**
Thank you,
Sarah
Thank you for posting about the issues you are experiencing. The R23.20 test build will not help resolve any issues with Quicken Bill Pay, I apologize. It is targeted specifically at resolving the slowness/hang or "freeze" when running the One Step Update.
When attempting to Add or Activate an online account or service, Quicken may present a message "Please enter your passwords. To Continue, enter the password for the following institutions." on what appears to be a blank screen with no place to actually enter the password(s). This is an informational message, not a "provide password here" screen.
The blank "enter password" window can occur for a few different reasons:
Cause
This message will be presented when one or more of the following conditions occur:
To resolve this message
NOTE: If you are attempting to add Quicken Bill Pay to one of your existing banking accounts with another financial institution, make sure you follow these steps for the financial institution before attempting to complete them for Quicken Bill Pay.
I hope this information is helpful, but if you are still experiencing issues with Quicken Bill Pay, please start a new thread to let us know.
Thank you,
Sarah
Thank you for reaching out! If you have several old/unused or no longer active securities, I would recommend following the steps provided by @qal2947
If Quicken is trying to refresh outdated or no longer valid information, the multiple failed requests during the update can cause a slowdown or hang to occur.
Removing any outdated information from the update should speed up the One Step Update since it is not having to process through internal errors/issues for invalid data requests.
I hope this information is helpful and if issues do persist after removing the outdated options, please start a new thread to let us know and continue troubleshooting.
Thank you,
Sarah
The internal root cause of the Quicken Bill Pay issues has been resolved for all Users, however, we are continuing to see reports of Users receiving an error while attempting to reconnect Quicken Bill Pay that we are further investigating.
If you are continuing to experience issues connecting with Quicken Bill Pay, please contact Quicken Support for assistance with further troubleshooting and/or re-establishing the connection.
Thank you,
Sarah
The purpose of this post/reply is to provide you and your team some positive fact-based feedback.
Just executed the upgrade (R23.21) and subsequently, the One Step Update.
Everything worked flawlessly with dramatically “quicker” performance processing my transaction downloads from 18 accounts (“pun” intended). All is well.
Please extend my thanks and compliments to everyone on your team who contributed to this prompt resolution.
Best regards,
Don Kelley
Just letting you know that I downloaded the R23.21 version and it is working with both animation on and animation off. Looks to be about the same speed of overall response.
Thanks for the attention to this. As many have said, without the one-step update, Quicken is not very valuable.
> @"Quicken Sarah" said:
> Hello All,
>
> After installing the R23.21 release, please start a new thread to report any issues, errors or concerns experienced.
> Thank you,
>
> Sarah
After reloading my Quicken 2020 all worked well and I am release 23.18 Build:
27.1.23.18 with no problem other than slow OSU. What is the timeframe for the formal general release/fix. I think I will wait till then instead of a patch or hotfix.
Decades old Quicken user.... Quicken 2020 Subscription, V: R23.18 ; Build 27.1.23.18 ; Windows 10 Home V: 1903 running in VMWare 11.1.1 shell on MAC OS Mojave 10.14.6 ; MAC Mini
> As part of what appears to be the roll-out of a possible fix that @Quicken Sarah referred to in a prior comment, I was notified of an update being available this morning upon loading. I chose to postpone installation of this update right now since after experiencing the issue in mid-December merely turning off animations has returned me to a working state for the past month. Continued reading of the other/additional issues over that time has not fostered confidence we truly have this issue resolved nor that any root cause has been found (or at least not communicated clearly). I fear many side-car issues have been connected to the initial OSU issue such as Bill Pay and stock symbol pruning. Once a formal root cause statement and more extended fix confirmation for OSU is available (hopefully within a week) I hope to install the update.
>
> Decades old Quicken user.... Quicken 2020 Subscription, V: R23.18 ; Build 27.1.23.18 ; Windows 10 Home V: 1903 running in VMWare 11.1.1 shell on MAC OS Mojave 10.14.6 ; MAC Mini
I agree 100%. Seems that there are some people that have had issues with this update as it has made their situation worse. Seems to me that the main issue might have been on the Quicken server side as if a miracle appeared to get better.
1) Will Quicken provide some sort of compensation for the customer impact? Something like extending subscriptions by one month or something?
2) Will Quicken conduct a post-mortem on what happened and what is needed to make sure it will never happen again and will this post-mortem be shared with us together with an action plan to ensure stability in the future?
I really think most of us are frustrated and losing confidence in the product and that Quicken should proactively take steps to turn this around.
@QuickenSarah any comments?
Robert
Questions? Check out the Quicken Windows FAQ list
Don’t have a bill to pay, so haven’t tried billpay yet, although it was working fine yesterday.
I should note that I do NOT update stock prices, sync cloud, or update bills on OSU. Subscription with Windows 10.
During OSU, dialog seems to run successfully - "updating institution", then "requesting, receiving" as usual. I have 3 accounts there, and it runs through request-receive 3 times, seems to be getting the info. At least once, I even got a green check mark, though not always - but then I got, first error 803 - credentials are incorrect - and now error 800 - "may also be a server error". Rebranding did not help. Even deactivating online download for the accounts and setting up again did not work. The credentials are fine, and logging in to SDCCU website (in browser) works fine.
Again, hopefully an issue with the institution that will fix... but the timing...
FOLLOW UP - resolved 12 hours later after deactivating Online Update for all 3 accounts at this institution, and re-adding them. This has happened occassionally in the past with SDCCU, which uses Express Web Connect. Presumably and hopefully not related to the issues under discussion in this thread. Otherwise, all is well with the latest update.
"**Please Note: The R23.21 release has been created for Quicken 2020 (subscription) product versions and is not applicable for affected Quicken Windows 2017 Users. A new patch will be coming to resolve this behavior for Quicken Windows 2017 Users.**"
One strange behavior persists that maybe existed before the fiasco.
--Start up Quicken and click Update Settings (dropdown from the Update icon).
--After entering the vault password OSU starts, not the Update Settings window.
--After the OSU runs you can get to the Update Settings window any time during that Quicken session.
Shouldn't you be able to get to Update Settings without first running OSU?