One Machine - Parallel Builds - One License?

I just installed an older, parallel build on a dev machine with a commercial license installed.

I assumed that the licence would enable the older build (or that I could generate a commercial license for it, since it’s the same machine), but it’s asking for a new key or the creation of a non-commercial key. I’d rather not use up yet another non-commercial key (I think I’ve gone though a few dozen non-commercial keys so far, LOL).

Is the workflow to disable the key on Build X and then create a new one for Build Y? Having to do that every time is extremely inconvenient.

In theory, the newer key should provide a licence for both the old and the new builds, but I’m not sure how this works with parallel installations.

I did try to install the key for Build X on Build Y but if gives an “Unrecognized format(5)” error.

Thanks,

Sometimes the system code changes between major builds on machines due to the way the hardware reports things to us. If you disable your key on the newer build, and create it on the older build, then the newer build should still recognize the key generated by the older build as valid.

Thank you Malcom, that did the trick!