Display Driver Uninstaller для Windows

Оценка:	1 2 3 4 5 3.87 /5 голосов — 195
Лицензия:	Бесплатная
Версия:	18.0.3.8 | Сообщить о новой версии
Обновлено:	29.03.2021
ОС:	Windows 10, 8.1, 8, 7, XP
Интерфейс:	Английский, Русский
Разработчик:	Wagnard
Категории:	Деинсталяторы — Программы для драйверов
Загрузок (сегодня/всего):	120 / 491 689 | Статистика
Размер:	1,29 Мб
СКАЧАТЬ

Display Driver Uninstaller — утилита для полного удаления драйверов видеокарт AMD, NVIDIA, INTEL из системы, включая ключи реестра, папки и файлы.

Приложение будет полезно, когда стандартными способами системы Windows удалить драйверы не удается, или же когда есть сомнения относительно тщательности очистки от остатков. Удаляет текущие и предыдущие видеодрайверы из диспетчера устройств и хранилища драйверов Windows. Используя DDU, вы можете решить многие распространенные проблемы, связанные с графическими драйверами. Установка драйверов после использования DDU подобна «чистой» установке.

Рекомендации по применению:

• Для надежности удаления и безопасности запускайте программу в безопасном режиме.
• Во время работы с программой отключите интернет. Это позволит избежать повторной установки драйверов без запроса службой Windows Update.
• Перед использованием DDU рекомендуется создать точку восстановления системы или резервную копию для предотвращения возможных нежелательных последствий.

Display Driver Uninstaller — бесплатная программа для удаления из системы драйверов видеокарт NVIDIA и AMD.

Revo Uninstaller — бесплатное приложение для корректной деинсталляции программ из операционной.

Uninstall Tool — компактная и удобная в эксплуатации утилита, позволяющая полноценно заменить.

Удобный в использовании иснструмент для полного и безопасного удаления ядра DirectX любой.

IObit Uninstaller — бесплатная утилита для корректной деинсталляции ненужных приложений.

AVG Remover — утилита для удаления антивируса AVG с компьютера. Удаляет установочные файлы, пользовательские файлы и чистит реестр.

Отзывы о программе Display Driver Uninstaller

Никита про Display Driver Uninstaller 18.0.2.2 [18-03-2020]

дима про Display Driver Uninstaller 18.0.1.9 [09-11-2019]

на 7х64 работает , а на хр не поддерживается , пишет что не является приложением win32 , запускал в безосном режиме по кнопочке F8
5 | 8 | Ответить

Артём про Display Driver Uninstaller 18.0.1.5 [22-06-2019]

Всем здорова после тогда как скачал прогу запустил пк перезагрузился и пароль поменялся что за проблема ?
9 | 56 | Ответить

Нурлан про Display Driver Uninstaller 18.0.1.5 [16-06-2019]

ВАСИЛИСК ПОМОГИ ПОЖАЛУЙСТА
Требует пароль, мой неверный, твой совет я не понял как делать
8 | 21 | Ответить

Флибустьян про Display Driver Uninstaller 17.0.8.6 [26-05-2018]

У меня виндовс хрюшка сервис пак 3
Удалил драйвер радеона влет! А driver sweeper не справился !
2 | 12 | Ответить

Microsoft Basic Display Driver

In Windows 8, The Microsoft Basic Display Driver (MSBDD) is the in-box display driver that replaces the XDDM VGA Save and VGA PnP drivers.

The key benefits of using MSBDD are as follows:

• 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.
• 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 supports Unified Extensible Firmware Interface (UEFI) Graphics Output Protocol (GOP).
• MSBDD works on both XDDM and WDDM hardware.

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. The primary purpose of this driver is to enable Windows to write to the display controller’s linear frame buffer.

MSBDD can use the video BIOS to manage modes and resolutions on a single monitor. On UEFI platforms, MSBDD inherits the linear frame buffer that is set during boot; in this case, no mode or resolution changes are possible. As shown in Figure 1 Scenarios supported by Microsoft Basic Display Driver, MSBDD is used in the following scenarios:

Server: Server configurations that lack WDDM-capable graphics hardware can use MSBDD.

Windows setup: In the early phases of Windows setup, just before the final boot, only the MSBDD is loaded.

For 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. The user upgrades to Windows 8 and uses MSBDD for the setup, installation, and to retrieve an IHV driver if one is available.

Driver installation, in the following cases:

• When a user is installing a new WDDM IHV driver, MSBDD is used during the transition (from the point when the old WDDM IHV driver is uninstalled to the point before the new IHV driver is installed).
• When a user encounters problems installing the latest WDDM IHV driver, the user or system can disable the current graphics driver and fallback to using MSBDD.

Driver upgrade: By using MSBDD, there is no need to go through a system reboot when upgrading to the IHV-recommended driver.

Safe mode: In this mode, only trusted drivers get loaded; this includes MSBDD.

Figure 1 Scenarios Supported by Microsoft Basic Display Driver

Getting Started with Windows Drivers

Starting at some point after Windows 10, version 2004, drivers that run on Windows will be classified as either Windows Drivers or Windows Desktop Drivers.

Windows Drivers will run on all Window 10 variants, including Windows 10X and Windows 10 Desktop editions. Windows Desktop Drivers will only run on Windows 10 Desktop editions.

The Windows Driver classification will extend and replace the current Universal Driver classification.

This page provides a preview of the upcoming requirements for Windows Drivers.

The distinction between Windows Drivers and Windows Desktop Drivers does not affect any driver being submitted and certified for Windows 10 Version 2004. Changes in certification and submission will happen at a later date.

Windows Drivers Requirements

When Windows Drivers become a certification option, the following requirements will apply:

• Compliant with DCH Design Principles.
• Follow the principles of Driver Package Isolation.
• Follow API Layering Requirements.
• Certified with Windows Hardware Compatibility Program Certification Process using the Hardware Lab Kit. Note that the Windows Hardware Compatibility Program Certification Process requirements apply to both KMDF and UMDF drivers.

Windows Drivers vs. Windows Desktop Drivers

The following table summarizes the distinctions above:

Feature	Windows Drivers	Windows Desktop Drivers
Run on Windows 10 Desktop	Yes	Yes
Run on Windows 10X	Yes	No
Must be certified with WHCP	Yes	No
WDK & HLK are primary vehicles for developing and certifying drivers	Yes	Yes
Adhere to stricter reliability and serviceability requirements (e.g. driver package isolation)	Yes	No

While it won’t be required for a driver running only on Windows 10 Desktop to meet the additional requirements for a Windows Driver, doing so will enhance driver serviceability and reliability, as well as preparing the driver for possible future certification on Windows 10X.

Display Driver Initialization

Display driver initialization is similar to graphics driver initialization, as described in Supporting Initialization and Termination Functions. This section provides initialization details that are specific to display drivers.

Video miniport and display driver initialization occur after the NT executive and the Win32 subsystem are loaded and initialized. The system loads the video miniport driver or drivers that are enabled in the registry, and then determines which video miniport driver and display driver pair to use. During this process, GDI opens all necessary display drivers, based on the information provided by Window Manager.

The basic display driver initialization procedure, in which the desktop is created, is shown in the following figure.

When GDI is called to create the first device context (DC) for the video hardware, GDI calls the display driver function DrvEnableDriver. Upon return, DrvEnableDriver provides GDI with a DRVENABLEDATA structure that holds both the driver’s graphics DDI version number and the entry points of all callable graphics DDI functions that are implemented by the driver (other than DrvEnableDriver).

GDI then calls the driver’s DrvEnablePDEV function to request a description of the driver’s physical device’s characteristics. In the call, GDI passes in a DEVMODEW structure, which identifies the mode that GDI wants to set. If GDI requests a mode that the display or underlying miniport driver does not support, then the display driver must fail this call.

The display driver represents a logical device controlled by GDI. As shown in the following figure, a single logical device can manage several physical devices, each characterized by type of hardware, logical address, and surfaces supported. The display driver allocates the memory to support the device it creates. A display driver may be called upon to manage more than one PDEV for the same physical device, although only one PDEV can be enabled at a time for a given physical device. Each PDEV is created in a separate GDI call to DrvEnablePDEV, and each call creates another PDEV that is used with a different surface.

Because a driver must support more than one PDEV, it should not use global variables.

GDI automatically enables DirectDraw after calling DrvEnableSurface. After DirectDraw is initialized, the driver can use DirectDraw’s heap manager to perform off-screen memory management. See DirectDraw and GDI for details.

The following figure illustrates logical versus physical devices.

When installation of the physical device is complete, GDI calls DrvCompletePDEV. This function provides the driver with a GDI-generated physical device handle to use when requesting GDI functions for the device.

In the final stage of initialization, a surface is created for the video hardware by a GDI call to DrvEnableSurface, which enables graphics output to the hardware. Depending on the device and the environment, the display driver enables a surface in one of two ways:

• The driver manages its own surface by calling the GDI function EngCreateDeviceSurface method is required for hardware that does not support a standard-format bitmap and is optional for hardware that does.
• GDI can manage the surface completely as an engine-managed surface if the hardware device has a surface organized as a standard-format bitmap. A driver can call EngModifySurface to convert the device-managed primary bitmap to one that is engine-managed. The driver can still hook any drawing operations.

Any existing GDI bitmap handle is a valid surface handle. A driver can call EngModifySurface to convert the device-managed primary bitmap to an engine-managed bitmap. If the surface is engine-managed, GDI can handle any or all drawing operations. If the surface is device-managed, at a minimum, the driver must handle DrvTextOut, DrvStrokePath, and DrvBitBlt.

GDI automatically enables DirectDraw after calling DrvEnableSurface. After DirectDraw is initialized, the driver can use DirectDraw’s heap manager to perform off-screen memory management. See DirectDraw and GDI for details.

A display driver must implement DrvNotify in order to receive notification events, particularly the DN_DRAWING_BEGIN event. GDI sends this event immediately before it begins drawing, so it can be used to determine when caches can be initialized.

See the Plug and Play section for more information about the boot process.

Update Display Drivers

A Display Driver is basically the software that enables communication between the operating system and the graphics architecture or the video graphics card and the display itself. Display Drivers are designed for wireless devices, handhelds, monitors, laptops, televisions, or automotive applications.

There are basically two types of Liquid Crystal Display (LCD) displays: the Super-twisted nematic (STN) display or Color STN (CSTN) and the Thin Film Transistor (TFT) Display. The STN or CSTN displays are primarily used with PDAs, Mobile phones, Game consoles, and word processors. TFT displays are primarily employed in LCD Television, laptops, handheld video games, PDAs, projection television, or navigation systems.

The STN is a monochrome passive LCD that requires less power and are less expensive than TFT LCD. This technology provides the informational screens of some of the mobile phone technology. CSTN is the color version of STN and uses red, blue, and green filters to display colors. It was originally developed by Sharp in the 1990s, but suffered slow response times and ghosting, so the technology was upgraded to active matrix displays. TFT LCD is one type of active matrix display that significantly improved image quality and addressability. New technology offer 100ms response times. High-Performance Addressing (HPA) is a newer passive matrix technology that offers even faster response times and contrast than CSTN. Samsung, Intel, AMD, and OKI semiconductor are all providers of the silicon solutions that power these devices. Each provider has a slightly different solution and requires a separate display driver to facilitate the communication between the device and the operating system.

Windows Display Driver Model (WDDM) is a new graphic driver for video cards drivers using Microsoft Windows versions. WDDM provides new functionality and better graphics performance than its predecessor Windows XP. Overall, it has a more reliable desktop experience, while supporting graphics and applications. Desktop Window Manager runs over Direct3D and has increased functionality due to WDDM. WDDM requires at least a Direct3D 9-capable video card, along with the display driver interfaces Direct3D 9Ex runtime to run legacy Direct3D applications.

Common Problems Associated with Display Drivers

1) Conflicts between two or more drivers caused by missing or busy resources

2) Missing drivers

3) Corrupted driver files

4) Poorly designed drivers that reduce a system’s stability and performance

4) Incompatibility with the operating system or hardware device

5) Problems in the Windows Registry

Troubleshooting Display Drivers

Display driver errors are typically very apparent to the user. The screen will go black during a video application, such as a highly intensive graphic video game. The video will stop momentarily and restart. The screen may turn from color to monochromatic or the screen will freeze.

With display drivers, it may sometimes be difficult to determine if the display driver is the problem or if the hardware is the problem. If the user experiences difficulty begin by reinstalling the existing display driver, upgrading to the most recent display driver, or revert back to a previous version. Also, check the system for incompatible display drivers.

With display drivers, typically, the user wants the most updated version to ensure maximum performance. However, ensure that the most recent version is compatible with the existing hardware. If the user has an older operating system or video graphics card, updating the display driver may exacerbate the problem. To run graphic-intensive programs, the user may have to upgrade the hardware along with the driver. However, always attempt to upgrade the display driver before a hardware replacement.

Update Display Drivers For Windows

Outdated or corrupt Display drivers can also cause problems. The drivers updater software program driver whiz, is fully compatible with Windows 10, Windows 8, Windows 7, Windows Vista, Windows XP. If problems persist please contact the support for further assistance.

Description	OS Compatibility
Driver Whiz	Windows 10, 8, 8.1, 7, Vista & XP	DOWNLOAD

Are You Looking For Any Other Driver? See popular device drivers listed below.

Update Drivers In Windows 10, 8, 7, Vista & XP

By clicking “Download Now”, I agree to Site Terms and Conditions and Privacy Policy.

Download Size: 7.2MB
Compatibility: Windows 10, 8, 7, Vista, XP
Requirements: 300 MHz Processor, 256 MB Ram, 22 MB HDD

Note: Individual drivers may be available on manufacturer websites at no charge. Driver Whiz is a driver update service that will scan your computer for suitable drivers and provide them in an easy, convenient method. Driver Whiz registration is $29.95 USD for 1-year subscription. Driver Whiz provides advanced scanning of your computer system. After a system scan has been performed all users will be provided the option to update out-of-date or missing drivers. Updating drivers is provided at a charge while scanning is provided at an unlimited basis.