Update from one OS version to a different always runs this risk (actually the risk even is there within major updates within the same OS version(given the rolling release of Win 10, if this is a legacy version of production software, I would be concerned that a Win 10 major update (typically 2 a year) would cause something like this again for you down the road, may not, but I would at least plan for that to be the case) and keep in mind, from Win 7 to Win 10 is a 2 generation jump (skipped Win 8)).
Your best bet is to reinstall from disk (although it still may require some finessing to get it to still work right(I had one program when I went from 7 to 8.1, I had to manually move dll files from the disk to a specific location(which was mentioned in an error msg box) in order for it to work). I would also make sure that drivers for that converter will also work on Win 10 (the current version that your Win 10 OS is at anyway, sometimes support may be dropped within a very specific version of Win 10, which can also happen with the main software as well).
As to "running as admin", I know for some things it works and with a legacy piece of software like this, it is a viable option, but if software written today still requires that, that's no bueno. Sure, su/sudo for installing itself is one thing, but running it, no, but I digress.