virtualbox.org

Me too! I think I'll just stick with my desktop!

Am I right in thinking it probably isn't a VBox problem if Server 2012 runs on my desktop fine?

Well the COM error is definitly a Virtualbox issue, but it basically means that the VBoxSVC process (the one that actually perform all the tasks) could not be reached.
That can be for many reasons :
- Permissions issue
- Bad installation
- Using a technical user
- UAC...

Full desintall, reboot & reinstall should fix this normally, but you said you already tried...

I have tried to reinstall, yes, but not with UAC disabled. Then again, why did it work on Windows Server 2008 with UAC enabled?

Turning UAC didn't make a difference!

Since it is also meant to virtualize, Server 2012 may have features that interfere with another virtualizer, especially if it is the host.
I wonder if that has something to do with your issue.

Possible indeed
@tommy2k10: can you check if Hyper-V is installed?

How do I see if Hyper-V is enabled or disabled?

I managed to disable it and attached is the log file

Did you try to run the VM with Hyper-V disabled?

Yes, makes no difference!

I've read the full topic again and something is still not clear :

You managed to start the VM, since you provided us a log for it. At that point you got the STOP message.
But sine then, you get the COM error and you can't start the VM anymore.

What changed in between?

Ok, now one of two things happen:

1) I start the VM and the 0x0000001e message occurs
2) It boots into the loading (the new MS logo) screen and just hangs!

The only difference between the log for the VM on my laptop and the VM on my desktop is there is a line for video mode!

How come the VM now starts? what did you change? What happened to the COM error?

I just opened an elevated Command Prompt, disabled HyperV, went into the Command Prompt without elevation, managed to get the COM file!
I allocated a VM with 2GB RAM, 64GB HDD, and then it crashed in the part I mentioned