HOW TO: Install Interix

Support for Windows XP has ended

Microsoft ended support for Windows XP on April 8, 2014. This change has affected your software updates and security options. Learn what this means for you and how to stay protected.

This article was previously published under Q324081
This article has been archived. It is offered "as is" and will no longer be updated.
The Interix subsystem provides a fully POSIX-compliant environment that runs as a native subsystem in the Windows kernel. It includes both the Korn Shell and the C Shell and over 350 command-line utilities. If you install Interix Software Development Kit (SDK), you have full support for more than 1,900 UNIX functions.

back to the top

Installing Interix Subsystem, Base Utilities and SDK from the Command Line

Windows Services for UNIX version 3.0 uses Microsoft Installer for installation. As a result, you can install individual modules of the product from the command line. If previous components of Windows Services for UNIX have been installed, you must include these components in the addlocal parameter of the installation command line, separated by a comma (,). If you do not do so, these products are removed during the installation of Interix. If you install Interix SDK automatically, the Interix subsystem and the base utilities are automatically included in the installation.

To install Interix from the command line:
  1. Log onto the Windows computer with an administrative level account.
  2. Open a command window. Click Start, click Run, type in cmd and click OK.
  3. Insert the Services for UNIX version 3.0 CD into the CD drive. (Drive D: for this example.)
  4. You can install various combinations of the Interix subsystem and interix SDX. These include:
    • From the command prompt, to install the Interix Subsystem and BaseUtilities:msiexec /I D:\sfusetup.msi /qb addlocal="BaseUtils" [targetdir="installpath"]

    • To install Base Utilities and the GNU Utilitiesmsiexec /I D:\sfusetup.msi /qb addlocal="GNUUtils" \ [targetdir="install path"]

    • To install Base Utilities, UNIX Perl and GNU Utilitiesmsiexec /I D:\sfusetup.msi /qb addlocal="GNUUtils,UNIXPerl" \ [targetdir="install path"]

    • To install the Interix SDK, including Base Utilitiesmsiexec /I D:\sfusetup.msi /qb addlocal="InterixSDK" [targetdir="installpath"]

  5. To install the GNU SDK and GNU Utilities (includes Interix SDK and Base Utilities)msiexec /I D:\sfusetup.msi /qb addlocal="GNUSDKSDK,GNUUtils " \ [targetdir="install path"]

  6. Default install path is "\SFU".Note:Services for UNIX should be installed in a directory without spaces in the path to prevent problems with some components of SFU. Microsoft recommends that you install SFU to the default directory.

  7. To include the Product Key as part of the command line, add pidkey="key" where "key" is the 25 character product key, without dashes. Note: If you are installing the base utilities with the /qb option, you will be required to choose whether you want to enable setuid behavior for Interix programs. (If you are using the /q option, setuid behavior will be disabled by default.) The choice you make will affect both system security and how certain Interix programs behave.

    According to the POSIX standard, a file has permissions that include bits to set a UID (setuid) and set a GID (setgid) when the file is executed. If either or both bits are set on a file, and a process executes that file, the process gains the UID or GID of the file. When used carefully, this mechanism allows a nonprivileged user to execute programs that run with the higher privileges of the file's owner or group. When used incorrectly, however, this can present security risks by allowing nonprivileged users to perform actions that should only be performed by an administrator. For this reason, Windows Services for UNIX Setup does not enable support for this mechanism by default.

    You should enable support for setuid behavior only if you are sure you will be running programs that require support for this behavior. Even if you do not enable support for setuid behavior when installing Windows Services for UNIX, you can enable it later.

  8. A reboot will be required. Note: If installing from a telnet prompt, where no GUI is available, or via a script, modify the command line by changing the /qb to /q. This will install without any user interaction at all. By default the setuid behavior will be disabled. See the install.htm on the Services for UNIX CD.

    Note: The addlocal parameter to msiexec show above is case and spacesensitive. Installation will fail if the exact case above is not followed.

    Note: These options may also be installed from the Installation Wizard by selecting a custom installation.
back to the top

For additional information about performing maintenance tasks after a UNIX-to-Windows Migration, click the article number below to view the article in the Microsoft Knowledge Base:
324539 HOW TO: Perform Maintenance and Ancillary Tasks after a UNIX-to-Windows Migration
back to the top


Article ID: 324081 - Last Review: 12/07/2015 11:23:54 - Revision: 2.1

Microsoft Windows 2000 Server, Microsoft Windows 2000 Advanced Server, Microsoft Windows 2000 Professional Edition, Microsoft Windows XP Professional, Microsoft Windows NT 4.0 Service Pack 6a, Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows Services for UNIX 3.0 Standard Edition

  • kbnosurvey kbarchive kbhowto kbhowtomaster KB324081