nextpvrserver crashing

[atreistm]

I am running Windows Insider Dev 20206. The nextpvrserver.exe process crashes.

Application: NextPVRServer.exe
CoreCLR Version: 4.700.20.36602
.NET Core Version: 3.1.7
Description: The process was terminated due to an unhandled exception.
Exception Info: 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 Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.SocketConnectionListener.Bind()
  at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.SocketTransportFactory.BindAsync(EndPoint endpoint, CancellationToken cancellationToken)
  at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServer.<>c__DisplayClass21_0`1.<<StartAsync>g__OnBind|0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
  at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.BindEndpointAsync(ListenOptions endpoint, AddressBindContext context)
  at Microsoft.AspNetCore.Server.Kestrel.Core.ListenOptions.BindAsync(AddressBindContext context)
  at Microsoft.AspNetCore.Server.Kestrel.Core.AnyIPListenOptions.BindAsync(AddressBindContext context)
  at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.AddressesStrategy.BindAsync(AddressBindContext context)
  at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.BindAsync(IServerAddressesFeature addresses, KestrelServerOptions serverOptions, ILogger logger, Func`2 createBinding)
  at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServer.StartAsync[TContext](IHttpApplication`1 application, CancellationToken cancellationToken)
  at Microsoft.AspNetCore.Hosting.WebHost.StartAsync(CancellationToken cancellationToken)
  at Microsoft.AspNetCore.Hosting.WebHostExtensions.RunAsync(IWebHost host, CancellationToken token, String startupMessage)
  at Microsoft.AspNetCore.Hosting.WebHostExtensions.RunAsync(IWebHost host, CancellationToken token, String startupMessage)
  at Microsoft.AspNetCore.Hosting.WebHostExtensions.RunAsync(IWebHost host, CancellationToken token)
  at Microsoft.AspNetCore.Hosting.WebHostExtensions.Run(IWebHost host)
  at NPVR5.Program.Main(String[] args)


Event ID 1000
Faulting application name: NextPVRServer.exe, version: 1.0.0.0, time stamp: 0x5f1757ad
Faulting module name: KERNELBASE.dll, version: 10.0.20206.1000, time stamp: 0xac004ce1
Exception code: 0xe0434352
Fault offset: 0x00000000000735bc
Faulting process id: 0x3ddc
Faulting application start time: 0x01d686cca10765dc
Faulting application path: C:\Program Files\NextPVR\NextPVRServer.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: 2d98bbae-7228-4e8f-9a27-53a973038e51
Faulting package full name:
Faulting package-relative application ID:

[mvallevand]

Are you running a VPN, firewall or a/v internet suite which might be getting in the way create ports on a local LAN?

Also are you running the exe or the service?

Martin

[atreistm]

Are you running a VPN, firewall or a/v internet suite which might be getting in the way create ports on a local LAN? 

Also are you running the exe or the service?

Martin

Windows Defender. I can double check the firewall again.  The service crashes, and running the exe crashes the same.  The app used to work fine, maybe there are breaking changes in the latest version of .Net core?

[mvallevand]

I expect it is a local issue. You can rerun installservice.bat as admin to reset the firewall.

Martin

[atreistm]

I think the problem is that later Windows updates are blocking many ports, including port 8866.  Maybe because I have Hyper-V installed. 

See https://superuser.com/questions/1486417/...t-in-a-way

I switched to port 30000 and it now works.

[mvallevand]

You can disable hyper-v and exclude 8866 tcp for ipv4/6 and 16891 ipv4 udp There is no guarantee that 30000 won't be randomly grabbed.

Martin