Hello
I have a problem with a guest of Windows 10. When I put the 3D acceleration I have the image which is lived as a parasite to see joined picture.
I have enabled 2D and 3D acceleration. The host is Windows 10 x64 1709. I am using VirtualBox v5.1.30 r118389 with guest additions installed on the Windows 10 64b guest. It may also be relevant to this situation that I have a GTX 460 installed and using the latest and stable v388.13 drivers
Thank you for your answers.
Graphic corruption with Guest Windows 10
Re: Graphic corruption with Guest Windows 10
Sounds like the same problem I am having too. Here is my thread: viewtopic.php?f=2&t=85331
Re: Graphic corruption with Guest Windows 10
Hello
Yes it's the same problem.
A moderator could signal the problem to have a solution
Cordially
Yes it's the same problem.
A moderator could signal the problem to have a solution
Cordially
-
- Site Moderator
- Posts: 39156
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Graphic corruption with Guest Windows 10
When we hear about a solution we certainly won't keep it a secret. The mods are not the devs, so we don't know any more than you do at this point.Losada wrote: A moderator could signal the problem to have a solution
Re: Graphic corruption with Guest Windows 10
Hello
I did not mean to say that you know a solution but
I wanted to say how did the devolapper report the problem.
Cordialy
excuse my english is from a translation:
I did not mean to say that you know a solution but
I wanted to say how did the devolapper report the problem.
Cordialy
excuse my english is from a translation:
-
- Site Moderator
- Posts: 39156
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Graphic corruption with Guest Windows 10
Well as I said, we mods don't yet know a solution. As for the devs they rarely are drawn into support questions from users of the free download, after all they charge good money for support contracts. All we can do is ensure that the devs know about the problem (and I'm aware of several similar problems reported the in the 5.2.0 discussion topic), then sit back and await events.