New Release: Tor Browser 10.0.11 (Windows Only)

Why not put it on your normal download page? Why the distribution directory, which is confusing for a lot of users. Surely, unsuspecting users will still be downloading the bad version (10.0.10) with the critical security issue from your normal download page? That's not good.

Hi there!
Why didn't you compile 0.4.4.7-binaries for it?

At least distribution directory is still pointing to
- tor-win32-0.4.4.6.zip and
- tor-win64-0.4.4.6.zip

CY

It seem like I got increased "CPU Usage" playing video at Youtube (360p). Does any one observe such performance degradation?
(Also I will try to test and reproduce and post here updates concerning the issue)

sounds good

Lovely

As of today (Feb.11) pluggable transport (obfs4) ceases to function on multiple (win10 x64 and x86) installations. Only direct connection to Tor through entry guard works (partially - not all the time).
The only thing these installations had in common was the latest Windows Update SSU (KB4592449) and .NET security update (KB4601056) - removing these through system restore didn't improve the situation though (SSU's cannot generally be uninstalled though, so I have a hunch saying that SSU KB4592449 can be the cause).

Are the pluggable transports malfunctioning in v10.0.11 (starting today?), under general attack today or are we seeing or are we seeing an unwanted impact from Microsoft Updates?

Copy of log:

2/10/21, 21:19:22.789 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
2/10/21, 21:19:22.790 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
2/10/21, 21:19:22.790 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
2/10/21, 21:19:22.790 [NOTICE] Opening Socks listener on 127.0.0.1:9150
2/10/21, 21:19:22.790 [NOTICE] Opened Socks listener on 127.0.0.1:9150
2/10/21, 21:19:22.790 [WARN] CreateProcessA() failed: The system cannot find the file specified.
2/10/21, 21:19:22.791 [WARN] Pluggable Transport process terminated with status code 0
2/10/21, 21:19:22.791 [WARN] Failed to start process: (null)
2/10/21, 21:19:22.791 [WARN] Managed proxy at 'TorBrowser\Tor\PluggableTransports\obfs4proxy.exe' failed at launch.
2/10/21, 21:19:23.540 [WARN] We were supposed to connect to bridge '[obfs4 bridge IP]' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
2/10/21, 21:19:23.540 [WARN] Problem bootstrapping. Stuck at 0% (starting): Starting. (Can't connect to bridge; PT_MISSING; count 1; recommendation warn; host [obfs4 bridge])
2/10/21, 21:19:23.700 [WARN] We were supposed to connect to bridge '[obfs4 bridge 2 IP]' ... etc..