search

ContinuumIO / anaconda-issues

Anaconda issue tracking
646 stars 220 forks source link

Just installed 5.2 on Windows 7 Enterprise SP1 system, no activate.bat in Scripts dir #9520

Open ijstokes opened 6 years ago

ijstokes commented 6 years ago

Actual Behavior

I open the Anaconda Prompt and I get the message C:\Anaconda\Scripts\activate.bat not found. I checked that path, and there are lots of files but no activate.bat

Expected Behavior

The Anaconda Prompt should open and activate Anaconda adding it to the PATH.

Steps to Reproduce

Windows 7 Enterprise SP1 installation with virgin install of Anaconda 5.2.0 installed as Administrator.

Anaconda or Miniconda version:

5.2.0

Operating System:

Windows 7 Enterprise SP1

conda info
conda list --show-channel-urls
msarahan commented 6 years ago

We've seen issues with antivirus causing this sort of thing. I don't think there's much we can do about it, beyond completely reworking our installer on something better than nsis.

ijstokes commented 6 years ago

So that suggests that it could be in the AV quarantine logs? If I find out the AV software, what's the best process to escalate this and get activate.bat whitelisted? For me to do it or for you to do it?

msarahan commented 6 years ago

If you're able to figure that out, I'm guessing it would probably be good to report it to the AV vendor from both sides - you as the customer and us as the provider both saying "yes, this is fine" might have more impact than just one of us.

It may or may not be in the quarantine, though. We've seen more subtle things about race conditions and perhaps timeouts of some sort? Like sometimes those files don't end up in place because the AV slows the filesystem down so much that NSIS just doesn't do the right thing. That'll probably be harder to recover from. Fingers crossed that you have everything in the quarantine.