[1] The Interix subsystem included in SFU 3.0 and 3.5 and later released as SUA Windows components provided header files and libraries that made it easier to recompile or port Unix applications for use on Windows; they did not make Linux or other Unix binaries (BSD, Solaris, Xenix etc) compatible with Windows binaries.
Like the Microsoft POSIX subsystem that Interix replaced, it is best thought of as a distinct Unix-like platform.
Previously Microsoft had released Interix 2.2 (actually version 2.2.5) as a separate product around the same time frame as SFU 2.0.
This release could only be installed to an NTFS file system (earlier versions supported FAT; this was for improved file-security requirements in Interix 3.5).
The following UNIX versions were supported for NFS components: Solaris 7 and 8, Red Hat Linux 8.0, AIX 5L 5.2, and HP-UX 11i.
It included the following components: Microsoft does not intend to produce any further standalone versions of SFU, opting instead for the integrated SUA.
Files with the same name but different cases are also not allowed by default, but can be enabled on installation with the side-effect of making the underlying partition's filesystem case-sensitive,[6][7] even for the Win32 subsystem.
Microsoft has released several hotfixes for Windows Services for UNIX, and at least one Security Update (KB939778).
A separate port of the up-to-date Debian utilities was started in 2007, but apparently abandoned in 2009.
[9] Windows Server 2003 R2 contains most SFU components, namely Microsoft Services for Network File System (NFS), Subsystem for UNIX-based Applications (SUA, a.k.a.
[22] In Windows 8, the NFS client gained krb5p (Kerberos 5 with full data encryption) support.
In Windows 7, Kerberos 5 was supported for authentication, but only packet integrity checking was available for data.