Quanta Port Devices Driver

Posted By admin On 13/10/21
  1. Right-click on your EHD and select “Uninstall device” from the pop-up menu. When that has finished, unplug the USB cable. Wait a minute, then plug the USB cable back in. Windows should see the.
  2. The Bluetooth profile driver, BthPort.sys, reads the COD Major and COD Type values to determine how it should respond to a device inquiry. These values affect only the CODMAJORXXX and CODXXXMINORXXX bits of the Class of Device. The CODSERVICEXXX bits are not affected by this registry entry.

These downloads cover most Intel® Ethernet Adapters and install the latest drivers when you run them. The network adapter property sheet in Windows® 10 provides information about the network adapter and driver on the computer. Follow these steps to open the adapter properties: Right-click the Start button. Click Device Manager from the list.

2.1. Drivers and Modules

For your webcam to work you will need support for the connection and support for the actual camera hardware. Those who are already versed in kernels and modules and how to load them should skip to Section 2.2, which addresses support of the connection type. If you know your USB, IEEE 1394 or whatever bus you will be connecting your camera to is already configured and working, you should move on to the list of specific webcam hardware listed in Section 2.3.

Webcam drivers are usually available one of three ways: within the kernel, as a compilable stand alone module, or available as a pre-compiled (packaged) binary driver from your Linux distribution.

Devices2.1.1. Module or In-Kernel?

As a rule, often the stock kernel, or working part of the operating system, of your initial installation may already have support for what you need. Your Linux distribution vendor has likely enabled the most common options already, including the bus, or connection type, and drivers for common camera models. The driver exists either as a loadable module or within the already running kernel.

An easy way to tell if the driver is enabled is to use the dmesg command piped into less (for easy paging) to look for an acknowledgement that it was loaded when your system started up:

...which may yield something like the following, depending on your hardware:

If you don't see it, the particular driver may exist as a loadable module. If you know what that module is named, try using find; in this example we are looking for the 'ibmcam' module:

Note that up until the 2.4 series modules had the suffix .o; for 2.6+ series kernels this was replaced with .ko.

You can get a list of all modules available by typing the following at the command line:

Where `uname -r`, surrounded by forward tick marks, is your kernel version number.The following output is an example of what you might find in a USBwebcam-ready kernel , where everything is loaded as a module (allbut the relevant lines have been edited for brevity):

Once you know which module your camera needs you can find out if it is already loaded by typing the following at the command line:

As shown by the prompt above, you will need to have root privilegesto do this.You should get output similar to the following:

Most stock kernels are compiled with kmod, which enabling automatic loading of necessary modules when the appropriate hardware is detected. It may not always do so, however, so if you don't have the particular module you're seeking loaded andyou think the module may be available, try loadingit manually with modprobe, as in the following using the ibmcam module as an example:

Drivers for specific webcam models, or links to project pages hosting code for drivers, are outlined in Section 2.3. The drivers are usually available one of three ways: within the kernel, as a compilable stand alone module, or available as a pre-compiled binary from your Linux distribution.

If the support for your driver is not found either enabled statically within the kernel or as a module, don't despair. Drivers for numerous models are in the Linux kernel source (available directly from kernel.org source code repository), or in code offered separately from the kernel that can be configured to work with your current setup as oulined in Section 2.1.2. If your webcam driver is available in the kernel source but not enabled as a module or otherwise in your default system, you can either recompile the kernel from the source code you have or obtain a new version of the kernel source, either pre-packaged by your Linux distributor or directly from the previous link (as a so-called 'vanilla' kernel).If you are unfamiliar with the prerequisites and procedure of compiling your own kernel, I direct you to the Kernel HOWTOfor more information.

2.1.2. Patching, Source-Only or Precompiled Binary?

You may find that your webcam is supported by only a kernel patch, by a source-only driver not requiring a kernel recompile, or you may even be lucky enough to have a distribution that makes a pre-compiled and packaged binary driver available for your computer's architecture. The procedure involved in the former is largely beyond the scope of this document and is probably best outlined in the documentation available on the web page of your particular model's driver found in Section 2.3. Some further more general documentation on these processes are, however, addressed in Section 5

2.2. Supporting the Connection Type2.2.1. USB Webcams

If you have a USB webcam, it is likely a Linux driver has been written for your device.There are two ways of supporting USB devices in Linux.One is the more traditional kernel support, and the other is throughlibusb.For at least one webcam category, the STV0680-based models, working libusb support is recommended, at least according to the Sourceforge page on the subject.

Unless you know your driver requires libusb support, you should probably stick with the more conventional in-kernel support for USB devices beginning in Section Libusb

Libusb is a library that allows access to the USB functions inLinux through userspace and without the need to enable kernel supportand insert modules. Most distributions, at this point, are offering libusb in their stablebranches (and some install it by default), so if you don't already havekernel support for USB devices, then you may only have to install thelibusb package in order to access your device.You must have USB device filesystem support enabled in your kernel,which most distributions do.To find out for sure, issue the following at the command line:

You should see (among others):

You may need to mount usbdevfs to enable it and see the devicefiles, which you can do at the command line with mount -tusbdevfs none /proc/bus/usb.Don't try to use libusb while your particular kernelwebcam support is enabled either statically or the module loaded; youcan only use one at at time.

You can obtain the libusb package in .rpm,.tgz or .deb format from yourLinux distribution. Linux Kernel USB Support

Kernel support is required for USB webcam support if not usinglibusb (outlined above).

For 2.2 and 2.4 series kernels, your USB webcam may require the module usbvideoto function. This is not required in the 2.6+ series.

For generic USB bus support in Linux, you will need USB subsystemsupport in your kernel, whether usb-ohci, usb-ehci, or whatever flavorof USB driver your system prefers.USB subsystem support has been present in the Linux kernel since thelate 2.2 series.For a more in-depth discussion of USB support in general, I direct you tothe Linux-usb project site.If you want to find out which modules are loaded, at the command lineor in an xterm, type the following:

As shown by the prompt above, you will need to have root privilegesto do this.You should get output similar to the following:

If you don't have the particular module you're seeking loaded andyou think the module may be available, try loadingit directly (using the usb ibmcam module as an example):

...at which point you should see something like thefollowing:

By placing the entry ibmcam (for example) in/etc/modules (note that this varies by distribution),you can have the module load at boot-time automatically.You can then confirm the module was loaded by checking the syslog or inthe boot-time record with dmesg less), where youshould see an entry such as the following:

2.2.2. IEEE 1394 (Firewire™,i.Link™)

IEEE 1394 webcams require an IEEE 1394 PCI card or an IEEE 1394bus port on your mainboard.The IEEE interface has been supported in Linux since the early 2.4-serieskernel.If you are lucky enough to own such a device, generic informationon support of the IEEE 1394 bus in Linux can be found at www.linux1394.org.If you have a kernel older than 2.4.2, you will need topatch your kernel with one of the patches found on this pagematched to your kernel version.In addition, you will require libraw1394.The previously referenced linux1394.org site has a great installationguide.

The IEEE1394Digital Camera List, by Damien Douxchamps, offers an outstandingsummary of the capabilities of IEEE 1394 cameras as well as the currentstatus of support for individual models.

Drivers2.2.3. Generic Parallel Port Support for Parport Webcams

For 2.2 and 2.4 kernel systems, parallel-port support must beenabled statically or as a module (stock kernels usually have thisenabled by default).You may want to read moregeneric info about parallel-port device support under the Linuxkernel before starting this process.To find out for sure if the module parport is loaded,you can check the dmesg file or use lsmod as outlined above.Using dmesg less, you should see (among many otherlines) the following:

If you are compiling your own kernel, enable 'Parallel Portsupport'.You should enable 'IEEE 1284 transfer modes', and if you have x86 typearchitecture, you should also enable 'PC-style hardware'.

If modprobe returns an error when you attempt to load the module,note that you may need to determine and supply the hardware address wheninvoking modprobe.The most common address is 0x378 for an x86 system; 0x278 and 0x3BC areother possibilities for integrated or ISA parallel ports.Add-in PCI parallel ports may have unusual base addresses.You can also arrange multiple devices with either the parport_pc orparport_arc modules, though that topic is beyond the scope of thisdocument.

WARNING: Be sure you have the correct address beforeentering this information at the command line or else your machine maybecome unstable, crash or otherwise implode.

Your parallel port should be set to preferably 'EPP'mode, or alternatively ECP/EPP.'Bidirectional' (also known as 'BPP' or'PS/2') may work, albeit much more slowly.'Unidirectional' mode is unsuitable for scanning.The above setting can usually be accessed through your BIOS menu, atleast on x86 systems.

2.3. Specific Webcam Models

Note that this information is frequently changing.The Linux-USBDevice Overview site is a great place to look if you have aUSB webcam.Also, you will want to check for your model's homepage at http://www.exploits.org/v4l/.The information compiled below on specific webcam models is from thesame source, so you may find more up-to-date information through theprevious link.If you can't find an entry for your particular hardware, you can findlinks to resources on how to write your own driver!

It is important to note that if your camera isn't listed,the easiest way to find out if your camera is supported is to find outwhat chipset is used in its manufacture.

This information is usually present in the specifications published inyour webcam's manual or on the manufacturer's website.

If you can't find your camera model listedand aren't sure what chipset your camera is made with,you should consider searching and/or subscribing to thevideo4linux-list mailing list hosted by Redhat.

2.3.1. 3com HomeConnect PC Digital Webcam

This driver is supported with the kernel patch located atthe homeconnectusbproject web page.It may require a kernel recompile after patching depending on yourkernel version.

2.3.2. CPiA based Webcams

Please see the projecthome page for up-to-date information.This chipset has been used in the manufacture of both USB and parallelport webcams including the following:

Aiptek HyperVcam Fun USB (non-OV511 based)

Creative Video Blaster WebCam II USB and parallel-port

CVideo-Mail Express parallel-port

Digicom Galileo USB and Digicom Galileo Plus

Dynalink Digital Camera

Ezonics EZCam (not Pro or Plus)

I-View NetView NV200M

Microtek EyeStar USB

Pace Color Video Camera USB

SuperCam WonderEye

TCE Netcam 310 USB

Terracam USB (non-OV511 based or Terracam Pro)

Trust [email protected] Lite USB and [email protected] 100

Utopia USB Camera

ZoomCam USB and parallel-port

2.3.3. SE401, SE402 and EP800 based USB webcams

Thisproject is a work in progress.The drivers and other useful information areavailable at the project homepage located here.As of writing this, it is necessary to patch and recompile your kernelin order to obtain support for these models.The driver supports the following:

SE401 chipset via the 'se401' driver:

Aox SE401 camera

Philips PCVC665 USB VGA webcam 'Vesta Fun'

Kensington VideoCAM PC Camera (Models 67014-67017)

SE402 and EP 800 chipsets via the 'epcam' driver

Spypen Actor

Rimax Slim Multicam

Concord Eye-Q Easy

Creative PD1001

Chicony DC-100

Endpoints SE402 and EP800

2.3.4. OmniVision based Webcams

This category includes amultitude of webcam and video-capture devices manufactured by Omnivision,including the OV511(+), OV518(+), OV6620, OV6630, OV7610, and OV7620AE.The project homepage is here.Supported models include:

Aiptek HyperVcam Home and Mobile

Amitech AWK-300

I-view NetView NV300M

TEVion MD9308

Intel Me2Cam

Dlink DSB C100, C300

Hawking Tech. UC-110, UC-300 and UC-310

Puretek PT-6007

Alpha Vision Tech AlphaCam SE model AC-520

Creative Labs WebCam model PD1001 with OV518 chipset

Creative Labs WebCam 3, WebCam Go, Webcam Go Plus

Elecom UCAM-C1C20

Elta WEBCam 8211 PCC

Ezonics EZPhone Cam

Philips ToUCam XS (old version with OV518)

LG Electronics LPC-UM10

Lifeview various USB Life TV models

Genius VideoCam Express

AverMedia Intercam Elite

Maxxtro Cam22U

MediaForte MV300, PC Vision 300

Terratec TerraCam PRO and some TerraCam models

OmniVision (except those with OV519)


Trust [email protected]@m USB

Lifetec LT9388

BestBuy EasyCam U

Maxell Maxcam

TCE NetCam 310u

Medion MD9388

Webeye 2000B

Suma eON

Prochips PCA-3100

Ezonics EZ USB Cam II (the OV511+ models)

Waytech I-Pac VIC-30

Zoom Telephonics ZoomCam III USB (model 1598)

2.3.5. Logitech (formerly Connectix) QuickcamSupport

The QuickCam VC USB and parallel port modelwebcams are supported by the driver offered here.A kernel patch and recompile are necessary for support of this model.

The Quickcam driver is represented by two different projects that offer two different flavorsof driver for certain Quickcam models, both of which are stand-alonedrivers that do not require a kernel patch or recompile.The qce-ga and qc-usbdrivers support the following models:

Logitech (earlier models of) Quickcam Express

Quickcam Web


Dexxa Webcam

Labtec Webcam

The qc-usb driver is more experimental but reportedly works betteron some models such as the Quickcam Web. Also, I have recieved correspondence that newer versions of the Logitech Quickcam Express no longer work with the above drivers; instead this page offers an experimental driver that claims to support the newer model.

Note to Redhat users: The qce-ga driver doesn't compile properly using themodified kernel source provided in Redhat 9, but a fix is available here.

Some Logitech camera models are supported by the Philips driverin Section 2.3.8.

2.3.6. ICM532 Based Webcams

One driver for this chipset, homepage here, is now merged into the 2.6 kernel source; the other is (per the developer's own description) experimental and available here. Either or both claim to support the following models:

IC-Media Corp Pencam

Newer versions of the Logitech Quickcam Express

Newer versions of the Labtec Webcam

Biolux 654 microscope

Ezonics EZCam USB II (uvt8532)

Ezonics EZCam USB III

TerraCam USB

Stick Webcam

Mini WebCam

Tucan PenCam

Che-ez! Webbie

SNAKE EYE SI-8480/8481


WEB Camera PBC0006


2.3.7. NW802 Based Webcams

This chipset, manufactured by DIVIO, is supported by the driverfound here.The models supported include the following:

Quanta Port Devices Driver License Test

BTC SurfCam CMOS300k

Mustek WCam 300

Logitech QuickCam Pro USB (the earlier 'dark focus ring' model)

2.3.8. Philips USB Webcams

Because of the expiration of the Non-Disclosure-Agreement between Philips Corporation and the former maintainer of the pwc driver, the previous kernel support for Philips PWC-chip-based webcams has been removed. Luckily a new, still experimental driver that does not require a proprietary module is under development. The old site, with a discussion of the change, can be seen at http://www.smcc.demon.nl/webcam/; the new driver is maintained at saillard.org with more information at the PWC Documentation Project.

Philips models supported by the above include the following.



PCVC675K Vesta, Vesta Pro and Vesta Scan

PCVC720K/40 ToUCam XS, ToUCam Fun, ToUCam Pro and ToUCam Scan

Askey VC010

Creative Labs Webcam 5, Pro Ex

Logitech 3000 and 4000 Pro, Notebook Pro, and Zoom

Samsung MPC-C10 and MPC-C30

Sotec Afina Eye

Visionite VCS UM100 and UC300

2.3.9. SPCA50X USB Camera Linux Driver

Information regarding this chipset can be found here, and is under heavy development and includes partial or complete support for the following models:

Kodak DVC-325 and EZ200

Creative PC-CAM 300, 600, 750

Genius VideoCAM Express V2

Micro Innovation IC 200/IC 150

Logitech ClickSmart 310, 420, 510, 820 and Cordless models

Logitech Pocket750

Benq DC 1016, 1300, 1500, 3410

Flexcam 100

Aiptek MegaCam, [1.3 Megapixel] Mini PenCam and PocketCam 1.3M Smart

Finet Technology Palmpix DC-85

Pure DigitalDakota

3Com Home Connect lite

Megapix V4

Mustek gSmart: Mini, Mini2, Mini3, LCD 2, LCD 3

Digital Dream Enigma 1.3, Epsilon 1.3

Maxwell Compact Pc PM3

Jenoptik models

Minton S-Cam F5

D-Link DSC-350

Trust [email protected] 300 Movie

Aiptek Pocket DV, PocketDVII, DV3100+, mini PenCam 2, PocketCam 3M, Pencam SD 2, Pocket DV3500

Hama Sightcam 100

Micro Innovations IC50C, IC400c

FlyCam USB100

Arowana USB Camera 300 K


Intel Easy PC Camera, CS120 (Easy PC Share), PC Camera Pro (CS431), Pocket PC Camera (CS630)

Grandtec V.cap

Sigma-Apo Petcam

2.3.10. STV0680 based Models

The USB version of webcams made with this chipset are supported bythe 2.4.18 and above kernel with the stv680.o module.Alternatively, you can obtain the source from the project homepage.This driver supports models including the Aiptek Pencam and the NisisQuickpix 2.

If you have a serial version, the main oneof which is the Scan e-Studio, you should go here.

2.3.11. Winbond w9966cf

This is a driver for the parallel-port interface that supportsthe Philips SAA7111 CCD-control chip as found on the Lifeview FlycamSUPRA webcam. It is included in the late 2.4 kernel series and laterunder the heading 'video4linux' support.The homepage for this project is here.

2.3.12. Xirlink C-it™ HDCS-1000based Webcams

This driver is for the USB webcams manufactured by Xirlink, IBM(PC Camera) and Veo Stingray model webcams.Support has been in the Linux kernel USB section since 2.2.12.The homepage is at http://www.linux-usb.org/ibmcam.

PrevHomeNextIntroductionAccessing the Video Device
USBDeview v3.01
Copyright (c) 2006 - 2020 Nir Sofer

See Also

  • USB over Ethernet - USB Network Gate enables work with the remote USB devices over Ethernet (Internet/LAN/WAN) as if they were plugged into your own machine. It helps you share a USB device over network among multiple computers so people from all over the world (or your office) can use it. (Available for Windows, Mac and Linux)
  • NK2Edit - Edit, merge and fix the AutoComplete files (.NK2) of Microsoft Outlook.
  • DevManView - Alternative to device manager of Windows.
  • WirelessNetView - Monitor wireless networks on your area.


USBDeview is a small utility that lists all USB devices that currently connected to your computer, as well asall USB devices that you previously used.
For each USB device, extended information is displayed: Device name/description, device type, serial number(for mass storage devices), the date/time that device was added, VendorID, ProductID, and more...
USBDeview also allows you to uninstall USB devices that you previously used, disconnect USB devices that are currently connected to your computer, as well as to disable and enable USB devices.
You can also use USBDeview on a remote computer, as long as you login to that computer with admin user.

Search for other utilities in NirSoft


This utility is released as freeware. You are allowed to freely distribute this utility via floppy disk, CD-ROM, Internet, or in any other way, as long as you don't charge anything for this. If you distribute this utility, you must include all files inthe distribution package, without any modification !


The software is provided 'AS IS' without any warranty, either expressed or implied,including, but not limited to, the implied warranties of merchantability and fitnessfor a particular purpose. The author will not be liable for any special, incidental,consequential or indirect damages due to loss of data or any other reason.

System Requirement

  • This utility works on Windows 2000, Windows XP, Windows 2003, Windows Vista, Windows Server 2008, Windows 7, Windows 8, and Windows 10. Both 32-bit and 64-bit systems are supported.Windows 98/ME is not supported.

Known Issues

  • In order to disable/enable USB items on x64 systems, you also must use the x64 version of USBDeview.
  • The 'Created Date' column doesn't display correct values on Windows 7/8/Vista/2008.
  • Some USB devices with bad driver may cause USBDeview to hang.In order to bypass this problem, you should turn off the 'Retrieve USB Power/Version Information' option:
    USBDeview.exe /RetrieveUSBPower 0

Versions History

  • Version 3.01
    • Added 'Copy Clicked Cell' option to the right-click context menu, which copies to the clipboard the text of cell that you right-clicked with the mouse.
  • Version 3.00
    • Added 4 new columns: Install Time, First Install Time, Connect Time, Disconnect Time.
    • You can view the new fields only when you run USBDeview as Administrator (Elevation). You can run USBDeview as Administrator by pressing Ctrl+F11.
    • 'Install Time' and 'First Install Time' fields are available starting from Windows 7.
    • 'Connect Time' and 'Disconnect Time' fields are available only on Windows 8 and Windows 10.
    • These properties are stored in the Registry under Properties{83da6326-97a6-4088-9453-a1923f573b29} subkey of every USB device, and only SYSTEM user can read them.
    • Changed the 'Created Date' column to 'Registry Time 1' and the 'Last Plug/Unplug Date' column to 'Registry Time 2'.The change is made because the actual meaning of these timestamps is different from one system to another.
  • Version 2.86
    • Added 'RegEdit Open Mode' option - 'Without Elevation' or 'With Elevation'.
  • Version 2.85
    • Added option to create a shortcut on your desktop to disable,enable,disable-enable, or disconnect a USB device.
    • In order to create the shortcut, select the desired item you want to disable/enable/disconnect, go to File -> Create Desktop Shortcut and from thesubmenu choose the desired action for the shortcut.
    • The shortcut will work only for the USB item you selected.
  • Version 2.81
    • Added 'Open Device Properties Window' option.
  • Version 2.80
    • Fixed the serial number command-line options (/stop_by_serial , /enable_by_serial , /disable_by_serial , /remove_by_serial) to accept decoded serial numbers.
  • Version 2.79
    • Added 'Always On Top' option.
  • Version 2.78
    • Added /cfg command-line option to start USBDeview with the specified config file.
  • Version 2.77
    • You can now change the number of milliseconds to wait between disable and enable actions when using the 'Disable+Enable Selected Devices' option (or disable-enable command-line options).
      In order to change it - edit the config file (USBDeview.cfg) and change the 'DisableEnableWaitTime' value (The default is 100 milliseconds).
  • Version 2.76
    • You can now send the data to stdout by specifying empty string as filename, for example:
      USBDeview.exe /scomma ' more
  • Version 2.75
    • When connecting a remote computer, the computer name is now displayed in the window title.
    • Added 'Select All' and 'Deselect All' to the 'Column Settings' window.
  • Version 2.74
    • Fixed bug: The /regfile , /remote and /remotefile command-line options stopped working properly because the USBDeview loaded the settings from the .cfg file...
  • Version 2.73
    • USBDeview now detects the port name (COM1, COM2, COM3... ) of FTDI devices.
  • Version 2.72
    • Added 'Friendly Name' column.
  • Version 2.71
    • When running USBDeview locally, the 'Computer Name' column now displays the local computer name (In previous versions it was empty)
  • Version 2.70
    • Added new command-line options to check whether a USB device is connected (USBDeview returns 0 if the device is not connected):/is_connected , /is_connected_by_serial , /is_connected_by_drive, /is_connected_by_class , /is_connected_by_pid
      For example:USBDeview.exe /is_connected 'USBVid_1058&Pid_10238539583490834690'
    • Added new command-line options to check whether a USB device is disabled (USBDeview returns 0 if the device is not disabled):/is_disabled , /is_disabled_by_serial , /is_disabled_by_drive, /is_disabled_by_class , /is_disabled_by_pid
      For example:USBDeview.exe /is_disabled 'USBVid_1058&Pid_10238539583490834690'
  • Version 2.66
    • USBDeview now can start the Remote Registry service even if it's disabled.
  • Version 2.65
    • Added option to automatically start the Remote Registry service on the remote machine for reading the USB devices information (In 'Advnaced Options' window).
  • Version 2.62
    • Added /RunAsAdmin command-line option. You can use it with other command-line options of actions that require elevation ( /remove, /disable , /enable , /disable_enable ),for example:
      USBDeview.exe /RunAsAdmin /disable 'USBVid_1058&Pid_10238539583490834690'
  • Version 2.61
    • Fixed bug: The 'Run As Administrator' option failed to work randomly on some systems.
  • Version 2.60
    • Improved the detection of device connect status (Connected column) on Windows 10 and Windows 8.
  • Version 2.55
    • Added 'Display Only Devices With Drive Letter' option.
  • Version 2.52
    • USBDeview now saves the last selected font in the .cfg file.
  • Version 2.51
    • Added 'Open INF File' option.
  • Version 2.50
    • Added 'Driver InfSection' and 'Driver InfPath' columns.
  • Version 2.46
    • Added 'Run As Administrator' option.
  • Version 2.45
    • You can now choose to connect a remote computer or external Registry file from the 'Advanced Options' window (In previous versions, you could do it only from command-line)
    • Fixed to display an error message when USBDeview fails to connect a remote computer.
  • Version 2.42
    • Added 'Capabilities' column. You can read about the meaning of every string inside this column in this article
  • Version 2.41
    • Fixed bug: USBDeview failed to remember the last size/position of the main window if it was not located in the primary monitor.
  • Version 2.40
    • Added 'Sort On Every Update' option.
  • Version 2.37
    • Added 'Decode Serial Numbers' option. When it's turned on, a serial number that is encoded as hexadecimal string is decoded to Ascii.
  • Version 2.36
    • Added secondary sorting support: You can now get a secondary sorting, by holding down the shift key while clicking the column header. Be aware that you only have to hold down the shift key when clicking the second/third/fourth column. To sort the first column you should not hold down the Shift key.
  • Version 2.35
    • Added 'Reload USB Hub' option (Ctrl+R). When you select a USB hub item and use the 'Reload USB Hub' option, all USB devices connected to this hub arereconnected, including USB devices that you previously disconnected. Be aware that in order to use this option, you also have to turn on the 'Show USB Hubs' option (Ctrl+F7).
  • Version 2.31
    • Added 'Copy Sorted Column Data' option, which copies to the clipboard the text of all selected items, but only the column that is currently sorted.
  • Version 2.30
    • Fixed bug on Windows Vista/7/8 with UAC turned on: USBDeview failed to remove USB devices when running without elevation.
  • Version 2.29
    • Fixed to display the correct Power value of USB 3.0 devices.
  • Version 2.28
    • Fixed to display date/time values according to daylight saving time settings.
  • Version 2.27
    • You can now use the 'Open In RegEdit' features on Windows Vista/7/8 (with UAC turned on) without running USBDeview.exe as Administrator.Elevation window will appear to confirm every action.
  • Version 2.26
    • Update for Windows 7/8/Vista/2008: USBDeview now extracts the real device name directly from hardware when the device is connected and the 'Retrieve USB Power/Version Information' option isturned on.
  • Version 2.25
    • Added new command-line options to disable and then enable again a device:/disable_enable,/disable_enable_by_serial ,/disable_enable_by_drive ,/disable_enable_by_class , /disable_enable_by_pid ,/disable_enable_all
    • You can now specify the device Instance ID string in the following command-line options:/disable, /enable, /remove, /disable_enable, /stop
      For example:USBDeview.exe /disable 'USBVid_1058&Pid_10238539583490834690'
    • You can now use the disable/enable/uninstall features on Windows Vista/7/8 (with UAC turned on) without running USBDeview.exe as Administrator.Elevation window will appear to confirm every action.
  • Version 2.22
    • Fixed USBDeview to add header line to the csv/tab-delimited files when exporting the USB information from command-line.In order to add the header line, you can use the /AddExportHeaderLine command-line option, or simply turn on the 'Add Header Line To CSV/Tab-Delimited File' optionfrom the user interface.
  • Version 2.21
    • You can now use the disable/enable/remove command-line options according to the com number of a USB to serial device. For example:
      USBDeview.exe /disable_by_drive com62
  • Version 2.20
    • Update for Windows 8: It seems that on Windows 8, it's impossible to detect from the Registry whether a device is connected or disconnected, soinstead of using the Registry, a device is displayed as connected if it has power/version information.Be aware that if the 'Retrieve USB Power/Version Information' option is turned off on Windows 8, all devices will displayed as disconnected.
  • Version 2.18
    • Fixed issue: The %drive% variable returned empty string for USB to serial devices.
  • Version 2.17
    • Fixed bug: When plugging 2 USB devices with the same pid/vid, USBDeview disabled/enabled/removed the wrong device.
  • Version 2.16
    • Added new variable to the execute command option: %usb_version%
  • Version 2.15
    • Added 'Auto Size Columns+Headers' option, which allows you to automatically resize the columns according to the row values and column headers.
    • Fixed issue: The properties and the options windows opened in the wrong monitor, on multi-monitors system.
  • Version 2.12
    • Fixed issue: USBDeview failed to detect some devices as connected, even if they were connected.
  • Version 2.11
    • Fixed USBDeview to detect the version/power information of Etron USB 3.0 host controller, and possibly other USB host controllers.
  • Version 2.10
    • Fixed the 'Last Plug/Unplug Date' value on Windows 7.
    • Fixed the 'Device Mfg' value on Windows 7.
  • Version 2.06
    • Fixed bug: USBDeview froze for a few seconds if there was a disconnected network drive on the system.
  • Version 2.05
    • Fixed the speed test error messages of USB 3.0 devices. Also, you can now submit the speed tests of USB 3.0 devices tohttp://usb3speed.nirsoft.net Web site
  • Version 2.00
    • Changed the USB status icons so it'll be much easier to distinguish between them, especially on small LCD monitors.
  • Version 1.97
    • Added more accelerator keys.
    • Fixed the minimum size of Advanced Options window.
    • Added a few more command-line options.
  • Version 1.96
    • Fixed to USBDeview to detect USB hubs (and probably some other devices) as connected.
  • Version 1.95
    • Added 'USB Version' column, which displays the USB version of the device.This column is active only when 'Retrieve USB Power/Version Information' option is turned on.
  • Version 1.92
    • Added 'Turn Off Device On Disable/Remove' option, only for Windows 7/2008/Vista.As opposed to Windows XP, Windows 7/2008/Vista doesn't turn off the USB device when you disable or 'Safely Remove' the device.This new option make a small Registry change to make Windows 7/2008/Vista behave like Windows XP and turn off the device after disable or 'Safely Remove' action.For more information: USB Port Remains Active for Disabled or Safely Removed USB Device.
      Be aware that this change takes effect only after reboot, and requires full admin rights (execute USBDeview.exe with 'Run As Administrator')
  • Version 1.91
    • For USB To Serial devices, USBDeview now displays the port name (Com1, Com2, Com3,...), if it's stored in the Registry.The port name is displayed on the 'Drive Letter' column.
  • Version 1.90
    • Improved the detection of the 'Last Plug/Unplug Date' value.
  • Version 1.89
    • Added 'Mark Odd/Even Rows' option, under the View menu. When it's turned on, the odd and even rows are displayed in different color, to make it easier to read a single line.
  • Version 1.88
    • Added 'Mark Connected Devices' option. When it's turned on, the plugged USB devices are marked with green background color.
  • Version 1.87
    • Added Device Instance ID column.
  • Version 1.86
    • USBDeview now displays a message with instructions to run as administrator when you tryto disable/enable/remove a device on Windows 7/2008/Vista with UAC turned on.
  • Version 1.85
    • Added 'Change Assigned Drive Letter' option, which allows you to change the drive letterthat is assigned to a USB device. In the next time that you plug the device, the new drive letter that you chose will be used.
  • Version 1.84
    • Added new variables to the execute command option: %firmware_revision%, %product_name%, %vendor_name%
  • Version 1.83
    • Fixed bug: When typing commands in the 'Advanced Options' with quotes as the first or last letter, the quotesdisappeaed when saving to the .cfg file.
  • Version 1.82
    • The properties window now contains 2 properties columns, instead of one very long properties column in the previous versions.
  • Version 1.81
    • Added new variables to the execute command option: %driver_file%, %driver_version%, and %power%
  • Version 1.80
    • Added 'Firmware Revision' column.
  • Version 1.77
    • Added 'Display Tray Balloon When Device Is Disconnected' option.
  • Version 1.76
    • Added 'Add Header Line To CSV/Tab-Delimited File' option. When this option is turned on, the column names are addedas the first line when you export to csv or tab-delimited file.
  • Version 1.75
    • Added 'Driver Description' and 'Driver Version' columns.
    • The status and version of usb.ids (The VendorID/ProductID file) is now displayed in the right side of the bottom status bar. Clicking this usb.ids status will open http://www.linux-usb.org/usb.ids in your default Web browser.
  • Version 1.70
    • Added option to execute a command when you unplug a USB device (In 'Advanced Options' window)
  • Version 1.67
    • You can now send the USB devices information to stdout by specifying an empty filename (') in the command-line. (For example: usbdeview.exe /stext ' >> c:tempusb.txt)
    • Added new variables to the execute command option: %device_type%, %service_name%, %device_class%, and %device_mfg%
  • Version 1.65
    • Added 'Power' column, which displays the power required by the device in mA. (Works only forlocal computer)
  • Version 1.60
    • Added 2 new columns: 'Device Class' and 'Device Mfg'.
  • Version 1.56
    • Fix bug: when saving USB devices list from command-line, USBDeview saved all items, without considering the last saved configuration.
    • Added command-line options that controls what devices to save or display (/DisplayDisconnected, /DisplayHubs, /DisplayNoPortSerial, /DisplayNoDriver).
  • Version 1.55
    • Added 3 new columns of service/driver information: Service Name, Service Description, Driver Filename.
  • Version 1.50
    • Improved drive letter detection: USBDeview now also detect the drive letter of hard-disk drives connected to USB. (This improvement only works only for local computer)
  • Version 1.48
    • Fixed bug: USBDeview didn't allow you to make a speed test when the drive letter of the USB drive was A: or B:
  • Version 1.47
    • Fixed bug: USBDeview displayed wrong drive letters when the serial number or ParentId Prefix contained only one character.
    • Added a separated version for x64 systems, in order to allow you to disable/enable items on x64 systems.
  • Version 1.46
    • Added 'ParentId Prefix' column, which shows the ID string of the parent device.
  • Version 1.45
    • Fixed bug: On Windows Vista/7, USBDeview failed to detect that USB devices are disabled.
    • Added support for sorting the USB devices list from command-line.
  • Version 1.43
    • Fixed issue with Windows 7/Vista: The description field displayed unneeded prefix string like '@oem4.inf,%athr.devicedesc.5523%'.
  • Version 1.42
    • Added a few reliability checks for flash drive speed tests.If USBDeview detect that the final speed test result might not be reliable, an error message will be displayed.
  • Version 1.41
    • Fixed issue: When USBDeview window is hidden and there is an icon in the taskbar, running USBDeview again will open the existing instance of USBDeview, instead of creating another one.
  • Version 1.40
    • Added 'Speed Test' option for testing the read/write speed of your USB flash drive.Also, Added an option to publish your speed test results in http://usbspeed.nirsoft.net.
  • Version 1.36
    • Fixed bug: USBDeview didn't display some partly installed devices.
  • Version 1.35
    • Added 'Vendor Name' and 'Product Name' columns. (Requires to download an external USB IDs file)
    • New variables in command-string: %vid_hex% and %pid_hex% (vid and pid values as hexadecimal number)
    • Add icons legend in the help file and in the Web page.
  • Version 1.30
    • Added new option: Show Time In GMT.
  • Version 1.29
    • Fixed bug: For USB flash drives with multiple drives (like SanDisk Cruzer With U3), USBDeviewdisplayed only one drive letter randomly. Now it can display multiple drive letters.
  • Version 1.28
    • Added command-line options: /stop_by_pid, /disable_by_pid, /enable_by_pid, /remove_by_pid
  • Version 1.27
    • Added new option: Open In RegEdit.
  • Version 1.26
    • The 'Advanced Options' dialog-box is now resizable.
    • Added 'USB Hub' column (yes/no).
  • Version 1.25
    • Added Disable+Enable option - gives you the affect similar to unplugging and then plugging back the device.
    • Added 'Open Drive' option (For USB flash drives).
  • Version 1.22
    • Added new command line options: /remove_all_connected, /remove_all_disconnected
    • Fixed bug: using /remove_all removed also the USB hubs and caused the USB to stop working untilrestarting the computer.
  • Version 1.21
    • Added new option: Select Another Font.
  • Version 1.20
    • Added new command-line options to disable/enable/remove USB devices.
  • Version 1.18
    • Fixed bug: The main window lost the focus when the user switched to another application and then returned back to USBDeview.
  • Version 1.17
    • Fixed bug in saving as comma-delimited file when description or name fields contained comma character.
  • Version 1.16
    • Added support for saving comma-delimited (.csv) files.
    • Added new command-line option: /scomma
  • Version 1.15
    • New options: Disable/enable the selected USB devices (Works only with admin rights)
    • New Option: Start USBDeview As Hidden (Only when 'Put Icon On Tray' is turned on)
  • Version 1.12
    • The configuration is now saved to a file, instead of the Registry.
    • New option: Display a balloon in the tray icon when a new device is connected (only for Windows XP or above).
  • Version 1.11
    • Fixed bug: Changing the status of 'Put Icon On Tray' also changed the status of 'Show Tooltips'.
  • Version 1.10
    • New Option: Put Icon On Tray
    • New Option: AutoPlay on selected devices.
    • New Option: AutoPlay When Device Is Connected.
    • New Option: Execute a command when you insert a USB device. (In Advanced Options)
    • New Option: Disconnect All Devices.
  • Version 1.06
    • Added Disconnect/Uninstall buttons to the toolbar.
  • Version 1.05
    • New command-line option: /regfile
    • New option: Display USB Hubs.
  • Version 1.03 - New command-line option: /stop_by_class
  • Version 1.02 - New option: Display devices without drivers.
  • Version 1.01 - Fixed bug: In some computers, the USB devices list was loaded from the wrong hardware configuration.
  • Version 1.00 - First release.

Using USBDeview

USBDeview doesn't require any installation process or additional DLL files.Just copy the executable file (USBDeview.exe) to any folder you like, and run it.
The main window of USBDeview displays all USB devices installed on your system.You can select one or more items, and then disconnect (unplug) them , uninstall them, or just savethe information into text/xml/html file.

USBDeview Columns Description

  • Device Name:Specifies the device name. For some device, this column may display meaningless name, like 'USB Device'.If the device name is meaningless, try to look at the Description column.
  • Device Description:The description of the device.
  • Device Type:The device type, according to USB class code.For more information about USB classes: USB Class Codes.
  • Connected:Specifies whether the device is currently connected to your computer.If the device is connected, you can use the 'Disconnect Selected Devices' option (F9) to disconnect the device.
  • Safe To Unplug:Specifies whether it's safe to unplug the device from the USB plug without disconnecting it first.If the value of this column is false, and you want to unplug this device, you must first disconnect this device by using the 'Disconnect Selected Devices' option (F9) of USBDeview utility, orby using the 'Unplug or Eject Hardware' utility of Windows operating system.
  • Drive Letter:Specifies the drive letter of the USB device.This column is only relevant to USB flash memory devices and to USB CD/DVD drives.Be aware that USBDeview cannot detect drive letters of USB hard-disks.
  • Serial Number:Specifies the serial number of the device.This column is only relevant to mass storage devices (flash memory devices, CD/DVD drives, and USB hard-disks).
  • Registry Time 1:This date/time value is taken from the timestamp of the device Registry key.In many cases, this date/time value represents the time that you first plugged the device to the USB port.However, be aware that in some circumstances this value may be wrong.Also, On Windows 7, this value is initialized with the current date/time on every reboot.
  • Registry Time 2:This date/time value is taken from the timestamp of the device Registry key.On some systems this time values Specifies the last time that you plugged/unplugged the device.This date value is lost when you restart the computer.
  • VendorID/ProductID:Specifies the VendorID and ProductID of the device.For unofficial list of VendorID/ProductID, click here.
  • USB Class/Subclass/Protocol:Specifies the Class/Subclass/Protocol of the device according to USB specifications.For more information about USB classes: USB Class Codes.
  • Hub/Port:Specifies the hub number and port number that the device was plugged into.This value is empty for mass storage devices.
  • Install Time:Specifies the date/time when the USB device was installed. USBDeview can read this property only when you run it as Administrator.This property is stored under Properties{83da6326-97a6-4088-9453-a1923f573b29} subkey, property number is 0064.
  • First Install Time:Specifies when the USB device was installed in the first time. USBDeview can read this property only when you run it as Administrator.This property is stored under Properties{83da6326-97a6-4088-9453-a1923f573b29} subkey, property number is 0065.
  • Connect Time:Specifies the last time that the USB device was plugged. USBDeview can read this property only when you run it as Administrator. This property is available only on Windows 10/8.This property is stored under Properties{83da6326-97a6-4088-9453-a1923f573b29} subkey, property number is 0066.
  • Disconnect Time:Specifies the last time that the USB device was unplugged. This property is available only on Windows 10/8.USBDeview can read this property only when you run it as Administrator.This property is stored under Properties{83da6326-97a6-4088-9453-a1923f573b29} subkey, property number is 0067.

USBDeview Icons Legend

Quanta Port Devices Driver Device

The device is not connected.
The device is connected. It's safe to physically unplug the device without disconnecting it.
The device is connected. You must disconnect the device from USBDeview or from Windows 'Safely Remove Hardware' option before you physically unplug it.
The device is disabled.

Quanta Port Devices Driver Updater

'Vendor Name' And 'Product Name' Columns

Starting from version 1.35, you can view the vendor name and product name of your USB devices.In order to use this feature, you have to download the USB ID's list of Stephen J. Gowdy(http://www.linux-usb.org/usb.ids) and put the file in the same folder of USBDeview.exe
The name of the file must remain as 'usb.ids'.

Speed Test for USB Flash Drives

Starting from version 1.40, USBDeview allows you to test the read/write speed of your USB flash drive.The test is made by writing a large file (named $speed_test_nirsoft$.dat) into your USB flash drive, and then reading it back for testing the read speed.Be aware that you need at least 100 MB of free disk space in order to successfully make this speed test.Also, be aware that this test is made with sequential read and write operations. When using multiple small files, the read/write performances are usually much lower than sequential read/write.

In order to make a speed test to your flash drive, simply select the desired item in the main window, and then choose the 'Speed Test' option from the File menu, or press Ctrl+T.In the speed test window, verify that the selected drive letter is the right one, and then press the 'Start Test' button.Wait a few seconds until the write and read tests are finished.

Publishing Your Speed Test Result

If you want to share your speed test results, so other people that want to purchase a USB flash drive will be able to easily compare the speedof different flash drives, you can use the 'Publish Test Result' option to do that.

When you successfully finish a speed test, the 'Publish Test Result' button is automatically enabled.Clicking this button opens a new window that displays all the data that will be sent to http://usbspeed.nirsoft.net Web site, and ask you the confirm the speed test publishing.Be aware that only the data displayed in this window is transmitted to http://usbspeed.nirsoft.net Web site.USBDeview doesn't send the serial number of your USB device or any other information that may violate your privacy.


Starting from version 1.10, USBDeview allows you to automatically run a file on USB flash memory devices, according to AutoRun.inf filename.You can manually activate the AutoPlay feature by selecting the desired device and pressing F8.Alternatively, You can check the 'AutoPlay When Device Is Connected' option, and then the AutoPlayfeature will be automatically activated when you insert a USB flash memory device.

Quanta Port Devices Driver

Be aware that this feature only works if USBDeview detects the drive letter of the device.

Execute a command when you insert a USB device

Starting from version 1.10, USBDeview allows you to execute a command from exe/cmd/bat file in every time that inserta USB device to your system.In order to use this feature, go to 'Options->Advanced Options', select the 'Execute..' check-box, and typethe exe/cmd file that you want to run.You can also use the following special variables in this command string: %device_name%, %device_desc%, %drive%, %serial_number%, %vid%, %pid%, %vid_hex%, %pid_hex%, %device_type%, %service_name%, %device_class%, %device_mfg%
USBDeview will automatically replace these variables with the appropriate data of the device that you inserted.For example, if you want to pass to your exe file 2 parameters - the serial number of the device, and the drive letter:
c:temptest.exe '%serial_number%' '%drive%'

Known Limitations/Issues

  • For all devices except 'Mass Storage' Devices:If you plug a device to one USB port, and then you plug the same device to another USB port, a newrecord of the same device will be created for each USB port that you plug. So if you see multiple lines for exactly the same device, it means that you plugged it to different USB ports. The USB ports that you plugged are specified in 'Hub/Port' column.
    However, for 'Mass Storage' device, only one record is created for each device, even if you plug it todifferent USB port.
  • When a USB device is added/removed on your local computer, UDBDeview utility automatically updates the list of USB devices.
    But... If you UDBDeview is connected to a remote computer, the list won't refresh automatically when a deviceis added or removed. You must refresh it manually, by pressing F5 key.

Connecting To Remote Computer

The following command-line options allows you to connect to remote computers.You must login to the remote computer with admin user in order to use these options.
  • /remote <Computer Name>
    Allows you to connect a single remote computer.
    For Example:
    USBDeview.exe /remote MyComp
  • /remotefile <Computers List File>
    Allows you to connect multiple computers, and view all their USB activity in one window.The computers list file should be a simple Ascii text file with computer names separated by colon, semicolon, space, tab characters or CRLF.
    For Example:
    USBDeview.exe /remotefile 'c:tempcomp.txt'
In order to successfully get full admin access to the remote computer, read this Blog post:How to connect a remote Windows 7/Vista/XP computer with NirSoft utilities.

Connecting To external SYSTEM registry file

If you have the 'SYSTEM' registry file of external operating system, you can usethe following command-line option to read the USB devices list from it:
/regfile <SYSTEM Registry File>Quanta port devices driver updater

For Example:
USBDeview.exe /regfile 'c:tempregfilesSYSTEM'
USBDeview.exe /regfile 'd:windowssystem32configSYSTEM'

This option has some limitations:

  • You cannot read a Registry file of Windows XP/2003/Vista from Windows 2000 Machine.
  • USBDeview works in read-only mode. (You cannot uninstall a device from external file)

Stop/Disconnect Command-Line Options

  • /stop {/showmsg} {RemoteComputer} <Device Name>
    Stop/disconnect a USB device by specifying its name or description.
    You don't have to specify the whole name or description.You can also specify only a part of the name or description string, and USBDeviewwill identify it. For example, If the device name is 'Kingston DataTraveler 2.0', you can simply put 'kingston' or 'DataTraveler' in the device name parameter, and USBDeview will disconnect theright device.You can also specify the instance ID string of the device.
    If you want that a message/balloon will be displayed after the device is disconnected, add the '/showmsg' parameter. (Windows 2000 displays a message-box, Windows XP displays a balloon)
    If you want to disconnect a device in a remote computer, specify the remote computer name,with prefix. You must login to the remote computer with admin rights in order to do that.
    USBDeview.exe /stop /showmsg 'DVD RW'
    USBDeview.exe /stop 'DataTraveler'
    USBDeview.exe /stop comp01 'SanDisk Cruzer'
    USBDeview.exe /stop 'USBVid_1058&Pid_10238539583490834690'
  • /stop_by_serial {/showmsg} {RemoteComputer} <Device Serial>
    Similar to /stop command, but instead of specifying a device name, you should specify the serial number of the device. Works only with mass storage devices.
    USBDeview.exe /stop_by_serial ea051261
    USBDeview.exe /stop_by_serial /showmsg 876534513
  • /stop_by_drive {/showmsg} {RemoteComputer} <Drive Letter>
    Stop/disconnect a USB device by specifying its drive letter.Works only with USB flash drives and CD/DVD devices.
    USBDeview.exe /stop_by_drive g:
    USBDeview.exe /stop_by_drive /showmsg f:
    USBDeview.exe /stop_by_drive /showmsg comp02 t:
  • /stop_by_class {/showmsg} {RemoteComputer} <USB Class;USB SubClass;USB Protocol>
    Stop/disconnect a USB device by specifying the class/subclass/protocol combination.
    For example, if you want to stop all 'Mass Storage' devices, you should specify the following class/subclass/protocol combination: 08;06;50
    USBDeview.exe /stop_by_class /showmsg 08;06;50
    USBDeview.exe /stop_by_class 03;01;02
  • /stop_by_pid {/showmsg} {RemoteComputer} <VendorID;ProductID>
    Stop/disconnect a USB device by specifying the VendorID/ProductID. You can specify only the VendorID if you want to disconnect all devices with that VendorID.
    USBDeview.exe /stop_by_pid /showmsg 13fe;1a00
    USBDeview.exe /stop_by_pid 04f9
  • /stop_all {/showmsg} {RemoteComputer}
    Stop/disconnect all USB devices currently connected to your computer.

Disable/Enable/Remove Command-Line Options

Starting from version 1.20, you can also use the following commands to disable, enable or remove USB devices from command-line:
  • /disable {RemoteComputer} <Device Name>
  • /disable_by_serial {RemoteComputer} <Device Serial>
  • /disable_by_drive {RemoteComputer} <Drive Letter>
  • /disable_by_class {RemoteComputer} <USB Class;USB SubClass;USB Protocol>
  • /disable_by_pid {RemoteComputer} <VendorID;ProductID>
  • /disable_all {RemoteComputer}
  • /enable {RemoteComputer} <Device Name>
  • /enable_by_serial {RemoteComputer} <Device Serial>
  • /enable_by_drive {RemoteComputer} <Drive Letter>
  • /enable_by_class {RemoteComputer} <USB Class;USB SubClass;USB Protocol>
  • /enable_by_pid {RemoteComputer} <VendorID;ProductID>
  • /enable_all {RemoteComputer}
  • /disable_enable {RemoteComputer} <Device Name>
  • /disable_enable_by_serial {RemoteComputer} <Device Serial>
  • /disable_enable_by_drive {RemoteComputer} <Drive Letter>
  • /disable_enable_by_class {RemoteComputer} <USB Class;USB SubClass;USB Protocol>
  • /disable_enable_by_pid {RemoteComputer} <VendorID;ProductID>
  • /disable_enable_all {RemoteComputer}
  • /remove {RemoteComputer} <Device Name>
  • /remove_by_serial {RemoteComputer} <Device Serial>
  • /remove_by_drive {RemoteComputer} <Drive Letter>
  • /remove_by_class {RemoteComputer} <USB Class;USB SubClass;USB Protocol>
  • /remove_by_pid {RemoteComputer} <VendorID;ProductID>
  • /remove_all {RemoteComputer}
  • /remove_all_connected - Remove all connected USB devices.
  • /remove_all_disconnected - Remove all disconnected USB devices.
Disable, enable and remove actions require elevation ('Run As Administrator').You can use the above command-line options with elevation by adding /RunAsAdmin to the command, for example:
USBDeview.exe /RunAsAdmin /disable 'USBVid_1058&Pid_10238539583490834690'

Check if a device is connected/disconnected or enabled/disabled

Starting from version 2.70, you can check whether a device is connected/disconnected or enabled/disabled by using the following command-line options:
  • /is_connected {RemoteComputer} <Device Name>
  • /is_connected_by_serial {RemoteComputer} <Device Serial>
  • /is_connected_by_drive {RemoteComputer} <Drive Letter>
  • /is_connected_by_class {RemoteComputer} <USB Class;USB SubClass;USB Protocol>
  • /is_connected_by_pid {RemoteComputer} <VendorID;ProductID>
  • /is_disabled {RemoteComputer} <Device Name>
  • /is_disabled_by_serial {RemoteComputer} <Device Serial>
  • /is_disabled_by_drive {RemoteComputer} <Drive Letter>
  • /is_disabled_by_class {RemoteComputer} <USB Class;USB SubClass;USB Protocol>
  • /is_disabled_by_pid {RemoteComputer} <VendorID;ProductID>

Quanta Port Devices Drivers

When using the above commands, USBDeview returns the number of disabled or connected devices that match the specified string.
For example, the following batch file will display 1 if the device with serial number 7538957348957398 is connected or 0 if the device is not connected:
USBDeview.exe /is_connected_by_serial '7538957348957398'

Save Command-Line Options

/stab <Filename>Save the list of all USB devices into a tab-delimited text file.
/stabular <Filename>Save the list of all USB devices into a tabular text file.
/sverhtml <Filename>Save the list of all USB devices into HTML file (Vertical).
/sort <column>This command-line option can be used with other save options for sorting by the desired column.If you don't specify this option, the list is sorted according to the last sort that you made from the user interface.The <column> parameter can specify the column index (0 for the first column, 1 for the second column, and so on) orthe name of the column, like 'Device Name' and 'Description'.You can specify the '~' prefix character (e.g: '~Description') if you want to sort in descending order.You can put multiple /sort in the command-line if you want to sort by multiple columns.

USBDeview.exe /shtml 'f:tempusb-list.html' /sort 2 /sort ~1
USBDeview.exe /shtml 'f:tempusb-list.html' /sort 'Device Type' /sort 'Device Name'

/DisplayDisconnected <0 1>Specifies whether to show disconnected devices. 0 = No, 1 = Yes.
/DisplayNoDriver <0 1>Specifies whether to show devices without driver. 0 = No, 1 = Yes.
/RetrieveUSBPower <0 1>Specifies whether to retrieve USB power/version information.
/TrayIcon <0 1>Specifies whether to start USBDeview with a tray icon.
/cfg <Filename>Start USBDeview with the specified configuration file.For example:
USBDeview.exe /cfg 'c:configudv.cfg'
USBDeview.exe /cfg '%AppData%USBDeview.cfg'

Translating USBDeview to other languages

In order to translate USBDeview to other language, follow the instructions below:
  1. Run USBDeview with /savelangfile parameter:
    USBDeview.exe /savelangfile
    A file named USBDeview_lng.ini will be created in the folder of USBDeview utility.
  2. Open the created language file in Notepad or in any other text editor.
  3. Translate all string entries to the desired language.Optionally, you can also add your name and/or a link to your Web site. (TranslatorName and TranslatorURL values) If you add this information, it'll be used in the 'About' window.
  4. After you finish the translation, Run USBDeview, and all translated strings will be loaded from the language file.
    If you want to run USBDeview without the translation, simply rename the language file, or move it to another folder.


If you have any problem, suggestion, comment, or you found a bug in my utility, you can send a message to [email protected]
Download USBDeview
Download USBDeview for x64 systems
Check Download MD5/SHA1/SHA256 Hashes
USBDeview is also available in other languages. In order to change the language of USBDeview, download the appropriate language zip file, extract the 'usbdeview_lng.ini', and put it in the same folder that you Installed USBDeview utility.
LanguageTranslated ByDateVersion
ArabicMohamed.Bajdouai13/12/2015USBDeview v2.51
Brazilian PortugueseGeraldo Coimbra29/02/20202.86
Brazilian PortuguesePaulo Guzmán11/09/20182.75
BulgarianHristo Drumev15/09/2007
CzechMiroslav Machacek10/04/2010
CzechShar (viteco(at-sign)centrum.cz)12/09/20203.01
DanishChristian Læssøe29/10/2009
DutchJan Verheijen10/09/20203.01
FrenchEric FICHOT15/09/20203.01
French07/08/2017 2.71
FrenchCyril KRR28/06/20192.80
GalicianXosé Antón Vicente Rodríguez13/01/2007
German«Latino» auf WinTotal.de10/09/20203.01
HungarianTamás Ferenc19/06/20162.60
ItalianLuca Barattini (MS)31/08/2016
JapaneseISHIGAKI, Kazuhito08/06/2009
KoreanJ. K. Lee.(Wave)24/09/2019v2.80
NorwegianJohnny Dag Hansen28/07/2009
RomanianJaff (Oprea Nicolae)05/02/20162.52
RussianDmitry Yerokhin11/09/20203.01
Simplified Chinese火焰大佐09/04/20162.55
Simplified ChineseDaiXQ021_2.86汉化版07/03/20202.86
Simplified ChineseDickMoore08/10/20203.01
SlovakFrantišek Fico15/09/20203.01
SlovakJuraj Vana20/10/20152.46
SwedishGöran Helsingborg05/12/20182.78
Traditional ChineseWing Lee11/07/20142.35
Traditional ChineseDanfong Hsieh22/09/2020
Traditional ChineseAbel Chuang19/06/20122.11
Thaiประสิทธิ์ แคภูเขียว26/03/2008
TurkishCemil Kaynar25/03/20172.65
Ukrainian Lembergman, March 201830/03/20182.75