virtualbox.org

VBox 5.0.2r102096

Host = Win7 sp1 Ultimate on 64bit i7 16gb RAM / 500gb SSD

Guest = Win7 sp1 32bit 2gb RAM

TIA for Help to solve this -- Advanced searching the forum for "Actual Window Manager" finds nothing.

I did find a mention of others with this problem about 6 weeks ago, failed to log the url, haven't been able to locate it again.

Whilst Actual Window Manger v8.2 / 8.3 / 8.4 is running, a VM will hang infinitely following initial Windows splash logo screen.

A lucky hunch 2 months ago had me turn off AWM, then VBox started & ran wonderfully - no problems.

Now I have need to run some VMs daily, so finally need to solve this for good.

Just now I deleted accumulated log files, rebooted, shut off AWM, started & ran VBox successfully,
then copied that log file into a folder named "Success".

Then I turned on AWM, re-Started the VM, let it hang for a minute or so -- this time it forcefully aborted itself,
then I copied that log file into a folder named "Fail".

Kindly advise me what log files to attach and exactly how.
Thanks again for any Help.

It seems obvious from your post that "Actual Window Manager" and VirtualBox are not compatible. You can either stop using AWM with VirtualBox or ask the AWM folks to fix their software to work with VB.

Here's more data to help the Helpers here, to Help us:

#1: VMWare Workstation Pro 12 does NOT have any issues with AWM -
just installed VMWW 12 Pro and it co-exists with AWM with no apparent problems through multiple reboots.

#2: Turns out I did log the url of the previously reported problem --
I couldn't find it in the Forums 'proper' because it's on VBox in the 'Tickets' area :
#3: A couple more observations/test results:

Thinking the problem might be AWM's "active interference" --
trying to overlay its Controls onto VBox, I unchecked the "Default Settings" in the Config Mgr.

That allowed VBox to run successfully a couple of times - until I rebooted the physical machine,
then it glitched again -- except that when it glitched, now I got a Memory-Resource "Application Error" :

The instruction at 0x0659a690 referenced memory at 0x0659a690.
The memory could not be written.

Click on OK to terminate the program.

Upon physical machine reboot and start VBox again, the same error message appeared
w/ a different memory address of: 0x0646a690 .

Again, I'll be happy to submit the log file if a moderator will let me know specifically how/what.

Thanks again for your assistance.

[Edit -- 1 more observation -- It seems that VBox belongs to the " QWidget Class " .
StrokeIt is a mouse-gesture application that also belongs to this class,
and I had to add the " QWidget Class " to StrokeIt's Disabled list in order for StrokeIt to work w/ VBox --

the interesting thing is that I have StrokeIt working as a portable inside the w7-Guest running instance.

So maybe this whole issue is between AWM & " QWidget Class " instances?
because VMWare Workstation Pro 12 belongs to the " VMUIFrame " Class. ]

If running AWM involves injecting DLLs into the VirtualBox program space - and I rather suspect that it will - then those DLLs need to be signed. See the "hardening" sticky topic near the top of this forum.

Thanks mpack - i'll have a study through that resource