Odd startup problem with recent Windows update

[zape 2]

My Windows 10 system installed 2 updates yesterday KB5027215 and KB5027538.  Since then, Emby crashes on startup when loading port 8096: 

2023-06-14 20:25:28.580 Info App: Adding HttpListener prefix http://+:8096/
2023-06-14 20:25:28.680 Error Main: Error in appHost.Init
 ...
    System.Net.Sockets.SocketException: System.Net.Sockets.SocketException (10013): An attempt was made to access a socket in a way forbidden by its access permissions.
       at System.Net.Sockets.Socket.UpdateStatusAfterSocketErrorAndThrowException(SocketError error, String callerName)
       at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
       at System.Net.Sockets.Socket.Bind(EndPoint localEP)
       at Emby.Server.Implementations.HttpServer.KestrelHost.KestrelListener.CreateBoundSocket(EndPoint endpoint)
       at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.SocketConnectionListener.Bind()

Fill log file attached.  I've ran netstat and nothing is using 8096.  Any thoughts?  I'm by no means an expert.

 

I have rebooted, and I have tried running the server as admin.  No change to behaviour.

embyserver-63822370900.txt

Edited June 15, 2023 by zape

[ebr 16187]

Hi.  Have you checked your firewall settings to be sure no blocking rules were added?

[zape 2]

I didn't know how to find rules by date, so I turned off the firewall in windows defender for all groups (domain, private: what I was connected to, and public)

 

Same behavior

[ebr 16187]

I don't think turning off the Firewall in Windows actually opens everything up.

Make sure that your local network was not reset to "Public" by the updates.  It should be "Private".

[zape 2]

Yes, I'm on private...  a couple of screenshots attached showing no active public connections, and the details under private.  The only thing that I can tell changed was the new patches applied by Microsoft at the time it started failing.

[ebr 16187]

What rules exist in the firewall for embyserver.exe?

[zape 2]

Name	Group	Profile	Enabled	Action	Override	Program	Local Address	Remote Address	Protocol	Local Port	Remote Port	Authorized Users	Authorized Computers	Authorized Local Principals	Local User Owner	PolicyAppId	Application Package	
Emby Server		All	Yes	Allow	No	C:\Users\james\AppData\Roaming\Emby-Server\system\EmbyServer.dll	Any	Any	TCP	Any	Any	Any	Any	Any	Any	None	Any	
Emby Server		All	Yes	Allow	No	C:\Users\james\AppData\Roaming\Emby-Server\system\EmbyServer.dll	Any	Any	UDP	Any	Any	Any	Any	Any	Any	None	Any	
EmbyServer.exe		All	Yes	Allow	No	C:\Users\james\AppData\Roaming\Emby-Server\system\EmbyServer.dll	Any	Any	TCP	Any	Any	Any	Any	Any	Any	None	Any	
EmbyServer.exe		All	Yes	Allow	No	C:\Users\james\AppData\Roaming\Emby-Server\system\EmbyServer.dll	Any	Any	UDP	Any	Any	Any	Any	Any	Any	None	Any	
Port 8096		All	Yes	Allow	No	Any	Any	Any	TCP	8096	Any	Any	Any	Any	Any	None	Any	
Port 8920		All	Yes	Allow	No	Any	Any	Any	TCP	8920	Any	Any	Any	Any	Any	None	Any	

 

[Luke 42083]

Can you try rebooting your machine?

[zape 2]

I can do that again.  As mentioned in the original post, that is one of the things I tried.  Do you want me to make any firewall changes before I reboot?

[ebr 16187]

There are no rules there for "embyserver.exe".  They are all just for the dll...

There is also no rule allowing UDP (the discovery protocol).

[zape 2]

it's worked before.  I'll add all of those then reboot.

[zape 2]

That did it!  How strange that the new rules were needed.  Thanks very much!   Family will be happy.