Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

Question

VM error in Windows 10

Sep 8, 2017 3:59AM PDT

Hi All,
I have installed VM in windows 10. Till yesterday i can able to start my VM, but today suddenly it stops and gives below error. Please help to resolve this. Thanks in Advance


There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "7cfc32d2-f9a1-48ab-a0bc-474607500b66", "--type", "headless"]

Stderr: VBoxManage.exe: error: The virtual machine 'plive-dev-vm' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\Balagangadharan.R\VirtualBox VMs\plive-dev-vm\Logs\VBoxHardening.log'
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine

Discussion is locked

- Collapse -
Answer
Since this is not Windows 10 but some app
Sep 8, 2017 7:05AM PDT
- Collapse -
VM error in Windows 10
Sep 11, 2017 10:04PM PDT

Tried all the steps. still not working. Please help to resolve this. It was working one, suddenly stopped working.

- Collapse -
Re: VM error
Sep 12, 2017 12:30AM PDT

Then go back to the last backup you made of your virtual machine. It's just one (big) file, I think. Or delete it and start over with a new VM in which you install Windows 10 again.

- Collapse -
VM error in Windows 10
Sep 12, 2017 12:34AM PDT

I am not installing Windows 10 in VM. I am installing Debian 64 bit in VM from my windows 10 os.

- Collapse -
Re: Debian
Sep 12, 2017 1:01AM PDT

Rename the VM, and create a new one. Install Debian in that. If that works, the old VM is to blame. If that doesn't work either it's the Vagrant program or your Windows 10 that is the cause.
Start with reinstalling Vagrant. If that doesn't help, use system restore to go back to when it still worked or refresh or reset Windows 10.

- Collapse -
May have to make a new VM.
Sep 12, 2017 6:19AM PDT

Of course the last good backup is best. My view here is that it's not a W10 issue and supplied the search so you don't go down blind alleys chasing ghosts.

Even with all the lessons and advice I'm still finding folk that never did a backup of their PC, smart phone, tablet or such.

- Collapse -
Answer
Not the windows 10 issue
Sep 13, 2017 5:57AM PDT

Maybe your VM software has a problem not windows 10 os.

- Collapse -
We can test for that.
Sep 13, 2017 7:24AM PDT

They should have a few other VMs. If those work then this VM is likely blown.

- Collapse -
VM error in Windows 10
Sep 14, 2017 1:44AM PDT

I tried re-installing latest version of VM, which doesn't solve my problem.

- Collapse -
Answer
Reinstalling VirtualBox never fixes a bad VM.
Sep 14, 2017 6:52AM PDT

Remember you have a lot of priors to repeat this. Reinstalling VirtualBox does not and has never fixed a blown virtual machine.