Command Line and Windows Subsystem for Linux

The Windows Subsystem for Linux (WSL) has dramatically changed the development opportunities on Windows, and has become very popular. Microsoft has updated it continuously as well, bringing requested features and updates to really improve the experience. With the April Update, there’s once again some nice additions to Linux support on Windows.

What was once a somewhat arduous task, installing Linux distros on Windows now is something that’s moved to the Store, and for the April Update, there’s a couple of new distros available. Kali Linux is now an option, as well as the very popular Debian GNU/Linux. For those that want to run multiple distros, Windows 10 supports having multiple versions installed and running simultaneously.

Likely a very vocal request, background tasks were previously available but would end if the console window was closed. With the April Update, that’s no longer the case.

The WSL team has now brought Unix sockets to Windows as well, so you can communicate over these sockets between Windows and WSL.

People that do Linux admin will be aware of OpenSSH, and Microsoft has brought both a the OpenSSH client and server to Windows. The client is enabled by default, and the server is an on-demand feature as it likely should be.

Both Tar and Curl commands have also arrived in Windows 10’s command line interface, and Microsoft has created a new tool called wslpath to let you easily convert paths between Windows and Linux.

You can now do Linux permissions on files, with the new permission added as metadata to the file, and case sensitivity is now an opt-in feature, although to start an argument, case sensitivity is one of the most annoying features of Linux.

Console Applications Now Supported as UWP

There’s often no easier solution to a problem than a quick console application, but before the April Update, there was no way to distribute these apps through the Store. With the April Update, Console UWP is now supported, so developers can ship and update through the store just like any other UWP app.

Microsoft Edge Updates: PWA Support And More Design Tweaks and Settings
Comments Locked

161 Comments

View All Comments

  • ಬುಲ್ವಿಂಕಲ್ ಜೆ ಮೂಸ್ - Saturday, May 26, 2018 - link

    I wish the staff would openly discuss the problem with Microsofts DRM instead of deleting my posts without comment

    YES, it may be against the "LAW" to discuss getting around DRM but those Laws only help Criminals who wrote the Law

    A permanent backdoor into everyones computer IS a matter of National and Personal Security

    Bill Gates once asked for an open discussion on security

    When are you willing to actually have it ?

    I believe James Comey even asked for an open discussion on the problems affecting National Security such as Encryption Backdoors

    I am ready for an honest open discussion

    AnandTech is definitely NOT Ready!

    Be a part of the solution, instead of the problem
  • ChristopherFortineux - Friday, June 8, 2018 - link

    Being from India yourself. You know better than breaking the law discussing breaching the DRM. Why you keep mentioning it on random comments is redundant. Also, "Bullwinkle J. Moose" LOL
  • Azurael - Saturday, May 26, 2018 - link

    I think this one went better than FCU. No complete reinstalls required yet, but one of the machines I manage still won't install it. Still, I'm not going to hold it against Microsoft because I insist on running all of my EFI-capable machines _in_ EFI boot mode and some of the early UEFI implementations (2007-2010ish) are flakey as hell. On this particular (personal) machine, I don't think the fact that the ESP is shared with a Linux install is helping, Microsoft seem to like a lot of free space on it to successfully install, even though their default partition map creates an ESP about half the size of the 'standard' 256MB...

    Sill, about 20 machines and no other issues, as I said, much better than FCU! I had to reinstall 3 at work last time today round... One thing I've learned is that it really isn't worth trying to diagnose issues with the updater. If you have to try and run it more than twice, a clean install is invariably quicker...
  • landerf - Saturday, May 26, 2018 - link

    The amount of hoops I've had to jump through to replace homegroup functionality is mind boggling and I'm still not sure it will keep working the next time I reboot and all the solutions are far less secure than homegroup.
  • coburn_c - Sunday, May 27, 2018 - link

    They turned last access time stamp back on. I can't understand why, considering the i/o performance hit of the latest security patches and the fact that it has been off for the last decade.
  • exactopposite - Sunday, May 27, 2018 - link

    i have tried the update on 4 machines
    Ryzen x370 syste updated with no problem
    Kaby lake desktop updated ok but network settings changed which prevented network shares form working. It was a simple fix but annoying
    Kaby lake HTPC and Broadwell laptop both refuse to install it. The install almost completes but then uninstalls and rolls back
  • lfred - Monday, May 28, 2018 - link

    What fix did you use? shares keeps disconnecting from time to time here?
  • ChristopherFortineux - Friday, June 8, 2018 - link

    No luck with clean install?
  • Schmide - Sunday, May 27, 2018 - link

    11 pages and a full article and no mention of the fact that they took away Workgroup?

    For shame
  • ChristopherFortineux - Friday, June 8, 2018 - link

    What did you still need Workgroup for? The issue is it has become unnecessary for most things. Share for networks is already built into Windows 10. File storage is built into the OS with OneDrive. There are superior alternatives to sharing over network.

Log in

Don't have an account? Sign up now