tbh i wouldnt bother with teh compatibility troubleshooter like @polar_nomad suggseted... if youre seeing that specific "cant run on your pc" dialog on a 64-bit build, its almost always a 16-bit architecture issue or a corrupted header, and the troulbeshooter just tries to swap some basic settings that wont fix a fundamental binary mismatch lol.
in a setup like mine, these kinds of vendor tools are usually prtety poorly built anyway. instead of fighting with the exe, i'd check if teh vendor has a web-based config portal or a legacy driver package. sometimes just installing teh old driver package gives u the registry keys u need to map teh buttons without actually needing to launch that buggy ui app. it's a bit of a pain to dig through the logs but way more reliable than trying to force a dead binary to open.
