These are some personal notes about setting up a very nice combined Windows and Linux productivity and development environment. It uses open source software combined with some key proprietary pieces on a single machine. This is now possible when using a Windows 10 workstation1.
I have thought about automating this (especially since I have a tendency to refresh systems fairly often), but I make enough changes between installs, and I’m using retail Windows licenses rather than volume licenses, so automation is not really practical.
It is important to note this environment is geared to those who are used to the Linux ecosystem and are migrating to the new hybrid model.
Use at least Windows 10 Pro Version 2004, with Version 21H1 preferred. Windows 10 Home might work for some of this, but not all features are available.
I won’t go into a lot of detail here as there are many guides on basic Windows installation, instead I will just a list a few key points.
- Make sure your machine is activated and fully up to date with ‘Windows Update’.
- In the
Time & Language
- If your ‘Windows display language’ is for your region you probably don’t need to do anything more.
- Otherwise, look in the list of ‘Preferred Languages’
- Select the language corresponding to your region, or ‘Add a language’ if your language and region are not in the list.
Optionsfor your language and region.
- For any and all
Downloadbuttons in your Language options page, click
- Wait for the downloads and installs to complete.
- Verify your desired keyboard type and layout is first (or only) in the list of keyboard types/layouts
- Go back to the main
- Set your
Windows display languageto your language and region.
- Tweak the base install (before adding any software or apps) and settings to your preferred base configuration2.
- You should go through these settings as many of them are useful to power users and developers – be careful though as there are often security implications to the options. I certainly don’t enable all the options.
- You should review the notes in configuring for developers when in a Libvirt/KVM VM and configuring for developers when on physical hardware as operating in a VM is different from physical hardware for the choices you will can make.
This could almost be part of the ‘Base Windows Install’ except that we are adding components that wouldn’t make sense for an environment that doesn’t need Linux and/or some handy developer features.
- Install Hyper-V if you need virtualization (your machine or virtual machine needs to support it) — Also enable all the Hyper-V options in the control panel applet. If Hyper-V is not supported on your machine you can install VirtualBox using Chocolatey (see below) (again provided your machine for virtual machine supports it).
- Extras — Likewise, you might want the “Telnet Client” and “TFTP Client”, depending on your planned uses.
- “Services for NFS” — There is also a small possibility you will benefit from “Services for NFS”, depending on the hosts on your network.
- Install “OpenSSH Server” if you plan on using SSH into the machine or virtual machine — See Microsoft’s instructions for installing OpenSSH, and the related configuration guides. Similar to the ‘Remote Desktop’ option, if you have enabled networking into the machine or virtual machine so that you can use SSH into it, you probably should change the default firewall rule for SSH to be more restrictive (e.g. Private networks only).
Windows Terminal — It’s a Microsoft Open Source project that you can participate in on GitHub. It is also has quite a nice and usable terminal, that is only likely to get better with time. Currently it’s nice and light.
WinDbg Preview — This allows you to look at Windows ‘Crash dumps’
A Linux distribution from the available choices – I now use Ubuntu LTS but have used Debian. You can use whichever suits your needs.
Microsoft 365 — If you can afford it, there are may be advantages over a free office suite, which I’ll mostly leave it to other sites to discuss, except…
I will say I’m not so sure about this one. I like the native desktop apps, but I am not a fan of the Software as a Service (SaaS) model of MS 365. As it happens I have licenses for Office 2016 Home and Business which gives me the desktop apps I want from the MS 365 offering, and without all the SaaS baggage.
I think the standalone 2019 offering is too expensive, so in future I may abandon the Microsoft office products altogether and just use LibreOffice
LibreOffice software is really more than enough for what I actually need, and MS Office is getting to be too much of a hassle.
Besides that, on my Linux desktops I don’t have MS Office native apps as an option anyway.
Your call for your install.
NOTE: The original software licenses still apply so it is important that
they are compatible with your situation. You can verify that by using
the Chocolatey online package
ChocolateyGUI (a graphical interface for Chocolatey).
Most of the software is open source and ought to be no problem for internal use; if you are planning on ‘distributing’ anything then you need to pay close attention to licensing terms. I’ve made note of any software that you may need to play closer attention to the licensing terms, even for internal use, for which I am aware of the more complicated situation.
When running Windows in a Linux virtual machine, one doesn’t need the same set of packages one would when running Windows on bare metal because much of the software available for Windows is also available for Linux and it makes more sense to run software natively (i.e. on the host) when possible.
The following is a list of software that is useful even when running in a Windows virtual machine, with most software you use running on the Linux host.
This particular list is for regular users (i.e. not related to Linux, development, or system administration, those are listed later). Obviously you will want to modify according to your needs and wants.
choco install 7zip.install adobereader chocolateygui Firefox gpg4win keepassxc libre-hardware-monitor notepadplusplus.install paint.net rufus screentogif
synctrayzor vlc wincompose.install
|Compress/Decompression and archiving/unarchiving
|Adobe Acrobat Reader DC
|The official Adobe PDF reader; proprietary license
|GUI for Chocolatey
|Privacy-oriented Web Browser
|GnuPG for Windows
|Public/Private Key encryption tool
|Password management tool
|System (CPU, memory, disk, temp, and so on monitoring in system tray)
|A better notepad (text editor) for Windows
|Photo editing software
|USB and SD card writer
|Screen, webcam, and sketch board recorder and editor
|System tray and GUI for Syncthing, for syncing files without ’the cloud’ — note that nowadays I use a local Nextcloud server and use
nextcloud-client in my machines and virtual machines
|Video and audio player
|Compose key for windows – intuitive entry of unusual characters
The following list of software is interesting if you are running Windows on bare metal (that are not listed above).
choco install audacity audacity-lame calibre cdburnerxp dia freac gimp InkScape libreoffice-fresh kmymoney quodlibet rufus scribus workrave zoom
|Audio recording and editing software
|LAME for Audacity
|Allow Audacity to create MP3 files
|e-Book Library Management
|Create and burn data CD, DVDs, and Blu-ray
|Create and edit diagrams
|Audio file converter/encoder/decoder and CD ripper
|A very powerful graphics / image manipulation program
|Vector graphics creator and editor
|Personal Financial Management
|Stable version of LibreOffice
|Music Collection / Player Software
|USB and SD card writer
|Desktop publishing software (cross-platform)
|RSI prevention utility (require regular breaks)
|Video conferencing / chat. NB If you have more than one computer your probably need to install manually due to download restrictions; also pay attention to the licensing terms.
choco install putty.install rsync sysinternals vcxsrv wireshark
|SSH GUI (unrelated to OpenSSH above)
|One-way file sync common on other OSes
|Power tools for Windows
|An X-Windows server for Windows; useful for running X11 applications remotely and using a local display
|Watch and analyze activity on your network
choco install OpenSSL.Light xca
|The command line tool for SSL certificates and more
|SSL certificate creation and management
This is highly dependent on what you are developing and what languages you are using. This list is an example.
choco install git git-credential-manager-for-windows golang openscad vagrant vim virtualbox vscode yarn
|Git for Windows
|The major version control and source code management system in the software world
|Git Credential Manager for Windows
|Manage Git credentials using the Windows system secrets store
|The Go language and standard library
|command line tools for creating and using virtual machines (vagrant ‘boxes’) similar to the way one would use docker containers
|Run Virtual Machines under Windows (with or without Hyper-V).
|Visual Studio Code
|Code and text editor and development environment, and more
|An improved package manager for Node.js
This is highly dependent on what you are developing and what languages you are using. The following is a list that reflects my current situation.
choco install arduino docker-compose docker-desktop html-tidy hugo nodejs.install pandoc shellcheck thonny
|IDE for developing Arduino sketches
|Tool for launching and managing Docker machines
|Docker for modern machines, integrates with WSL2; for older machines use Docker Toolbox instead
|Validate and clean HTML5
|Static website generator
|Convert between document formats (e.g. markdown, pdf, docx, xml, html, and tex) on the command line
|Check bash / sh / dash / ksh scripts for syntax and common errors and style issues
|Python IDE for beginners
While I don’t need it, you want Visual Studio if you need to develop software for Windows only, the Microsoft way. Chocolatey can probably install what is needed by most developers. Verify what you are installing though — licensing can be tricky here.
In addition to the Visual Studio Installer and Visual Studio 20XX Community or Visual Studio 20XX Build Tools core applications you will want to install ‘workloads’ that support the type of applications you are wanting to develop or to which you wish to contribute. A fairly ‘kitchen sink’ example install command is given below.
choco install -y visualstudio2019buildtools visualstudio2017feedbackclient visualstudio2017buildtools VisualStudio2017Community visualstudio2019community visualstudio2017-workload-visualstudioextension visualstudio2019-workload-visualstudioextension visualstudio2017-workload-python visualstudio2017-workload-azure visualstudio2017-workload-visualstudioextensionbuildtools visualstudio2015-nugetpackagemanager microsoft-build-tools visualstudio2017-remotetools visualstudio2019-remotetools visualstudio2017-workload-node visualstudio2019-workload-node visualstudio2019-workload-azure visualstudio2019-workload-python visualstudio2019-workload-visualstudioextensionbuildtools visualstudio2017sql visualstudio2017-performancetools visualstudio2019-performancetools visualstudio2017-workload-nativecrossplat visualstudio2019-workload-nativecrossplat visualstudio2017-workload-azurebuildtools visualstudio2017-workload-nodebuildtools visualstudio2019-workload-azurebuildtools visualstudio2017-workload-netcorebuildtools visualstudio2017-workload-manageddesktop visualstudio2019-workload-manageddesktop visualstudio2017-workload-vctools visualstudio2019-workload-vctools visualstudio2017-workload-netcoretools visualstudio2017-workload-netcrossplat visualstudio2017-workload-netweb visualstudio2017-workload-universal visualstudio2017-workload-webcrossplat visualstudio2019-workload-netcrossplat visualstudio2017-workload-nativedesktop visualstudio2017-workload-data visualstudio2019-workload-universal visualstudio2019-workload-netweb visualstudio2019-workload-nativedesktop visualstudio2019-workload-netcoretools visualstudio2017-workload-universalbuildtools visualstudio2019-workload-nodebuildtools visualstudio2019-workload-universalbuildtools visualstudio2019-workload-manageddesktopbuildtools visualstudio2019-workload-netcorebuildtools visualstudio2017-workload-webbuildtools visualstudio2019-workload-webbuildtools visualstudio2017-workload-manageddesktopbuildtools windowsdriverkit10 vcredist2017
choco install AndroidStudio
There may be additional software you want to install that is not available from the Windows Store or Chocolatey. That’s not covered here, although a personal recommendation is Zim Desktop Wiki. Unfortunately the version in Chocolatey is rather old and due to the technology used in the installer, it gets a number of false positives on the virus scan.
I don’t cover installation of packages and configuration of the general Linux environment except as is particular to this hybrid setup, as there are a great many guides for general Linux setup and configuration already written, and the WSL2 environment doesn’t have much that isn’t generic Linux.
Now that the software is installed there is a bit of configuration to do.
In the WSL environment you should add
/etc/wsl.conf containing something like:
enabled = true
options = metadata,uid=1000,gid=1000,umask=0022,fmask=0011
generateHosts = true
generateResolvConf = true
Once you restart WSL (which involves more than just closing your current WSL terminal; the easiest way to guarantee a WSL restart is to reboot Windows), while in WSL files and directories from Windows (e.g. under /mnt) will have more normal Unix permission. You will be able to override with chmod for the effective permissions in WSL. Also note that in some cases there are Windows ACLs that also affect your effective permissions.
And finally, it’s generally not possible to delete files which are opened by another process in Windows, and therefore in WSL (which differs from plain Linux).
This assumes use of SSH public/private keys for Git. If you prefer to use the Git Credential Manager for Windows with Git over HTTPS and using API keys, see Git Credential Manager for Windows
On the latest Windows 10 Pro OpenSSH agent should be installed by default. If not it can be installed by installing the “OpenSSH Client” Windows ‘feature’.
Execute the commands:
Set-Service -Name 'ssh-agent' -StartupType 'Automatic' Start-Service 'ssh-agent'
To set this for a single user set the environment variable
point to the OpenSSH binary in the user’s environment variables.
[Environment]::SetEnvironmentVariable("GIT_SSH_COMMAND", "cat - | $((Get-Command ssh).Source.Replace('\','/'))", [System.EnvironmentVariableTarget]::User)
Also, makes sure
GIT_SSH is unset for the user:
[Environment]::SetEnvironmentVariable("GIT_SSH", "", [System.EnvironmentVariableTarget]::User)
To set it for all users, set
GIT_SSH_COMMAND in the system environment
In an admin PowerShell:
[Environment]::SetEnvironmentVariable("GIT_SSH_COMMAND", "cat - | $((Get-Command ssh).Source.Replace('\','/'))", [System.EnvironmentVariableTarget]::Machine)
Also, makes sure
GIT_SSH is unset in the system environment:
In an admin PowerShell:
[Environment]::SetEnvironmentVariable("GIT_SSH", "", [System.EnvironmentVariableTarget]::Machine)
|Ignore changes do file ‘mode’ bits (e.g. execute permissions)
|Make the default line ending for files Unix mode line endings. Windows 10 2004 supports text/source files of this type easily.
|Disable changing the line endings depending on whether checking out on Windows or under WSL.
|Set the default user name for commits and emails
|Set the default user email for commits and emails
|Make the default credential manager Git Credential Manager for Windows
This option prevents pulls from creating a merge or a forced update (i.e.
rewriting history) or rebase. You can still
git fetch and manually merge or
rebase as necessary.
git config --global pull.ff only
Install your backup program (e.g.
apt-get install borgbackup).
Create a script to do the backup.
- You want your ‘regular’ user for a home dir only backup.
- If you want to backup parts like /etc, you want the script to be executable by root, but readable only by root (or at least any passwords, etc.)
In Windows, as the user account in which you installed the Linux distribution use
Task Schedulerto create a period task that runs the script.
Create a task (you probably want it to run even if you are not logged in).
Choose your triggers.
For the action:
wsl.exeas the program to execute: NB Using the bare filename and making the
C:\WINDOWS\System32the working folder is (was?) required due to a bug in
- Set the folder to use as
- Set the arguments to
-u user_to_runas -- /path/to/your/script.
Complete creating the task.
Save and do a test run. The ‘action’ should complete with exit code 0.
The rest is about learning what makes for a comfortable environment for you. I personally tend to get annoyed with ‘opinionated’ or ‘perfect’ setup guides, and am trying to create more flexible set of suggestions that can easily be adapted to suit you.
The Windows 10 20H2 Update WSL2 (Windows Subsystem for Linux 2) combined with a number of other Windows enhancements has made the promises of WSL (that one can develop Linux software and firmware on Windows and easily run Linux binaries on Windows machines) much more of a reality. It is now practical to develop and run many types of Linux non-X114 software on Windows. Even the original WSL is more usable than when first released for general availability. The parallel development of Visual Studio Code (a very nice cross-platform editor and development environment) is an important factor as well. ↩︎
Specifics depend on you or your organization. A collection of things I like to ensure on a single user desktop is:
- Use BitLocker hard drive encryption (enable the non-TPM option if necessary).
- Require using of Ctrl-Alt-Del (if on real hardware) so you use the ‘Secure Desktop’ to enter credentials
- Increase the UAC settings so you always are prompted for credentials on the secure desktop, and never just click through for elevation to Administrator access.
- Set a soft lockout for too many password attempts.
- Don’t use a maximum password age (it causes more problems than it helps).
- Enforce at least eight characters passwords with complexity requirements met.
- For SMB encrypt all communications and require NTLMv2 (if you have a external device that is too old to support that, it’s time to upgrade it, unless, perhaps, you are experimenting with a new OS that isn’t mature enough to have implemented this yet).
- Set a machine inactivity timeout (which doesn’t rely on setting the screensaver per-user to ensure that the desktop will lock when not in use).
- Use File History for backing up the folders for backing up your data. It’s not a bare metal restore option, but it makes sure you have your data backed up, as well as giving you the ability to go back to previous versions of files. Needless to say you should make sure your back up location is encrypted on disk. It is also important to use ‘Advanced Options’ and check the Event Log for errors on a regular basis.
- Enable system checkpoints.
- Once you’ve got a good base image, don’t forget to make a system image.
In my opinion, there are two main conditions under which one would not use WSL2:
- One’s machine (or virtual machine) doesn’t support WSL2 (e.g. due to missing CPU features).
- One needs the bare metal virtualization mode of a hypervisor other than Hyper-V (e.g. if you need VMWare or VirtualBox with their native virtualization rather than the Hyper-V compatible virtualization).
Actually, while not recommended, it is possible to use VcXsrv or Xming (X servers for Windows) in order to be also be able to run X11 apps from WSL/WSL2 on your Windows desktop. The free version of Xming and VcXsrv (which is free) are somewhat dated. ↩︎