Weird transparent window on W10

[veeectorm]

First post here, so i hope i dont break ALL the rules of the forum.

Running OSX mojave (but this has been happening since high sierra i believe).
Latest windows 10 pro build.(17134.286)
VBOX 5.2.18 124319 qt563

Whenever i resume a machine that was saved and closed, i end up with a black, blank window in addition to my virtual screen. On OSX mojave its getting worse, as i end up with multiple, unmovable, white windows. The only way of getting rid of those is shUtting down the guest, and restarting it in windowed mode. After that i switch to fullscreen and it is ok.

I hope someone can help me out on this one. Sorry if im missing details.

V.


EDIT: LOLOLOOLLL Fixing "5hitting down the guest"

[socratis]

First post here, so i hope i dont break ALL the rules of the forum.

Welcome to the forums! And don't worry, you only "broke" one rule about "mild foul language", but it's not a big deal

i end up with a black, blank window in addition to my virtual screen

Any chance of seeing what that looks like?

as i end up with multiple, unmovable, white windows

or that?

The only way of getting rid of those is shitting down the guest

I'm not sure that such an "aggressive action" would help your situation!

We're going to need to see a VM log from a complete VM run:

• Start the VM from cold-boot (not from a paused or saved state) / Observe error / Shutdown the VM (force close it if you have to).
• With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
• Save only the first "VBox.log", ZIP it and attach it to your response. See the "Upload attachment" tab below the reply form.

[veeectorm]

Ive uploaded the logs here, and the screenshots to:

https://imgur.com/a/taeP0eN

I cant seem to replicate this behavior by starting from a cold boot. I can however, make it happen if i cold boot, save state, and resume.

The screenshots show a few things:
-First that weird pseudo second screen that is not really a second screen on the VM. Tells me there is just one monitor connected to the vm. This is the machine running on windowed mode, but that second screen still comes up there blank. No idea why.
-Switching to fullscreen ends up having "2" screens,the blank one, and the actual screen of the VM. (screenshot shows both spaces on OSX, im holding 4 fingers on the trackpad to show both at the same time here.
-Last screenshot shows that weird unmovable window.

Hope this helps.

Thanks for the quick response!

V.

[veeectorm]

That weird a and some other letters is imgur....im supposed to have an account older than a day

Let me know if you can reach it, and ill try something else.

EDIT: updated link now that im one day old here https://imgur.com/a/taeP0eN

[Michael.TW]

Hi there,

I’ve got the same problem but the different are I’m using MacOS High Sierra (as Veeectrom mentioned he had same problem in since High Sierra version), and the VM installed Windows XP.

the log file is attached. hope can figure out the problem soon!

[socratis]

@veeectorm
What you're seeing I believe is a demonstration of the weird behavior of ticket #17168: "VB display frame and content are no longer bound in High Sierra (osx 10.13)", artifacts from the window management code in 10.13.

To verify it, disable the 3D acceleration from your guest and try it again. See if you can get it to repeat with the 3D acceleration disabled.

@Michael.TW
I'm not sure that you have the same problem. I'm seriously considering split your post from this thread. A "me too" without a picture showing exactly what "me too" means, is not that helpful. So, please provide a screenshot of what the problem looks like. Plus your Guest Additions are still at 4.1.0, talk about outdated :

00:00:09.122856 VMMDev: Guest Additions information report: Version 4.1.0 r73009 '4.1.0'

[veeectorm]

Interesting.
Now that ive read that entry, i remember this started happening when i enabled 3d accell. I think i was getting pretty back scrolling performance on my vm, so i enabled 3daccell and after one vbox update this started.

Ill play around with my settings and try the workarounds. Ill post my results back here soon!

V.