title: Anaconda3 2.4 with python 3.5 installation error (procedure entry not found; Windows 10)
body: <p>I have just made up my mind to change from python 2.7 to python 3.5 and therefore tried to reinstall Anaconda (64 bit) with the 3.5 environment. When I try to install the package I get several errors in the form of (translation from German, so maybe not exact):</p>
  <blockquote>
  <p>The procedure entry &quot;__telemetry_main_return_trigger&quot; could not be found in the DLL &quot;C:\Anaconda3\pythonw.exe&quot;.</p>
  </blockquote>
  <p>and</p>
  <blockquote>
  <p>The procedure entry &quot;__telemetry_main_invoke_trigger&quot; could not be found in the DLL &quot;C:\Anaconda3\python35.dll&quot;.</p>
  </blockquote>
  <p>The title of the second error message box still points to pythonw.exe. Both errors appear several times - every time an extraction was completed. The installation progress box reads</p>
  <blockquote>
  <p>[...]</p>
  <p>extraction complete.</p>
  <p>Execute: &quot;C:\Anaconda3\pythonw.exe&quot; &quot;C:\Anaconda3\Lib_nsis.py&quot; postpkg</p>
  </blockquote>
  <p>After torturing myself through the installation I get the warning</p>
  <blockquote>
  <p>Failed to create Anaconda menus</p>
  </blockquote>
  <p>If I ignore it once gives me my lovely error messages and tells me that</p>
  <blockquote>
  <p>Failed to initialize Anaconda directories</p>
  </blockquote>
  <p>then</p>
  <blockquote>
  <p>Failed to add Anaconda to the system PATH</p>
  </blockquote>
  <p>Of course nothing works, if I dare to use this mess it installs. What might go wrong? On other computers with Windows 10 it works well.</p>
  <p>P.S.: An installation of Anaconda2 2.4 with python 2.7 works without any error message, but still is not able to be used (other errors).</p>