Skip to main content

Installation of Windows Subsystem for Linux


I'm sure many saw this and wondered what this is. Let me explain.
This is known as Windows Subsystem for Linux(WSL). Basically, WSL is like a Linux Environment running on Windows without a need to have VM or Dual Boot.
WSL allows you to integrate your Linux Applications, Tools, directly inside Windows.
Refer What is Windows Subsystem for Linux | Microsoft Learn for more details.


  • Basic Understanding of Linux
  • Basic Understanding of Virtual Machine 
  • Basic Understanding of OS Installation / Dual Boot

Books & References:


1. Direct Installation via  wsl --install:

You can open PowerShell running as Administrator.

Note that this method is only available to Windows 10 version 2004 and higher (Build 19041 and higher) or Windows 11.

2. I will follow the Manual way of installation:

i. Enable Windows Subsystem for Linux:

Run the following command in Powershell with Administrator rights.
dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart

ii. Enable Virtual Machine Feature:

Run the following command in Powershell with Administrator rights.

dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart

You will need your machine to have virtualization capabilities. Restart the machine to complete WSL install correctly.

iii. Download the Linux Kernel Update Package and Install:

You can get the package from Linux Kernel Update Package from here and run the installer.

iv. Set WSL2 as the default version:
Run the following command in Powershell with Administrator rights.
wsl --set-default-version 2

v. Install a Linux Distribution from Microsoft App Source:
Go to Microsoft App Source and install Ubuntu Linux Distro.

vi. Open the Linux Distribution App and complete User Setup:

You will see a CLI version of Ubuntu started asking for Username and Password.

vii. Setup a GUI through LXDE Desktop Environment:
I tried setting up LXDE Desktop Environment. However, it did not work as expected.


I hope this blog clarifies what is WSL and how to setup. More follow-up blogs will come up soon.
For any questions feel free to reach out to me at



Popular posts from this blog

Something went wrong. An Error occurred - Error Resolution

Introduction: With the installation of NAV 2018 or BC On-premise, I have observed that when creating New Server Instance and New WebServer Instance, you will get the error 'Something went wrong. An Error occurred '. I referred to the community questions below but didn't find my resolution. Hence, I decided to write this blog. Pre-requisites: Microsoft Dynamics Business Central - On-Premise / NAV 2018 Understanding of Business Central Authentication  Books & References: Demonstration: 1. Creation of NAVServerInstance: In order to create NAVServerInstance, you can either add the Server Instance through Business Central Administration or Powershell command. Add Instance - Business Central Administration Add Insta

Setting up OAuth Authentication for Business Central Web Services / APIs

Introduction: After upgrading Business Central to version 17 (Wave2 2020), I found that there was an error telling me that WebService Key is going to be deprecated soon. Web Service Access Key is deprecated. Hence, I decided to explore and probably make it easier through this blog. Pre- requisites : Admin Access to Office 365 Admin Access to Azure Demonstration: 1. App Registration on Azure Portal: To enable OAuth authentication for any apps in Azure Active Directory, you will need to perform App Registration and set up the permissions and security details. i.) Register the App: Search for 'App Registration' on the Azure Portal. Click on New Registration Type in the App Names, Account Types and Redirect URI. Registering Application ii.) Setup API Permissions: Go to API Permissions > Add Permissions > Business Central App > Select Delegated Permissions > Select Other Permissions and Financials > Add Permissions Button. Setup API Permissions iii.) Setup Client Secr

How to Upgrade Data from Microsoft Dynamics NAV to Microsoft Dynamics Business Central On Premise - Part 2

 Introduction: Now that the first step of the problem preprocessing of the NAV Database to make it ready to be migrated to BC is done(refer Part 1 ), we can now proceed further with connecting the database in Business Central On-Premise. Pre- requisites : Microsoft Dynamics 365 Business Central Microsoft Dynamics for NAV Microsoft SQL Server Management Studio (SSMS) Powershell ISE Understand NAV to BC Upgrade Considerations -  Click here Understand Upgrade Path -  Click here Books & References: Demonstration: 1. Install Business