I'm sorry you feel upset by my queries for more information. It's a axiom in software support that the bug-reporting user _never_ provides all the relevant information, because they don't know what is relevant. And the exact process you go through to make system changes (such as Java runtime upgrades) is very relevant, as are the exact versions of the upgrades.

It turns out that there is a reported bug in Java itself

https://bugs.openjdk.org/browse/JDK-8307616

so YAAC isn't the only application affected by this problem.

There's nothing I can do to fix this. All I can suggest is that you disable auto-updating Java and avoid taking further Java updates until the Java team fixes this upgrader bug.

Andrew, KA2DDO

author of YAAC

---

Andrew ,

This discussion seems to have gone full cirle and ended up back where it started. I thought I had already answered this previously but I must a failed to be clear. Lets address this question from you

So, _after_ you apply a Java runtime upgrade to an existing (not new) YAAC system but _before_ you try to restore a YAAC configuration, what configuration do you find in that freshly restarted (with new runtime) but pre-existing YAAC instance?

With the preexisting Yacc instance on a freshly updated Java runtime. Its like a brand new install of Yaac. Theres nothing. I knows not my callsign or my maps or my Ports config and comes up to ask me if I want to use a wizard to help me configure it or do it manually. I forget the exact wording.

You said "Either you are having some major bugs in installing Java runtime upgrades, or you are trying to replicate a template YAAC system into hardware clones."
Iam not sure just what that all means. Sounds like a accusation. If Yaac has to be installed in a specific place or in a special way then I just have not seen this anywhere.
I have been using Yaac literally for years now. Has something changed along the way with the way it needs to be installed ? I dont know.

I start off with a working personalised version of Yaac that runs repeatedly day after day just fine and then when a Java update comes along I end up with a Yaac that acts like its a first time execution.

Ive given you everything you asked for previously I thought by catching the execution in a command window.