Having issues with drivers can be frustrating, especially when you can’t seem to completely uninstall a driver in Windows 11. This guide is to help you navigate the process of removing problematic drivers from your system, ensuring a fresh start. We’ll cover various methods, including using command lines and PowerShell, to help you completely remove any driver from your OS.
Also see: How to Uninstall Drivers in Windows 11
Page Contents
Why is it important to completely uninstall a driver in Windows 11?
Before we dive into the solutions, it’s essential to understand why completely uninstalling a driver is necessary. Often, when a driver is causing issues or has become outdated, a clean uninstall allows for a fresh installation, ensuring the new driver works seamlessly with your system. Partially uninstalling a driver can lead to conflicts, performance issues, or instability.
How to list all installed drivers with publisher names
Before proceeding with any of the following methods, it is crucial to identify the driver you want to uninstall. You can list all drivers in Windows 11 using the Command Prompt or PowerShell (requires administrative privileges).
Learn more: How to See What Drivers Are Installed in Windows 11
- Click on the Start icon or press the Windows key.
- Type “Command Prompt” in the search bar, right-click on it from the search results, and select “Run as administrator“. Click “Yes” if prompted by the UAC dialog box.
- Type the following command and hit Enter:
dism /online /get-drivers /format:table
Here’s an example of the output you can expect to see after running the command:
-------------- | --------------------- | ----- | --------------------- | ---------------------------- | ---------- | ---------------- Published Name | Original File Name | Inbox | Class Name | Provider Name | Date | Version -------------- | --------------------- | ----- | --------------------- | ---------------------------- | ---------- | ---------------- oem0.inf | oculus_vigembus.inf | No | System | Facebook, Inc. | 8/2/2017 | 1.5.8.0 oem1.inf | rzrbtldr.inf | No | USB | Razer Inc. | 8/12/2015 | 6.2.9200.16384 oem10.inf | ntprint.inf | No | Printer | Microsoft | 6/21/2006 | 10.0.22000.1098 oem11.inf | oculus119b.inf | No | Media | Oculus VR, LLC | 3/14/2016 | 10.0.1.54 oem12.inf | rzendpt.inf | No | HIDClass | Razer Inc | 10/26/2016 | 6.2.9200.16385 oem13.inf | rz0501audpt.inf | No | HIDClass | Razer Inc | 10/26/2016 | 6.2.9200.16385 oem14.inf | rz0506audpt.inf | No | HIDClass | Razer Inc | 10/26/2016 | 6.2.9200.16385 oem15.inf | netaapl64.inf | No | Net | Apple | 7/15/2013 | 1.8.5.1 oem17.inf | wintun.inf | No | Net | WireGuard LLC | 12/10/2019 | 0.8.0.0 oem18.inf | cmuac.inf | No | Media | C-MEDIA Inc. | 2/13/2015 | 8.1.12.26 oem19.inf | riftdisplay.inf | No | Monitor | Oculus VR, LLC | 9/17/2015 | 1.0.0.0 oem2.inf | usbaapl64.inf | No | USB | Apple, Inc. | 5/19/2017 | 6.0.9999.69 oem20.inf | rzuddmou.inf | No | Mouse | Razer Inc | 10/26/2016 | 6.2.9200.16385 oem21.inf | rzuddkb.inf | No | Keyboard | Razer Inc | 10/26/2016 | 6.2.9200.16385 oem22.inf | rzvmouse.inf | No | HIDClass | Razer | 10/26/2016 | 6.2.9200.16385 oem23.inf | rz002caudpt.inf | No | HIDClass | Razer Inc | 10/26/2016 | 6.2.9200.16385 oem24.inf | rzuddmouex.inf | No | Mouse | Razer Inc | 10/26/2016 | 6.2.9200.16385 oem25.inf | oemvista.inf | No | Net | TAP-Windows Provider V9 | 10/8/2020 | 9.24.6.601 oem27.inf | rtkfilter.inf | No | Bluetooth | Realtek Semiconductor Corp. | 4/1/2021 | 1.6.1015.3018 oem28.inf | rzjstk.inf | No | HIDClass | Razer | 10/26/2016 | 6.2.9200.16385 oem3.inf | riftsusb.inf | No | USB | Oculus VR, LLC | 3/27/2019 | 1.0.0.8 oem30.inf | rz050daudpt.inf | No | HIDClass | Razer Inc | 10/26/2016 | 6.2.9200.16385 oem31.inf | nvmoduletracker.inf | No | NvModuleTracker | NVIDIA | 11/29/2019 | 6.14.24033.38719 oem32.inf | oculusvad.inf | No | MEDIA | Oculus | 2/11/2021 | 13.3.46.740 oem33.inf | rz0f07mou.inf | No | Mouse | Razer Inc | 10/26/2016 | 6.2.9200.16385 oem34.inf | oculusud.inf | No | Media | C-MEDIA Inc. | 4/25/2019 | 10.0.1.10 oem35.inf | rz0203dev.inf | No | HIDClass | Razer Inc | 1/2/2017 | 6.2.9200.16485 oem36.inf | rzrbtldr.inf | No | USB | Razer Inc. | 10/26/2016 | 6.2.9200.16385 oem37.inf | rzmpos.inf | No | HIDClass | Razer Inc | 10/26/2016 | 6.2.9200.16385 oem38.inf | logi_joy_vir_hid.inf | No | HIDClass | Logitech | 9/2/2022 | 2022.3.0.2 oem39.inf | appleusb.inf | No | USBDevice | Apple, Inc. | 5/7/2018 | 423.36.0.0 oem4.inf | riftssensor.inf | No | Image | Oculus VR, LLC | 4/30/2019 | 1.0.0.1 oem40.inf | riftsensor.inf | No | HIDClass | Oculus | 2/22/2015 | 1.1.0.0 oem41.inf | fxvad.inf | No | MEDIA | FxSound | 3/17/2021 | 14.1.0.0 oem42.inf | mg2500sc.inf | No | Image | Canon | 6/25/2013 | 20.2.1.4 oem43.inf | smbusamd.inf | No | System | Advanced Micro Devices, Inc | 8/30/2017 | 5.12.0.38 oem44.inf | nvvad.inf | No | MEDIA | NVIDIA | 9/13/2021 | 4.39.0.0 oem45.inf | amdgpio3.inf | No | System | Advanced Micro Devices, Inc. | 8/29/2017 | 2.0.1.0 oem46.inf | rz0f07endpt.inf | No | HIDClass | Razer Inc | 10/26/2016 | 6.2.9200.16385 oem48.inf | si3114r5.inf | No | SCSIAdapter | Silicon Image | 4/28/2008 | 1.5.19.0 oem49.inf | scpvbus.inf | No | System | Scarlet.Crush Productions | 5/5/2013 | 1.0.0.103 oem5.inf | android_winusb.inf | No | AndroidUsbDeviceClass | Oculus VR, LLC. | 10/1/2019 | 13.0.0.0 oem50.inf | logi_joy_hid.inf | No | HIDClass | Logitech | 9/2/2022 | 2022.3.0.2 oem51.inf | rz0056btendpt.inf | No | HIDClass | Razer Inc | 10/26/2016 | 6.2.9200.16385 oem52.inf | rz0a02audpt.inf | No | HIDClass | Razer Inc | 10/26/2016 | 6.2.9200.16385 oem53.inf | heci.inf | No | System | Intel | 7/7/2015 | 11.0.0.1157 oem54.inf | rz0206btendpt.inf | No | HIDClass | Razer Inc | 10/26/2016 | 6.2.9200.16385 oem55.inf | ocusbvid.inf | No | OculusVRDevs | Oculus VR | 8/26/2016 | 1.0.20.0 oem56.inf | hdxrt.inf | No | MEDIA | Realtek Semiconductor Corp. | 6/14/2017 | 6.0.1.8186 oem57.inf | netrtwlanufb.inf | No | Net | Realtek Semiconductor Corp. | 7/19/2022 | 1.20.630.2022 oem58.inf | rt640x64.inf | No | Net | Realtek | 4/10/2015 | 9.1.410.2015 oem59.inf | ntprint.inf | No | Printer | Microsoft | 6/21/2006 | 10.0.22000.856 oem6.inf | rzdaendpt.inf | No | HIDClass | Razer Inc | 10/26/2016 | 6.2.9200.16385 oem60.inf | rz0f07kb.inf | No | Keyboard | Razer Inc | 10/26/2016 | 6.2.9200.16385 oem61.inf | mg2500p6.inf | No | Printer | Canon | 7/11/2013 | 2.70.2.10 oem63.inf | rzp1endpt.inf | No | HIDClass | Razer Inc | 10/26/2016 | 6.2.9200.16385 oem64.inf | prnms006.inf | No | Printer | Microsoft | 11/29/2016 | 16.0.7629.4000 oem65.inf | rz0504audpt.inf | No | HIDClass | Razer Inc | 10/26/2016 | 6.2.9200.16385 oem66.inf | rzhnet.inf | No | USB | Razer Inc | 10/26/2016 | 6.2.9200.16385 oem67.inf | nv_dispig.inf | No | Display | NVIDIA | 11/13/2022 | 31.0.15.2698 oem68.inf | amdgpio2.inf | No | System | Advanced Micro Devices, Inc | 9/29/2019 | 2.2.0.121 oem69.inf | rzbtendpt.inf | No | HIDClass | Razer Inc | 10/26/2016 | 6.2.9200.16385 oem7.inf | sippd.inf | No | System | Silicon Image | 4/28/2008 | 1.5.19.0 oem70.inf | rzvkeyboard.inf | No | HIDClass | Razer | 10/26/2016 | 6.2.9200.16385 oem71.inf | rz050faudpt.inf | No | HIDClass | Razer Inc | 10/26/2016 | 6.2.9200.16385 oem72.inf | rz0049btendpt.inf | No | HIDClass | Razer Inc | 10/26/2016 | 6.2.9200.16385 oem73.inf | rzkeypadendpt.inf | No | HIDClass | Razer Inc | 10/26/2016 | 6.2.9200.16385 oem74.inf | prnms009.inf | No | Printer | Microsoft | 6/21/2006 | 10.0.22000.1 oem75.inf | prnms001.inf | No | Printer | Microsoft | 6/21/2006 | 10.0.22000.1 oem76.inf | klim6.inf | No | NetService | Kaspersky Lab | 12/18/2021 | 30.587.0.2440 oem77.inf | s2716dg.inf | No | Monitor | Dell Inc. | 8/13/2015 | 1.0.0.0 oem78.inf | amdpsp.inf | No | SecurityDevices | Advanced Micro Devices Inc. | 6/11/2021 | 5.17.0.0 oem8.inf | amdpcidev.inf | No | System | Advanced Micro Devices | 5/18/2021 | 1.0.0.83 oem80.inf | nvhda.inf | No | MEDIA | NVIDIA Corporation | 6/22/2022 | 1.3.39.14 oem81.inf | vbvmvaio64_win10.inf | No | MEDIA | VB-Audio Software | 1/11/2019 | 2.1.5.2 oem82.inf | logi_joy_bus_enum.inf | No | System | Logitech | 9/2/2022 | 2022.3.0.2 oem83.inf | vboxusb.inf | No | USB | Oracle Corporation | 9/1/2022 | 6.1.38.3438 oem84.inf | vboxnetadp6.inf | No | Net | Oracle Corporation | 9/1/2022 | 6.1.38.3438 oem85.inf | vboxnetlwf.inf | No | NetService | Oracle Corporation | 9/1/2022 | 6.1.38.3438 oem87.inf | nvppc.inf | No | USB | NVIDIA | 4/28/2022 | 1.50.831.832 oem88.inf | nvhda.inf | No | MEDIA | NVIDIA Corporation | 7/18/2022 | 1.3.39.16 oem9.inf | rz011dmouex.inf | No | Mouse | Razer Inc. | 10/26/2016 | 6.2.9200.16385
This command will display a list of all drivers installed on your system, including their published names. Take note of the driver you want to remove and its published name, as you will need this information when using the methods below.
Useful tip: How to Correctly Install and Update Driver in Windows 11
Precautions to take before uninstalling any driver in Windows 11
Before proceeding with any of the methods outlined in this guide, it’s important to understand that removing drivers from your Windows 11 system carries some risks. While uninstalling a problematic driver can help resolve issues, it can also cause new ones if not done correctly. Here are some potential risks to keep in mind:
- Uninstalling the wrong driver can cause system instability or even render your system unusable.
- Some devices may require specific drivers to function correctly. Uninstalling these drivers can lead to the device not working at all.
- Partially uninstalling a driver can leave behind residual files or registry entries that can cause conflicts with new drivers.
To minimize these risks, it’s recommended to create a system restore point before removing any drivers. This allows you to revert your system to its previous state if anything goes wrong during the uninstallation process.
Method 1: Using Command Prompt (CMD) to completely uninstall drivers
Utilizing the Command Prompt to uninstall drivers is a straightforward approach that allows users to target specific drivers using the pnputil
command. This method is suitable for advanced users who are familiar with command-line interfaces and want a quick way to remove drivers.
Benefits: The Command Prompt method provides a fast and efficient way to uninstall drivers without the need for additional software.
Things to note: Users should be cautious when using command-line interfaces, as entering incorrect commands or uninstalling the incorrect drivers can cause system instability or other issues. Make sure to double-check the driver name before executing any command.
To uninstall drivers using the Command Prompt:
- Go to Start menu and search for “cmd“.
- Right-click Command Prompt from the search results and select “Run as administrator“.
- Type the following command and hit Enter:
pnputil /delete-driver <published name> /uninstall /force
- Replace
<published name>
with the name of the driver you want to uninstall, such asoem67.inf
. - For example, if you want to uninstall the specific driver “oem64.inf,” your full command should look like this:
pnputil /delete-driver oem67.inf /uninstall /force
Related guide: How to Reinstall Bluetooth Driver in Windows 11
Method 2: Using PowerShell to remove drivers
If you are unable to use the Command Prompt for any reason, you can use the same command-line tool “pnputil” in Windows PowerShell to uninstall any device driver.
Things to note: Similar to the Command Prompt, users must exercise caution when using PowerShell, as incorrect commands can lead to system issues. Ensure you have the correct driver name before executing any command.
To use PowerShell for driver removal:
- Press
Win + X
and choose Windows Terminal (Admin) or PowerShell (Admin) to open an elevated PowerShell prompt. - Type the following command and hit Enter:
pnputil /delete-driver <published name> /uninstall /force
- Replace
<published name>
with the name of the driver you want to uninstall, for example,oem33.inf
.
Method 3: Deleting drivers from the registry
Removing drivers from the Windows registry is an advanced method that can help when other approaches fail. By deleting the driver entry directly from the registry, users can ensure that the driver will not be loaded on startup.
Benefits: This method can be helpful in cases where traditional driver removal methods are unsuccessful or when a driver is causing severe system issues.
Things to note: Editing the registry can be very risky, and mistakes can cause system instability or other problems. It is crucial to have experience working with the registry and create a system restore point before making changes.
To remove drivers from the registry:
- Press
Win + R
and typeregedit
in the Run dialog box to open the Registry Editor. - Navigate to the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles
- Locate the driver entry you want to remove and delete the corresponding registry key.
- Additionally, it is important to check if there are any related driver or service entries in
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
that are associated with the driver you want to delete. If there are, you should delete those entries as well.
Important: Always backup your registry before making changes.
Similar issue: How to Reinstall Printer Driver on Windows 11
Method 4: Uninstalling drivers using Device Manager
Device Manager is a built-in Windows tool that allows you to manage and uninstall drivers. This method is ideal for users who prefer using graphical interfaces and is more suitable for less experienced users.
Benefits: Device Manager provides a user-friendly way to remove drivers and offers a clear overview of the devices and drivers installed on your system.
Things to note: Removing drivers using Device Manager may not always result in a complete removal, as some residual files or registry entries may remain. In such cases, you might need to use other methods to ensure a thorough removal.
To uninstall drivers using Device Manager:
- Press
Win + X
and choose Device Manager from the menu. - Locate the device for which you want to uninstall the driver, right-click on it, and choose Uninstall device.
- A confirmation window will appear, check the box next to Delete the driver software for this device if available, and click Uninstall.
Recommended resource: How to Update Realtek Drivers in Windows 11
Method 5: Using DISM (Deployment Image Servicing and Management)
DISM is a command-line tool that can be used to service a Windows image or prepare a Windows Preinstallation Environment (Windows PE) image. This method is ideal for advanced users who are comfortable with command-line tools and want to uninstall drivers before boot (using the Command Prompt in Windows RE).
Benefits: DISM provides greater control over the driver removal process and can remove drivers from an image via environments such as Windows RE, which can be useful for system administrators managing multiple devices.
Things to note: DISM commands can be complex, and users should be cautious when using this method to avoid causing system issues.
To remove drivers using DISM:
- Boot your computer into Windows Recovery Environment and select Command Prompt.
- Type the following command to list all drivers in the Windows installation on the C: drive (change the drive letter if necessary):
dism /image:c:\ /get-drivers /format:table
- Then, type the following command to uninstall a specific driver:
dism /image:c:\ /remove-driver /driver:<Published Name>
- Replace
<published name>
with the name of the driver you want to uninstall, for example,oem11.inf
. - For example, if you want to uninstall the specific driver “oem11.inf,” your full command should look like this:
dism /image:c:\ /remove-driver /driver:oem11.inf
Uninstalling a failed Windows driver update
Failed driver updates can cause system issues, and uninstalling them might be necessary to restore system stability. This method is suitable for users experiencing problems after a Windows driver update.
Benefits: Uninstalling failed driver updates can help resolve issues caused by conflicts between drivers or compatibility issues with the system after an update.
Things to note: Uninstalling a failed driver update might revert the driver to a previous version, so make sure you have an alternative driver ready for installation.
To uninstall a failed Windows driver update:
- Press
Win + I
to open the Settings app. - Navigate to Windows Update > Update history.
- Expand Driver updates. You will see a list of drivers that were recently installed by Windows Update.
- Take note of the driver you want to remove and use either the Device Manager, Command Prompt, or any other method to completely uninstall the driver.
Final thoughts
Managing drivers in Windows 11 can be a challenging task, especially when encountering problematic drivers that can cause system instability or performance issues. However, with the methods outlined in this guide, you should be able to completely uninstall any driver from your Windows 11 system and ensure a fresh start for your new driver installation. It is important to exercise caution when removing drivers and always back up your data before making changes to your system.
In addition, it is recommended to keep your drivers up to date to ensure that your system operates smoothly and efficiently. You can check for updates manually or use third-party tools that automate the process. Moreover, some manufacturers may have their own driver update tools, so it’s worth checking their website for any available updates.