Tor Browser 7.0.1 is released

Tor Browser 7.0.1 is now available from the Tor Browser Project page and also from our distribution directory.

This release features important security updates to Firefox.

This is the first minor release in the 7.0 series, updating Firefox to 52.2.0esr, Tor to, and HTTPS-Everywhere to 5.2.18. Additionally, we worked around an annoying freezing of Tor Browser which is due to a NoScript bug and made the security slider window slightly larger.

Here is the full changelog since 7.0:

  • All Platforms
    • Update Firefox to 52.2.0esr
    • Update Tor to
    • Update Torbutton to
      • Bug 22542: Security Settings window too small on macOS 10.12
    • Update HTTPS-Everywhere to 5.2.18
    • Bug 22362: NoScript's XSS filter freezes the browser
  • OS X
    • Bug 22558: Don't update OS X 10.7.x and 10.8.x users to Tor Browser 7.0

June 13, 2017


Avast(antivirus) flipped out on tor after it updated to 7.0.1 for me, same with the 7.0.1 installer. (Both got were "IDP generic Infection") Now I can't even download the installer (Avast is blocking it), what do I do?


June 13, 2017


Cloudflare is going crazy again?
Can't goto with tbb7.0.1, tested without javascript.
Is this the permanent state of affairs now?

I see this.
"Please turn JavaScript on and reload the page.
DDoS protection by Cloudflare"
but I don't go to theregister regularly.

I have same problem but find that hitting "reload" and surfing back seems to "work".

Confirm both the problem and the awkward workaround.

In torbrowser-install-x.x.x_ru (Russian localization) a long-standing problem when after two restarts website (gmail, youtube, livejournal ...) with several of the language versions opens in English. Although in the settings of TB priority is set - Russian.

Hm. I think that might depend on your exit relay. If that is in an english speaking country it often happens that you'll get english content. There is not much we can do about that. The localized bundles should give you a localized user interface.

It's not because of the exit relay. After unpacking until the first two restarts TB - everything is fine, but it's worth twice to restart TB - this problem manifests itself. If you move Up "Русский [ru-ru]" in the settings, the problem is solved. But exactly up to two restarts TB - then everything repeats.

Thanks, what do you mean with "If you move Up [...] in the settings"? Where do I need to do that in order to reproduce your problem?

Настройки > Содержимое > Языки (Выбрать).

[Options > Content > Languages (Choose)]

So, I looked at it and found at least one bug (I opened but I am not sure whether it is your bug. :) So, when you hit this issue did [ru] get dropped (again) from Options -> Content -> Languages or do you see the problem but it is still there?

Giving your "longstanding issue" I am assuming the latter but I want to be sure to investigate further if necessary.

EDIT: Re-reading your original post I found "Although in the settings of TB priority is set - Russian. " so it seems you experience that problem despite Russian still be the top priority, hm.

Yes, that problem despite Russian still be the top priority.

Tor Browser v7.0.x (Linux x86_64) seems slower than the previous v6.5.x series. It this because the underlying Firefox ESR got slower, or something to do with the Tor mods?

By "slower"I mean browser functionality, not networking throughput.

I'd assume that's because of the underlying Firefox ESR, although it is hard to tell. What does "seems slower" mean? Do you have some kind of measurements? If so, how can I repeat those?

Before, when I clicked New Identity, the browser was immediately closed and re-opened. With v7.0.x there's a hesitation of a few moments before the browser window is closed. In some cases the new window is opened even before the old one is closed, leaving 2 browser windows on the screen for an instant.

There is a way to instrument Firefox performance, and one of the metrics is browser start up. Sorry, I don't recall how to enable the metrics. It's been years since I've done it.

Okay, thanks. That particular issue is tracked in We might be able to do something about it, not sure yet, though.

Again Tails comes out at the same time on the day Torbrowser has a new release, leaving Tails insecure and unusable with an insecure version of Torbrowser.

This ongoing cooperative disconnection is a gift for governments and organizations that want to break peoples safety and security.
What is the agenda behind this ongoing not working together?
Please give the Tails people a chance to put the latest Torbrowser versions in their newest Tails versions.
Please work together.

Or is it mozilla that is always planning important security updates on release dates of Tails?
It is not a coincident anymore and it is not good for trust in your products.

Tails shipping at the same day as Tor Browser gets out already includes that new Tor Browser version. We coordinate with the Tails folks to avoid exactly the scenario you describe.

Your news update on Tails in

"Update Tor Browser to 7.0 (based on Firefox 52 ESR) ".

If your work together which is and would off course highly be appreciated, why do you mention 'update to Torbrowser 7.0" instead of "7.0.1" ?
7.0 is both mentioned on Torproject blog page as on the tails website.

Please make clear which browser version of Tor is in Tails.
The latest 7.0.1 one or the 7.0 one?

Thank you very much

A bigger problem with Tails is you get NO persistent Guard nodes!

Tails should come out with a new Debian release on June 17 to prevent such cases.

I wonder why 7.0 asks me to update to 7.0.1, and I found out that's because, but I hadn't change it! Possibly, it happened during 6.5.2 to 7.0 update. I'm on Windows 10.

Hard to tell what is going on. I just tried to reproduce your theory but the preference stay "true"...

Unable to print preview, crashes the tor browser (windows 10).

This is repeatable? In case you did use a previously installed version, does this happen as well with a clean, new Tor Browser installed in a different location?

There's indeed some problem with the print preview since TOR version 7.00 including 7.01 and 7.02 :_

Only a scale setting of 100% or "scale to fit page size" shows a correct print preview window. Any other value below 100% shows a grey area only.

This is on Ubuntu Linux with an European localised TOR version where our decimal point is a comma (i.e. "3,14" instead of "3.14"). When setting the scale factor in the print preview to, say, 80%, the localised TOR stores in about:config window this:
print.print_scaling = 0.50

But it should be:
print.print_scaling = 0,50

When I manually set the "0,50" in the about:config window, I can see a correct print preview once, and then I can also print with the correct scaling, but after I close the print preview window, the next time It opens it's again a grey area only, and with value = "0.50" again in the about:config window.

In TOR versions 6.x the values always have been "0,x" i.e. with comma instead of point, and everything worked fine. When having automatically upgraded from 6.x to 7.x the print preview worked (i.e. "0,50" values were stored in print_scaling) but with a fresh TOR 7.x installation, it won't work.

It has problems with fonts (tofu on buttons), but not crashes.

I dont have Mac Os. Why does the bug 22542 report that ? it is a cause of concern?

No. It was just reported in a macOS context and we fixed it for that one.

Bug 22542: Security Settings window too small on macOS 10.12

It is still too small to fit Medium level description on Windows :)

Which is why you have a scrollbar. :)

Maybe, make it wider this time? :)16

why it's not possible to create account on Instagram via tor browser?it says :"Sorry, something went wrong creating your account. Please try again soon."

Thank you for this. I think you keep improving Tor and I appreciate it.

The following custom torrc for Tor causes it to exit unexpectedly only when launched through the browser:

AvoidDiskWrites 1
Log notice stdout
CookieAuthentication 1
ControlPort 9622
SocksListenPort 9623

The problem lies with these three variables:


Remove all three of them, the browser can start tor without issue. Put any one of them back and tor crashes.

The strange thing is if you launch tor.exe separately and supply those on the commandline it launches without crashing:

NOTE: I also tried HashedControlPassword with same result

So I tried the following thing:

1) I took a clean Tor Browser 7.0.1
2) I started it and closed it
3) I edited the torrc file and added
ControlPort 9622
SocksPort 9623
4) I restarted Tor Browser and it worked
Regarding SocksListenAddress see:

Do you have by chance steps to reproduce your issue?

It appears to be a problem with the ports, It works fine if I change the ports to something else.

The strange thing is that netstat (windows) does not report those ports in use but tor.exe definitely crashes before the browser can even connect to it. The browser reports it exited unexpectedly.

Are they maybe used by the browser already without specifying them in the torrc file? network.proxy.socks_port and extensions.torlauncher.control_port are the relevant preferences (you can look the values of those up on the about:config page in Tor Browser).

How to enable torrent-magnets to work ?
I.e, calling the torrent client on a click.

I would expect magnet: link to show up in
Options (or Preferences), Applications pane

The help button (question mark in upper right side) goes to…

Then the follow link to…
Adding Download actions.
Does that help?

Both 7.0 and 7.0.1 don't work for me. Tabs crashes immediately when trying to open an url.

Could you give us more details about your setup? Does that happen with a newly download Tor Browser? Does it matter which URL (i.e. can you give us an example)? Which operating system are you on? If Windows, do you have antivirus/firewall software installed that could interfere with Tor Browser? If so, could you uninstall it for testing purposes (disabling is often not enough)?

Should I change dom.ipc.processCount to i.e. 8 to launch a new process for every tab (8) open in the browser?