VERR_ACCESS_DENIED (rc=-38) or Integrity error (rc=-38) on VM start

[Mihai Hanor]

This is a follow-up to bug #13295, at the request made by sunlover.

Sometimes, when starting a VM from a desktop shortcut, the second VirtualBox process returns VERR_ACCESS_DENIED (rc=-38) or Integrity error (rc=-38) and exits. The Vbox.log file is not even created, the COM process doesn't get started. Just in case, I have provided the VBox.log of a successful VM start. All the attached VBoxStartup logs contain a rc=-38 error.

Sometimes it feels like it's being triggered more often by starting the VM after copying large files or using RAM intensive applications, or after a "rest" period. It's like the host OS has flushed or paged out something.

Host Windows 8.1 x64, VirtualBox 4.3.19.96945
I won't even try 4.3.18 or anything before 4.3.19.96923, because it will most likely trigger a BSOD, see bug #13295.

[sunlover]

Ticket #13632 is the same problem and contains some logs.

[Carsten H.]

Strange: In Ticket #13632 I have appended my files.

And I've found the following: The VBoxStartup.log was not written. Timestamp was from the day before.

[Carsten H.]

I have now installed the version of VirtualBox 4.3.20-96996-Win.exe.

On the previous days, I could start Virtualbox error-free. Today I again received error code VERR_ACCESS_DENIED (rc = -38). However, it was still not generate any log. Neither the VBox nor VBoxStartup or VBoxSVC.log. (???)

[Mihai Hanor]

You have to add an extra parameter to your VM shortcuts --sup-startup-log="z:\path\to\virtual\machine\folder\VBoxStartup.log", for it to create the VBoxStartup.log file. See bug report #13629. The VboxSVC.log is not created because the COM service never gets a chance to start, when the VERR_ACCESS_DENIED (rc = -38) error occurs.

[Carsten H.]

Thank you mhanor for the comment. Today the start again aborted with VER_ACCESS_DENIED error (rc = -38). Here the log.

[Peter Hull]

I also see this intermittently on 4.3.20r96997, Win 8.1 64-bit. It seems to happen if I start a VM from a direct shortcut rather than via the Manager. A second attempt to start the VM usually succeeds.

[Carsten H.]

Daily I'm watching here for a solution...
Can I help anything?

[Carsten H.]

The problem is not resolved with the new version (4.3.22-98236-Win.exe) on my system.
Someone any idea?

[sunlover]

azh65, please attach VBoxStartup.log from VirtualBox 4.3.22.

[Mihai Hanor]

4.3.23-98520

[Carsten H.]

VBoxStartup from Crash Start with VB 4.3.24 r98716

[Carsten H.]

VBoxStartup 4.3.26 r98988

[feier]

this webpage:​http://unun.in/linux/92.html

[azh65_]

VBoxStartup 4.3.28 r100309

[Mihai Hanor]

It still occurs with VirtualBox 5.0.1 r101908. Here's what DebugView (from Sysinternals) displays when it occurs:

vboxdrv: 00000000000011dc is not a budding VM process.
[4848] Error -38 in suplibOsInit!
[4848] Integrity error (0xe986ffda/-38): [àÿÿ[¤&[àÿÿ

[Frank Mehnert]

Sorry, is this still in issue with 5.0.2 / the lastest 5.0.3 test build?

[Mihai Hanor]

I think it's ok with 5.0.2 and 5.0.3-102467

[Frank Mehnert]

Thanks.