"0.0.0.0" is an alias to "all interfaces of the local machine". So failure to bind to "0.0.0.0:8555" means the program cannot open the port on your local machine (so the problem is on the local machine, not on an external gateway).

There generally could be two reasons: 1) That port is already opened by some other program; 2) you have a general problem with access to ports (or to any network resources) on that machine. The first assumption could be resolved by running TCPView and checking whether you have any program bound to the ports in question; the second assumption could be checked by the same TCPView - to see if you have ANY program successfully bound to ANY port on that machine. In any case you would need to use TCPView.

Not sure what could have been broken by using bcdedit, but you might have screwed the networking engine on that machine somehow. TCPView might show whether you have any program successfully using the networking stack, especially whether there is any kind of server program running.