Windows 10 Pro - BSOD when launching Local



I’m on Windows 10 Pro x64 (with Hyper-V enabled).
Ordinary Docker for Windows works fine.

When I’m trying to launch Local 2.0.5 or 2.1.0 - I get BSOD with SYSTEM_SERVICE_EXCEPTION.

Here is a screenshot:

I can provide a dump file that is generated on BSODs if required.

Dell XPS 13", i7 Kaby Lake, 16GB RAM

Installation problem: VirtualBox ✓, Host Machine ⟲, Local Image [Hyper-V Conflict]

Unfortunately, VirtualBox and Hyper-V conflict with each other.

In order to use Local you’ll need to disable Hyper-V. With that said, we do plan on supporting Hyper-V on Windows 10 Pro down the road.


Are there any ETA of that support? Currently, disabling Hyper-V is not an option for me.


Is there any information about the support schedule?


Sorry for missing your reply!

The best estimate I can give is sometime next year. It’s something we’re definitely interested considering we want to move away from VirtualBox wherever possible.


Hi @clay, I still have a hope that this problem is somewhere on a roadmap…



Yup! This is planned for 2018.


Awesome, you can count me in as a beta-tester of that integration when (if) needed.


Hi! Are there any updates regarding this issue?
2018 is slowly coming closer to its end…


waiting for the update can’t use docket and local fly on one system, I like local but it’s stops us from using docker.


@clay Any updates?


Local is awesome, but lack of support for Hyper-V on Windows 10 Pro is a bit of a non-starter for me. I’ve tried the whole disable/enable thing but it’s a bit of a productivity buzz kill.

Eagerly looking forward to an update on this.


And 2018 finished, and we’re mid February in 2019… Any news?


How can it be installed then?