vboxme / Portable-VirtualBox

Portable-VirtualBox is a free and open source software tool that lets you run any operating system from a usb stick without separate installation.
Other
806 stars 234 forks source link

fails to start vm, cannot access the kernel driver #13

Open Nighoo opened 10 years ago

Nighoo commented 10 years ago

Hi,

Portable-VirtualBox fails to start a vm on windows 7 with the error: Cannot access the kernel driver! The same problem was mentioned in https://www.virtualbox.org/ticket/4140, but reinstallation is not the intended solution when using a portable version of virtualbox.

Any clue?

Megachip commented 10 years ago

restart you System should solve this

Nighoo commented 10 years ago

On 19.05.14 06:56, Megachip wrote:

restart you System should solve this

It does not and should not be a solutions for a portable version of any software.

Megachip commented 10 years ago

Am 19.05.2014 16:09, schrieb Nico:

On 19.05.14 06:56, Megachip wrote:

restart you System should solve this

It does not and should not be a solutions for a portable version of any software.

— Reply to this email directly or view it on GitHub https://github.com/vboxme/Portable-VirtualBox/issues/13#issuecomment-43508520.

In that case it would be hard to solve, cause it is a problem with you system not with (portable) virtualbox.

Did you have installed VB before? Possible a registry cleanup could help.

Nighoo commented 10 years ago

On 19.05.14 07:35, Megachip wrote:

Did you have installed VB before? Possible a registry cleanup could help.

No, I've used a fresh installation of Windows and tested Portable VirtualBox on another maschine (also using Windows 7): same error.

Could this be related to the OS version? Did anyone also ended up in this error?

LordJABA commented 10 years ago

Affects me too...

SergioRius commented 9 years ago

Same there

pimgeek commented 9 years ago

It also affects me...

Zoli1972 commented 9 years ago

Hi,

I was experiencing exactly this issue recently. As I found out, on a clean Windows install, no matter what version, you should install VCRedist 2010 first, of course according to your system architecture (x86 or x64).

When trying to start Virtualbox without VCRedist 2010 installed, it fails to run virtual machines, especially on fresh installed systems (like mine) and pops up this error: "cannot access the kernel driver"

So, in my case, it had nothing to do with the often mentioned broken Windows update KB300494 issue (see https://forums.virtualbox.org/viewtopic.php?f=6&t=64107) or missing installed drivers (see https://forums.virtualbox.org/viewtopic.php?f=6&t=46845), which were seemingly affecting other user's Virtualboxes. The update KB300494 was even missing on my system in the first place.

Zoli

Ruffio commented 9 years ago

@Megachip should this issue still be open?

tech3869 commented 3 years ago

Fix VirtualBox Errors - List Of Helpful Guides https://windowsreport.com/tag/virtual-box-errors/