How To Install Windows Subsystem For Linux 2 WSL2 On Windows 10 2004 Step By Step Walk Through Hindi. Let me walk you through a detailed tutorial about installation windows subsystem for linux 2 wsl2 on windows 10 2004.

I will share will you secrets that no one else will tell you. There is a fair amount of architecture deep dive which will tickle the senses of the nerds.

Linux Kernel Update Package https://docs.microsoft.com/en-us/windows/wsl/wsl2-kernel

My Channel https://www.youtube.com/channel/UCi_6--KS6qRmOn5bNQsxLNw?sub_confirmation=1

==================================================================== Track: In the Void Music provided by YouTube Audio Library

Timestamps 00:00 Windows Sub System For Linux 2 ( WSL 2 ) Demonstration 00:20 Enable Virtualization Technology In PC Basic Input Output System ( BIOS ) 01:03 Use 'winver' Command To Check Windows Installation Version Need Windows 10 May 2020 Update Or Join Windows Insider To Update To Latest Bits 01:32 Turn On Virtual Machine Platform And Windows Sussystem For Linux 02:23 Restart Windows 03:11 Check Out Different Flavours Of Linux On The Microsoft Store 04:22 Search And Download Ubuntu 20.04 LTS (Long Term Support) From The Microsoft Store 06:25 Download The Linux Kernel Update Package For WSL 2 06:55 Install The Linux Kernel Update Package For WSL 2 07:17 Install Ubuntu 20.04 LTS (Long Term Support) 08:30 Convert Ubuntu 20.04 LTS Installation From WSL 1 To WSL 2 09:34 Set WSL 2 To Default Installation Version For Any Linux Distribution 09:47 Run WSL 2 From Windows PowerShell 10:04 Run Ubuntu 20.04 LTS On WSL 2

Microsoft did a lot of work behind the scenes to make wsl 2 possible to fully explain all of the architecture changes that we did.

First you need to understand the architecture of the wsl 1, which is the current version that's widely available

In wsl 1, we have a translation based approach. So we have actual Linux user space binaries that are provided by the maintainers like canonical Debian open Sousa. These are the actual binaries that run, and whenever they have a system call like accessing memory, or files or network, we call down to yourself translation layer, we translate these system calls from a Linux system call to a Windows system call. And that goes down to the Windows NT kernel NT kernel sends a response back up to our translation layer we translate that back to something that Linux would understand anything the day we've implemented the application binary interface for Linux. This works great, because everything ran under the same kernel. However, there were some challenges, Windows and Linux have very different semantics. And so this could be complicated, especially when the semantics ... https://www.youtube.com/watch?v=Jr6UbV6soyw