The insider channel renaming is described here.

The windows insider page currently lists 19042.423 as the highest build available in Beta and 19041.423 as Release Preview, so for the moment this will not work correctly without using the Dev channel. One of the features required didn't come into Windows 10 until build 19619 and the nested virtualisation support for AMD didn't come in until build 19636 either, so that's a must if you are on AMD too.

The insiders Fast ring which is mentioned in the pre-requisites is now the Dev channel. You'll also need to be running a windows insider build of Windows 10. If you're already running a hypervisor, it's likely this is good to go. If your CPU does support virtualization it might not be enabled in your BIOS, it's worth a check before you start.

Unless you're running an Intel CPU from the early 2000s or even earlier you should be OK. One thing that's not obvious is your CPU needs to support virtualisation.

I am still stunned how good the performance is having run through this! I've tried a couple of other Linux distro's too, seriously slick.īefore starting check out the requirements from the top of the 'Accelerated KVM guests on WSL2' post. Then I realised, I finally had an excuse to give this a go! I've been itching to since I read - Accelerated KVM guests on WSL 2, an awesome write-up on how to run accelerated KVM guests on WSL2 from is a walkthrough of how I used the excellent work of and and got my 3 year old XPS Intel i7 to run MacOS on Windows 10! Without their writeups and scripting this post probably wouldn't exist. I needed to record a demo on a Mac, I don't own a Mac and was contemplating borrowing one from a friend.

Macos vm on windows