Display Driver Uninstaller — completely remove your graphics drivers
Editor’s Rating
User Rating
6
Popularity
XP/Vista/7/8/10/11
Portable
View all screenshots
completely remove your graphics drivers
Display Driver Uninstaller (DDU) makes it easy to completely remove AMD, NVIDIA and Intel graphics card drivers and packages from your system, without leaving any leftovers behind.
The program will automatically detect your current GPU and allows you to remove the drivers, registry keys and related files with the click of a button. It will also prevent Windows from automatically reinstalling the drivers when your restart your computer, leaving you with a generic graphics driver until you install your new drivers.
DDU is most useful if the standard Windows removal procedure fails or if you want to make sure the all leftovers of the previous drivers are completely removed (e.g. upgrading or downgrading).
For best results, it is recommended to run DDU is Safe Mode
Copyright Snapfiles.com
Download Display Driver Uninstaller
Product Details
| Publisher | WagnardMobile
|
Price | Free |
| Version | 18. 0.6.2
|
Last updated | Apr 03, 2023 |
| File Size |
1.12 Mb |
Requirements | None |
|
|
|||
Chocolatey Software | Display Driver Uninstaller 18.0.6.2023012901
Requires Puppet Chocolatey Provider module. See docs at https://forge.
puppet.com/puppetlabs/chocolatey.
## 1. REQUIREMENTS ## ### Here are the requirements necessary to ensure this is successful. ### a. Internal/Private Cloud Repository Set Up ### #### You'll need an internal/private cloud repository you can use. These are #### generally really quick to set up and there are quite a few options. #### Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they #### are repository servers and will give you the ability to manage multiple #### repositories and types from one server installation. ### b. Download Chocolatey Package and Put on Internal Repository ### #### You need to have downloaded the Chocolatey package as well. #### Please see https://chocolatey.org/install#organization ### c. Other Requirements ### #### i. Requires puppetlabs/chocolatey module #### See https://forge.puppet.com/puppetlabs/chocolatey ## 2. TOP LEVEL VARIABLES ## ### a.Your internal repository url (the main one). ### #### Should be similar to what you see when you browse #### to https://community.chocolatey.org/api/v2/ $_repository_url = 'INTERNAL REPO URL' ### b. Chocolatey nupkg download url ### #### This url should result in an immediate download when you navigate to it in #### a web browser $_choco_download_url = 'INTERNAL REPO URL/package/chocolatey.2.0.0.nupkg' ### c. Chocolatey Central Management (CCM) ### #### If using CCM to manage Chocolatey, add the following: #### i. Endpoint URL for CCM # $_chocolatey_central_management_url = 'https://chocolatey-central-management:24020/ChocolateyManagementService' #### ii. If using a Client Salt, add it here # $_chocolatey_central_management_client_salt = "clientsalt" #### iii. If using a Service Salt, add it here # $_chocolatey_central_management_service_salt = 'servicesalt' ## 3. ENSURE CHOCOLATEY IS INSTALLED ## ### Ensure Chocolatey is installed from your internal repository ### Note: `chocolatey_download_url is completely different than normal ### source locations.
This is directly to the bare download url for the ### chocolatey.nupkg, similar to what you see when you browse to ### https://community.chocolatey.org/api/v2/package/chocolatey class {'chocolatey': chocolatey_download_url => $_choco_download_url, use_7zip => false, } ## 4. CONFIGURE CHOCOLATEY BASELINE ## ### a. FIPS Feature ### #### If you need FIPS compliance - make this the first thing you configure #### before you do any additional configuration or package installations #chocolateyfeature {'useFipsCompliantChecksums': # ensure => enabled, #} ### b. Apply Recommended Configuration ### #### Move cache location so Chocolatey is very deterministic about #### cleaning up temporary data and the location is secured to admins chocolateyconfig {'cacheLocation': value => 'C:\ProgramData\chocolatey\cache', } #### Increase timeout to at least 4 hours chocolateyconfig {'commandExecutionTimeoutSeconds': value => '14400', } #### Turn off download progress when running choco through integrations chocolateyfeature {'showDownloadProgress': ensure => disabled, } ### c.
Sources ### #### Remove the default community package repository source chocolateysource {'chocolatey': ensure => absent, location => 'https://community.chocolatey.org/api/v2/', } #### Add internal default sources #### You could have multiple sources here, so we will provide an example #### of one using the remote repo variable here #### NOTE: This EXAMPLE requires changes chocolateysource {'internal_chocolatey': ensure => present, location => $_repository_url, priority => 1, username => 'optional', password => 'optional,not ensured', bypass_proxy => true, admin_only => false, allow_self_service => false, } ### b. Keep Chocolatey Up To Date ### #### Keep chocolatey up to date based on your internal source #### You control the upgrades based on when you push an updated version #### to your internal repository.
#### Note the source here is to the OData feed, similar to what you see #### when you browse to https://community.chocolatey.org/api/v2/ package {'chocolatey': ensure => latest, provider => chocolatey, source => $_repository_url, } ## 5. ENSURE CHOCOLATEY FOR BUSINESS ## ### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down. ### a. Ensure The License File Is Installed ### #### Create a license package using script from https://docs.chocolatey.org/en-us/guides/organizations/organizational-deployment-guide#exercise-4-create-a-package-for-the-license # TODO: Add resource for installing/ensuring the chocolatey-license package package {'chocolatey-license': ensure => latest, provider => chocolatey, source => $_repository_url, } ### b. Disable The Licensed Source ### #### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package. ## Disabled sources still need all other attributes until ## https://tickets.puppetlabs.com/browse/MODULES-4449 is resolved. ## Password is necessary with user, but not ensurable, so it should not ## matter what it is set to here. If you ever do get into trouble here, ## the password is your license GUID. chocolateysource {'chocolatey.licensed': ensure => disabled, priority => '10', user => 'customer', password => '1234', require => Package['chocolatey-license'], } ### c. Ensure Chocolatey Licensed Extension ### #### You will have downloaded the licensed extension to your internal repository #### as you have disabled the licensed repository in step 5b. #### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension) package {'chocolatey.extension': ensure => latest, provider => chocolatey, source => $_repository_url, require => Package['chocolatey-license'], } #### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them.
You may want to visit the feature pages to see what you might want to also enable: #### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder #### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer #### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization #### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer #### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit #### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle #### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn #### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding #### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.
org/en-us/features/paid/self-service-anywhere #### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management #### - Other - https://docs.chocolatey.org/en-us/features/paid/ ### d. Ensure Self-Service Anywhere ### #### If you have desktop clients where users are not administrators, you may #### to take advantage of deploying and configuring Self-Service anywhere chocolateyfeature {'showNonElevatedWarnings': ensure => disabled, } chocolateyfeature {'useBackgroundService': ensure => enabled, } chocolateyfeature {'useBackgroundServiceWithNonAdministratorsOnly': ensure => enabled, } chocolateyfeature {'allowBackgroundServiceUninstallsFromUserInstallsOnly': ensure => enabled, } chocolateyconfig {'backgroundServiceAllowedCommands': value => 'install,upgrade,uninstall', } ### e.
Ensure Chocolatey Central Management ### #### If you want to manage and report on endpoints, you can set up and configure ### Central Management. There are multiple portions to manage, so you'll see ### a section on agents here along with notes on how to configure the server ### side components. if $_chocolatey_central_management_url { package {'chocolatey-agent': ensure => latest, provider => chocolatey, source => $_repository_url, require => Package['chocolatey-license'], } chocolateyconfig {'CentralManagementServiceUrl': value => $_chocolatey_central_management_url, } if $_chocolatey_central_management_client_salt { chocolateyconfig {'centralManagementClientCommunicationSaltAdditivePassword': value => $_chocolatey_central_management_client_salt, } } if $_chocolatey_central_management_service_salt { chocolateyconfig {'centralManagementClientCommunicationSaltAdditivePassword': value => $_chocolatey_central_management_client_salt, } } chocolateyfeature {'useChocolateyCentralManagement': ensure => enabled, require => Package['chocolatey-agent'], } chocolateyfeature {'useChocolateyCentralManagementDeployments': ensure => enabled, require => Package['chocolatey-agent'], } }
Use Device Manager to remove devices and driver packages — Windows drivers
E-mail address
- Article
This page describes how to remove a device or driver package on Windows 10 and Windows 11.
We recommend that you physically disconnect the device from the system before removing the device. If a device is removed before it is disabled, the operating system may re-detect the device and reinstall drivers for it in the period between removal and disabling the device.
First, open Settings (this can be done using the Windows+I keyboard shortcut) and enter the uninstall command. Select Add or Remove Programs . If the device or driver package you want to remove appears in the program list, select Remove.
If the device or driver package is not listed, you must use Device Manager to uninstall the device. if this device is the only device using the driver package, then the driver package can also be uninstalled using Device Manager. To launch Device Manager, click the start button, type device manager, and then press enter.
Then do the following:
- Select the View menu and enable Show hidden devices .
- Expand the node representing the type of device you want to remove, right-click the device entry you want to remove, and select Remove .
- If you want to remove the driver package in addition to removing the device in dialog box Confirm device removal, select option uninstall the driver software for this device . When everything is ready for the operation, press the button OK .
You may also need to restart your computer.
For more information about uninstalling driver packages and driver packages, see How to uninstall devices and driver packages.
How to roll back a driver in Windows 10
Sometimes after installing new versions of hardware drivers — video card, system devices, sound card, you may encounter the fact that it starts to work incorrectly. In this case, one of the first things to try is to roll back the installed driver.
This guide is about the general way to roll back device drivers in Windows 10, as well as some additional information on how to roll back the NVIDIA GeForce driver to a previous version, as This topic is often asked the most questions.
You may also find it helpful: How to disable driver updates in Windows 10.
Roll back a device driver using Device Manager
Windows 10, like previous versions of the OS, provides a built-in method to roll back device drivers to their previous versions if necessary. You can perform the necessary actions in the device manager:
- Open the device manager: to do this, you can right-click on the «Start» button and select the appropriate menu item, or press the Win + R keys, type devmgmt.msc and press Enter.
- In the device manager, find the device you need, right-click on it and select «Properties».
- Click the Driver tab and check if the Roll Back button is enabled. If yes, click it.
- The latest version of Windows 10 may ask you why you want to roll back a driver. After answering, click «Yes».
- Immediately after this, the device driver will be uninstalled, and the previous version of the driver (and in some cases the generic system driver) will be installed instead.
Sometimes, after the described actions, it is also necessary to restart the computer so that the old driver is used as the device in use (a notification will appear about this).
Installing a previous version of a driver manually
Sometimes, the Roll Back button in the driver properties is not active. In this case, you can do something slightly different:
- Find and download the driver of the version you need, ideally from the official website of the manufacturer of the motherboard, laptop or equipment.
- Select the device in the device manager, right-click on it and select «Uninstall device». In the next window, check the box «Delete the driver software for this device».
- After the device is removed, run the previously downloaded installer for the required driver version and install it.
Some additional information about rolling back the NVIDIA GeForce driver
If you need to roll back the NVIDIA GeForce driver, and it is not possible to do this using Device Manager, I recommend that you keep in mind this path:
- Look in the C:\ProgramData\ folder NVIDIA Corporation\Downloader — in this location, in subfolders, you will most likely find installers for older versions of drivers and you will not have to download them from somewhere.
