The user upgrades to the current version of Windows and uses MSBDD for the setup, installation, and to retrieve an IHV driver if one is available.ĭriver installation, in the following cases: Windows setup: In the early phases of Windows setup, just before the final boot, only the MSBDD is loaded.įor example, a user has an older platform that is currently in working condition although it has no in-box graphics driver support for Windows 8 or later.

Server: Server configurations that lack WDDM-capable graphics hardware can use MSBDD. As shown in the figure below, MSBDD is used in the following scenarios:

On UEFI platforms, MSBDD inherits the linear frame buffer that is set during boot in this case, no mode or resolution changes are possible. MSBDD can use the video BIOS to manage modes and resolutions on a single monitor. MSBDD works on both XDDM and WDDM hardware.MSBDD supports Unified Extensible Firmware Interface (UEFI) Graphics Output Protocol (GOP).Server scenarios can benefit from the higher functionality (specifically, features like reboot-less updates, dynamic start and stop, and so on) that are provided by the WDDM driver model.MSBDD helps to enable a consistent end user and developer experience because it is compatible with DirectX APIs and technologies such as the Desktop Composition.The key benefits of using MSBDD are as follows: The primary purpose of this driver is to enable Windows to write to the display controller's linear frame buffer. MSBDD is the default in-box display driver that is loaded during setup, in safe mode, in the absence of an IHV graphics driver, or when the inbox installed graphics IHV driver is not working or is disabled. Starting in Windows 8, The Microsoft Basic Display Driver (MSBDD) is the in-box display driver that replaced the XDDM VGA Save and VGA PnP drivers.

Microsoft display adapter windows 10 d5