Windows EFI Guests & Additions' Display Adapter Driver

[corhsin]

5.1.30/5.1.30 . When Guest Additions is installed it blacks the screen. The disconnect sound plays. The guest is active, it allows RDP'ing in. There is a stability issue. This was a problem with a Win10 1607 or 1703 (IDR) after conversion and I assumed VBox was having trouble adapting. It was just attempted with an RTM 1709 EFI install. The outcome is predictable.

The host is Win10 1709 x64 (MBR/BIOS), an X58 with a W3690 Xeon (6-core) and 48 gigs of DDR3. GeForce 1080 8GB and a selection of drives and other hardware. It has for years been a workhorse and to date there are zero complaints (e. g. the 250 Chrome tabs open chug right along).

Any suggestions? I can supply logs on request. Arriving here I noticed 5.2 is available. Starting that VM post upgrade:
This VM was configured to use 3D acceleration. However, the 3D support of the host is not working properly and the VM cannot be started. To fix this problem, either fix the host 3D support (update the host graphics driver?) or disable 3D acceleration in the VM settings (VERR_NOT_AVAILABLE).

Result Code:
E_FAIL (0x80004005)
Component:
ConsoleWrap
Interface:
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

I see the VirtualBox install has conflict with Sandboxie, which is understandable. I can attempt to remove it. Here are some other ideas, logged during the GA upgrade, after 3D acceleration was disabled:

The application \Device\HarddiskVolume4\Windows\explorer.exe with process id 4724 stopped the removal or ejection for the device PCI\VEN_80EE&DEV_CAFE&SUBSYS_00000000&REV_00\3&267a616a&0&20.

Driver Management has concluded the process to add Service VBoxGuest for Device Instance ID PCI\VEN_80EE&DEV_CAFE&SUBSYS_00000000&REV_00\3&267A616A&0&20 with the following status: 0.

Driver Management concluded the process to install driver vboxguest.inf_amd64_c1c3a23271b0e375\vboxguest.inf for Device Instance ID PCI\VEN_80EE&DEV_CAFE&SUBSYS_00000000&REV_00\3&267A616A&0&20 with the following status: 0x0.

Driver Management has concluded the process to add Service VBoxVideoW8 for Device Instance ID PCI\VEN_80EE&DEV_BEEF&SUBSYS_00000000&REV_00\3&267A616A&0&10 with the following status: 0.

Driver Management concluded the process to install driver vboxvideow8.inf_amd64_9f5029660fd5d8b4\vboxvideow8.inf for Device Instance ID PCI\VEN_80EE&DEV_BEEF&SUBSYS_00000000&REV_00\3&267A616A&0&10 with the following status: 0x0.

Driver Management concluded the process to install driver vboxvideow8.inf_amd64_9f5029660fd5d8b4\vboxvideow8.inf for Device Instance ID PCI\VEN_80EE&DEV_BEEF&SUBSYS_00000000&REV_00\3&267A616A&0&10 with the following status: 0x0.

The system has been constrained to a periodic tick
Reason: No HW support.

The following boot-start or system-start driver(s) did not load:
dam
EhStorClass


Disabling 3D (or the new 5.2) does have a positive effect on other configurations. I was having a hard time getting windows sized or scaled. If a V. M. was set to permanently scale, it would be black beyond roughly the area of an unscaled 100% window in the upper left. If enlarging then reducing by any amount the problem was gone until the next load. I finally realized it could be paused/unpaused for the same effect. The trouble may be related.

I suppose I could remove and try to cleanly remove (I assume someone has instructions out there) VBox. My VMs are spread around drives and ultimately a hassle is anticipated. I was under the assumption the video problem is an EFI issue and unrelated. I fall upon the community's expertise (and intend instant regret). Thanks in advance.

[socratis]

Can you please discuss clearly a single problem at a time? And please read the following: Minimum information needed for assistance.