Virtual Display Blank

[Paul1964]

Hi,

I have a strange problem with a win 10 guest(on insider programme) running on a win 10 host. Both 64bit (fall update)

The VM has worked fine for some time, following the upgrade to 5.2, I needed to use a beta release to resolve the no bridged network with wifi host issue. This worked fine for some time.

However I started the VM today, and got the usual win 10 logo and the progress wheel, but then a black screen. I left this over an hour and it didn't change. Now the strange bit... When I clicked to close the window to close the VM, I could see the correct screen in black & white. Cancelling the close, I was then able to use the mouse and type, but with no change to the display. Clicking close again shows the correct screen again.

Even with the output restrictions, I managed to reinstall the guest additions, and reinstall the VB graphics adapter driver, I also managed to upgrade the guest to the fall update. However non of these actions resolved the issue.

I also tried the original general release 5.2 and the latest beta, again, the issue was not resolved.

Connecting via mstsc seems to work fine.
I also tried an Oracle Enterprise Linux 6.6 gui VM, which worked fine in the VB console.

Does anyone have any ideas? The only change I can think of is the host being upgraded to the fall update.

Thanks

[Paul1964]

After trying a few things, I've found a work around.

Disabling 3d acceleration on the guest VM resolves the problem.

So it looks like an issue with the VB console running on a win 10 host with a windows guest. I suspect the issue started after the host was updated to the fall release, but I can't test this as both my physical machines are updated.

VB - Version 5.2.1 r119001 (Qt5.6.2)
Guest Extensions - 5.2.0r118431
Host - Win 10 pro 64bit Version 1709 (OS build 16299.64)
Guest -Win 10 pro 64bit Insider Preview (fast path) Version 1709 (OS build 17040.1000)

[Paul1964]

I've just upgraded to 5.2.2. I still have the same issue.

Is anyone else seeing this?

[socratis]

Did you try clicking anywhere on the black screen? Not on the close window, but on the screen itself. I get that with my Win10 guest, but it's a nuisance at best, since I have to click anyway in order to login. And what about the preview window in the VirtualBox Manager? Does it display the state of the VM correctly?

If you're still having problems:

1. Start the VM. Not from a saved or paused state. Clean start.
2. Take the steps required to generate/observe the error.
3. Shut down the VM. Not saved or paused. Completely shut down. If you can't shut it down by normal means, close the VM window and select "Power off".
4. Right-click on the VM in the VirtualBox Manager. Select "Show Log..."
5. Save it (only the first VBox.log), ZIP it and attach it to your response (see the "Upload attachment" tab below the reply form).

[Paul1964]

Hi,

If I click (or type) on the black screen, the screen does not change, however the click/typing is recognised. Clicking to close the window again shows the correctly updated screen. The preview window works fine, so when you click the black screen to logon, the black screen is unchanged, but the preview window changes to show the login screen. Everything works, you just cant use the vb console. RDP is fine

The attached log is from a clean start (I just re-enabled 3d acceleration) and a clean shutdown. I clicked the power off etc from the black screen.

[socratis]

00:00:04.831719 NumCPUs <integer> = 0x0000000000000004 (4)
00:00:05.392609 CPUM: Physical host cores: 4

You have assigned all your CPUs to the VM. The host is going to run low on resources, since VirtualBox cares about physical processors, not logical ones. See: CPU Cores versus threads and Why is it a bad idea to allocate as many VCPUs as there are physical CPUs?

00:01:04.681477 supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: rc=VERR_CR_PKCS7_KEY_USAGE_MISMATCH fImage=1 fProtect=0x0 fAccess=0x0
                \Device\HarddiskVolume3\Windows\System32\DriverStore\FileRepository\nvbl.inf_amd64_aa900d663b62b12b\nvldumdx.dll: fKeyUsage=0x0,
                missing 0x1: \Device\HarddiskVolume3\Windows\System32\DriverStore\FileRepository\nvbl.inf_amd64_aa900d663b62b12b\nvldumdx.dll
00:01:04.681582 supR3HardenedErrorV: supR3HardenedMonitor_LdrLoadDll:
                rejecting 'C:\WINDOWS\System32\DriverStore\FileRepository\nvbl.inf_amd64_aa900d663b62b12b\nvldumdx.dll'
                (C:\WINDOWS\System32\DriverStore\FileRepository\nvbl.inf_amd64_aa900d663b62b12b\nvldumdx.dll): rcNt=0xc0000190

And this is where your problem lies. Your Nvidia drivers are either not properly signed, or the Windows certificate database is corrupt. For more detailed information, please read really carefully the following FAQ: Diagnosing VirtualBox Hardening Issues.

[VBTech88]

I have been having this same issue on one of my host machines running VirtualBox v5.2.2. That machine has two video cards: (1) Intel HD Graphics 530, (2) NVIDIA Quadro M1000M. One monitor is driven by each video card. On the monitor driven by NVIDIA, the guest screen is black (but respond to moue and keyboard input). If I move the window to the other monitor (driven by the Intel display adapter), everything is fine.

Your solution of turning off the "Enable 3D Acceleration" option for the guest machine worked. Thanks! ... But it is annoying to not be able to have 3D Acceleration.

It appears I might be having a signing issue also? Here are the relevant portions of the logs:

00:00:03.053241 supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: rc=VERR_CR_PKCS7_KEY_USAGE_MISMATCH fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume9\Windows\System32\DriverStore\FileRepository\nvdmwi.inf_amd64_951523cdc6c8d23f\nvinitx.dll: WinVerifyTrust failed with hrc=CERT_E_CHAINING on '\Device\HarddiskVolume9\Windows\System32\DriverStore\FileRepository\nvdmwi.inf_amd64_951523cdc6c8d23f\nvinitx.dll'
00:00:03.053318 supR3HardenedErrorV: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\WINDOWS\System32\DriverStore\FileRepository\nvdmwi.inf_amd64_951523cdc6c8d23f\nvinitx.dll' (C:\WINDOWS\System32\DriverStore\FileRepository\nvdmwi.inf_amd64_951523cdc6c8d23f\nvinitx.dll): rcNt=0xc0000190

00:00:06.494471 supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: cached rc=VERR_SUP_VP_NOT_OWNED_BY_TRUSTED_INSTALLER fImage=1 fProtect=0x0 fAccess=0x0 cHits=2048 \Device\HarddiskVolume9\Users\ausername.domain\AppData\Local\Temp\ammemb64.dll
00:00:06.494595 supR3HardenedErrorV: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Users\USER~1.DOM\AppData\Local\Temp\ammemb64.dll' (C:\Users\USER~1.DOM\AppData\Local\Temp\ammemb64.dll): rcNt=0xc0000190

00:00:50.516913 supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: cached rc=VERR_SUP_VP_NOT_OWNED_BY_TRUSTED_INSTALLER fImage=1 fProtect=0x0 fAccess=0x0 cHits=4096 \Device\HarddiskVolume9\Users\ausername.domain\AppData\Local\Temp\ammemb64.dll
00:00:50.516973 supR3HardenedErrorV: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Users\USER~1.DOM\AppData\Local\Temp\ammemb64.dll' (C:\Users\USER~1.DOM\AppData\Local\Temp\ammemb64.dll): rcNt=0xc0000190

[Sundog1966]

After trying a few things, I've found a work around.

Disabling 3d acceleration on the guest VM resolves the problem.

So it looks like an issue with the VB console running on a win 10 host with a windows guest. I suspect the issue started after the host was updated to the fall release, but I can't test this as both my physical machines are updated.

VB - Version 5.2.1 r119001 (Qt5.6.2)
Guest Extensions - 5.2.0r118431
Host - Win 10 pro 64bit Version 1709 (OS build 16299.64)
Guest -Win 10 pro 64bit Insider Preview (fast path) Version 1709 (OS build 17040.1000)

I am having the same problem with linux mint 18.1 and a similar windows 10 1709 configuration.

[socratis]

@VBTech88, @Sundog1966
The answer is still the same... Please read really carefully the following FAQ: Diagnosing VirtualBox Hardening Issues. Take appropriate action. There is *no* specific action, only each and everyone of you on its own have to figure this out.

Re-installing the drivers and/or fixing the Windows certificate database might help you @VBTech88.

[Paul1964]

I wonder whether there's an issue with the NVidia drivers?
I have an HP elite book 8570w with an NVidia Quadro K2000M graphics card. I've always taken updates from windows update or HP softpaq download manager. I only started having issues recently, but can't remember if it was a graphics update or the windows fall update. There is a newer driver on the NVidia site which I've downloaded, but its still the same.

I also have graphics issues with remote desktop manager. When I initially open a connection, the console looks like its in the wrong reolution. Minimising and opening the windows fixes it. This has always been the case, but at the same time as the VB issues started, if I played a video in the remote desktop manager window, the display would remain incorrect (looking like wrong resolution/interlacing) and the session had to be reconnected.

I think it may be a case of waiting for another nvidia update.