How to fix common Hyper-V errors on Windows 10
This short post is more of a note to myself for when I run into the same problem. I just wasted an hour on it so I guess that justifies it.
So, what happened? I wanted to check out the new Docker Machine with Hyper-V support, but the Hyper-V Manager told me it could not connect to my local computer.
When I opened Hyper-V Manager all I saw was an introduction. I then clicked Connect to server and selected my local computer. A confusing error message appeared telling me that an object was not found. It was the Hyper-V Virtual Machine Management service which seemed to be missing.
My hypervisor was running, the mentioned service was running, there were no errors in the Event Viewer… everything seemed to be working fine.
A lot of Googling led me to a post mentioning a command that fixed this problem:
This command reinitializes Hyper-V management on your computer and fixes this error. It seems to be a frequent cause of headaches on Windows 10 hosts.
You might also like
Docker image for Hugo builds (with Wercker)
This blog is built with Hugo , which allows me to use some great CI tools like Wercker . The first part of writing a wercker.yml is picking a build container. A build container on Wercker is the environment in which your build or deploy steps run. Wercker used to build its own containers for that, but they’ve moved away from that approach to Docker containers.
Experiences with Windows 10 on a new Dell XPS 13 (2015)
Ordering a new workhorse Windows 10 RTM has been out for about a month now after little less than a year of public Insider preview builds. The motherboard of my old, trusty, Asus laptop was slowly dying and the Dell XPS 13’s thinness and battery life looked very attractive. I decided to go for it and order a Dell XPS 13 (2015), without the touch screen.