VMs Don't Work After Update

Otus · Post by **Otus** » 27. Feb 2009, 11:15

I updated VirtualBox to 2.1.4 (from 2.0.6) and all the VMs stopped working. After trying to run one I get VERR_INVALID_PARAMETER and error code E_FAIL 0x80004005.

Creating a new VM and running it also gives me the same error message.

I'm running VirtualBox on Windows Vista and have various Linux guests.

Post by **Sasquatch** » 27. Feb 2009, 13:04

It would help if you can post the exact error. There should be a file and line number where it failes with the parameter.

Otus · Post by **Otus** » 27. Feb 2009, 22:10

Sasquatch wrote:It would help if you can post the exact error. There should be a file and line number where it failes with the parameter.

Let me know what info would help and how to get it. Here's a screenshot of the error message.

Post by **vbox4me2** » 27. Feb 2009, 22:39

What if you create a new VM with the same settings you had before and then attach this VDI ?

Otus · Post by **Otus** » 28. Feb 2009, 10:27

vbox4me2 wrote:What if you create a new VM with the same settings you had before and then attach this VDI ?

As I wrote in the first post, creating a new VM and running it (with or without a hard disk) gives the same error, so I don't think that's a solution.

Post by **vbox4me2** » 28. Feb 2009, 15:12

You might have to remove all traces of 2.06 and do a fresh install of 2.14, maybe something got left behind from 206 that 214 doesn't like.

Otus · Post by **Otus** » 1. Mar 2009, 10:52

vbox4me2 wrote:You might have to remove all traces of 2.06 and do a fresh install of 2.14, maybe something got left behind from 206 that 214 doesn't like.

I just made a full uninstall, including removing both folders from Program Files and my profile. Didn't help - the same message appears after I create and run a new VM.

Post by **vbox4me2** » 1. Mar 2009, 15:30

It seems to be either a .net problem or a virtual NIC problem, I think 2.06 has left some NIC device drivers behind, have a good look at your device manager including hidden devices.

Otus · Post by **Otus** » 1. Mar 2009, 16:45

vbox4me2 wrote:It seems to be either a .net problem or a virtual NIC problem, I think 2.06 has left some NIC device drivers behind, have a good look at your device manager including hidden devices.

After an uninstall I found two VirtualBox related device drivers: VirtualBox Service and VirtualBox USB Monitor Device. I removed them and tried a reinstall, but it fixed nothing.

I downgraded to 2.0.6 for now - it works fine. I hope someone will figure this out eventually.