After I sent the answer I realised you deleted the config file so you knew exactly what I was writing about 
You need the API server running, yes. But other components like coredns could be in pending status for example.
This is why I included the section starting with the following:
If you tried that already and could not find any Kubernetes related container then it could be a networking issue or…
this means Windows cannot resolve the internal domain which should be set in the hidden C:\Windows\System32\drivers\etc\hosts
You can try to edit it as an Adminisrator and insert this line:
127.0.0.1 kubernetes.docker.internal
I don’t know why would that be missing but it looks like this is the case. It could mean the installation could not even reach the step where those domains are set or the cluster at least partially installed but you cannot use kubectl to see. Again, I recommend enabling system containers.