Page 1 of 1

Cannot access kernel driver - VBoxUSBMon.inf cannot be insal

Posted: 11. Jun 2012, 16:42
by International
I have problem when trying to run VB in safe mode ( I need to install Guest Additions in safe mode) - "cannot Access kernel driver" . Tried all possible solutions include the one below.

When trying to install drivers manually ( C:\Program Files\Oracle\VirtualBox\drivers\USB\filter - VBoxUSBMon.inf) get an error " The INF file u selected doesn't support this method of installation" . With the VBoxDrv.inf everything looks ok.

When trying to go for the installation of that particular driver through Device Manager, as suggested in some tech forums, I get message as in the pic below.

I run WindowsXP (Service pack 3) guest on a Vista Home Premium 32bit host

Any suggestions ???

Attachments

Re: Cannot access kernel driver - VBoxUSBMon.inf cannot be i

Posted: 11. Jun 2012, 16:48
by mpack
You need admin rights to install drivers on Vista/Win7 hosts. Also look in control panel for options on how the system will handle uncertified drivers. Make sure you set it to "Allow" or "Prompt", never set it to "Block automatically" (AIUI, VBox 64bit Windows drivers are certified, but 32bit drivers are not).

Re: Cannot access kernel driver - VBoxUSBMon.inf cannot be i

Posted: 11. Jun 2012, 23:22
by International
Could you give me some more precise directions on where in Control Panel I will find settings you've mentioned ?

really appreciate your help

Thanks in advance

Re: Cannot access kernel driver - VBoxUSBMon.inf cannot be i

Posted: 12. Jun 2012, 03:57
by BillG
That is really a Windows Vista question, not a VirtualBox one.

Have you tried starting VirtualBox using the "run as administrator" option? That normally fixes this sort of problem in Vista\Win 7.

Re: Cannot access kernel driver - VBoxUSBMon.inf cannot be i

Posted: 12. Feb 2013, 23:14
by ashok maggam
i encountered the same problem after suffering for days

i found that my systems32 folder is secured from any modification
so please make sure any of your system32 or drivers subfolder in that are not secured
from modification i.e. change their security status to modify or execute mode
for the administrator hope this solves your problem