loukingjr wrote:please attach the vbox.log (compressed)
Sorry about the late reply, see attachment for what you requested.
Additionally, in another thread someone suggested that the problem was that the VM was originally created in VMware, Which is the case. They suggested I remove VMware tools, which I did through the windows uninstall programs feature, as well as sweeping through the registry to remove any remains and deleting services through cmd.
I suppose getting a fresh start on Virtual box would be the answer here but would really rather not have to go through the effort of setting up a new VM and reinstalling all required programs if there's a faster solution.
All help and advice is greatly appreciated.
Update:
This thread is no longer relevant for myself, trouble shooting from the attached logs won't help me anymore. I decided to try updating Virtual box after skimming the logs myself and seeing a version conflict between the extensions and my version. Anyhow, I updated Virtual box and now I can't open any of my Virtual Machines at all, which is a huge problem. I will leave the thread for the possibility of anyone having the same problem, while I attempt to recover my VMs.