Mastodawn

mcc Aug 5, 2023

Last year I had Docker briefly running on my Win10 machine, just long enough to verify it was working, then today I ran it and it said it can't run because of my BIOS settings. Is this surprising? Does this imply I changed my BIOS, possibly by accident, sometime in the last nine months? If I changed out my boot disk, might that have reset some BIOS settings?

Show thread

Sgeo Aug 5, 2023

@mcc Is Core Isolation Memory Protection on? Can Hyper-V or WSL2 run?

I sometimes disable those to get VirtualBox and VMware to run more smoothly. Although recently discovered on Windows 11, memory integrity causes the OS to be virtualized, even if I tried to turn that off. Although that sounds like the opposite of your problem, where the VM stuff is disabled when you want it enabled.

Show thread

mcc Aug 5, 2023

@sgeo I don't know, unless I can check that without going into BIOS. I use WSL1 because it has faster disk access so I don't know if WSL2 can run.

Show thread

Christopher Snowhill Aug 5, 2023

@mcc @sgeo A fun thing is that until about July of this year, my motherboard's BIOS defaulted to disabling hardware virtualization, and cleared its settings on every BIOS upgrade. And then I learned recently that Windows Update is now capable of performing BIOS updates on some motherboards, even desktop machines, and may not ask permission to do this. In the case I'm aware of, it even downgraded the user to a version that didn't fully support the CPU they were using.

Show thread

ckfinite

@chris @mcc @sgeo This is exactly what happened to me. One day, WSL2/Docker worked, WUpdate ran, the next WSL2/Docker didn't work. I had to go back and reenable the various virtualization flags in the BIOS to make them work again.