Windows 10 guest graphical issues on ubuntu host

[DeGarcen]

windows 10 guest on linux host > graphical issues
windows 10 guest on windows 10 host > fine

See screenshots attached.

01.jpg (90.19 KiB) Viewed 3848 times

02.jpg (42.54 KiB) Viewed 3848 times

[socratis]

Did you seriously paint over the name of the "Recycle Bin" and "Edge"!?!

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 or recreate the 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.

[scottgus1]

Did you seriously paint over the name of the "Recycle Bin" and "Edge"!?!

Doesn't matter, 'LibreCrypt Explorer' and 'DoNotSpy 10' were unwisely left exposed. Vectors loaded.

Tighten that tin-foil hat, this is going to be a bumpy ride...

ALL YOUR BASE ARE BELONG TO US!!!!

[MrFree]

same problem (ubuntu 19,10. vb6.1)

Also the problem was present at me on ubuntu 18.04 on vb 6.0. The problem disappears with disabling 3d acceleration.

[mpack]

"graphical issues" covers a wide range of problems. It would be nice if you were more specific. The OPs problem looks like a host compositing issue.

In another topic the poster reporting that turning off "Transparency Effects" (in Personalisation|Colors) worked around a similar looking problem.

[socratis]

MrFree,

00:00:01.048784 File system of '/home/mrfree/Downloads3/iso
                /Windows10_InsiderPreview_Client_x64_ru-ru_19035.iso' (DVD) is ext4
...
00:01:48.440289 VMMDev: Guest Log: Windows version 10.0 build 19035 (uNtVersion=0xa0000000004a5b)

Are you running an "Insider Preview" build? Does this happen with the official release?

00:00:00.924450 OS Release: 5.3.0-24-lowlatency

Though not strictly related to your current report, "low latency" kernels have had issues with VirtualBox, generally speaking.

00:00:01.102404 ICH9 <integer> = 0x0000000000000001 (1)

Any particular reason why you decided to override the template defaults, and go with an unsupported, experimental, OSX-guests-only option? Please change it back to the default PIIX3. Do not change the defaults unless you know what you're getting into. Same with EFI...

[MrFree]

"Insider preview" build ? > It does not depend on the build, with stable release too.
Disabling transparency helped with Win10. Disabling Aero helped on Win7.
However, some glitches remained. The login window has a black background in the list of users at the bottom left. Pro glitches in 3d programs (not game) think to mention not worth?

-lowlatency
My system behaves strangely with a generic kernel. Very similar to the famous Linux kernel bug (number i forgotten). I'll try to switch to generic and see what happens. So same like would revere much detail where was written about this. To read at all all consecutive I unfortunately not can. English I understand not very well and write here through the interpreter.
There are no changes after the kernel change

EFI&ICH9
Thanks, I forgot to return the options after the experiments. The installation was initially on PIIX3 and normal bios. efi from threr vdi.
Changing these options did nothing.

[DeGarcen]

Here's the log, sorry for the delay.

UPDATE: disabling this option works: Settings > Display > Screen > Acceleration: Enable 3D Acceleration

[mpack]

Did you try this?

In another topic the poster reporting that turning off "Transparency Effects" (in Personalisation|Colors) worked around a similar looking problem.

[DeGarcen]

Did you try this?

In another topic the poster reporting that turning off "Transparency Effects" (in Personalisation|Colors) worked around a similar looking problem.

Yes, just tried it just now, and works, no more issues with black parts. This is the registry reg file. Note that i have to use this since Windows is not activated and doesn't allow to disable transparency from settings so it has to be done through registry:

Code: Select all

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Themes\Personalize]
"ColorPrevalence"=dword:00000000
"EnableTransparency"=dword:00000000

Desktop and all windows work, however there's still a glitch remaining when windows is booting and the balls are running in circles, see attachment.

[DeGarcen]

No further updates?

[mpack]

What update were you expecting? Have you seen a new VirtualBox release in the last week? Did you try a test build? Did you report the problem in the 6.1.2 feedback discussion or BugTracker?

In any case we're not here to support Windows bugs, e.g. use of transparency when you think it's disabled (though clearly the above happens during Windows login, so the current user settings profile may not be loaded).

[DeGarcen]

What update were you expecting? Have you seen a new VirtualBox release in the last week? Did you try a test build? Did you report the problem in the 6.1.2 feedback discussion or BugTracker?

In any case we're not here to support Windows bugs, e.g. use of transparency when you think it's disabled (though clearly the above happens during Windows login, so the current user settings profile may not be loaded).

I've been told 6 times by @socratis on bug tracker, that I do use forums to report issues.

[scottgus1]

I've been told 6 times by @socratis on bug tracker, that I do use forums to report discuss issues.

'Twas probably more like this, though if you have links we could see exactly what was said.

If one jumps straight to the Bugtracker, one might get told to go to the forum first. Often issues have a discovered workaround or fix, and the forums can relay those fixes quicker than the developers can. (They kinda have their plates full.) The forums are for discussing the issues first.

Eventually an issue may not have a fix discovered on the forum, then going to the Bugtracker might be of help. A complete story of what was happening, with repeatable steps to cause the bug if possible, and guest logs (from guest cold-start - not save state - to seeing the problem to shutting down the guest) will provide the developers with the best possible info, if there's info to be found.

The fact that you got the black spots to go away with the registry hack is interesting and may be of interest to the developers on the Bugtracker. The fact that the hack goes in "HKEY_CURRENT_USER" shows, as Mpack points out, that the fix probably won't apply until the account is logged in. Are there similar locations in "HKEY_LOCAL_MACHINE" for such a hack?

[DeGarcen]

I've been told 6 times by @socratis on bug tracker, that I do use forums to report discuss issues.

'Twas probably more like this, though if you have links we could see exactly what was said.

Here are the threads:

• https://www.virtualbox.org/ticket/18864
• https://www.virtualbox.org/ticket/18865
• https://www.virtualbox.org/ticket/18888
• https://www.virtualbox.org/ticket/18910
• https://www.virtualbox.org/ticket/18929
• https://www.virtualbox.org/ticket/19051

The fact that you got the black spots to go away with the registry hack is interesting and may be of interest to the developers on the Bugtracker. The fact that the hack goes in "HKEY_CURRENT_USER" shows, as Mpack points out, that the fix probably won't apply until the account is logged in. Are there similar locations in "HKEY_LOCAL_MACHINE" for such a hack?

Not that I'm aware, probaby you are right, that's user setting not system setting. Notice that it's inside CURRENT_USER