I have started to complain about this several times in the last year or so but have always checked myself. Now, I am going to do it.
The TOAD for Oracle installer executable does not have the product version (16.1) in its name.
Instead, it has the version as '2022R3'. Today, I was asked to provide my company a copy of TOAD for Oracle 16.1. I had the file "Toad_for_Oracle_2022R3_x64_Full.exe", but I had to execute the installer and get to the (I think) third screen to confirm that it was indeed 16.1.
I cannot find anywhere in TOAD that 16.1 is referred to as 2022R3. So, the file version is not the product version as known in the wild. Either we have to keep track of the relationship of TOAD installer file names to product versions. or we have to actually run the installer and get a bit into it before we find out. We have several enclaves where TOAD is to be installed, and they are not all to be the latest version. To figure out the software version, we have to execute the installer to find out what's in it and then keep our own notes about it.
So, why don't you put the software version that everyone can relate to in the file name? That other version string does not convey the information that we need, that it is 16.1 or whatever version. The association of the file name to the software version is not even in the release notes or the About info or the Help. If the different teams would keep the docs with the installers, then we could at least see the relationship there. But, what invariably happens is that the installer gets staged by itself, and the docs remain on the PC of the acquisition POC if they are ever even downloaded by them.