I cant even get the Client to launch at all even with UAC off and running as Admin, have deleted and downloaded 4 times. Running Windows 7 64bit downloading in Chrome and extracting with WinRar. I have no firewall or antivirus on my PC. Anyone have any idea why it wont even open?
If the app appears to start (no dialog appearing), but then doesn't, it means you do not have the .Net Framework 4.5 installed.
Even though the framework does not request a reboot, a reboot dialog will pop the first time you launch the app. The app will run fine without the reboot, however, it is still very much recommended you reboot after installing the framework.
You can get the install for that from Microsoft. It's a healthy size, but not too bad.
As for the blocking. This is actually a problem because of a few reasons.
1) It is a .Net application. (There are special UAC handlers for .Net framework applications)
2) It attempts to access system level functions. (Certain system operations automatically trigger UAC blocks)
3) It does not have RequiresAdmin in the application manifest. (Without the RequiresAdmin some functions will fail unless the process is manually elevated... AKA Right click and run as Admin)
4) It is not "Installed" as an administrator (Installation software is recognized by Microsoft as a valid source medium, where zip files are not, so installed files do not get blocked... However, a raw MSI file for example will be flagged as blocked, as it could be potentially harmful)
The purpose of the blocking is to prevent people from downloading and running applications without knowing what they are doing. By downloading an executable, that attempts to use system level operations and simply running it, Windows is (rightly so) attempting to protect you from yourself.
The easiest fix for this would be to have this wrapped in an installer which then runs from an executable bootstrap that requests elevated privileges for the installation. The application itself should have it's manifest updated so that it too RequiresAdmin (as it really does) to allow for proper functioning.
And please, don't get me wrong, this is not meant to be a bash on the application. It is a rather elegant app that, so far, I have enjoyed using. It's just I have spent years designing and building installation, build, and release solutions, and personally hated these issues when they were introduced... However, having helped people recover their systems (and having to do it much less since they introduced this) do appreciate the pain the Microsoft introduced with UAC. And I also understand from a development standpoint how annoying it can be...