Win10 Java8_111 Vassal doesn't start

Hi,

Below is a copy of the errorlog file that is generated when I try to start Vassal.
The vassal module manager window appears for a split second, then closes.

ErrorLog file contents:
[size=85]
2017-01-11 11:27:02,779 [0-main] INFO VASSAL.launch.StartUp - Starting
2017-01-11 11:27:02,782 [0-main] INFO VASSAL.launch.StartUp - OS Windows 10 10.0
2017-01-11 11:27:02,783 [0-main] INFO VASSAL.launch.StartUp - Java version 1.8.0_111
2017-01-11 11:27:02,783 [0-main] INFO VASSAL.launch.StartUp - VASSAL version 3.2.17
2017-01-11 11:27:02,887 [0-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManager - Manager
2017-01-11 11:27:03,769 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - VASSAL: Problem with socket on port 49501
2017-01-11 11:27:03,769 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2017-01-11 11:27:03,769 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - java.net.SocketException: Permission denied: connect
2017-01-11 11:27:03,770 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2017-01-11 11:27:03,770 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.DualStackPlainSocketImpl.connect0(Native Method)
2017-01-11 11:27:03,770 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2017-01-11 11:27:03,770 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)
2017-01-11 11:27:03,770 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2017-01-11 11:27:03,770 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
2017-01-11 11:27:03,771 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2017-01-11 11:27:03,771 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
2017-01-11 11:27:03,771 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2017-01-11 11:27:03,771 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
2017-01-11 11:27:03,771 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2017-01-11 11:27:03,771 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.PlainSocketImpl.connect(Unknown Source)
2017-01-11 11:27:03,771 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2017-01-11 11:27:03,771 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.SocksSocketImpl.connect(Unknown Source)
2017-01-11 11:27:03,771 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2017-01-11 11:27:03,771 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.Socket.connect(Unknown Source)
2017-01-11 11:27:03,772 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2017-01-11 11:27:03,772 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.Socket.connect(Unknown Source)
2017-01-11 11:27:03,772 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2017-01-11 11:27:03,772 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.Socket.(Unknown Source)
2017-01-11 11:27:03,772 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2017-01-11 11:27:03,772 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.Socket.(Unknown Source)
2017-01-11 11:27:03,772 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2017-01-11 11:27:03,772 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at VASSAL.launch.ModuleManager.main(ModuleManager.java:216)
2017-01-11 11:27:03,772 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - [/size]

Thanks,
Billiamson

Thus spake Billiamson:

2017-01-11 11:27:03,769 [0-main] WARN
VASSAL.tools.logging.LoggedOutputStream - VASSAL: Problem with socket on
port 49501
2017-01-11 11:27:03,769 [0-main] WARN
VASSAL.tools.logging.LoggedOutputStream -
2017-01-11 11:27:03,769 [0-main] WARN
VASSAL.tools.logging.LoggedOutputStream - java.net.SocketException:
Permission denied: connect

This happens when VASSAL is unable to connect to a socket on your
loopback device (127.0.0.1), because it was blocked by a local
firewall or AV program.


J.