That problem can happen if Windows "thinks" one of more of the installed files are "damaged" (i.e. no longer the same as the files that were originally installed). The easiest way to "fix" it is to re-run the installation and selec the [Repair] option. however, that can have other side effects such as resetting some things to "installation defaults".
Unfortunately, if you are part of the beta test teat and have downloaded any beta updates which require you to manually copy the beta files over the top of the existing installation, then that can cause Windows to "think" the installation is demaged and may cause the msi installer to start up when you double click on the *.tun files.
Its really just a case of Windows trying to be "smarter" than the user but failing miserably. Windows can't tell the difference between a file that has been changed for a valid reason and a file that has been changed by a trojan, virus or other malicious software.
Then again, maybe your system has been compromised and one or more installed EFILive files have been damaged.
Regards
Paul