4.5 Uninstalling WinDriver
This section will help you to uninstall either the evaluation or registered
version of WinDriver.
4.5.1 Windows WinDriver Uninstall Instructions
You can select to use the graphical
wdreg_gui.exe utility instead of
- wdreg.exe and
wdreg_gui.exe are found in the
WinDriver\util directory (see Chapter 10 for details regarding these utilities).
Close any open WinDriver applications, including DriverWizard, the Debug
Monitor, and user-specific applications.
Uninstall all Plug-and-Play devices (USB/PCI/PCMCIA) that have been registered
with WinDriver via an INF file:
Uninstall the device using the wdreg
wdreg -inf <path to the INF file> uninstall
Verify that no INF files that register your device(s) with WinDriver's
kernel module (windrvr6.sys) are found in the
On the development PC, on which you installed the WinDriver
Run , OR run
the uninstall.exe utility from the
WinDriver installation directory.
The uninstall will stop and unload the WinDriver kernel module
(windrvr6.sys); delete the copy of the windrvr6.inf file
from the %windir%\inf directory; delete WinDriver
from Windows' menu; delete the
WinDriver installation directory (except for
files that you added to this directory); and delete the shortcut icons
to the DriverWizard and Debug Monitor utilities from the Desktop.
On a target PC, on which you installed the WinDriver kernel module
(windrvr6.sys), but not the entire WinDriver toolkit:
Use the wdreg utility to stop and
unload the driver:
wdreg -inf <path to windrvr6.inf> uninstall
When running this command, windrvr6.sys should reside in the
same directory as windrvr6.inf.
(On the development PC, the relevant
wdreg uninstall command is executed
for you by the uninstall utility).
If you attempt to uninstall WinDriver while there are open handles to
the WinDriver service (windrvr6.sys or your renamed
driver [12.2], or there are
connected and enabled Plug-and-Play devices that are registered to work
with this service, wdreg will fail
to uninstall the driver. This ensures that you do not uninstall the
driver while it is being used.
You can check if the WinDriver kernel module is loaded by running the
Debug Monitor utility
(WinDriver\util\wddebug_gui.exe) [7.2]. When the driver is loaded, the Debug
Monitor log displays driver and OS information; otherwise, it
displays a relevant error message. On the development PC, the
uninstall command will delete the Debug Monitor executables; to use
this utility after the uninstallation, create a copy of
wddebug_gui.exe before performing
the uninstall procedure.
If windrvr6.sys was successfully
unloaded, erase the following files (if they exist):
Reboot the computer.
4.5.2 Linux WinDriver Uninstall Instructions
The following commands must be executed with root privileges.
Verify that the WinDriver driver modules
are not being used by another program:
View the list of modules and the programs using each of them:
Identify any applications and modules that are using the WinDriver
driver modules. (By default, WinDriver module names begin with
Close any applications that are using the WinDriver driver modules.
Unload any modules that are using the WinDriver driver modules:
/# /sbin/modprobe -r <module_name>
Unload the WinDriver driver modules:
/# /sbin/modprobe -r windrvr6
If you are not using a Linux 2.6.x kernel that supports the udev
file system, remove the old device node in the
/# rm -f /dev/windrvr6
Remove the file .windriver.rc from the
/# rm -f /etc/.windriver.rc
Remove the file .windriver.rc from
/# rm -f $HOME/.windriver.rc
If you created a symbolic link to DriverWizard, remove the link using the
/# rm -f /usr/bin/wdwizard
Remove the WinDriver installation directory using the command
/# rm -rf ~/WinDriver
Remove the WinDriver shared object file, if it exists: