![]() Mpack Site Moderator Posts: 35846 Joined: 4. Shut down the VM again, restore the graphics controller to VBoxSVGA and enable 3D acceleration.Scroll until you see "Show transparency in Windows" and disable it (Microsoft move this option around: previously it was on Personalize|Colors). Open the Win10 Settings panel and click on Ease of Access.Don't try Direct3D or OpenGL - those will fail). The problem appears to be an incompatibility between the Virtualbox guest additions display adapter and the final cleanup boot. ![]() Launch Windows 10 (basic graphics should now be stable, but slower.Perhaps also change the graphics controller to VBoxVGA (I don't recall if I did this). Shut down the VM and disable 3D acceleration temporarily.Possibly I updated my own Win10 VM to 2004 some time after the above, and hence had not yet seen the problem myself.Īnyway, follow these steps to work around the transparency glitches: Installed/re-installed the 'Guest additions' The command: Code: Select all Expand view Collapse view VBoxManage. vbox file is a useful diagnostic tool, we need to see a complete VBox. However, reading your post again this now looks like a clear example of the "transparency" issues we've seen with Win10 (2004). In the Devices menu in the virtual machine's menu bar, Oracle VM VirtualBox has a menu item Insert Guest Additions CD Image, which mounts the Guest Additions ISO file inside your virtual machine. Confirm what issue? The passage of mine that you quote makes a suggestion, I didn't undertake to do any more investigation: I'm a user like yourself, not a dev.
0 Comments
Leave a Reply. |