This error message is almost always a result of something on the local machine blocking interprocess communication. This can happen on new installs, or on updates if an over-aggressive security application decides that it will block the differing binary.
For others locating this post examples of configuring a few firewall applications to exempt Sighthound Video can be found here:
https://www.sighthound.com/support/fire ... gs-windowsAdditionally, in the past there have been a few scanners on more obscure antivirus applications that could cause problems if the data directory for Sighthound Video was not exempted. The data directory location varies based on OS and can be located as described here:
https://www.sighthound.com/support/wher ... store-data@Paul
Sorry you're experiencing trouble with the upgrade. Does the problem continue after rebooting the machine?
@Boomer
If you'd be willing to zip the "logs" folder and send it to our support email or to me here in a private message I'd be happy to take a look and see if anything out of the ordinary is occurring. You can locate the "logs" folder in the data directory as described by this article:
https://www.sighthound.com/support/wher ... store-data