#30609 closed defect (not a bug)

Issue Starting Tor Browser On Windows

Reported by: broman Owned by: tbb-team
Priority: Very High Milestone:
Component: Applications/Tor Browser Version:
Severity: Critical Keywords: tor browser error
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:



So on the newest tor browser 8.5, something causes it to crash on Windows.
I have tried several times, and each time it gets stuck on this message. I have tried reinstalling tor browser and configuring my network settings, only to get the same message.

Tor failed to establish a network connection.

Establishing an encrypted directory connection failed (done -

Any thoughts on why this is happening is appreciated. Thank you.

This is the tor log when this is happening:

5/24/19, 20:57:51.790 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server
5/24/19, 20:58:26.238 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host 6EF897645B79B6CB35E853B32506375014DE3621 at
5/24/19, 20:58:26.240 [WARN] 10 connections have failed:
5/24/19, 20:58:26.240 [WARN] 7 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE
5/24/19, 20:58:26.240 [WARN] 2 connections died in state connect()ing with SSL state (No SSL object)
5/24/19, 20:58:26.240 [WARN] 1 connections died in state handshaking (Tor, v3 handshake) with SSL state SSL negotiation finished successfully in CLOSED
5/24/19, 20:58:26.267 [NOTICE] Closing no-longer-configured Socks listener on
5/24/19, 20:58:26.267 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
5/24/19, 20:58:26.267 [NOTICE] Closing old Socks listener on

Child Tickets

Change History (1)

comment:1 Changed 16 months ago by gk

Resolution: not a bug
Status: newclosed
Version: Tor:

That's not Tor crashing but not being able to connect properly. It seems someone/something is intefering with the Tor connection and Tor therefore fails. You could try using a built-in bridge to work around that, see: https://tb-manual.torproject.org/transports/

Note: See TracTickets for help on using tickets.