virtualbox.org

I have a Windows 10 Insider Preview running under VirtualBox 6

For the past couple of weeks it has become unusable - see this image for an example of the Start menu open, trying to pick a shutdown option. There's two levels of menu with no background and the top level (the shut down options themselves) are invisible.

i.imgur. com/YBN7QuU.png (Remove the space...)

I have tried the latest dev build of VB (6.0.11 r133017) and it makes no difference. Windows 10 updated to the latest build just now and also no change.

Trying to work out which side the problem lies! Any suggestions?

Please attach the image locally in your response (see the "Upload attachment" tab below the reply form). Not a lot of people will go to 3rd party sites. Plus, it's more convenient if the image goes along with the message...

We need to see a complete VBox.log, from a complete VM run, where the problem occurs:

• Start the VM from cold-boot (not from a paused or saved state) / Observe problem / 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.

Ah - sorry - missed that option!

Anyway; having just made the post; I thought to try options in VB and turned off 3D Accelleration. Bingo! Display working again. So it's either VB Guest Extensions driver or possible my video card (nVidia 1060) driver. Going to update that and then try re-enabling 3D to see if it's still broken. It used to work, so it's some combination of Win10\VB drivers and nVidia drivers!

Thanks for looking anyway!

Newest GeForce drivers make no difference.
So I guess there's something screwy in VBs 3D support chain somewhere.

You forgot the 2nd part, the ZIPPED complete VBox.log...

One log file!

00:00:03.068031   VMSVGA3dEnabled  <integer> = 0x0000000000000001 (1)
00:00:03.068032   VMSVGAEnabled    <integer> = 0x0000000000000001 (1)
00:00:03.068032   VRamSize         <integer> = 0x0000000010000000 (268 435 456, 256 MB)

Can you turn off 3D acceleration? Does it work?
Alternatively, can you switch to the older VBoxVGA (minus the 'S')? Does it work?

socratis wrote:Can you turn off 3D acceleration? Does it work?
Alternatively, can you switch to the older VBoxVGA (minus the 'S')? Does it work?

Yes - as I said in my earlier post, turning off 3D makes it work. It was fine before, so it looks like some update in VB or nVidia drivers has broken things.

The VBoxVGA driver has the same issue (display problem with 3D on, OK with it disabled).