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; } } }

Issue User Alert for Quicken Updates that have gone awry

jr_ece

It seems like an Alert method/system would help ease user tensions when an update turns out to be faulty. I think this could be an email to users, a popup on Quicken launch, and immediate post on the community forums.

Here is an example situation that I think would have benefited from such an alert.
https://community.quicken.com/discussion/7909601/r39-17-r39-21-paycheck-corruption-edited/p1

As you can read, a lot of users discovered the issue and worked hours to get their data restored. I think many could have avoided the install with an appropriate notice. Thanks!

Find more posts tagged with

Reviewed

Status: Reviewed

Comments

Jim_Harman

I think what you are describing is the "Alerts, Online Banking & Known Product Issues" section of the Community here
https://community.quicken.com/categories/alerts

The issue you describe is there, but as you can see it was buried quite quickly among the online banking issues. I think it would be a good idea to put the banking issues in a separate section so the alerts and product issues get more prominence.

jr_ece

Hopefully the community will get behind an idea like this and push it up in votes.

George P

@jr_ece Where do I vote?

Jim_Harman

Click on the up arrow below the vote count in the colored box at the bottom of the third post in the discussion

Ron Varley

YES! This would be much appreciated and easier than looking through several different threads. I DO NOT UPDATE until I read about what folks here post. That is why I am still on R38.30. Voted!

NotACPA

@Ron Varley R39.23 appears to be quite stable. I'm been on it since early March without incident.