Windows: On some systems, admin users cannot immediately install "for all users"

(Updated March 18, 2015)

On Windows Vista and above with User Access Control (UAC) enabled, the msi installer does not enable the "Install for All Users" option, which is required to install Canopy to "Program Files". In this case, you need to start the installation from a command prompt with elevated privileges, by doing these steps exactly (even if you are already an administrator):

  1. Type "cmd" in the start menu text entry box.

  2. Right-click on the "cmd" program which appears at the top of the start menu and select "Run as Administrator".

    (Sys admins: to automate this escalation step, you can use SysInternal's "PsExex -h", described at http://technet.microsoft.com/en-us/sysinternals/bb897553 .)

  3. At the command prompt, type the following (type the actual path and filename instead of "c:\<path-to-canopy-installer-file>.msi"): 
    msiexec /i "c:\<path-to-canopy-installer-file>.msi" ALLUSERS=1
  4. If you are presented with a dialog asking you whether to install for all users or for just this user, select "All Users".
  5. If you will be doing a Common Install (see link below), be sure to uncheck the "Launch application" option at the end of the installation. Do not start the application until after you have configured the common install.

These are Microsoft's recommendations for installation on UAC-enabled systems. Please contact us with further questions.

Related article:

For multi-user setups with more than a few users, we strongly recommend the "Common Install" procedure described here:  https://support.enthought.com/entries/26491185-Understanding-a-Canopy-system-wide-installation-common-install-

 

Please do not enter support requests in article comments

Please use article comments for suggestions to improve the article. For individual support requests, please follow these guidelines.

Have more questions? Submit a request

Comments

  • Avatar
    Terry Bradley

    These instructions are not working correctly with the canopy-1.4.0-full-win-64.msi installer -- it hangs somewhat on starting the installation, then appears to be "validating" correctly, then throws a network error ...    I have followed the above instructions exactly - and the .msi is located locally, not on a network share.  Any suggestions?  Thanks...

  • Avatar
    David Thompson

    Its not working for me either. The error message I get in the windows command line is: "The system cannot find the file specified".

  • Avatar
    David Thompson

    I was able to get it to work. At the command prompt I had initially failed to type in the correct path and filename. I relocated the file on my computer, created a shortcut and then copied the link from the properties box of the shortcut, and pasted this in at the appropriate place in the command line. It worked. I realized that the path has to be in quotation marks to run correctly. I also learned that even though my command prompt says C:\windows\system32 it is able to install a 64 bit application. I'm sure this is terribly basic for many, but hopefully may be helpful for a few like myself who are starting with little knowledge of these things.

  • Avatar
    mark conley

    "the system cannot find the file specified" is all i get, help ....

  • Avatar
    Terry Bradley

    David, glad you were able to get it to work - but that was not the source of the issue in my case.  ;-)

    The 1.4.1 version installation appears to work "better", but will still throw an error dialog at the end of the installation:  "Found invalid installation in C:\CanopyEnvironment\System! We will reset your Canopy environment to provide you a working installation. Your user data and packages will be preserved." 

    Well, that's bogus - this is a (relatively) new desktop, with no prior Canopy installation.  Clicking OK kicks to a successive dialog: "Please wait - Cleaning up broken install..." - which chews for a while, and returns to the "invalid installation" dialog. Clicking OK on this 2nd occurrence puts me back to the "Cleaning up broken install..." dialog, which chews for an even longer time, but finally begins setting up the Canopy environment, and starts the IDE.

    Mark, how are you specifying your installer file path?

  • Avatar
    Christopher Karystianos

    Instructions worked as described for me ..no errors! (Windows 8.1 , Canopy 1.4.1). Thank you ! (It was very annoying to waste 2GB in the AppData folder.)

  • Avatar
    Mark Stevison

    Has anyone had any success deploying Canopy with SCCM 2012?  I am able to get it installed using the command above but cannot figure out how to get the PsExec, SCCM and a batch file to play well together.

  • Avatar
    Jonathan March

    @Mark, not clear what your use case is, but for multi-user / network installs, have you looked at http://docs.enthought.com/canopy/configure/canopy-cli.html ? Feel free to email canopy.support@enthought.com if you'd like to provide details.

  • Avatar
    Matt Roush

    No luck using SCCM2012 for me either. The above command works, but still will not run the program for non local administrator accounts (student accounts). I have set the canopy.exe to run as administrator for all users, and still will not run. The error is in setting up the environment, Is there any other info on this? Project Lead The Way class at a standstill....

  • Avatar
    Jonathan March

    To Mark & Matt's questions above, see the "Related article link" added to the article above.

  • Avatar
    Terry Bradley

    Follow-up:  the canopy-1.5.1-full-win-64.msi installer (full package) does seem to work for all-users installation at this point -- I will note that we have to put the installer into a temp folder locally (installing over the network sometimes fails, even with GigE connection). On occasion, we have encountered the "Account already exists" error, in which case I've had to run the Microsoft Fix-It uninstaller and retry installing Enthought. But, generally, installations are working much more successfully for us - a good thing.