Serviio

Hello.
I've updated to 1.00 version today and after the update my PS3 and my LG TV stopped detecting my Serviio Server.
I've tested everything from binding the IP, push the Serviio service down in starting order or manually set up the firewall exceptions.
Nothing works. The serviio console detects a MediaRender (using a generic DLNA profile) instead the actual TV (as it used to be) and the TV doesn't detect the server.
Using the Device Spy i don't have any problems detecting the TV. (a 47LW980S-ZA)
Any ideas on what may be the problem?

post detailed log please

Added the log.
If you need more ask. (The rest is too big, added files information)

can you try disabling the Hamachi network interace?

Disabled it (disabled the interface, removed the profiles, removed the bound IP stopped the server and started it again) and no changes. Still the same behavior.

EDIT: I tried to disable all other interfaces and leaving only the one i need and i still get the same results. (Although the search for devices seem to be a bit quicker)

Can you install DeviceSpy (Intel tools, my signature) on another machine and run it - can you see Serviio in there?

Nop, it doesn't appear. Maybe a problem with the router? (strange that this didn't happen before)

might be router or firewall on your Serviio machine

Deactivated the firewall and nothing happened.
There was no changes in the router since i used 0.62 so i find it weird that I'm having this problem.

Update: I took a restart on the console/server but it appears that shutting down the the firewall made it available again.
Any idea why the firewall is messing with this new version of Serviio?

no idea, it's using the same ports. Maybe a Windows update?

Restart your rooter.

I also had some problems when upgrading from 0.62 to 1.0. After upgrading to 1.0, some files that were previously visible and also playable on a samsung 32D5000 suddently stopped appearing in the list. Enabling logging showed that for those files an error was returned stating that the file format was invalid. Rolling back to 0.62 fixed the issue.