nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

12/28/21 R37.62 has messed up my accounts

Michele B

I am shocked and stunned with the above update that automatically upgraded my quicken. I didn't think anything of it, and ran a ONE STEP UPDATE and the result was all checking accounts were messed up balances etc. I phoned in and they said it's a server connection issue. I'm even more confused as to why my backup from last night PRE-UPDATE did not work an roll back my quicken??? I do not SYNC to mobile, though I understand that EXPRESS WEB CONNECT stores certain data in the cloud.

Quicken Tech support said that the issue would be resolved within the hour, but I haven't seen any update on the bookmarked site: does anybody have any helpful navigation? My account balances are all messed up?

Find more posts tagged with

Comments

unknown

This content has been removed.

Sherlock

To revert to an earlier release, I suggest you perform a clean uninstall, install while disconnected from the internet, update by applying the appropriate Mondo Patch, and restoring a data file saved prior to updating from the earlier patch release. If you haven’t already, you may want to review: https://www.quicken.com/support/using-qcleanui-uninstall-quicken. To update Quicken, I recommend you download and apply the appropriate Mondo Patch: https://www.quicken.com/support/patching-updates-windows or http://www.quicknperlwiz.com/quickenpatches.html

To prevent Quicken from applying an update without your approval, I suggest you set Windows UAC settings appropriately (choose default or always notify).

unknown

This content has been removed.

Sherlock

Paula Miceli said:

@Sherlock you did notice that the current Mondo Patch is shown as R37.62, didn't you? That is the version that @Michele B is indicating above is causing issues with her one-step update. Again, it appears Quicken engineers have not fully tested the update before rolling it out. I mention this because over the past month and a half several updates have been rolled out and then backed off (but proper notification not given by Quicken) after people have installed them. They were supposed to correct problems created by the Schwab updated connection and download, but have caused further issues.

@Paula Miceli
Yes. I did notice that you and @Michele are attempting to use the staged releases. You're much braver than we are. We're still using R36.38. In my opinion, if you are knowingly choosing to use a staged release, you should not be shocked when there are issues. If you aren't already, you may want to bookmark:
https://community.quicken.com/discussion/7901682/windows-r37-xx-release-us
https://community.quicken.com/discussion/7899697/windows-r36-xx-release-us

unknown

This content has been removed.

Sherlock

Paula Miceli said:

> @Sherlock said:
> @Paula Miceli
> Yes. I did notice that you and @Michele are attempting to use the staged releases. You're much braver than we are. We're still using R36.38. In my opinion, if you are knowingly choosing to use a staged release, you should not be shocked when there are issues. If you aren't already, you may want to bookmark:
> https://community.quicken.com/discussion/7901682/windows-r37-xx-release-us
> https://community.quicken.com/discussion/7899697/windows-r36-xx-release-us

@Sherlock thank you for the links. I will subscribe to receive further comments to them. I was not made aware of these particular posts, and I obviously would not intentionally download an update that I suspected might cause issues with my Quicken file/account.

Please note that in Quicken Support’s posts that instructed users to use the Mondo patches (R37.XX), it is not indicated that these are “staged” updates. Schwab users were instructed to update using these patches if they expect to again be reconnected to their Schwab accounts. We were not given a “choice”. I suspect you are not personally dealing with the Schwab connection change issues, but if you’re interested in why users have updated using the Mondo patches, review this:

https://community.quicken.com/discussion/comment/20228625#Comment_20228625

@Paula Miceli

Quicken Support is attempting to provide solutions to Schwab specific issues in the Quicken program as soon as the fixes become available. This does not mean you must bite the apple.

My recommendation regarding Schwab accounts has been to either maintain the registers offline until you're convinced the significant issues Schwab has caused have been resolved or you have moved your accounts from Schwab. We moved our accounts from Schwab a few years ago.

unknown

This content has been removed.

Sherlock

Paula Miceli said:

> @Sherlock said:
> @Paula Miceli
>
> Quicken Support is attempting to provide solutions to Schwab specific issues in the Quicken program as soon as the fixes become available. This does not mean you must bite the apple.
>
> My recommendation regarding Schwab accounts has been to either maintain the registers offline until you're convinced the significant issues Schwab has caused have been resolved or you have moved your accounts from Schwab. We moved our accounts from Schwab a few years ago.

@Sherlock, I think you'll find that Schwab did not cause the problems. It is Quicken changing the method they use to connect (from Direct Connect to Web Express+). Also, users had no way of knowing (or should have to expect) that Quicken would not have a fully vetted procedure and all necessary updates completed before beginning the changes to connection type.

@Paula Miceli My understanding is Schwab decided to no longer support Quicken access using the Direct Connect connection method to save money. Instead, Schwab decided to only provide access to their customer's data using a Schwab proprietary API. Intuit is attempting to provide access to the accounts Schwab exposes through this API to Quicken using their unreliable Express Web Connect connection method.

Note: To date, there are only four ill-advised financial institutions that only provide support for investment accounts using the unreliable Express Web Connect connection method:

Arvest Investments - Wealth
Charles Schwab & Co., Inc.
Momentum Financial
Titan Investments

Chris_QPW

Sherlock said:

Paula Miceli said:

> @Sherlock said:
> @Paula Miceli
>
> Quicken Support is attempting to provide solutions to Schwab specific issues in the Quicken program as soon as the fixes become available. This does not mean you must bite the apple.
>
> My recommendation regarding Schwab accounts has been to either maintain the registers offline until you're convinced the significant issues Schwab has caused have been resolved or you have moved your accounts from Schwab. We moved our accounts from Schwab a few years ago.

@Sherlock, I think you'll find that Schwab did not cause the problems. It is Quicken changing the method they use to connect (from Direct Connect to Web Express+). Also, users had no way of knowing (or should have to expect) that Quicken would not have a fully vetted procedure and all necessary updates completed before beginning the changes to connection type.

@Paula Miceli My understanding is Schwab decided to no longer support Quicken access using the Direct Connect connection method to save money. Instead, Schwab decided to only provide access to their customer's data using a Schwab proprietary API. Intuit is attempting to provide access to the accounts Schwab exposes through this API to Quicken using their unreliable Express Web Connect connection method.

Note: To date, there are only four ill-advised financial institutions that only provide support for investment accounts using the unreliable Express Web Connect connection method:

Arvest Investments - Wealth
Charles Schwab & Co., Inc.
Momentum Financial
Titan Investments

And it is my understanding that in fact this the start of the industry moving to a new system (even if we don't like that system).
This is the system they are going to:
https://financialdataexchange.org/FDX/News/Announcements/FDX_Security_Specification_Boosted_with_FAPI.aspx

Take a look at the "members":
Members - All Members (financialdataexchange.org)

I hate aggregators, but that is what the US financial institutions are standardizing on.
So, blaming just one party in this really not reasonable.

And in the future, there might even be some benefits, certainly for the Quicken Mac users that have had a much better roll out of this. From their latest release post:
https://community.quicken.com/discussion/7904319/quicken-for-mac-v6-5-released

Image: https://us.v-cdn.net/6031128/uploads/editor/0c/0yhpqysrbmgg.png

Note in another Quicken Mac thread there is even mention that the Federal Thrift Savings Plan is one of the ones that is going to be supported (but at the moment they are escalating a problem on it).

unknown

This content has been removed.