Tomorrow Windows 10 it’s going to be available and I would like to know if I should update or wait.
We haven’t tested it ourselves, it should work as long as .net 4.0 is available (.net 4.5 should include it). Beware of Edge though:
Thanks Markus
sonarr no longer starts at boot with windows 10, even the service is set to automatic.
manually starting the service does work.
it looks like several services are broken in windows 10 - show automatic but not starting
Did you upgrade or do a clean Windows 10 install?
upgrade from 8.1
also killed drivepool
i upgraded from Win7 to Win10 (pro) and ever since i can only access Sonarr through localhost. 127.0.0.1 or the I.P. or the DNS don’t load the page. All my other web services still work (Sabnzbd, CouchPotato, µTorrent).
When analyzing logs i notice the following error (having set the bind address to the ip address, it only launches when * is inserted as bind address):
— End of inner exception stack trace —
—> (Inner Exception #0) System.IO.IOException —> System.Net.HttpListenerException: The handle is invalid
at System.Net.HttpResponseStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at Microsoft.Owin.Host.HttpListener.RequestProcessing.ExceptionFilterStream.Write(Byte[] buffer, Int32 offset, Int32 count)
— End of inner exception stack trace —
I tried installing Sonarr on a newly installed Win10 Virtual machine and get the exact same error.
@joachim_buyse run Sonarr once as administrator. maybe it just needs the http reservation.
Ow and also check your firewall, Win10 may have changed the zone of your home network to ‘public’.
2 Likes
Taloth, thanks for the quick reply.
I have already running it with admin rights first time after a clean install. also tried running it as a service with both “network service” and with my local admin account as the “logon to” for the service.
I checked the zone as you suggested and it is still showing as a home network. also i don’t have any firewall active both on private and public networks.
when i do a “netsh http show urlacl” it does show be the entry
"Reserved URL : http://*:8989/
User: \Everyone
Listen: Yes
Delegate: No
SDDL: D:(A;;GX;;;WD)"
but it still will not allow me to access Sonarr without using http://localhost:8989 …
Did you set a bind address in Sonarr? (General settings)
1 Like
Hey Guys,
First of all thanks for the quick and constructive response: this is how a forum should be!
I took my time this evening to reinstall Windows 10 from scratch just to start with a clean setup as I suspected that the issue was underlying Windows error and I was right. Basically the error I wrote first is related to a .NET4.0 call and as Windows 10 now uses the new Windows Universal App platform instead, I think that during the in place upgrade it messed something up with the way windows handled that call.
Anyways, after a clean reinstall all my issues have been solved and it works beautifully.
Thanks a lot for the help!
Also did a clean install of Win10, no problems noticed with sonarr as yet, installed fine, working fine
Win10 seems to default to Public which is a bit annoying - it didnt ask
Yeah I noticed that as well, but found a quick solution:
https://tinkertry.com/how-to-change-windows-10-network-type-from-public-to-private
Still not having any problems with Sonarr so the issue was indeed from the upgrade install. Clean install for the win!
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.