Why can't Tor Browser establish a connection?

Question

Browsers

Updated Tor Browser to the latest version 5.0.7, but after starting it can't connect. This has never happened before and I haven't been able to find a definitive answer. In the logs, if I understand correctly, it asks to correct the time, but the time is displayed correctly on the computer. What are your thoughts on this, maybe someone came across?
Here are the Tor event logs
: 01/12/2016 21:04:00.100 [NOTICE] Opening Socks listener on 127.0.0.1:9150
1/12/2016 21:04:00.100 [NOTICE] Renaming old configuration file to "C:\Users\Admin\ Desktop\Tor Browser\Browser\TorBrowser\Data\Tor\torrc.orig.1"
1/12/2016 21:04:00.300 [NOTICE] Bootstrapped 5%: Connecting to directory server
1/12/2016 21:04:00.400 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server
2016/01/12 21:04:01.000 [NOTICE] Bootstrapped 15%: Establishing an encrypted
directory
connection Bootstrapped 25%: Loading networkstatus consensus
01/12/2016 21:04:03.600 [WARN] Received directory with skewed time (server '171.25.193.9:80'): It seems that our clock is behind by 2 hours, 0 minutes, or that theirs is ahead. Tor requires an accurate clock to work: please check your time, timezone, and date settings.
1/12/2016 21:04:03.600 [NOTICE] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
01/12/2016 21:04:05.200 [NOTICE] Bootstrapped 40%: Loading authority key certs
2016/01/12 21:04:06.000 [WARN] Received directory with skewed time (server '199.254.238.52:443'): It seems that our clock is behind by 2 hours, 0 minutes, or that theirs is ahead. Tor requires an accurate clock to work: please check your time, timezone, and date settings.
2016/01/12 21:04:06.000 [WARN] Our clock is 1 hours, 55 minutes behind the time published in the consensus network status document (2016-01-12 19:00:00 UTC). Tor needs an accurate clock to work correctly. Please check your time and date settings!
2016/01/12 21:04:06.000 [NOTICE] I learned some more directory information, but not enough to build a circuit: We have no recent usable consensus.
2016/01/12 21:24:24.100 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150
01/12/2016 21:24:24.100 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
2016/01/12 21:24:24.100 [NOTICE] Closing old Socks listener on 127.0.0.1:9150
2016/01/12 21:24:24.300 [NOTICE] Delaying directory fetches: DisableNetwork is set.

Answer 1

google translate know where? In the logs it is clearly written that the torus does not like it.

Answer 2

Always or once? Sometimes it needs to be restarted five times in order to establish a connection.

Answer 3

Installed Thor. There is no connection at all. I have been waiting for 4 hours. Provider Kazakhtelecom-Kazakhstan. Can you advise me too.