As it stands, <a href="https://docs.docker.com/docker-for-windows/install/">Docker for Windows</a> still requires Hyper-V to be enabled on the host machine. If you've been around long enough, you may still believe (falsely, it turns out) that Hyper-V doesn't work with hyper-threading. The problem with Hyper-V was apparently never that it <i>disabled</i> hyper-threading but that it led to <i>sub-optimal cache-usage</i> on older chips (single-core). Newer chips have many more cores and much larger caches, so the cache-poisoning issue from 2005 is no longer a problem. There are still some issues because the core-virtualization of hyper-threading can also conflict with the virtualization of Hyper-V, but opinions differ on whether turning off hyper-threading is an improvement. Read <a href="https://serverfault.com/questions/47411/hyper-v-and-hyper-threading-on-or-off">Hyper-V and Hyper-threading: On or off?</a> and <a href="https://www.360ict.nl/blog/use-hyper-threading-with-hyperv/">Use Hyper-Threading with HyperV?</a> for more information and analysis.