Thanks for your reply.
I did as you suggested and had the same error with no Comodo.
I attach hardening log
Cannot create virtual mqachine
-
scbs29
- Posts: 23
- Joined: 26. Apr 2009, 19:10
- Primary OS: PCLinuxOS
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: XP
Re: Cannot create virtual mqachine
- Attachments
-
- VBoxHardening.zip
- (3.29 KiB) Downloaded 5 times
-
scottgus1
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows, Linux
Re: Cannot create virtual mqachine
Commode is gone:
Please uninstall Virtualbox and reboot the PC. Now right-click the Virtualbox installer and click Run As Administrator, even if you are already an administrator.
If installing via Run As Admin does not get you going, try setting VboxDRV service to Demand Start:
viewtopic.php?f=6&t=82277
The log says this:1b00.1628: supR3HardenedWinFindAdversaries: 0x0
Seems to be the same error as before.1b00.1628: NtCreateFile(\Device\VBoxDrvStub) failed: 0xc0000034 STATUS_OBJECT_NAME_NOT_FOUND (0 retries)
Driver is probably stuck stopping/starting. Try 'sc.exe query vboxdrv' to get more information about its state. Rebooting may actually help.
Please uninstall Virtualbox and reboot the PC. Now right-click the Virtualbox installer and click Run As Administrator, even if you are already an administrator.
If installing via Run As Admin does not get you going, try setting VboxDRV service to Demand Start:
viewtopic.php?f=6&t=82277
-
scbs29
- Posts: 23
- Joined: 26. Apr 2009, 19:10
- Primary OS: PCLinuxOS
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: XP
Re: Cannot create virtual mqachine
Thanks again for your reply.
I tried every solution in viewtopic.php?f=6&t=82277 and VBox will still not open a VM.
sfc /scannow showed mstsc.exe was corrupt, but since I do not have Remote Desktop enabled I fail to see how this could have
any bearing on the problem (please correct me if I am wrong)
If I open an elevated command prompt and type sc start vboxdrv I get
SERVICE_NAME: vboxdrv
TYPE : 1 KERNEL_DRIVER
STATE : 4 RUNNING
(STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
In this case I do not receive the STATUS_OBJECT_NAME_NOT_FOUND error, but still get the other that it cannot create a virtual machine.
I attach the latest hardening log
I tried every solution in viewtopic.php?f=6&t=82277 and VBox will still not open a VM.
sfc /scannow showed mstsc.exe was corrupt, but since I do not have Remote Desktop enabled I fail to see how this could have
any bearing on the problem (please correct me if I am wrong)
If I open an elevated command prompt and type sc start vboxdrv I get
SERVICE_NAME: vboxdrv
TYPE : 1 KERNEL_DRIVER
STATE : 4 RUNNING
(STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
In this case I do not receive the STATUS_OBJECT_NAME_NOT_FOUND error, but still get the other that it cannot create a virtual machine.
I attach the latest hardening log
- Attachments
-
- VBoxHardening.zip
- (37.23 KiB) Downloaded 5 times
-
scottgus1
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows, Linux
Re: Cannot create virtual mqachine
Comodo is back:
In my opinion, your PC is too messed up to pass the hardening checks. Something put Comodo back on, after all the effort gone through to get it off (unless that was a pebkac issue, at which I give up). I would suggest swapping hard drives as a temporary measure, reinstalling the host OS (Windows 7) on the new drive, then Virtualbox first. If Virtualbox runs, start adding the other programs & AV you have and then reboot, one at a time, checking Virtualbox after every new install & reboot. (on occasions a reinstall of everything, even the non-hardenable programs, can allow coexistence with Virtualbox. Only way to tell is to try.)
These files are not hardenable:16c4.1ff8: ProductName: COMODO Internet Security Sandbox Driver
16c4.1ff8: FileDescription: COMODO Internet Security Eradication Driver
16c4.1ff8: ProductName: COMODO Internet Security Firewall Driver
....
user32.dll
\Device\HarddiskVolume6\Program Files (x86)\KeyCryptSDK\KEYCRY~4.DLL
\Device\HarddiskVolume6\Windows\System32\ddraw.dll
If you believed sfc and let the file get fixed, then good.scbs29 wrote:sfc /scannow showed mstsc.exe was corrupt
What exactly did you try: Precise steps please, if you don't wish to try the next paragragh.scbs29 wrote:I tried every solution in viewtopic.php?f=6&t=82277
In my opinion, your PC is too messed up to pass the hardening checks. Something put Comodo back on, after all the effort gone through to get it off (unless that was a pebkac issue, at which I give up). I would suggest swapping hard drives as a temporary measure, reinstalling the host OS (Windows 7) on the new drive, then Virtualbox first. If Virtualbox runs, start adding the other programs & AV you have and then reboot, one at a time, checking Virtualbox after every new install & reboot. (on occasions a reinstall of everything, even the non-hardenable programs, can allow coexistence with Virtualbox. Only way to tell is to try.)