With small adjustment you can make your product better identifiable by SAM Tools (Software Asset Management Tools). These SAM tools are used in large companies for inventory purposes.
Your executable “sublime_text.exe” uses the FileVersion “1.0.0.1”, ProductVersion “1.0.0.1” and the ProductVersion “3083”.
Problem 1:
The version scheme is not helpful for SAM. Most SAM tools will extract ProductVersion “1.0.0.1”. Thus they will come to the conclusion that a license 1.0 can be used to cover this product. However in this case a license 3.0 is needed. Thus the naming scheme for the version should be “3.0.3083.0” = “Major.Minor.Build.Revision” as recommended by Microsoft. Now imagine you release the next version of your product but 4.0 would need a new license. With a version “4.0.6013.0” most SAM tools will conclude automatically that a new license is needed. So you can support these SAM tools by providing the version information they expect from commercial software products.
Problem 2:
Naming: The Installer Information under Add/Remove Program should just be named “Sublime Text” with the Version being set to “3.0.3083.0”. The current Windows Editions will always provide the Version information in a seperate column. This way you can exactly determine which “Sublime Text” to remove. But your current installer does not provide any Version information and your current naming “Sublime Text Build 3065” is also not helpful for Installer oriented SAM processing.
Better use MSI package: Many bigger companies can distribute MSI packages with their internal Software Distribution. They do not need to adjust an MSI package but can distribute it right away. Furthermore an MSI package will preserve the internal relationship of the executables/files to the installer entry. These dependencies are valuable for SAM tools in general. Unfortunately your current package does not follow the MSI standard. Thus I would like to recommend the free WiX tool to create packages following the MSI standard for the installation.