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

Manual Patch Update - needed if already at that version?

LexLuther

I'm being told by Support to download and install QW27.1.66.28MPatch from the Manual Patch Update page. However, I'm already at the latest version 66.28. What's the difference? The support person declared confidently it would fix the known bug, but there is nothing in the release notes that talks about the issue I'm having.

Find more posts tagged with

Comments

splasher

A re-install of a release is sometimes suggested to make sure that there is nothing with the original patch install.

There is no harm in running it again, just make sure that you get it from Quicken.

LexLuther

That would make sense if the issue started with the most recent release installation, but it started months ago. Also, I've demonstrated that the bug is data dependent. That is, I can open a database from before the behavior began and it works as expected.

If he had said, this was an instrumented build that could detect issues that an automated update version could not, or something like that, I'd go along with it. But this wasn't the case, and he couldn't tell me why he thought it would fix the issue, or why there was nothing in any release notes related to it. In other words, he was just following a script rather than make any effort to analyze the situation I was inquiring about.

For the record, though, I did apply the manual update, and it had no impact on the problem reported.

NotACPA

What's the specific issue, the specific post, that you're referencing?

LexLuther

This one:

Why does One Step Update stop by Settings when choosing Update Now on Password Vault dialog — Quicken

But if you have anything to add on the actual issue, please comment there (as you already have). This post is totally regarding the question of what value there is to upgrading via manual patch when automatic patch has already done it.

retird

Have you tried installing the manual patch and then opening the last known good backup data file and just updating the data to bring the file up to date?

For years I would let Quicken update from within Quicken. No more… I always do a manual update only after the update has been out for long enough to show it has no issues. Works for me. I just did a manual update for R66.28 without issue.

LexLuther

This behaviour started several months ago. I've been through a dozen updates since then. I can bring back a data file from three months ago and the issue doesn't occur. Re-entering three months of transactions would be impractical, and since we don't know what the problem is, would likely not change anything.

Off-topic, but I note that several of us in this thread are long-time users. I believe I converted from Andrew Tobias Manage Your Money to Quicken in the late 1980s.

retird

I guess you have also uninstalled Quiucken and reinstalled it….