Upgrading to RT 8.1 broke this driver - windows doesn't recognize the driver signature anymore and refuses to start the device, although it is still detected and installed properly. Until a new driver turns up, or a work-around or hack has been found: don't upgrade to RT 8.1 if you need wired Ethernet! I'll post back if I find a solution. Uninstall and Reinstall the Network Card Drivers. Step 1: Uninstall the Network Adapter Drivers. Press “Windows Logo” + “X” keys on the keyboard. Click on “Device Manager” from that list. Search for the Network Adapter from the device list, right click on it and then select “Uninstall”. So, lets walk through the device management and control of devices. USB Device management on Windows. Once a USB device has been inserted within the windows ecosystem, the device driver(s) have been installed and the ability to prevent use is no longer available, until the driver(s) have been removed/uninstalled. Installing the Cisco Microsoft Windows USB Device Driver. The first time a Microsoft Windows based PC is connected to the router, a USB driver must be installed. Installing the Cisco Microsoft Windows XP USB Driver. This procedure shows how to install the Microsoft Windows XP USB driver.

Describes the architecture of the USB function stack.

On a USB device, the USB function stack refers to a group of drivers that are enumerated by the Plug and Play Manager, when ACPI creates a USB device physical device object (PDO).

In a single configuration device, a USB device can define one or more interfaces. For example, the Media Transfer Protocol (MTP) for transferring files to and from the device. A composite USB device can support multiple interfaces in a single configuration. The USB function stack creates PDOs for each interface and PnP Manager loads the class driver that creates the function device object (FDO) for that interface.

The USB function stack is conceptualized in this image:

Applications and Services

• All user-mode requests are sent to the Microsoft-provided kernel-mode class driver GenericUSBFn.sys. You can create a user-mode service that communicates with GenericUSBFn.sys by sending I/O control codes (IOCTLs) as defined in genericusbfnioctl.h. For more information about these IOCTLs see Communicating with GenericUSBFn.sys from a user-mode service

USB function class driver

A USB function class driver implements the functionality of a specific interface (or group of interfaces) on the USB device. MTP and IpOverUsb are examples of system-supplied class drivers. The class driver may be implemented purely as a kernel-mode driver, or it may be a user-mode service paired with the system-supplied class driver GenericUSBFn.sys.

A function class driver sends requests to the controller by using USB function class driver to UFX programming interfaces.

USB function class extension (UFX)

The USB function class extension (UFX) is a system-supplied extension to Kernel-Mode Driver Framework (KMDF). USB is a standard bus and has some required functionality and capabilities. UFX is responsible for implementing USB function logic that is common to all USB function controllers and handling and/or dispatching requests from USB function class drivers. In particular, UFX handles the process of enumerating the device and processing standard control transfers. To perform some of these operations, UFX needs to know about the capabilities of the bus. Those capabilities are reported to UFX when the class-extension interface is established.

UFX exposes standard IOCTLs that the upper layers (USB function class driver and user mode services) can use to send requests to the controller. Additionally, UFX notify upper layers about the standard requests received from the host.

USB function client driver

UFX provides an abstracted interface that works consistently across different controllers. However, controllers have different capabilities, with limitations such as the number of endpoints, the types of endpoints, low power, remote wake-up. For example, certain controllers support DMA, while others do not. Some controllers implement streams in the hardware while other controllers expect the driver to handle streams. For these reasons, only common functionality is handled in UFX. Transfers, power management, stream support, and other features which vary from controller to controller are handled by the client driver.

The USB function client driver is responsible for implementing controller-specific operations. These include implementing endpoint data transfers, USB device state changes (reset, suspend, resume), attach/detach detection, port/charger detection. The client driver is also responsible for handling power management, and PnP events.

The function client driver is written as Kernel-Mode Driver Framework (KMDF) driver by using USB function class driver to UFX programming interfaces.

Microsoft provides in-box function client drivers (UfxChipidea.sys, Ufxsynopsys.sys) for ChipIdea and Synopsys controllers.

USB lower filter driver

A USB lower filter driver supports detection of chargers if the function controller uses the in-box Synopsys and ChipIdea drivers. The filter driver manages USB charging starting from USB port detection. t must publish a GUID for each charger type it supports, and a list of that charger’s properties. If a specific charger is configurable, the lower USB filter driver defines a list of supported PropertyIDs and their corresponding value types that can be sent to it, to configure the charger. The driver also notifies the battery stack when it can begin charging and the maximum amount of current the device can draw. For client drivers other than Synopsys and ChipIdea drivers, charging logic can be implemented in the client driver.

A function class driver sends request to UFX by using Programming interfaces for supporting proprietary chargers.

Related topics

Note

Please use the PnPUtil tool instead of DevCon.

DevCon (Devcon.exe), the Device Console, is a command-line tool that displays detailed information about devices on computers running Windows. You can use DevCon to enable, disable, install, configure, and remove devices.

DevCon runs on Microsoft Windows 2000 and later versions of Windows.

This section includes:

What you can do with DevCon

Windows driver developers and testers can use DevCon to verify that a driver is installed and configured correctly, including the proper INF files, driver stack, driver files, and driver package. You can also use the DevCon commands (enable, disable, install, start, stop, and continue) in scripts to test the driver.

DevCon is a command-line tool that performs device management functions on local computers and remote computers.

Note To run DevCon commands on a remote computer, the Group Policy setting must allow the Plug and Play service to run on the remote computer. On computers that run Windows Vista and Windows 7, the Group Policy disables remote access to the service by default. On computers that run Windows 8 and later operating systems, the remote access is unavailable.

Installing The Cisco Microsoft Windows Usb Device Driver

Devcon features include:

Cisco Microsoft Windows Usb Device Driver

• Display driver and device info DevCon can display the following properties of drivers and devices on local computers, and remote computers (running Windows XP and earlier):

  • Hardware IDs, compatible IDs, and device instance IDs. These identifiers are described in detail in Device Identification Strings.
  • The devices in a device setup class
  • INF files and device driver files
  • Details of driver packages
  • Hardware resources
  • Device status
  • Expected driver stack
  • Third-party driver packages in the driver store

• Search for devices DevCon can search for devices on a local or remote computer by hardware ID, device instance ID, or device setup class.

• Change device settings DevCon can change the status or configuration of Plug and Play (PnP) devices on the local computer in the following ways:

  • Enable a device
  • Disable a device
  • Update drivers (interactive and noninteractive)
  • Install a device (create a devnode and install software)
  • Remove a device from the device tree and delete its device stack
  • Rescan for Plug and Play devices
  • Add, delete, and reorder the hardware IDs of root-enumerated devices
  • Change the upper and lower filter drivers for a device setup class
  • Add and delete third-party driver packages from the driver store

• Restart the device or computer DevCon can restart a local device, reboot the local system on demand, or reboot the local system if required for another DevCon operation.

DevCon source code

The DevCon source code is also available so that you can examine the methods that DevCon uses to retrieve and change setup and configuration data. DevCon illustrates the use of general setup functions, device installation functions, and PnP Configuration Manager functions. The source code for the Device Console (DevCon) Tool is available in the Windows driver samples repository on GitHub.

Related topics