Generic GL Renderer used, leading to crash when accessing 3D functionality.

[Bueffel]

Host : Windows 8.1pro 64, i7 Haswell with integrated 4600HD Graphics. Latest Intel HD driver 10.18.10.3621.

Guest : Ubuntu 14.04 LTS 64bit, guest additions 4.3.14

Virtual Box 4.3.14r95030 does not recognize Intels OpenGL driver, but falls back to Microsoft generic GDI. Linux is booting, when trying to login, crashes with Exception 0xc000094 at 0x2370aeff (unknown software exception). Working when disabling 3D support in VBox.

Logfile shows generic MS GDI driver 00:00:30.456612 OpenGL Info: Render SPU: GL_VENDOR: Microsoft Corporation 00:00:30.456629 OpenGL Info: Render SPU: GL_RENDERER: GDI Generic 00:00:30.456633 OpenGL Info: Render SPU: GL_VERSION: 1.1.0

Using VBox 4.3.12, OpenGL from Intel is being recognized and system is working : 00:00:27.446361 OpenGL Info: Render SPU: GL_VENDOR: Intel 00:00:27.446378 OpenGL Info: Render SPU: GL_RENDERER: Intel(R) HD Graphics 4600 00:00:27.446381 OpenGL Info: Render SPU: GL_VERSION: 4.2.0 - Build 10.18.10.3621

(I am not using RDP oder two graphics adapters or similar).

[Bueffel]

Logfile showing usage of generic OpenGL driver instead of Intel HD driver as in previous versions of VB.

[mslootweg]

(Possible duplicate of #13455)

I ran into this issue as well. VirtualBox was reverting to the Microsoft GDI Generic OpenGL renderer when using the Intel video driver on a Windows host. I tracked the issue down to the Intel driver being incorrectly signed. The signature on the file C:\Windows\System32\igdusc32.dll was not verifiable causing VirtualBox to reject the Intel driver. This is a hardening feature introduced in VirtualBox 4.3.14. Removing the digital signature from igdusc32.dll fixes the issue.

This bug appears in versions 4.3.14 through 4.3.18, the bug appears to be fixed in the just released 4.3.20. I suggest you give that version a try.