The relevant error seems to be the following:
An attempt was made to access a socket in a way forbidden by its access permissions
Based on this, my guess is that you are having problems starting up the web server and that there is something wrong either with your system or with your setup. Ideally the TCP plugin should handle this error more gracefully. While it may not be able to start the simple web server, it should still be able to handle the exception and load the plugin, so I will have a look at that.
There are a few reasons I can think of why you would get this error. I will start with the most likely causes / fixes and work my way down.
#1 - Firewall or antivirus is blocking you. More likely the firewall. Normally you are asked to create a firewall exception when you start VoxCommando, but to be sure you can temporarily disable your firewall to see if it is a factor. Antivirus... I'm not sure if this is as likely, but you might as well disable it too to test.
#2 - The port specified for the web server is already being used by a program or service on your system. Try changing to a different port. The plugin won't load due to the error which means you can't access the plugin settings at the moment. To resolve this you can either delete file "Options.xml" in the plugin\TCP folder and then restart voxCommando. This will reset the settings and then you can use the UI to adjust the plugin settings. Or you can edit this file by hand and change the line that reads: <Option name="webServerPort" value="
8095" />
The reason #2 is not at the top of the list is because I would expect a slightly different error message in the case of a port that is already being used, but you never know.
#3 - Less likely, but easy enough to check. Normally you should not need any special permissions to open a socket, but you can try to disable UAC and/or run VC as administrator to see if it makes a difference.
#4 - You've got some other corruption in your system dlls. I think this is quite unlikely but again, with computers you never know.
#5 - You only have .Net 4.6 installed and it is not 100% backwards compatible. You could try to install .Net 4.1 and/or .Net 3.5 but again this is quite unlikely.
I would start with #2 and just set the port to something you are sure is not being used, then try #1.
Good luck.
