Thanks. The Updater "sees" both the Start10.exe and the Start11.exe, so it's making no assumption (other than both being in its DB). Of course, I do NOT use the Update checkers I use to actually do the updates and I always go to a program's publisher for the update to manually install if I need to. Since Stardock's automatic updates work, these utilities merely "alert" me to their current status. As I said, I can set my Updater to "Ignore" Start 10's existence. By compatibility, are you saying Start 11 is built to work on BOTH Win 11 and Win 10? Or do we need Start 10 there to have Start 11 to even work? Neither sounds like a best coding practice.
Due to existing shortcuts to universal apps potentially pointing to the Start10.exe it had to remain, As these would be user created we wouldn't have been able to replace them hence including the file to ensure things work seamlessly for existing customers. Start10.exe is merely a stub file like Start11.exe, Start11_64.exe and Start10_64.exe (which is not included in S11 as nothing external linked to it)
You will also notice the dlls have _10 in them not _11 for compatibility reasons with other software which is aware of Start10 as this avoids us and third parties having to change software to be aware of it for no reason.
Start11 works on both Win10 and Win11 and this is good coding practice. Most software works like this and to do otherwise would be a terrible idea as you would have multiple versions of things depending on the OS you are using.
Ultimately the issue seems to be the updater utility you are using has incorrect data in the database and whoever entered it made a wrong assumption about what the important files are.
