Download here: http://gg.gg/wh2yb
Contents
*Cisco Microsoft Windows Usb Device Drivers Downloads
*Cisco Microsoft Windows Usb Device Driver
*Installing The Cisco Microsoft Windows Usb Device Driver
If your Windows 10 phone is already running the latest version of Windows 10 Mobile, try to connect your device to a Windows 10 PC instead. There’s a driver in the device you connected to that isn’t supported in the version of Windows 10 Mobile your phone is running. For information about the supported devices, see Universal Serial Bus (USB). Looking in Device Manager the driver was USB Serial instead of Cisco USB. It kept reverting back to the default Windows driver on every boot. What finally did the trick for me was to right click on the port in device manager and tell it to roll back drivers. It retained them after doing that. A USB device driver must be installed the first time a Microsoft Windows-based PC is connected to the USB console port on the switch. Installing the Cisco Microsoft Windows XP USB Driver. Installing the Cisco Microsoft Windows 2000 USB Driver. Installing the Cisco Microsoft Windows Vista and Windows 7 USB Driver. 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.Accessing the CLI Through Express Setup
You can access the CLI on an unconfigured switch. Set the switch in Express Setup mode and connect a switch Ethernet port to an Ethernet port on your PC or workstation. Follow the steps described in the getting started guide for turning on the switch and using Express Setup.
When the switch is in Express Setup mode, open a Telnet session to the switch by entering the IP address 10.0.0.1. Enter the setup user EXEC command. Enter the information described in the “IP Settings” section on page C-6and the “Completing the Setup Program” section.
After you have entered the configuration information for the switch, save it to flash memory by using the write memory privileged EXEC command.Note
In Express Setup mode, the IP address 10.0.0.1 remains active on the switch until you enter the write memory command. You lose the Telnet connection after entering the write memory command.Accessing the CLI Through the Console Port
You can access the CLI on a configured or unconfigured switch by connecting the RJ-45 console port or USB console port of the switch to your PC or workstation and accessing the switch through a terminal emulation program.Note
If you have stacked your switches, connect to the console port of one of the switches in the stack. You can initially configure the entire stack from any member switch.Connecting the RJ-45 Console Port ProcedureStep 1Connect the RJ-45-to-DB-9 adapter cable to the 9-pin serial port on the PC. Connect the other end of the cable to the switch console port. Step 2Start the terminal-emulation program on the PC or the terminal. The program, frequently a PC application such as HyperTerminal or ProcommPlus, makes communication between the switch and your PC or terminal possible.Step 3Configure the baud rate and character format of the PC or terminal to match the console port default characteristics:
*9600 baud
*8 data bits
*1 stop bit
*No parity
*None (flow control)Step 4Power on the switch as described in the switch getting started guide.Step 5The PC or terminal displays the bootloader sequence. Press Enter to display the setup prompt. Follow the steps in Entering the Initial Configuration Information.Connecting the USB Console PortProcedureStep 1If you are connecting the switch USB console port to a Windows-based PC for the first time, install the USB driver. See Installing the Cisco Microsoft Windows USB Device Driver.Figure 1. Connecting the USB Console Cable to the Switch
1
USB console port (5-pin mini-Type B)
3
USB Type A connection on the laptop
2
USB Type A to 5-pin mini-Type B cableStep 2Connect a USB cable to the PC USB port. Connect the other end of the cable to the switch mini-B (5-pin-connector) USB console port. Step 3Start the terminal-emulation program on the PC or the terminal. The program, frequently a PC application such as HyperTerminal or ProcommPlus, makes communication between the switch and your PC or terminal possible.Step 4Configure the baud rate and character format of the PC or terminal to match the console port default characteristics:
*9600 baud
*8 data bits
*1 stop bit
*No parity
*None (flow control)Step 5Power on the switch as described in the switch getting started guide.Step 6The PC or terminal displays the bootloader sequence. Press Enter to display the setup prompt. Follow the steps in the Setup program.Installing the Cisco Microsoft Windows USB Device Driver
A USB device driver must be installed the first time a Microsoft Windows-based PC is connected to the USB console port on the switch.Installing the Cisco Microsoft Windows XP USB DriverProcedureStep 1Obtain the Cisco USB console driver file from the Cisco.com web site and unzip it.Note
You can download the driver file from the Cisco.com site for downloading the switch software.Step 2If using 32-bit Windows XP, double-click the setup.exe file in the Windows_32 folder. If using 64-bit Windows XP, double-click the setup(x64).exe file in the Windows_64 folder.Step 3The Cisco Virtual Com InstallShield Wizard begins.Step 4The Ready to Install the Program window appears. Click Install.Step 5The InstallShield Wizard Completed window appears. Click Finish.Step 6Connect the USB cable to the PC and the switch console port. The USB console port LED turns green, and the Found New Hardware Wizard appears. Follow the instructions to complete the driver installation.Installing the Cisco Microsoft Windows 2000 USB DriverProcedureStep 1Obtain the Cisco USB console driver file from the Cisco.com web site and unzip it.Note
You can download the driver file from the Cisco.com site for downloading the switch software.Step 2Double-click the setup.exe file.Step 3The Cisco Virtual Com InstallShield Wizard begins. Click Next.Step 4The Ready to Install the Program window appears. Click Install.Step 5The InstallShield Wizard Completed window appears. Click Finish.Step 6Connect the USB cable to the PC and the switch console port. The USB console port LED turns green, and the Found New Hardware Wizard appears. Follow the instructions to complete the driver installation.Installing the Cisco Microsoft Windows Vista and Windows 7 USB DriverProcedureStep 1Obtain the Cisco USB console driver file from the Cisco.com web site and unzip it.Note
You can download the driver file from the Cisco.com site for downloading the switch software.Step 2If using 32-bit Windows Vista or Windows 7, double-click the setup.exe file in the Windows_32 folder. If using 64-bit Windows Vista or Windows 7, double-click the setup(x64).exe file in the Windows_64 folder.Step 3The Cisco Virtual Com InstallShield Wizard begins. Click Next.Step 4The Ready to Install the Program window appears. Click Install.Note
If a User Account Control warning appears, click Allow - I trust this program to proceed.Step 5The InstallShield Wizard Completed window appears. Click Finish.Step 6Connect the USB cable to the PC and the switch console port. The USB console port LED turns green, and the Found New Hardware Wizard appears. Follow the instructions to complete the driver installation.Uninstalling the Cisco Microsoft Windows USB DriverUninstalling the Cisco Microsoft Windows XP and 2000 USB Driver
Use the Windows Add or Remove Programs utility or the setup.exe file.Using the Setup.exe ProgramBefore You Begin
Disconnect the switch console terminal before uninstalling the driver.ProcedureStep 1Run setup.exe for Windows 32-bit or setup(x64).exe for Windows-64bit. Click Next.Step 2The InstallShield Wizard for Cisco Virtual Com appears. Click Next.Step 3When the Program Maintenance window appears, select the Remove radio button. Click Next.Step 4When the Remove the Program window appears, click Remove.Step 5When the InstallShield Wizard Completed window appears, click Finish.Using the Add or Remove Programs UtilityBefore You Begin
Disconnect the switch console terminal before uninstalling the driver.ProcedureStep 1Click Start > Control Panel > Add or Remove Programs.Step 2Scroll to Cisco Virtual Com and click Remove.Step 3When the Program Maintenance window appears, select the Remove radio button. Click Next.Uninstalling the Cisco Microsoft Windows Vista and Windows 7 USB DriverBefore You Begin
Disconnect the switch console terminal before uninstalling the driver.ProcedureStep 1Run setup.exe for Windows 32-bit or setup(x64).exe for Windows-64bit. Click Next.Step 2The InstallShield Wizard for Cisco Virtual Com appears. Click Next.Step 3When the Program Maintenance window appears, select the Remove radio button. Click Next.Step 4When the Remove the Program window appears, click Remove.Note
If a User Account Control warning appears, click Allow - I trust this program to proceed.Step 5When the InstallShield Wizard Completed window appears, click Finish.Entering the Initial Configuration Information
To set up the switch, you need to complete the setup program, which runs automatically after the switch is powered on. You must assign an IP address and other configuration information necessary for the switch to communicate with the local routers and the Internet. This information is also needed to use Device Manager or Cisco Network Assistant to configure and manage the switch.IP Settings
Obtain this information from your network administrator before you start the setup program:
*Switch IP address
*Subnet mask (IP netmask)
*Default gateway (router)
*Enable secret password
*Enable password
*Telnet passwordCompleting the Setup Program
If your switches are stacked and there are multiple console connections to individual switches in the stack, the initial setup dialog box appears at the console where you first press Enter.ProcedureStep 1Enter Yes at these two prompts:Step 2Enter a host name for the switch, and press Return.
On a command switch, the host name is limited to 28 characters; on a member switch the name is limited to 31 characters. Do not use -n, where n is a number, as the last character in a host name for any switch.Step 3Enter an enable secret password, and press Return.
The password can be from 1 to 25 alphanumeric characters, can start with a number, is case sensitive, allows spaces, but ignores leading spaces. The secret password is encrypted, and the enable password is in plain text.Step 4Enter an enable password, and press Return.Step 5Enter a virtual terminal (Telnet) password, and press Return.
The password can be from 1 to 25 alphanumeric characters, is case sensitive, allows spaces, but ignores leading spaces.Step 6To configure the country code, enter yes and press Return.Step 7Enter the country code, and press Return.Step 8(Optional) Configure Simple Network Management Protocol (SNMP) by responding to the prompts. You can also configure SNMP later through the CLI, Device Manager, or the Network Assistant application. To configure SNMP later, enter no.Step 9Enter the interface name (physical interface or VLAN name) of the connection to the management network, and press Return. For this release, always use vlan1 as that interface.Step 10Configure the interface by entering the switch IP address and subnet mask and pressing Return. The IP address and subnet masks shown are examples.Step 11Enter Y to configure the switch as the cluster command switch. Enter N to configure it as a member switch or as a standalone switch.
If you enter N, the switch appears as a candidate switch in the Network Assistant GUI. You can configure the switch as a command switch later through the CLI, Device Manager, or the Network Assistant application. To configure it later, enter no.
You have now completed the initial configuration of the switch. This is an example of the configuration output that appears:Step 12From these choices that appear, make your selection and press Return.
The switch now runs this default configuration. If you want to change this configuration or perform other management tasks, see Management Options. -->
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.Where can I download DevCon?
DevCon (Devcon.exe) is included when you install the WDK, Visual Studio, and the Windows SDK for desktop apps. For information about downloading the kits, see Windows Hardware Downloads.
Windows Driver Kit (WDK) 8 and Windows Driver Kit (WDK) 8.1 (installation path)
%WindowsSdkDir%toolsx64devcon.exe
%WindowsSdkDir%toolsx86devcon.exe
%WindowsSdkDir%toolsarmdevcon.exeNote The Visual Studio environment variable, %WindowsSdkDir%, represents the path to the Windows kits directory where the kits are installed, for example, C:Program Files (x86)Windows Kits8.1.
This section includes:What you can do with DevConCisco Microsoft Windows Usb Device Drivers Downloads
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.
Devcon features include:
*
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.Cisco Microsoft Windows Usb Device DriverDevCon 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.Installing The Cisco Microsoft Windows Usb Device DriverRelated topics
Download here: http://gg.gg/wh2yb
https://diarynote.indered.space
Contents
*Cisco Microsoft Windows Usb Device Drivers Downloads
*Cisco Microsoft Windows Usb Device Driver
*Installing The Cisco Microsoft Windows Usb Device Driver
If your Windows 10 phone is already running the latest version of Windows 10 Mobile, try to connect your device to a Windows 10 PC instead. There’s a driver in the device you connected to that isn’t supported in the version of Windows 10 Mobile your phone is running. For information about the supported devices, see Universal Serial Bus (USB). Looking in Device Manager the driver was USB Serial instead of Cisco USB. It kept reverting back to the default Windows driver on every boot. What finally did the trick for me was to right click on the port in device manager and tell it to roll back drivers. It retained them after doing that. A USB device driver must be installed the first time a Microsoft Windows-based PC is connected to the USB console port on the switch. Installing the Cisco Microsoft Windows XP USB Driver. Installing the Cisco Microsoft Windows 2000 USB Driver. Installing the Cisco Microsoft Windows Vista and Windows 7 USB Driver. 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.Accessing the CLI Through Express Setup
You can access the CLI on an unconfigured switch. Set the switch in Express Setup mode and connect a switch Ethernet port to an Ethernet port on your PC or workstation. Follow the steps described in the getting started guide for turning on the switch and using Express Setup.
When the switch is in Express Setup mode, open a Telnet session to the switch by entering the IP address 10.0.0.1. Enter the setup user EXEC command. Enter the information described in the “IP Settings” section on page C-6and the “Completing the Setup Program” section.
After you have entered the configuration information for the switch, save it to flash memory by using the write memory privileged EXEC command.Note
In Express Setup mode, the IP address 10.0.0.1 remains active on the switch until you enter the write memory command. You lose the Telnet connection after entering the write memory command.Accessing the CLI Through the Console Port
You can access the CLI on a configured or unconfigured switch by connecting the RJ-45 console port or USB console port of the switch to your PC or workstation and accessing the switch through a terminal emulation program.Note
If you have stacked your switches, connect to the console port of one of the switches in the stack. You can initially configure the entire stack from any member switch.Connecting the RJ-45 Console Port ProcedureStep 1Connect the RJ-45-to-DB-9 adapter cable to the 9-pin serial port on the PC. Connect the other end of the cable to the switch console port. Step 2Start the terminal-emulation program on the PC or the terminal. The program, frequently a PC application such as HyperTerminal or ProcommPlus, makes communication between the switch and your PC or terminal possible.Step 3Configure the baud rate and character format of the PC or terminal to match the console port default characteristics:
*9600 baud
*8 data bits
*1 stop bit
*No parity
*None (flow control)Step 4Power on the switch as described in the switch getting started guide.Step 5The PC or terminal displays the bootloader sequence. Press Enter to display the setup prompt. Follow the steps in Entering the Initial Configuration Information.Connecting the USB Console PortProcedureStep 1If you are connecting the switch USB console port to a Windows-based PC for the first time, install the USB driver. See Installing the Cisco Microsoft Windows USB Device Driver.Figure 1. Connecting the USB Console Cable to the Switch
1
USB console port (5-pin mini-Type B)
3
USB Type A connection on the laptop
2
USB Type A to 5-pin mini-Type B cableStep 2Connect a USB cable to the PC USB port. Connect the other end of the cable to the switch mini-B (5-pin-connector) USB console port. Step 3Start the terminal-emulation program on the PC or the terminal. The program, frequently a PC application such as HyperTerminal or ProcommPlus, makes communication between the switch and your PC or terminal possible.Step 4Configure the baud rate and character format of the PC or terminal to match the console port default characteristics:
*9600 baud
*8 data bits
*1 stop bit
*No parity
*None (flow control)Step 5Power on the switch as described in the switch getting started guide.Step 6The PC or terminal displays the bootloader sequence. Press Enter to display the setup prompt. Follow the steps in the Setup program.Installing the Cisco Microsoft Windows USB Device Driver
A USB device driver must be installed the first time a Microsoft Windows-based PC is connected to the USB console port on the switch.Installing the Cisco Microsoft Windows XP USB DriverProcedureStep 1Obtain the Cisco USB console driver file from the Cisco.com web site and unzip it.Note
You can download the driver file from the Cisco.com site for downloading the switch software.Step 2If using 32-bit Windows XP, double-click the setup.exe file in the Windows_32 folder. If using 64-bit Windows XP, double-click the setup(x64).exe file in the Windows_64 folder.Step 3The Cisco Virtual Com InstallShield Wizard begins.Step 4The Ready to Install the Program window appears. Click Install.Step 5The InstallShield Wizard Completed window appears. Click Finish.Step 6Connect the USB cable to the PC and the switch console port. The USB console port LED turns green, and the Found New Hardware Wizard appears. Follow the instructions to complete the driver installation.Installing the Cisco Microsoft Windows 2000 USB DriverProcedureStep 1Obtain the Cisco USB console driver file from the Cisco.com web site and unzip it.Note
You can download the driver file from the Cisco.com site for downloading the switch software.Step 2Double-click the setup.exe file.Step 3The Cisco Virtual Com InstallShield Wizard begins. Click Next.Step 4The Ready to Install the Program window appears. Click Install.Step 5The InstallShield Wizard Completed window appears. Click Finish.Step 6Connect the USB cable to the PC and the switch console port. The USB console port LED turns green, and the Found New Hardware Wizard appears. Follow the instructions to complete the driver installation.Installing the Cisco Microsoft Windows Vista and Windows 7 USB DriverProcedureStep 1Obtain the Cisco USB console driver file from the Cisco.com web site and unzip it.Note
You can download the driver file from the Cisco.com site for downloading the switch software.Step 2If using 32-bit Windows Vista or Windows 7, double-click the setup.exe file in the Windows_32 folder. If using 64-bit Windows Vista or Windows 7, double-click the setup(x64).exe file in the Windows_64 folder.Step 3The Cisco Virtual Com InstallShield Wizard begins. Click Next.Step 4The Ready to Install the Program window appears. Click Install.Note
If a User Account Control warning appears, click Allow - I trust this program to proceed.Step 5The InstallShield Wizard Completed window appears. Click Finish.Step 6Connect the USB cable to the PC and the switch console port. The USB console port LED turns green, and the Found New Hardware Wizard appears. Follow the instructions to complete the driver installation.Uninstalling the Cisco Microsoft Windows USB DriverUninstalling the Cisco Microsoft Windows XP and 2000 USB Driver
Use the Windows Add or Remove Programs utility or the setup.exe file.Using the Setup.exe ProgramBefore You Begin
Disconnect the switch console terminal before uninstalling the driver.ProcedureStep 1Run setup.exe for Windows 32-bit or setup(x64).exe for Windows-64bit. Click Next.Step 2The InstallShield Wizard for Cisco Virtual Com appears. Click Next.Step 3When the Program Maintenance window appears, select the Remove radio button. Click Next.Step 4When the Remove the Program window appears, click Remove.Step 5When the InstallShield Wizard Completed window appears, click Finish.Using the Add or Remove Programs UtilityBefore You Begin
Disconnect the switch console terminal before uninstalling the driver.ProcedureStep 1Click Start > Control Panel > Add or Remove Programs.Step 2Scroll to Cisco Virtual Com and click Remove.Step 3When the Program Maintenance window appears, select the Remove radio button. Click Next.Uninstalling the Cisco Microsoft Windows Vista and Windows 7 USB DriverBefore You Begin
Disconnect the switch console terminal before uninstalling the driver.ProcedureStep 1Run setup.exe for Windows 32-bit or setup(x64).exe for Windows-64bit. Click Next.Step 2The InstallShield Wizard for Cisco Virtual Com appears. Click Next.Step 3When the Program Maintenance window appears, select the Remove radio button. Click Next.Step 4When the Remove the Program window appears, click Remove.Note
If a User Account Control warning appears, click Allow - I trust this program to proceed.Step 5When the InstallShield Wizard Completed window appears, click Finish.Entering the Initial Configuration Information
To set up the switch, you need to complete the setup program, which runs automatically after the switch is powered on. You must assign an IP address and other configuration information necessary for the switch to communicate with the local routers and the Internet. This information is also needed to use Device Manager or Cisco Network Assistant to configure and manage the switch.IP Settings
Obtain this information from your network administrator before you start the setup program:
*Switch IP address
*Subnet mask (IP netmask)
*Default gateway (router)
*Enable secret password
*Enable password
*Telnet passwordCompleting the Setup Program
If your switches are stacked and there are multiple console connections to individual switches in the stack, the initial setup dialog box appears at the console where you first press Enter.ProcedureStep 1Enter Yes at these two prompts:Step 2Enter a host name for the switch, and press Return.
On a command switch, the host name is limited to 28 characters; on a member switch the name is limited to 31 characters. Do not use -n, where n is a number, as the last character in a host name for any switch.Step 3Enter an enable secret password, and press Return.
The password can be from 1 to 25 alphanumeric characters, can start with a number, is case sensitive, allows spaces, but ignores leading spaces. The secret password is encrypted, and the enable password is in plain text.Step 4Enter an enable password, and press Return.Step 5Enter a virtual terminal (Telnet) password, and press Return.
The password can be from 1 to 25 alphanumeric characters, is case sensitive, allows spaces, but ignores leading spaces.Step 6To configure the country code, enter yes and press Return.Step 7Enter the country code, and press Return.Step 8(Optional) Configure Simple Network Management Protocol (SNMP) by responding to the prompts. You can also configure SNMP later through the CLI, Device Manager, or the Network Assistant application. To configure SNMP later, enter no.Step 9Enter the interface name (physical interface or VLAN name) of the connection to the management network, and press Return. For this release, always use vlan1 as that interface.Step 10Configure the interface by entering the switch IP address and subnet mask and pressing Return. The IP address and subnet masks shown are examples.Step 11Enter Y to configure the switch as the cluster command switch. Enter N to configure it as a member switch or as a standalone switch.
If you enter N, the switch appears as a candidate switch in the Network Assistant GUI. You can configure the switch as a command switch later through the CLI, Device Manager, or the Network Assistant application. To configure it later, enter no.
You have now completed the initial configuration of the switch. This is an example of the configuration output that appears:Step 12From these choices that appear, make your selection and press Return.
The switch now runs this default configuration. If you want to change this configuration or perform other management tasks, see Management Options. -->
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.Where can I download DevCon?
DevCon (Devcon.exe) is included when you install the WDK, Visual Studio, and the Windows SDK for desktop apps. For information about downloading the kits, see Windows Hardware Downloads.
Windows Driver Kit (WDK) 8 and Windows Driver Kit (WDK) 8.1 (installation path)
%WindowsSdkDir%toolsx64devcon.exe
%WindowsSdkDir%toolsx86devcon.exe
%WindowsSdkDir%toolsarmdevcon.exeNote The Visual Studio environment variable, %WindowsSdkDir%, represents the path to the Windows kits directory where the kits are installed, for example, C:Program Files (x86)Windows Kits8.1.
This section includes:What you can do with DevConCisco Microsoft Windows Usb Device Drivers Downloads
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.
Devcon features include:
*
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.Cisco Microsoft Windows Usb Device DriverDevCon 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.Installing The Cisco Microsoft Windows Usb Device DriverRelated topics
Download here: http://gg.gg/wh2yb
https://diarynote.indered.space
コメント