Please, check https://docs.docker.com/docker-for-win/troubleshoot/.
Issues without logs and details cannot be debugged, and will be closed.

• I have tried with the latest version of my channel (Stable or Edge)
• I have submitted Diagnostics
• I have included the Diagnostics ID in this Issue
• Windows Version: Windows 10; version 1803; OS build: 17133.73; Hyper-V enabled.
• Docker for Windows Version: Docker Edge 18.04.0-ce-win62 (17151) - but it happened before too.

Expected behavior

Kubernetes cluster should start, Settings panel should have green dot saying Kubernetes is running.
kubectl get pods should return empty set.

Actual behavior

Kubernetes is stuck in Kubernetes is starting phase. kubetctl get pods hangs.

Information

Diagnostic ID: 943836AC-0B99-4BEE-BC82-900781400047/2018-04-17_23-06-41

Steps to reproduce the behavior

This issue looks a lot like #1845, which I am not sure why OP closed.

1. Enter Settings
2. Go to Kubernetes menu
3. Select Enable Kubernetes
4. Hit Apply

Tried Reset to factory settings and different combinations of resetting. The port 6445 seems to be correctly tunneled, as I see vpnkit.exe listening on it. K8s images are downloaded, no k8s dockers are visible in docker ps and docker logs include following entries:

[23:04:53.517][ApiProxy       ][Info   ] time="2018-04-17T23:04:53+02:00" msg="Node status error: Get https://localhost:6445/api/v1/nodes: EOF"
[23:04:54.513][ApiProxy       ][Info   ] time="2018-04-17T23:04:54+02:00" msg="Node status error: Get https://localhost:6445/api/v1/nodes: EOF"
...
[23:05:59.014][ApiProxy       ][Info   ] time="2018-04-17T23:05:59+02:00" msg="Node status error: the server was unable to return a response in the time allotted, but may still be processing the request (get nodes)"
...
[23:06:52.721][ApiProxy       ][Info   ] time="2018-04-17T23:06:52+02:00" msg="Node status error: Get https://localhost:6445/api/v1/nodes: http2: server sent GOAWAY and closed the connection; LastStreamID=3, ErrCode=NO_ERROR, debug=\"\""