I then learned how to install rEFInd from Windows and solved the second piece of this puzzle. It turns out there’s a flag in rEFInd in the config file called ‘enable_and_lock_vmx’ that when uncommented and set to ‘true’ will resolve the issue. I’ve never liked BootCamp and in the past I’ve always relied on the rEFInd boot manager available here : and casually dealt with the odd occasion that virtualization wouldn’t work in Windows because a reboot would usually sort it out.Īs I wasn’t expecting to be dual-booting for the time being, I did not have rEFInd installed and spent a ton of time Googling the answer (which was always resetting the NVRAM or BootCamp or both). The traditional route would be to dual-boot macOS and Windows 11 using BootCamp and BootCamp will set the proper flags in the NVRAM. The problem here is that the NVRAM doesn’t enable hardware virtualization by default and no amount of resetting it will make it so. Crisis averted for now … until I wanted to start installing the additional Windows features required for WSL and found them greyed out. The tool was dead simple to use and Windows 11 not only installed but updated as well with no issues. This required a visit to for a workaround to create installation media as the Microsoft-provided fix will only allow you to install if you have TPM v1.2 and this generation of Macbook has no TPM at all. 2.0) to pass the hardware checks to install Windows 11. Unfortunately, the laptop is too old to have a compatible Trusted Platform Module (TPM v. I decided I wanted to test out Windows 11 from a clean install as well as the improvements to the Windows Subsystem for Linux. I happen to own a 13″ Macbook Pro from 2015 (i7, 8GB, 256GB SSD) as my daily driver.
0 kommentar(er)
