To clarify, I (probably mistakenly) understood that I had to perform both of these actions, a) and b) to preserve the 2.0 license.

Did I not have to ? ..and could I have only done (a), the first, and kept both 2.10 and 2.11 working?

I have the option to restore my system to the state of recent backup (and lose other things).  If the answer is yes to the above, I will restore my system and start all over again with only (a).  (Then do a new backup and try installing 14393 to keep Robert happy.)

Thanks

Hopefully my Win7 Ultimate 64 license will work.  Yes?  (assuming I can find it)

Wait, applying the upgrade patch to 2.10 converts it to 2.11 in the 2.10 folder?

That's not what I want.  I want to keep 2.10.  it works and sounds better than any other previous version. 

Can I just install 2.11 in a 2.11 folder and not apply any upgrade patch at all?

I'd like to end up with both 2.10 and 2.11 working in separate folders.

Thanks

Given that I already applied the Upgrade Patch to the previous version 2.10's folder, is it now valid to delete the entire contents of the new 2.11 folder and install it again?  (without the upgrade patch of course)

If I try that, will I break my 2.0 license or anything else?

(At least right now I can still run 2.10.)

Thanks Anthony.  To be clear, was your success with Win 7?

Thanks Robert.  Where can I get 14393?
     Depending on the size of the effort I may be willing to go through pain of installing 14393 and starting all over.  One reason I hesitate changing the OS, one big reason, is that my system is sounding better than ever right now.  I'm using two USB decr*pifiers in series, the latest Intona Industrial first, then the latest ISO REGEN from Uptone Audio powered by a big battery.  That's what it takes to dejitterify my PC almost completely.  XXHighEnd Does the rest.   I'm using an NVidia Quadro K620 to provide CUDA offload (the devil in this forum) for HQPlayer's latest advanced filters and it sounds too good to change anything at all,  except a new XXHighEnd of course.

That said, I still like to use XX about half of the time.  I like the interface much better;  and this is ironic because at first, maybe eight years ago, I only used XX for its sound and I didn't like the interface.  Now I like the interface more than any other player, except for the lack of a working pause button.  ...oh, and the lack of 705K playback  ...oh, and mouse selection sequences ....etc.  Some of these are addressed in 2.11.

Right now I can upgrade for free directly from microsoft and 12 weeks ago I made a USB key for that purpose.   But that is fraught with problems starting with it will be the wrong version of Win10 and MS automatically applies the latest updates if I use that method.  It's a "no go" and it's not 14393 without any updates.

I have to believe there are many others that are also running Win 7.  I can't be the only one.  Therefore, I assume for now that these problems have to be resolved, assuming there are problems to begin with.  There may not be.  I might have made an error in the installation process; and the first candidate for that is that I didn't exit MinOS before installing (something I've done with success before, I believe).

Also, I have to believe that the OS has nothing to do with some of these errors.  E.g.,  what does the OS have to do with XX reading and writing XXSS files?  ..what does it have to do with an invalid XX.AHK?

Thanks

2.11 and no Joy.  Doesn't work.  I'll explain below.  (And please note,  this is with Windows 7 Ultimate 64 and XXHE-PC.)

Firstly I remained in MinOS mode.  I was confident I could do that but maybe not.  Maybe that was my mistake.  Then...

-I created a folder under C:\XXHighEnd for this version, named 2.11.  Hence I copied and unpacked XX....rar in that folder (C:\XXHighEnd\2.11). 
-Then, without first running XX 2.11, I copied and unpacked the the patch file over the previous version's folder (C:\XXHighEnd\2.10).  Maybe I should have run XX before unpacking the patch file?

Then the many errors ensued.  There are too many to list.  But I'd classify them in three categories.  1) AHK errors;  2) Device not found or could not initialize or find audio devices; 3) Could not load or save XXSS or any other types of preset files; and 4) Could not shut down.

1) AHK errors
At first there was a problem XX.ahk, which never loaded.  The XX.ahk file was the wrong one:  it had no XX specific keys defined.  It looked only like the default example file from AutoHotKey.  (Not initially but I eventually stopped these errors by copying 2.10's XX.ahk file over to the 2.11 folder;  however this may not be a valid thing to do.)

2) Device not found or could not initialize or find audio devices
Initially I get an error window stating: Init Sound Device "Something wrong at initializing Sound Device"
Then, if I go into Settings to try to set the Output Device, the dropdown menu shows no options and takes a long time to eventually show an empty selection box.   So the usual choices like KS:..., and WASAPI, etc. are all missing.   (2.10 still sees all.)
And clicking that dropdown ends everything, but puts XX in a state where it cannot shut down.  It proceeds with the next type of error:

3) Could not load or save XXSS or any other types of preset files
and also
4) Could not shut down.
I get an error window:  Save or Load "Error at shutdown: The process cannot access the file PresetLoader...XXSS because it is being used by another process: 238"
Then I get: Settings are corrupt? : The settings Preset File looks to be corrupt ....  Close or kill XX through TaskManager and restart XX or try another Settings Preset File.
Then I get: Copy Settings: Something wrong with 'Copy Settings to' file (see Preset Settings): PresetLoader.XXSI   --  The process cannot access the file {...}.XXSS because it is being used by another process.  -- Stop?

And I proceed in an near infinite loop between those error windows until all my XXSS files (1200 or more) are exhausted.  Yes, I went through all of them because I had to make sure XXHE proceeded because I had asked it (eventually) to get out of MinOS mode.   I was afraid of what would happen if I did not complete the boot though XX after asking to exit MinOS mode.   PAINFUL!!!

What did I do wrong and how can I fix it?

Thanks

Awesome.  Thanks Peter.

I've been checking weekly for this for a long time. 

Still see it today.   I wonder if it is because I have a shorter subject line.

I can still see the Modify Button, as of today, now.

Peter please test post here so that someone other than me is posting.  So far I can still modify original post.  It's only  been a few hours.

Immediately after posting,  the Modify button is available.

Next I'll wait a few days to see if it is still there.

Here is a dummy post to test the ability to modify an initial post after posting, and well after.

Hi Peter

It would be nice to be able to change this myself, if not now in the future I will need to use the Modify button.  But,  whatever is best for you.  The text that needs to be replaced is this centered text:

Thanks either way

[Update: the other browser shows the same.]

I'll also try another browser, because in any case my buttons appear with strikeout text.  They work, just look funny.

Here's the screenshot: