You must be getting the “Windows installation encountered an unexpected error. Verify the installation sources are accessible, and restart the installation. Error code: 0xE0000100” error. This is actually a really easy error to fix!

The main reason for this on Hyper-V is that you have haven’t given Hyper-V enough memory. Because of this, Hyper-V/Windows Install could not pass some checks. The default is 512MB and I’ve noticed that on Windows Server  2012 (R2) Hyper-V this can be to little. I recommend 1024MB of RAM as the Minimum amount.

To change this go into the Memory section on the Virtual machine and change it from 512MB -> 1024MB

I hope this has helped you learn how to Fix: “Windows installation encountered an unexpected error. Verify the installation sources are accessible, and restart the installation. Error code: 0xE0000100” error!

You must be getting the “Windows cannot find the Microsoft Software License Terms. Make sure the installation sources are valid and restart the installation” error. This is actually a really easy error to fix!

The main reason for this on Hyper-V is that you have haven’t given Hyper-V enough memory. Because of this, Hyper-V/Windows Install could not pass some checks. The default is 512MB and I’ve noticed that on Windows Server  2012 (R2) Hyper-V this can be to little. I recommend 1024MB of RAM as the Minimum amount.

To change this go into the Memory section on the Virtual machine and change it from 512MB -> 1024MB

I hope this has helped you learn how to Fix: “Windows cannot find the Microsoft Software License Terms. Make sure the installation sources are valid and restart the installation” error!

This was one of those things when you make a mistake configuring something and then it doesn’t behave the way you’d expect it to.

When I setup a 3 Hyper-v VM’s one of the machines could not be reached from the network. All 3 machines were installed on a 2 node failover cluster. What was weird was the machine I couldn’t talk to (i.e.. I couldn’t ping or Remote desktop into) could ping machines on the network and receive responses. It also could get an IP address from a DHCP out on the network.

After failing miserably at troubleshooting the issue I installed a 4th VM to the same failover cluster. Everything worked. I went and installed a 5th machine and everything seemed to work.

I did some live migrations and fooled around with things. This morning I tried accessing a VM that could be communicated with last night. It started acting very similar to the machine that was “misbehaving” the day before.

It turns out I missed a small but VERY important step when configuring the VM. I forgot to “Enable spoofing of MAC addresses”.

In order to enable this the machine needs to be off. Once off, you can place a check mark into the selection box. Once done I rebooted the machine and it could now talk back and forth as one would normally expect.

If you right click a running virtual Machine in VMM you will notice that the option to “install virtual guest services” is greyed out.

This “issue” is by design. You can only “install the virtual guest services” while the machine is off or through Hyper-V manager which makes you reboot the computer. The install normally takes around 2 minutes but can vary due to the size of the VM.

Hope this helps.