Betreff: Applying Update 8 to FrameMaker 2019 Fails

[Be.eM]

I'm seriously worried about "raising the bar" of software reqirements in the post for software versions which aren't current (like FrameMaker 2019). This means a perfectly running combination of older software in an older OS (e.g. in a VM) can stop working one day for no reason, correct? The stereotypical answer of "just get the latest version" while pushing people from using their perpetual licenses into subscription is not a proper solution.

[Matt-Tech Comm Tools]

[Moved from thread related to Fm 2019 update issue]

I don't follow how running an older version of Fm in a VM with older OS would ever stop working.

If it does, I'd look at the VM architecture, since they're the ones sell us on the merits of the solution.

In fact, what you propose is 100% what I would recommend to anyone updating OS or other resources, but not updating their production software. So we're fully on the same page 😉

Without overcomplicating things, I thought Bill_M did a great job of alerting us to a problem updating to 15.0.8. And "just get the latest version" was not any part of my post. My suggestions were specifically related to getting Fm 2019 running on his machine, with installing a free 30-day download being one thing among many to help narrow down his issue.

Regarding your comment about older software, Adobe has no control over changes in a user's environment past the release date of the software.

1. I can recall a handful of times when a current version of FrameMaker has lost functionality as a result of a Windows update. It's certainly incumbent on Adobe to address these issues at the earliest opportunity.
2. I can point to a number of places where other resources (like a FrameMaker plugin) create issues with FrameMaker functionality. I feel Adobe has less of a responsibility to deploy resources to resolve issues if removing optional applications or resources resolves the problem.
3. While it may have happened, I can't recall a time Adobe ever issued an update for a non-current version of a product. And I'd prefer they deploy resources to developing current features and resolving issues with the current version of the product.

The current release of FrameMaker has software and hardware requirements, just like Fm 2019. If Windows 11 releases soon, and Fm 2020 doesn't run on it, I hope Adobe addresses it quickly. However, it's my responsibility to run software that's required by my installed, licensed version.

And, if Fm 2019 doesn't run on Win 11, I'll be sorely disappointed should Adobe choose to deploy limited resources to reengineer anything other than the most current patch of the most current release.

-Matt

[Be.eM]

Matt,

I believe it's possible you misunderstood my posting:

As I understand Bill_M's error report, the updater to FM2019 requires a software/OS update, on a machine which already had/has a running and working FM2019 installation. Now enforcing software/OS updates just for applying FM2019 patches seems a questionable thing to me. The linked information page from Adobe states "If you are not using the latest operating system or browser, you may see a warning when you try to sign in to Adobe software." Signing in (or out) is the current version of activating/deactivating software on your computer. Means: trying to sign in (into an exisiting FM2019 installation) may start failing one day, if you don't update your OS/software. 

This is the opposite of what you are talking about, i.e. the possible failure of FM2019 in a continuously updated OS, up to the latest versions of Win10 or even Win11. I'm not asking Adobe for updating FM2019 to run in future OS versions (after support for FM2019 has ended). I'm asking Adobe to allow trouble-free use (including applying patches) in an existing and untouched environment without requesting software/OS updates.

However, if this error is not caused by Adobe, but by other components of the OS, my worries have been stated in the wrong place… 😉

Bernd

[Matt-Tech Comm Tools]

But Adobe didn't release Updater 8 in the user's current environment. I suspect that if Bill and others had installed while Fm 2019 was the current release, either

a. the Updater would have worked as expected in the current environment

b. Adobe would have deployed any and all resources to ensure Bill and others could quickly get Update 8 installed.

You wrote, "I'm asking Adobe to allow trouble-free use (including applying patches) in an existing and untouched environment without requesting software/OS updates."

Is this a hypothetical? I didn't catch that Bill or anyone else said they couldn't install 15.0.8 using the OS in place at time of release, but were having issues with installation after the release of 16.0.2

[Be.eM]

Is this a hypothetical? I didn't catch that Bill or anyone else said they couldn't install 15.0.8 using the OS in place at time of release, but were having issues with installation after the release of 16.0.2

By @Matt-Tech Comm Tools

Matt,

Bill (and meanwhile obviously others) said he couldn't install update 8 in the environment in which FM2019 (earlier build) was successfully running. This should be a minimum requirement for patches (bugfixes), to work in the environment in which the host application is running. We're not talking about an FM2020 fix/patch, but an FM2019 patch.

Edit/update, just to make this as clear as possible: the error message/problem description does not say "your system is too new for the patch to work", which is what you're suggesting. The opposite is true, it says "your system/software is too old, update everything first". This is completely contradicting what you intend to say. The patch obviously doesn't allow to keep the system status as is, it enforces updating it.

Bernd