Filters:

  • Technologies

  • Instructors

  • Error code 0xE0000100 while installing Windows Server 2012 R2

    Recently while attempting to install Windows Server 2012 R2 on a virtual machine I received the following error after clicking the Install button:

    Error code 0xE0000100

    So based on the error my first assumption was my installation ISO must be corrupted, so I downloaded a new file from MSDN.  After the downloading the new ISO I received the same error.  So being a little stubborn I tried a Server 2012 ISO I had and again the same error.  I tried a Windows 8 ISO I had available, didn’t get the same error but an issue reading the license file.

    So next assumption maybe somehow Hyper-V has gotten corrupted.  So I completely uninstall the Hyper-V role and ensure I clean the registry of any instances of Hyper-V.  Reinstall Hyper-V wouldn’t you know it the same error.  Now I am getting a little frustrated.  So I started researching the 0xE0000100 error code.  Found lots of irrelevant stuff out there.  But, then stumbled across the true cause of the error.

    The default memory value when creating a virtual machine in Hyper-V is 512MB which is the minimum memory required to install Windows Server 2012 R2.  I had selected use Dynamic Memory so I assumed it allocate what was needed.  What I found was it doesn’t.  Because the drive is not formatted yet and no memory swap file exists the ISO was unable to extract into memory.  As a result the installation files were not available to continue.  There are 2 solutions to the problem.  The easiest is to up your memory larger the 800 MB or prior to pressing the Install button exit to a command prompt, format the drive and create a memory swap file.

    You may also like:  Using PowerShell to remove the MiniShell or Full Graphical Shell to convert Windows Server 2012 R2 Datacenter to a Core Edition

    I chose the easier of the 2 by upping my memory to 1024 MB.  Installation completed without any other issues.

    Hope this solves your installation problem and you research the error prior to jumping through hoops like I did.

    Until next time, RIDE SAFE!!

    See what people are saying...

    1. luke

      Had the same problem, also started with 512MB, adding RAM helped, thanks 🙂

    Share your thoughts...

    Please fill out the comment form below to post a reply.