Anaconda installation two or three things

The recent intention to transfer to the Python3 before the installation of the anaconda2 can not be normal use of Conda update (did not realize that has been transferred to the pit) to directly delete the anaconda2 change Anaconda3 did not expect to fall into the pit ...
But the pit is quite distinctive. Simply summed up a good first pit

Installation near end times wrong
Failed to create Anaconda menus
Failed to add anaconda to the system PATH


(The picture is from https://github.com/ContinuumIO/anaconda-issues/issues/732 to the owner of the pit)

Online solutions are as follows: To ensure that the installation directory does not include Chinese, the installation directory is not too long (the system is limited to the length of the path, seemingly normal 2048 characters, administrators run 1024 characters), directly dropped in a disk Fugen directory of the Anaconda folder is good to ensure that administrator rights are provided, Originally installed for a single user, try installing for all users, and vice versa. First install the Microsoft Visual C + + 2008 Redistributable Package (x64) Portal: https://www.microsoft.com/en-us/download/details.aspx ? id=15336 ", reboot and then install Anaconda (this is the case, Win10 Build14393.693, successfully installed into the next pit) pop-up dialog box all choose to ignore the installation completed after the implementation of the CMD manual operation

"C:\Anaconda\pythonw.exe"-e-s "C:\Anaconda\Lib\_nsis.py" Mkmenus
"C:\Anaconda\pythonw.exe"-e-s "C:\Anaconda\Lib\_nsis.py" mkdirs
"C:\Anaconda\pythonw.exe"-e-s "C:\Anaconda\Lib\_nsis.py" Addpath

(assuming you are installed in C:\Anaconda this directory) the previous method failed, try to manually

C:\Anaconda
C:\Anaconda\Scripts
C:\Anaconda\Library\bin

(Again, let's say you installed it in the C:\Anaconda directory.)
Add to environment variables and then find the program you need in both the C:\Anaconda and C:\Anaconda\Scripts folders manually add shortcuts to desktop/Start menu reload Windows system simply install Linux or MACOSX
a second pit .

Conda update failed
Yes, I was in this pit before.

PS c:\users\administrator> Conda Update Conda
fetching package metadata ...

Condahttperror:http none None for URL <None>
elapsed:none a

HTTP error occurred when trying to retrieve t His URL.
Sslerror (Sslerror (Sslerror ("Bad Handshake:syscallerror (10054, ' Wsaeconnreset ')",),)

Not only is the PIP not used

PS c:\users\administrator> pip Install virtualenv
collecting virtualenv could not
  fetch URL https:// pypi.python.org/simple/virtualenv/: There was a problem confirming the SSL certificate: [S
Sl:certificate_verify_ FAILED] Certificate Verify FAILED (_ssl.c:749)-skipping could not find
  a version that satisfies the requirement virt Ualenv (from versions:)
No matching distribution found for virtualenv

(Here take PIP installation virtualenv do an example actually update Conda also don't seem to be the same) and I was in the first pit trying to update the Conda and then manually install it with _nsis.py and then directly into the pit.

Condahttperror:http none None for URL <None>

This is a very interesting error. I didn't find a similar problem in overflow, which is why so many people around the world don't have this problem. In other words, it could be a xx-featured network problem.

Results in a non-existent search engine at the end of a G-beginning E, Tales's article "Portal: http://talesyuan.blog.163.com/blog/static/920046082016112102643429/" was found. The browser tried a bit Repo.continuum.io the site did not exist (there was no change in the network after it magically appeared)

Which means the problem is in my black technology.

Decisive changes. Condarc add these two lines

Proxy_servers:
    http:http://user:pass@corp.com:8080
    https:https://user:pass@corp.com:8080

The results came up.

PS c:\users\administrator> Conda Update Conda
fetching package metadata ...

Condahttperror:http none None for URL <None>
elapsed:none a

HTTP error occurred when trying to retrieve t His URL.
Proxyerror (maxretryerror httpsconnectionpool (host= ' mirrors.tuna.tsinghua.edu.cn ', port=443): Max retries exceeded
with URL:/anaconda/pkgs/free/win-64/repodata.json (caused by proxyerror) (' Cannot connect to proxy. ', Newconnectionerror (' <req
uests.packages.urllib3.connection.VerifiedHTTPSConnection object at 0x000002de06567898>: Failed to establish a new Conne
ction: [Winerror 10061] cannot connect because the target computer is actively rejecting. ',)))",),)

The PIP, however, is completely normal after using the –proxy and –trusted-host options.

Turn off the black tech tool at the end of my X-Net, Conda still unavailable, which means that black tech tools, like 370 software, modify what's in the registry, which causes global HTTPS to go through its proxy server, such as Conda.
370 I can get rid of black technology, I really hate to

Wait a minute... Global.
After canceling the global agent , Conda will be able to connect to the normal network.

WTF. I wasted a whole afternoon in this pit. Including reinstalling Anacond also because of this (manual antics)

Note: Not only the technology at the end of the X-Net, I guess there's a name with go. At least two S is possible. Open Global Agent SSL authentication is not Pip,conda, etc.