virtualbox.org

Thanks for your reply.
I did as you suggested and had the same error with no Comodo.
I attach hardening log

Commode is gone:

1b00.1628: supR3HardenedWinFindAdversaries: 0x0

The log says this:

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.

Seems to be the same error as before.

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

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

Comodo is back:

16c4.1ff8: ProductName: COMODO Internet Security Sandbox Driver
16c4.1ff8: FileDescription: COMODO Internet Security Eradication Driver
16c4.1ff8: ProductName: COMODO Internet Security Firewall Driver
....

These files are not hardenable:

user32.dll
\Device\HarddiskVolume6\Program Files (x86)\KeyCryptSDK\KEYCRY~4.DLL
\Device\HarddiskVolume6\Windows\System32\ddraw.dll

scbs29 wrote:sfc /scannow showed mstsc.exe was corrupt

If you believed sfc and let the file get fixed, then good.

scbs29 wrote:I tried every solution in viewtopic.php?f=6&t=82277

What exactly did you try: Precise steps please, if you don't wish to try the next paragragh.

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.)