Update ALL your missing drivers with just 1 click
What is Windows USB Troubleshooter ?
Microsoft has released a USB Troubleshooter for Windows 7, 8 & Windows 10. This tool will help Windows users to rectify common issues related to USB. Errors/issues such as “USB Device not recognized”, “USB Device Not Installing”, “Computer no longer connects to the phone via USB” can be fixed using this USB troubleshooting tool. Errors related to flash drives, keyboards, mice, external hard drives, Printers, Scanner, Mobile, cameras etc. can be rectified using this troubleshooter tool if the issue is not hardware-related. Find more about USB device errors and solutions here.
How to use USB troubleshooter for Windows ?
- Download and run the Windows USB Troubleshooter for Windows 7, 8 & 10 (WinUSB.diagcab)
- Run this troubleshooter as administrator
- Click “Next” to begin the diagnostics.
Next, The troubleshooter starts detecting problems..
This tool will automatically detect and clear issues with USB. USB audio, storage, and print devices—such as thumb drives, USB hard drives, and USB printers—that do not eject using the Safely Remove Hardware dialog box.
Download USB Troubleshooter for Windows 7, 8 & 10 (WinUSB.diagcab)
Issues that can be fixed using this troubleshooter
USB Devices Not Recognized |
USB Stopped Working After Latest Update |
Device Not Installing |
USB Not Detected |
USB Mouse Is Not Working On Windows 10 |
USB Drive Will Not Open |
USB Driver Problem |
USB Ports Are Not Detecting Any Devices |
USB Reconnecting Continuously With Blank Screen |
The computer no longer connects to the phone via USB |
USB not working |
How to Diagnose and Fix the Most Common Windows USB Issues
The most common windows usb issues are device install error code 0x80070005 and the device is not recognized by the computer.
There are different ways to fix this issue. One way is to uninstall and reinstall the USB device, another way is to disable driver signature enforcement, and lastly, you can use a third-party utility like Driver Easy to scan for corrupted or outdated drivers. The Windows 10 Device Install Error Code 0x80070005 error occurs when your computer does not recognize the new USB device you are trying to install. This error can be caused by any of the following:
- The USB port on your computer may be damaged or defective.
- The USB device may be incompatible with your system’s hardware or software configuration.
- The USB cable connecting the device to your computer is defective.To fix this issue, try reinstalling the USB driver or disconnecting and reconnecting your USB device. If you don’t see any improvement after trying these fixes, try disabling Driver Signature Enforcement in Windows 10. .If the issue persists, try using a different USB cable. If you’re not using a USB device such as a mouse or keyboard and are just trying to charge your device through the USB port, try moving it to another USB port on your computer.
- The USB device may be incompatible with your system’s hardware or software configuration.
- The USB cable connecting the device to your computer is defective.To fix this issue, try reinstalling the USB driver or disconnecting and reconnecting your USB device. If you don’t see any improvement after trying these fixes, try disabling Driver Signature Enforcement in Windows 10
List of Builtin Windows System USB Drivers
- Usbccgp.sys
- Usb.inf
- WudfUsbBID.dll
- WudfUsbBIDAdvanced.inf
- Wpdusb.sys
- Winusb.sys
- Winusb.inf
How to Verify Drivers installed on Windows 10/11 ?
Windows have a built-in tool called “Driver Verifier Manager”. This tool is built to verify and validate device drivers installed on Windows OS. Driver Verifier Manager is capable of a variety of functions such as displaying all drivers installed on the computer, Signed and unsigned driver list, schedule & verifying drivers, etc.
SYNTAX:
verifier {/? | /help}
verifier /standard /all
verifier /standard /driver <name> [<name> ...]
verifier {/ruleclasses | /rc} <options> [<ruleclass_1> <ruleclass_2> ...] /all
verifier /flags <options> [<options> ...] /all
verifier /flags <options> [<options> ...] /driver <name> [<name> ...]
verifier /rules {query | reset | default <id> | disable <id>}
verifier /query
verifier /querysettings
verifier /bootmode {persistent | resetonbootfail | oneboot | resetonunusualshutdown}
verifier /persistthroughupgrade
verifier /reset
verifier /faults [probability [pool_tags [applications [delay_minutes]]]]
verifier /faultssystematic [<options> ...]
verifier /log <file_name> [/interval <seconds>]
verifier /volatile /flags <options> [<options> ...]
verifier /volatile /adddriver <name> [<name> ...]
verifier /volatile /removedriver <name> [<name> ...]
verifier /volatile /faults [probability [pool_tags [applications
[delay_minutes]]]]
verifier /domain {wdm | ndis | ks | audio} [rules.all | rules.default ]
/driver ... [/logging | /livedump]
verifier /logging
verifier /livedump
PARAMETERS:
/? or /help
Displays this help message.
/standard
Specifies standard Driver Verifier flags.
/all
Specifies that all installed drivers will be verified after the next
boot.
/driver <name> [<name> ...]
Specifies one or more drivers (image names) that will be verified.
Wildcard values (e.g. n*.sys) are not supported.
/driver.exclude <name> [<name> ...]
Specifies one or more drivers (image names) that will be excluded
from verification. This parameter is applicable only if all drivers
are selected for verification. Wildcard values (e.g. n*.sys) are not
supported.
/flags <options> [<options> ...]
Specifies one or more options that should be enabled for verification.
Flags are applied to all drivers being checked by Driver Verifier. The
provided options values must be either in decimal, hexadecimal ("0x"
prefix), octal ("0o" prefix) or binary ("0b" prefix) format.
Standard Flags:
Standard Driver Verifier options can be specified using '/standard'.
WDF verification is included in /standard but is not shown here.
0x00000001 (bit 0) - Special pool
0x00000002 (bit 1) - Force IRQL checking
0x00000008 (bit 3) - Pool tracking
0x00000010 (bit 4) - I/O verification
0x00000020 (bit 5) - Deadlock detection
0x00000080 (bit 7) - DMA checking
0x00000100 (bit 8) - Security checks
0x00000800 (bit 11) - Miscellaneous checks
0x00020000 (bit 17) - DDI compliance checking
Additional Flags:
These flags are intended for specific scenario testing. Flags marked
with (*) require I/O Verification (bit 4) that will be automatically
enabled. Flags marked with (**) support disabling of individual
rules.
0x00000004 (bit 2) - Randomized low resources simulation
0x00000200 (bit 9) - Force pending I/O requests (*)
0x00000400 (bit 10) - IRP logging (*)
0x00002000 (bit 13) - Invariant MDL checking for stack (*)
0x00004000 (bit 14) - Invariant MDL checking for driver (*)
0x00008000 (bit 15) - Power framework delay fuzzing
0x00010000 (bit 16) - Port/miniport interface checking
0x00040000 (bit 18) - Systematic low resources simulation
0x00080000 (bit 19) - DDI compliance checking (additional)
0x00200000 (bit 21) - NDIS/WIFI verification (**)
0x00800000 (bit 23) - Kernel synchronization delay fuzzing
0x01000000 (bit 24) - VM switch verification
0x02000000 (bit 25) - Code integrity checks
/ruleclasses or /rc [<ruleclass_1> <ruleclass_2> ... <ruleclass_k>]
This parameter is larger set of '/flags' above. While '/flags' is
limited to 32 bit bitmap expression, this can include more than 32
verification classes. Each positive decimal integer represents a
verification class. Multiple classes can be expressed by separating
each class id with space character. Following rule classes IDs are
available and leading 0's can be omitted.
Standard Rule Classes:
1 - Special pool
2 - Force IRQL checking
4 - Pool tracking
5 - I/O verification
6 - Deadlock detection
8 - DMA checking
9 - Security checks
12 - Miscellaneous checks
18 - DDI compliance checking
34 - WDF Verification
Additional Rule Classes:
These rule classes are intended for specific scenario testing. Rule
classes are marked with (*) require I/O Verification (5) that will
be automatically enabled. Flags marked with (**) support disabling
of individual rules.
3 - Randomized low resources simulation
10 - Force pending I/O requests (*)
11 - IRP logging (*)
14 - Invariant MDL checking for stack (*)
15 - Invariant MDL checking for driver (*)
16 - Power framework delay fuzzing
17 - Port/miniport interface checking
19 - Systematic low resources simulation
20 - DDI compliance checking (additional)
22 - NDIS/WIFI verification (**)
24 - Kernel synchronization delay fuzzing
25 - VM switch verification
26 - Code integrity checks
/log.code_integrity
This option suppresses Code Integrity violation breaks and collects
only statistics for verified drivers. Statistics could be extracted
via /log option or kernel debugger. This parameter is applicable only
if Code Integrity checks are enabled.
/rules {query | reset | default <id> | disable <id>}
Specifies rules level control (advanced).
query Shows current status of controllable rules.
reset Resets all rules to their default state.
default <id> Sets rule ID to its default state.
disable <id> Disables specified rule ID.
/query
Display runtime Driver Verifier statistics and settings.
/querysettings
Displays a summary of the options and drivers that are currently
enabled, or options and drivers that will be verified after the
next boot. The display does not include drivers and options added
using /volatile.
/bootmode
Specifies the Driver Verifier boot mode. This option requires system
reboot to take effect.
persistent Ensures that Driver Verifier settings are
persistent across reboots. This is the default
value.
resetonbootfail Disables Driver Verifier for subsequent reboots
if the system failed to start.
resetonunusualshutdown
Driver Verifier persists until unusual shutdown
happens. Its abbrevation, 'rous', can be used.
oneboot Enables Driver Verifier only for the next boot.
/persistthroughupgrade
Makes the Driver Verifier settings persist through upgrade. Driver
Verifier will be active during system upgrade.
/reset
Clears Driver Verifier flags and driver settings. This option requires
system reboot to take effect.
/faults [probability [pool_tags [applications [delay_minutes]]]]
Enable the Randomized low resources simulation feature and optionally
control parameters for the Randomized low resources simulation.
Probability Specifies the probability that Driver Verifier will
fail a given allocation. The value represents the
number of chances in 10,000 that Driver Verifier will
fail the allocation. The default value 600, means
600/10000 or 6.
Pool Tags: Specifies a space separated list of the pool tags to
be injected with faults. By default, any pool
allocation can be injected with faults.
Applications Specifies a space separated list of image file names
(an executable) that will be injected with faults. By
default, any pool allocation can be injected with
faults.
DelayMinutes Specifies the number of minutes after booting during
which Driver Verifier does not intentionally fail any
allocations. This delay allows the drivers to load
and the system to stabilize before the test begins.
The default value is 8 minutes.
/faultssystematic [<options> ...]
Controls the Systematic low resources simulation parameters.
enableboottime Enables fault injections across reboots.
disableboottime Disables fault injections across reboots.
This is the default value.
recordboottime Enables fault injections in 'what if' mode
across reboots.
resetboottime Disables fault injections across reboots and
clears the stack exclusion list.
enableruntime Dynamically enables fault injections.
disableruntime Dynamically disables fault injections.
recordruntime Dynamically enables fault injections in
'what if' mode.
resetruntime Dynamically disables fault injections and
clears the previously faulted stack list.
querystatistics Shows the current fault injection statistics.
incrementcounter Increments the test pass counter used to
identify when a fault was injected.
getstackid <counter> Retrieves the indicated injected stack id.
excludestack <stack_id> Excludes the stack from fault injection.
/log <file_name> [/interval <seconds>]
Creates a log file with the specified name and periodically writes the
runtime statistics to this file. The interval between log file updates
is controlled by the '/interval' parameter. The default value is 30
seconds. Use CTRL+C to close the log and return.
/volatile
Changes Driver Verifier settings without rebooting the computer.
Volatile settings take effect immediately and are in effect until the
next system reboot.
/volatile /adddriver <name> [<name> ...]
Starts the verification for the specified driver or drivers.
/volatile /removedriver <name> [<name> ...]
Stops the verification for the specified driver or drivers.
/domain {wdm | ndis | ks | audio} [rules.all | rules.default] /driver ...
[/logging | /livedump]
Controls the verifier extension settings. The following verifier
extension types are supported:
wdm Enabled verifier extension for WDM drivers.
ndis Enabled verifier extension for networking drivers.
ks Enabled verifier extension for kernel mode
streaming drivers.
audio Enabled verifier extension for audio drivers.
The following extension options are supported:
rules.default Enables default validation rules for the selected
verifier extension.
rules.all Enables all validation rules for the selected
verifier extension.
/logging
Enables logging for violated rules detected by the selected verifier
extensions.
/livedump
Enables live memory dump collection for violated rules detected by
the selected verifier extensions.