We appreciate the contributions many of you have been able to make towards repairing the storm damage and keeping a roof over our heads. With your help we’ve been able to complete much of the critical work. There is still work to be done to secure the house and your continued support will be a huge help.
Guests have read-only access to our forums. If you wish to participate you will need to register. Be sure to activate your account from the email sent to you when you register.
Recently, I haven't been able to finish downloading updates. This has been going for at least a few weeks. As you can see in the screenshot below, the downloading just gets stuck at around 99% and it doesn't move further any more. Is this really because there are no seeders available or is it more likely that something is wrong on my end?
I've been using SDIO for years now, and this is the first time downloading has got stuck this way for such a long time. It was already stuck in SDIO v2.0.3, and now I've tried upgrading to SDIO v2.0.4 manually but to no avail. Also, I've tried to remove the updates folder, indexes, etc., i.e. basically start from scratch but it did not help either.
Have you got any idea what the culprit could be here? For the record, I'm on my home network, so no corporate firewalls, etc. are in effect.
There's plenty of seeders. In fact the we've got more seeders now than we've had in a long time. You've got 0 seeders and 0 peers showing, tells me something is amiss, possibly connection to trackers is failing. Are you able to test it using a different internet connection, say mobile phone hotspot?
Having the same issue since version 2.0.3, also happening on 2.0.4 as well. Shows 0 seeds/peers and vary rarely does it connect to a peer and download data. No changes to the network have been made since previous working versions and port is forwarded from the router to the pc running SDIO.
Ok. I'm wondering if it's because I've only added UDP trackers to the torrent. Maybe check your firewall to see if it allows udp torrent traffic.Having the same issue since version 2.0.3, also happening on 2.0.4 as well. Shows 0 seeds/peers and vary rarely does it connect to a peer and download data. No changes to the network have been made since previous working versions and port is forwarded from the router to the pc running SDIO.
I forgot to post an update, but it was in fact caused by the Windows Firewall... 😠
Not sure what happened exactly but it seems that the usual firewall pop-up had only been shown in the background behind all other opened windows with nothing indicated on the taskbar. I only saw it after closing and minimising all other programs. After allowing network access for SDIO, it immediately started to download the remaining updates.
I guess I need to pay more attention next time 😳.
I've been seeing that a bit lately. Another Windows improvement. 😆firewall pop-up had only been shown in the background behind all other opened windows with nothing indicated on the taskbar
Tried turning off windows firewall as well and still have no luck finding seeds removed link
@greyscourier That looks like our server.
Edit: I'm a bit confused. If the server is blocking your ip, how are you logging on?
I had similar problem, i spent few hours with AI to try solve this problem......
Subject: Bug Report / Feedback: Embedded torrent client fails to connect on systems with virtual adapters and ISP filtering
App Version: Snappy Driver Installer Origin v2.0.4
Environment: Windows 11 x64 (with WSL2 / Hyper-V / VPN virtual adapters installed)
Problem Summary
When attempting to download driver pack updates or the initial 22 MB indexes archive, the update window hangs indefinitely at 0 bytes (0%) with Seeds: 0 (0), Peers: 0 (0). While the application successfully fetches the list of available driver packs via HTTP, the embedded libtorrent engine never establishes peer or tracker connections.
Root Causes
-
Uncontrolled Socket/Interface Binding (Virtual NIC Conflict)
On modern developer and power-user workstations running WSL2, Hyper-V, Docker, or mesh VPNs (e.g., Tailscale), Windows exposes multiple virtual network interfaces.
-
By default, Windows routing tables and IPv6 prefix precedence often give lower metrics or higher precedence to these virtual adapters over physical IPv4 Ethernet.
-
SDIO’s embedded
libtorrentbinds its listening and outbound sockets to whichever interface Windows ranks highest (often a virtual adapter's internal IP or non-routable IPv6 tunnel). As a result, DHT bootstrapping and tracker announces fail completely. -
SDIO currently provides no flag or config option in
sdi.cfgto explicitly specify a network interface or bind IP (listen_interfaces).
-
-
Lack of BitTorrent Protocol Encryption (PE/MSE)
SDIO’s torrent implementation initiates unencrypted, plaintext handshakes on known default ports (
50171). Major residential ISPs (notably across the UK and parts of Europe) actively deploy Deep Packet Inspection (DPI) to throttle or drop unencrypted BitTorrent handshakes and block public tracker hostnames. Because the embedded client lacks encryption enforcement, all connection handshakes are dropped at the ISP exchange. -
No HTTPS Fallback for Critical Metadata (Indexes)
SDIO requires the ~22 MB
indexespackage just to scan local hardware and determine which.7zpacks are required. Locking this essential 22 MB bootstrap file strictly behind BitTorrent makes the entire application unusable in networks where P2P traffic is blocked or throttled.
Suggested Fixes
-
Expose Network Interface Binding in
sdi.cfgAllow users to pass a command-line argument or configuration parameter (e.g.,
-bind:<Adapter_IP>or-bind-interface:<Name>) to pass directly tolibtorrent::session_settings/listen_interfaces. -
Enable Protocol Encryption (PE/MSE) by Default
Configure
libtorrentto enable or prefer header/payload encryption (pe_settings::enabledorpe_settings::forced) so handshakes bypass ISP DPI filtering. -
HTTP/HTTPS Direct Fallback for Indexes
If the torrent session cannot find any peers or seeds within 30–60 seconds, fail over to fetching the 22 MB
indexesarchive directly via HTTPS from the web server/CDN, reserving BitTorrent solely for the multi-gigabyte driver archives.
@mh825 I've uploaded v2.0.5 here: https://www.glenn.delahoy.com/snappy-driver-installer-origin/
I've added the following options to sdio.cfg (not yet documented)
-bind-listen:10.0.xxx.xxx:50666,[2403:5817:a62e:0:xxxx:xxxx:xxxx:xxxx]:50667 -bind-outgoing:10.0.xxx.xxx,2403:5817:a62e:0:xxxx:xxxx:xxxx:xxxx -enc-policy-in:1 -enc-policy-out:1
* the -bind-listen option is a comma separated list of ip:port pairs. This can be any combination of ipv4 and ipv6. Note that ipv6 addresses must be enclosed in square brackets, followed by the colon and port number as above
* the -bind-outgoing option is a comma separated list of ip addresses, no ports. Note that ipv6 addresses are *not* enclosed in square brackets
* the -enc-policy-in and -enc-policy-out are encryption policies for incoming and outgoing connections where 0=forced, 1=enabled (default), 2=disabled
@mh825 is it listening on the correct network? check with netstat or Desktop Info or resource monitor
Unfortunately, I'm still experiencing the issue. I'm not sure what it is, but this time there is just no Windows Firewall pop-up at all. I've tried adding SDIO to Windows Firewall manually but it hasn't helped. Both seeders and peers are stuck at 0 removed link I've also upgraded to v2.0.5 but it hasn't made any difference 😥.