Hyper-V, Credential Guard, Device Guard, or why doesn’t VMware Workstation or VirtualBox work on Windows 10?

It’s frustrating if you’re seeing the the message from VMware Workstation about Device Guard or Credential Guard or the similar one from VirtualBox.

But, there are a few thing to clarify before going off on a search for those devices.  First, if you’ve got Hyper-V installed, that is the most likely culprit here and disabling or removing that feature should solve your issue.

Some things to consider:

If you’ve got Windows 10 Home, then you don’t have Hyper-V enabled. See: https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/reference/hyper-v-requirements

If you have Windows 10 Home or Pro you do not have Credential Guard enabled.  It is a feature only in Enterprise, Education, and IoT Enterprise versions of Windows 10. See: https://docs.microsoft.com/en-us/windows/security/identity-protection/credential-guard/credential-guard-requirements

 

This is great info, but what do you do about getting Workstation or VirtualBox to work?

Again, the most likely culprit is Hyper-V.  Disabling or removing and a reboot should resolve this.

Disable or Remove Hyper-V

Disable Hyper-V

Open an elevated command prompt or PowerShell (right-click and select Run as Administrator)

Enter: bcdedit /set hypervisorlaunchtype off

Reboot.  (To re-enable Hyper-V, open an elevated prompt and enter:  bcdedit /set hypervisorlaunchtype auto and reboot.)

Remove Hyper-V

Go to Control Panel–>Programs and Features, select Turn Windows features on or off.

Expand Hyper-V, then expand Hyper-V Platform.

Uncheck Hyper-V Hypervisor.

Reboot.  Please note that removing Hyper-V could affect the functionality of other features of Windows 10 such as Docker.

 

Windows Hypervisor Platform

While this is supposed to allow 3rd party virtualization to access the hardware virtualization on the host, it doesn’t seem to work for either Workstation or VirtualBox.  Workstation  gives the same standard Credential Guard message.  VirtualBox is supposed to work per their changelog, but the communities have posts reporting failure and a bug report on it.

Disable Windows Hypervisor Platform

Go to Control Panel–>Programs and Features, select Turn Windows features on or off.

Uncheck Windows Hypervisor Platform

Reboot.

 

Disable Device Guard

Editing the Registry will disable this feature.  Please make sure you have a backup of your system, as editing the Registry can result in an unusable or broken Windows.

Edit the following key:  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\HypervisorEnforcedCodeIntegrity

Set:  Name = “Enabled”  Type =dword  Data = 0

Reboot.

Alternately, you can use the Local Group Policy Editor to manage Device Guard.

Start gpedit.msc or find Local Security Policy from the start menu.

Expand Computer Configuration\Administrative Templates\System\Device Guard and change the state to disabled.  If you see the same settings as below, you probably don’t have Device Guard enabled.

 

Credential Guard

Credential Guard is controlled via Group Policy, so it’s likely that if this is the issue, you’ll be unable to do anything about it yourself.  You’ll need to contact your IT department to have this turned off.  Again, Credential Guard is only available on Enterprise, Education, and IoT Enterprise.  If you don’t have one of these versions, this isn’t the culprit.

 

Antivirus Utilities

There is one more culprit that could be causing the issue.  Some antivirus software blocks hardware virtualization.

Check with your antivirus vendor to confirm this isn’t an issue and if there is a way to disable it on your AV software.

 

Due to the various builds of Windows 10, you might not find these settings in exactly the same place as described or shown.

 

More info:  https://support.microsoft.com/en-us/help/3204980/virtualization-applications-do-not-work-together-with-hyper-v-device-g

 

Update: I’ve added a new post here:

https://smudj.wordpress.com/2023/10/02/why-is-there-a-hypervisor-enabled/

Another culprit that uses a hypervisor is Core Isolation.  Check the link above for more details, but if you’ve enabled Core Isolation, then you’ve got a hypervisor running.

To disable: Settings>Privacy & Security>Windows security>Device Security>Core Isolation

Slide to OFF.

 

VirtualBox 6.0.4 Released

VirtualBox 6.0.4 (released January 28 2019)

This is a maintenance release. The following items were fixed and/or added:

• Virtualization core: support Shanghai/Zhaoxin CPUs.
• User interface: handle command line arguments to VirtualBox correctly (bugs #18206 and #18197)
• User interface: improvements to machine manager window, virtual optical disk creator, storage selector window and log viewer window
• User interface: various small fixes and improvements
• Audio: implemented time scheduling for the AC’97 device emulation to keep audio and video in sync
• Graphics: basic support for VMSVGA graphics device in virtual machines using EFI
• Network: fix occasional NATNet crashes (bug #13899)
• Network: worked around problems in certain PCnet drivers on old operating systems
• Serial: fixed connecting to pseudo terminals on POSIX hosts (6.0.0 regression; bug #18319)
• Linux hosts and guests: fix for building kernel modules against Linux 5.0. Thank you Kyle Laker

https://www.virtualbox.org/wiki/Changelog

Setting up an All-In-One Windows AD Test Environment (VirtualBox Edition)

Build a basic all-in-one lab in VirtualBox. This how-to shows you how to build a virtual Windows Active Directory environment isolated from your home or work network.  See my follow-up post using VMware Workstation here: https://smudj.wordpress.com/2019/01/23/setting-up-an-all-in-one-windows-ad-test-environment-vmware-workstation-edition/

Note: I’m no AD expert, there are better, worse, and different ways to do this and you’re not required to use VirtualBox.

Requirements:
16GB RAM minimum
SSD or multiple HDDs
Quad-core or better CPU with hardware virtualization enabled

 

1. Download the necessary software. Download the ISOs for the OSes you’ll be installing. For this example, I’ll be using IPFire and MSDN versions of Windows Server 2012R2 and Windows 10 Pro.
   1. VirtualBox: https://www.virtualbox.org/wiki/Downloads
   2. Windows OS Evaluation: https://www.microsoft.com/en-us/evalcenter/
   3. IPFire: https://www.ipfire.org/download/ipfire-2.21-core124
2. Create your IPFire router VM
   1. Click New, enter the name of your router, ie “IPFire”
   2. Change the OS to Linux, Ubuntu 64bit is fine as the version. Click Next.
   3. Enter 512MB for memory. Click Next.
   4. Click Create for a new virtual HDD and select VDI. Click Next.
   5. Select Dynamically allocated and click Next.
   6. Change the location here if necessary. The 10GB default is large enough, click Create.
   7. Once created, click Settings and then click Network. We need to modify the networking options.
      1. Adapter 1 should be set to NAT or Bridged.
      2. Adapter 2 needs to be enabled and set to Internal Network. **Make note of the MAC address for adapter 2. You can find it by expanding the Advanced tab.** 
      3. Click OK.
      4. 

 

3. Mount the IPFire ISO and install
   1. Click Settings on the IPFire VM. Click Storage.
   2. Click “Empty” next to the CD icon. Click the CD icon next to the far right to mount the ISO.
   3. Select “choose a virtual optical disk file” and browse to the ISO’s location.
   4. Select to mount. Click Ok to close the window.
   5. Power on the VM.
   6. Follow the IPFire prompts. Press enter to select, tab to move between selections, and the space bar to select check boxes.
   7. All defaults can be used.
   8. 
4. Configure IPFire
   1. Select the keyboard mapping. I’m using “us.” Press Enter to accept.
   2. Set your timezone. By pressing the first letter of your timezone, you can jump to that section. Select the correct timezone via the arrow keys and press Enter to accept.
   3. Enter a host name, the default is fine for our lab. Press Enter twice.
   4. The default domain is fine for our lab, press Enter twice to continue.
   5. Enter the root password and press Enter each time and once more to continue.
   6. Do the same for the admin password. Password can be the same for both for our lab purposes.–Network Configuration–
      1. Press Enter for “network configuration type”
      2. Select “Green + Red” and press Enter
      3. Arrow down to “drivers and card assignments.” and press Enter.
      4. Green: This is our internal network. Press Enter to select. Compare the MAC and select the correct interface. Press Enter to select the Interface.
      5. Red: This is our internet facing network, NAT or Bridged. Select RED, press Enter, and press Enter again to select the remaining interface.
      6. Tab over to done and press Enter.–Address Settings–
         Press Enter to select.
         GREEN:
         1. Select GREEN and press Enter.
         2. This is a new private, virtual network for our lab. Select a different IP subnet than your host network to avoid confusion.
         3. The IP warning can be ignored as we are not logged in remotely. In this example, the subnet is 192.168.211.1/24. Since this will be the gateway, we can use 192.168.211.1. The subnet mask does not need to change.
         4. Press Enter until you return to the GREEN/RED menu.
         RED:
         1. Select RED and press Enter.
         2. Select DHCP. This interface will get the IP from the VBox NAT or your physical network’s DHCP server. You can modify the hostname here if necessary.
         3. Tab to Done and press Enter.
         –DNS and Gateway settings–
         1. DNS and Gateway settings are only needed if using a static IP. Since we are using DHCP, there is nothing to change here. Tab to Done and press Enter.–DHCP Configuration–
         We will be using Windows DHCP instead of IPFire’s. Tab to OK and press enter without enabling DHCP. Press Enter to close setup.
5. Create Windows Server 2012 R2 VM
   1. From the VBox main men, click New.
   2. Enter a name, ex: “WS2012R2”, select the appropriate type (Windows 2012) and version (64-bit). Click Next.
   3. Set RAM to 4096MB. If you have more than 16GB of RAM, you can increase to 6 or 8GB, if needed. Click Next.
   4. Create a new virtual hard disk, click Create.
   5. Select VDI and click Next.
   6. Select Dynamically allocated, and click Next.
   7. Enter 80GB and click Create.
   8. Click Settings, then click Network.
   9. Select Internal Network.
   10. Select Storage. Click the CD under storage devices, then click the CD icon to the left of Optical Drive.
   11. Select Choose virtual optical disk file. Browse and select your Windows Server ISO.
   12. Click OK.
6. Install Windows Server 2012
   1. Install Windows as you normally would.
7. Configure Windows Server and Domain
   1. Enter the IP information. The IP needs to be on the same subnet as configured for the GREEN network. EX: 192.168.211.200, GW: 192.168.211.1, DNS: 127.0.0.1 since we’ll be creating a domain controller with DNS and DHCP services.
   2. You should be able to ping an IP address, but not a DNS name.
   3. Change the name of your server and reboot.Start the Add Roles and Feature Wizard
      1. Add the following roles:
      –Active Directory Domain Services
      –DHCP Services
      –DNS Services
      2. Follow the wizard’s steps.
      3. Promote: Add a new forest.
      4. Enter your domain name and follow the wizard.  –you will get a warning about DNS, this will be resolved later.
8. Configure DNS and DHCP

DNS.  We need to add a forwarder for our DNS settings.

1. From Administrative Tools, open DNS
2. Right-click on your server and click Properties.
3. Click the Forwarders tab
4. Click Edit, and add your external DNS servers like 4.2.2.1, 4.2.2.2, 8.8.8.8, and 8.8.4.4.

DHCP
1. Double-click DHCP from Administrative Tools
2. Expand IPv4 and right-click, click New Scope from the menu.
3. Enter an IP range, ex: 192.168.211.50 to 192.168.211.100
4. The remaining settings can be default for now.
5. When asked to configure scop options, verify “Yes” and click Next.
6. Router/Default gateway will be the IP we used to configure the GREEN NIC, ex: 192.168.211.1
7. Domain name and DNS should be pre-configured. You should see the server’s IP in IP address box, ex: 192.168.211.200
8. WINS does not need to be configured at this time.
9.When prompted to activate scope, verify “Yes” and click Next.
10. Click Finish to complete the wizard.

Right-click on the server’s name under DHCP, and click Authorize from the menu. Refresh and IPv4 should have a green circle with a white check mark.

9. Managing IPFire via web interface

You can access IPFire’s management console via a web browser.
Enter https://ipfire_ip-address:444, ex: https://192.168.211.1:444
Use “admin” and the password entered during step 4.

Note: You will get a certificate error when accessing the IPFire management page.

9. Adding Client VMs.

Nothing special here.  Install Windows/Linux as usual.  Make sure to select Internal Network for the VM’s network

10. Completion!

Here’s the money shot:
-VirtualBox
-IPFire VM
-WS2012R2 VM – domain controller for sw.net, DHCP and DNS roles
-Win10 VM – joined to sw.net, displaying IPFire’s web management page and network settings.

VirtualBox 6.0.2 Released

https://www.virtualbox.org/wiki/Downloads

This is a maintenance release. The following items were fixed and/or added:

• User interface: fixed creation of desktop shortcuts for starting virtual machines (bug #18207)
• User interface: allow the first run window to selecting host drives (bug #18230)
• User interface: fixed attaching empty host optical drives (bug #18223)
• User interface: implemented a new virtual optical disk creation window
• USB: modified Linux backends to reset USB devices (previously, most guest attempts to reset USB devices were ignored)
• PCnet: fixed a regression which caused some PCnet PCI guest drivers to not detect the emulated hardware (bug #18286)
• Linux hosts: fixed conflict between Debian and Oracle build desktop files (bug #18264)
• Linux and MacOS hosts: VirtualBoxVM command not accessible (bug #18257)
• Windows guests: multiple monitor fixes with VBoxSVGA graphics
• Windows guests: black screen with VBoxSVGA graphics when 3D is disabled (bug #18205)
• Linux guests: fixed building drivers on SLES 12.4 (bug #18213)
• Linux guests: fixed building shared folder driver with older kernels (bug #18238)
• OS/2 shared folders: fixed write regression introduced in 6.0.0 GA

VirtualBox 6.0 Release

https://www.virtualbox.org/wiki/Downloads

This is a major update. The following major new features were added:

• Implemented support for exporting a virtual machine to Oracle Cloud Infrastructure
• User interface: greatly improved HiDPI and scaling support, including better detection and per-machine configuration
• Major rework of user interface with simpler and more powerful application and virtual machine set-up
• User interface: a new file manager enabling user to control the guest file system and copy files between host and guest.
• Graphics: major update of 3D graphics support for Windows guests, and VMSVGA 3D graphics device emulation on Linux and Solaris guests
• Added support for surround speaker setups (as used by Windows 10 Build 1809)
• Added utility vboximg-mount on Apple hosts to access the content of guest disks on the host
• Added support for using Hyper-V as the fallback execution core on Windows host, to avoid inability to run VMs at the price of reduced performance In addition, the following items were fixed and/or added:
• Execution core: fixed single-stepping in certain circumstances (bug #17316)
• User interface: video and audio recording can now be separately enabled
• Audio/Video recording fixes and improvements
• Audio: better support for attaching and detaching remote desktop connections
• Serial port emulation fixes
• Serial ports: allow changing the serial port attachment while a machine is running (bug #6115)
• Networking: Added a workaround for older guests which do not enable bus mastering for the virtio PCI device
• Networking: fixed wrong RCODE from DNS AAAA query with –natdnshostresolver1 (bug #18171)
• iSCSI: In cases where there is no ambiguity, the LUN of an iSCSI target is automatically determined, for targets with non-zero LUNs
• Transparently resize disk images when merging if possible
• VBoxManage: support for DHCP options
• Fixed VNC/RDP (bug #18153)
• Guest Control: various new interfaces and features (see SDK documentation)
• Linux hosts: support Linux 4.20 (thank you Larry Finger)
• Solaris: installer fixes
• Shared folders: performance improvements
• Guest Additions: improved shared folder auto-mounting
• Windows Guest Additions: fix incorrect tablet co-ordinate handling with recent Windows 10 builds
• Linux Additions: fix for building vboxvideo on EL 7.6 standard kernel, contributed by Robert Conde (bug #18093)
• Linux guests: support Linux 4.20 (thank you Larry Finger)
• Linux guests: support VMSVGA in the Linux and X11 Additions
• MacOS Guest Additions: initial support
• OS/2 Guest Additions: initial shared folder support
• BIOS fixes
• ACPI: Up to four custom ACPI tables can now be configured for a VM

VirtualBox 5.1.16 Maintenance Release

Download here: https://www.virtualbox.org/wiki/Downloads

This is a maintenance release.

The following items were fixed and/or added: Changelog https://www.virtualbox.org/wiki/Changelog

• VMM: don’t access the MSR_IA32_SMM_MONITOR_CTL MSR if dual-monitor treatment is not available (KVM workaround, bug #14965)
• VMM: another fix for handling certain MSRs on ancient CPUs without VT-x support for MSR bitmaps
• VMM: fixed VERR_SSM_LOAD_CPUID_MISMATCH errors when restoring a saved state with SMP guests on hosts without the CPUID/HTT bit set (bug #16428)
• VMM: fixed a bug in call gate emulation
• VMM: FWAIT instruction fix
• VMM: fixed a sporadic guest hang under certain conditions
• GUI: hide the mini-toolbar from the taskbar and the pager on certain X11 hosts
• GUI: better error handling on the global settings / network / host-only / DHCP server settings
• GUI: fixes for full-screen with multiple screens
• Host-only Network: fixed host-only adapter creation issue preventing VirtualBox installation on Windows 10 hosts (bug #16379)
• NAT network: fixed two potential crashes in the DHCP server
• ICH9: fixed incorrect initialization of the primary bus for PCI bridges (5.1.14 regression)
• Storage: LsiLogic fix for Windows 10
• USB: fixed not being able to attach certain USB devices having invalid characters in the device strings (5.0.18 regression; bug #15956)
• USB: several fixes for the USB/IP support (bug #16462)
• VBoxSVC: fixed another crash during shutdown under rare circumstances
• VBoxSVC: fixed a stack overflow on (Windows debug builds only; bug #16409)
• OVF: when importing an appliance handle more than 10 network adapters if the OVA was created by VirtualBox (bug #16401)
• OVF: fixes for exporting and importing appliances with many disks (bug #16402)
• VBoxManage: fixed regression with modifyhd –resize (bug #16311)
• rdesktop-vrdp: source code tarball fixes
• Linux Installers: do not rebuild kernel modules unnecessarily (bug #16408)
• Linux hosts: added an action for opening the VM manager window to the .desktop file
• Linux hosts / guests: Linux 4.11 compile fixes (bug #16506)
• Linux Additions: added vboxsf FS modules alias (bug #16404)
• Linux Additions: fix for the shared folders kernel module to compile on Linux 4.10
• Linux Additions: properly install the Linux kernel module override rule on distributions without /etc/depmod.d
• Windows Additions: fixed a crash with recent Windows 10 builds if 3D is disabled (bug #15973)

VirtualBox 5.1.6 Available

VirtualBox 5.1.6 (released 2016-09-12)

This is a maintenance release. The following items were fixed and/or added:

• GUI: fixed issue with opening ‘.vbox’ files and it’s aliases
• GUI: keyboard grabbing fixes (bugs #15771 and #15745)
• GUI: fix for passing through Ctrl + mouse-click (Mac OS X hosts only; bug #15714)
• GUI: fixed automatic deletion of extension pack files (bugs #11352 and #14742)
• USB: fixed showing unknown device instead of the manufacturer or product description under certain circumstances (5.1.0 regression; bug #15764)
• XHCI: another fix for a hanging guest under certain conditions as result of the fix for bug #15747, this time for Windows 7 guests
• Serial: fixed high CPU usage with certain USB to serial converters on Linux hosts (bug #7796)
• Storage: fixed attaching stream optimized VMDK images (bug #14764)
• Storage: reject image variants which are unsupported by the backend (bug #7227)
• Storage: fixed loading saved states created with VirtualBox 5.0.10 and older when using a SCSI controller (bug #15865)
• Storage: fixed broken NVMe emulation if the host I/O cache setting is enabled
• Storage: fixed using multiple NVMe controllers if ICH9 is used
• NVMe: fixed a crash during reset which could happen under certain circumstances
• Audio: fixed microphone input (5.1.2 regression; bugs #14386 and #15802)
• Audio: fixed crashes under certain conditions (5.1.0 regression; bug #15887 and others)
• Audio: fixed recording with the ALSA backend (5.1 regression)
• Audio: fixed stream access mode with OSS backend (5.1 regression, thanks to Jung-uk Kim)
• E1000: do also return masked bits when reading the ICR register, this fixes booting from iPXE (5.1.2 regression; bug #15846)
• BIOS: fixed 4bpp scanline calculation (bug #15787)
• API: relax the check for the version attribute in OVF/OVA appliances (bug #15856)
• Windows hosts: fixed crashes when terminating the VM selector or other VBox COM clients (bug #15726 and others)
• Linux Installer: fixed path to the documentation in .rpm packages (5.1.0 regression)
• Linux Installer: fixed the vboxdrv.sh script to prevent an SELinux complaint (bug #15816)
• Linux hosts: don’t use 32-bit legacy capabilities
• Linux Additions: Linux 4.8 fix for the kernel display driver (bugs #15890 and #15896)
• Linux Additions: don’t load the kernel modules provided by the Linux distribution but load the kernel modules from the official Guest Additions package instead (bug #15324)
• Linux Additions: fix dynamic resizing problems in recent Linux guests (bug #15875)
• User Manual: fixed error in the VBoxManage chapter for the getextradata enumerate example (bug #15862)

VirtualBox 5.1.2 released today

This a maintenance release.

VirtualBox 5.1.2 (released 2016-07-21)  Download here: https://www.virtualbox.org/wiki/Downloads

This is a maintenance release. The following items were fixed and/or added:

• VMM: several fixes
• GUI: fixed screenshot if the VM is started in separate mode
• GUI: fixed issue with double-click/opening registered file types (.vbox and .vbox-extpack) on Mac OS X (bug #15648)
• GUI: fixed a bug which made it impossible close some error/warning messages using the close button
• GUI: weakened the control over the VM window behavior allowing to resize it across multiple screens and to use in Snap Assist techniques
• GUI: jump to the second tab of the session information window (5.1.0 regression)
• GUI: fix for Alt-Tab
• Storage: fixed creating fixed size VHD images (bug #15601)
• Storage: fixed a hang during power off if the VM was suspended before and a NVMe controller is configured
• USB: fixed a crash under certain conditions
• Audio: make AC’97 volume control work again (5.1.0 regression; bug #15598)
• Audio: fixed rare VM hangs when using AC’97 emulation
• Audio: SB16 fixes
• EFI: fixed access to devices attached to SATA port 2 and higher (bug #15607)
• OVA: fix for checking certain signatures
• OVA: fixed MAC address generation for appliances created by VirtualBox (5.1.0 regression; bug #15623)
• API: fixed audio settings handling for older config files (bug #15626)
• API: fixed truncation of USB product/vendor IDs on Linux hosts (5.1.0 regression; bug #15644)
• API: fixed VRDP with authentication (bug #15653)
• API: don’t crash if there is no graphics controller configured (bug #15628)
• Linux hosts: fixed EL5 builds (bug #15634)
• non-Windows hosts: fixed a crash during shutdown under rare circumstances (bug #15568)
• Linux Additions: fixed SELinux issue which prevented certain Linux guests to work in 3D mode (bug #15574)
• User Manual: updates

VirtualBox 5.1 Released

VirtualBox 5.1 has been released. This is a major update.  Download here: https://www.virtualbox.org/wiki/Downloads

VirtualBox 5.1 (released 2016-07-12)

This is a major update. The following major new features were added:

• VMM: new APIC and I/O APIC implementations that result in significantly improved performance in certain situations (for example with networking, bug #15295)
• VMM: added support for Hyper-V paravirtualized debugging of Windows guests
• VMM: emulate even more MMIO and shadow pagetable exits without going back to user mode
• GUI: overall migration to Qt5 (bug #11775)
• GUI: passive API event listener improving the VM GUI performance and response time
• Audio: added HDA (High Definition Audio) support for newer Linux guests
• Audio: added on-demand timers which should improve the overall performance and reduce the CPU consumption
• Audio: more fine-grained volume control for the AC’97 emulation, which now also takes the master volume control into account
• better support for Python 3

In addition, the following items were fixed and/or added:

• VMM: activate the x2APIC by default for Linux guests
• VMM: many more fixes
• GUI: the Detach UI action is now a part of the VM Machine menu
• GUI: reworked session information window
• GUI: the new VM wizard now allows to choose the VM location for the VM which is being created
• GUI: fixed location of touch events in unscaled HiDPI mode (bugs #14366, #14367)
• GUI: various bugfixes and internal cleanup
• Storage: use fallocate() or similar if present to speed up creating fixed-sized disk images (bug #5967)
• Storage: implemented NVMHCI-compatible storage controller
• Audio: various bugfixes and infrastructure improvements
• E1000: implemented interrupt throttling for performance improvements
• EFI: many improvements, for example allow to boot from USB
• OVF: improved handling of signed manifests
• API: Windows XP guests and Windows 2003 server guests now default to the E1000 T Server network card
• VBoxSVC: fixed several memory leaks when handling .dmg images
• Installers: ship VBoxBugReport
• Windows hosts: reworked COM proxy (e.g. bug #8298)
• Linux installers: no longer rely on DKMS for module rebuilding
• Linux Additions: fix a problem when updating the initramfs after the guest modules are compiled (bug #15579)
• Linux Additions: try to fix a problem where the OpenGL libraries where loaded by the X server when we only support X clients (bug #15574)

VirtualBox 5.0.16 Maintenance Release

A little late, released March 4, a maintenance release. Download.

Change log:

The following items were fixed and/or added:

• VMM: fixed a problem which could lead to a wrong guest behavior on AMD CPUs (tickets #14831 and #15186)
• GUI: don’t try to synchronize the HID LEDs if the VM window is not active or if it’s minimized (Windows / Mac OS X hosts only; bug #14302)
• GUI: prevent a crash during startup under rare conditions
• GUI: sub-menu option to disable the guest-OS type overlay in the application dock icon on Mac OS X
• GUI: position off-screen windows to be fully visible again on relaunch
• GUI: hide the VT-x/AMD-V checkbox if raw-mode is not supported (usually Mac OS X hosts; bug #15178)
• PC speaker passthrough: new experimental feature, available on Linux host only
• Audio: several fixes for Mac OS X hosts + guests
• Audio: properly handle default audio device changes (Windows hosts)
• USB: serveral fixes for the xHCI controller (e.g. for webcam passthrough)
• BIOS: fixed int15/AH=83/AL=00 function (4.2.0 regression)
• iPXE: enable the HTTP download protocol on non-Linux hosts (bug #13628)
• Shared folders: fixed a failure to load the saved state under certain circumstances (bug #6314)
• Guest Control: added support for (cached) Active Directory authentication in case the domain controller is not reachable (anymore)
• Serial ports: raised the number of serial ports per VM from 2 to 4 (bug #9109)
• Serial ports: fix for the TCP/IP backend (Windows hosts only; bug #15188)
• SDK: make the Python webservice API binding work again (5.0 regression)
• Seamless mode: fixed a crash under certain circumstances (bug #15106)
• Linux hosts: fixed the /sbin/rcvboxdrv script as well as the missing shebang in two scripts (bugs #15055 and #15057)
• Linux hosts: properly uninstall Python files installed by the .run installer
• Windows hosts: hardening fix required for recent Windows insider builds (bug #14052)
• Windows hosts: fixed Python installation path (bug #13131)
• Windows hosts: support MTU larger than 2 KB with bridged networking (bug #15140)
• Windows hosts / guests: properly sign binaries using a sha-256 certificate (bug #15054)
• Windows Additions: fixed guest property enumeration of logged-in users
• Windows Additions: fixed sporadical failure of the graphics driver in Windows 10 guests (bug #14409)
• Windows Additions: under rare circumstances no mouse movement events were delivered to the guest