I could have seen this one going either way, but Microsoft confirmed this week that Windows 10 S will not include or support the Windows Subsystem for Linux.
“Windows 10 S does not run command-line applications, nor the Windows Console, Cmd / PowerShell, or Linux/Bash/WSL instances since command-line apps run outside the safe environment that protects Windows 10 S from malicious/misbehaving software,” Microsoft’s Rich Turner explains. “Even though Linux distro store packages are delivered via the Windows Store, and installed as standard UWP AppX [containers], they run as non-UWP command-line tools and this can access more of a system than a UWP can.”
The speculation around this topic was, for once, reasonable. Windows 10 S, after all, is “based on” Windows 10 Pro, and it will deliver most of the functionality that has so far been unique to that product version.
But the Windows Subsystem for Linux is very specifically targeted at developers, who should be using Windows 10 Pro. And because of the way it’s implemented, it’s almost certainly not in keeping with the reliability, performance, and battery life advantages of Windows 10 S.
Microsoft revealed at Build last week that additional Linux implementations—like Red Hat Fedora and SUSE—would be delivered through the Windows Store, further fanning theories that maybe, just maybe, the Windows Subsystem for Linux would be included with Windows 10 S.
“Just because an ‘app’ comes from the Windows Store does NOT automatically mean that it’s safe and suitable for running in Windows 10 S,” Turner wrote. “There are some apps that are not allowed to run on Windows 10 S, including all command-line apps, shells and Consoles.”
<blockquote><a href="#118168"><em>In reply to hrlngrv:</em></a></blockquote><p>If "desktop" Office provided through the Windows Store doesn't support all existing capabilities including VBA macros it's simply NOT desktop Office. </p>
<blockquote><a href="#118335"><em>In reply to hrlngrv:</em></a></blockquote><p>Well, given that there is a diverse set of special needs requirements among customers, it's more logical and efficient to provide a single Office set to everyone. The possible exception is to add a bare-bones version like Microsoft Works. Even so, it's not unusual for beginners to use Office as a minimal tool only to use more advanced features as their understanding and requirements grow.</p>
<blockquote><a href="#118255"><em>In reply to Sai Rahul:</em></a></blockquote><p>I suspect that Linux on any version of Windows is of minimal effect on Windows developers.</p>
<p> " ..after all, is “based on” Windows 10 Pro, and it will deliver most of the functionality that has so far been unique to that product version."</p><p><br></p><p>Other than being able to upgrade to Windows 10 Pro, what exclusive W10 Pro capabilities does Windows 10S have that Windows 10 Home Premium doesn't?</p>
<blockquote><a href="#118302"><em>In reply to Waethorn:</em></a></blockquote><p>Do you have a link? Perhaps I didn't look carefully enough. I could find a comparison chart between Pro and Home but not between S and Home.</p>
<blockquote><a href="#118359"><em>In reply to skane2600:</em></a></blockquote><p>OK. I found it after all.: https://support.microsoft.com/en-us/help/4020089/windows-10-s-faq</p><p>S appears to add mostly centralized management capabilities. </p>
<blockquote><a href="#118606"><em>In reply to Boris Zakharin:</em></a></blockquote><p>Handy tech tools but the target market for Windows S has never heard of them. </p>