When connecting a Serial to USB Console cable in Windows 10, it might not open a COM port automatically.
Use the URL above to download the VCP Driver for your platform (Windows) and architecture (x64).
- Open it and extract the contents (there’s no installer).
- Then open Device Manager and find the missing driver for FT232R USB UART.
- Right-click and update driver and navigate to the root of the folder above.
- Afterwards, if another missing driver shows up called USB Serial Port (or something like that), repeat the same process and you should now see a new (old familiar) tab in Device Manager called Ports.
Microsoft-provided in-box driver (Usbser.sys) for your communications and CDC control device.
In Windows 10, the driver was rewritten using the Kernel-Mode Driver Framework, improving the overall stability of the driver.
- And it should say something like USB Serial Port (COM3).
- If you don’t, in Device Manager, expand USB Controllers at the bottom, then right-click on USB Serial Converter.
In addition, UWP applications can now use the APIs provided by the Windows.Devices.SerialCommunication namespace that allow apps to talk to these devices.
Load the Microsoft-provided in-box driver (Usbser.sys) for your communications and CDC control device.
Make sure “Load VCP” Is checked, then reinsert the USB cable.
You should now be able to use something like Putty to connect to COM3 using your Serial to USB Console cable. Products Integrated Systems Servers Storage Networking Software. Integrated Systems . We no longer support Internet Explorer v10 and older, or you have compatibility view enabled.
Windows 10 and later
Starting in Windows 10, Usbser.inf was added to the %Systemroot%\INF directory, which loads Usbser.sys as the functional device object (FDO) in the device stack. If your device belongs to the communications and CDC control device class, Usbser.sys is loaded automatically. You do not need to write your own INF to reference the driver. The driver is loaded based on a compatible ID match similar to other USB device class drivers included in Windows.
- Disable Compatibility view, upgrade to a newer version, or use a different browser. Beginning Nov 15, 2021, the Networking Forum discussion boards moved to the Aruba Airheads community . Aruba & ProVision-based. ForumsProductsCompanyLocal Language.
- InformationCommunityResourcesInformation LibrariesOther HPE Sites. Information Libraries. Other HPE Sites. Information Libraries. Other HPE Sites. 05-11-201810:25 AM. Hello everyone,. I'm looking for the Usb Console DRIVER for Windows 10, to get access to HP Aruba 2930F switchs,. Could you please tell where can I find it ?
- it's been several days that i'm looking for it. Thank you in advance. 05-11-201811:06 AM - last edited on 10-28-202011:59 PM by . 05-11-201811:06 AM - last edited on 10-28-202011:59 PM by . I just found the driver, it has nothing to do with the device, it' only related to the cable . Here is the link if it could help: http://www.winchiphead.com/download/CH341/CH341SER.ZIP.
[ ADMIN Note: Broken link removed].
Alternate link: https://support.arubanetworks.com/ToolsResources/tabid/76/DMXModule/514/Default.aspx?EntryId=4229. Moderator Note: [Updated with new links]. 06-05-201809:07 PM. This is the link to the HPE download for the USB driver. Yes it is dated 2013 but I've not had any trouble with it on Windows 10.
Windows 8.1 and earlier versions
In Windows 8.1 and earlier versions of the operating system, Usbser.sys is not automatically loaded when a USB-to-serial device is attached to a computer. To load the driver, you need to write an INF that references the modem INF (mdmcpq.inf) by using the Include directive. The directive is required for instantiating the service, copying inbox binaries, and registering a device interface GUID that applications require to find the device and talk to it. That INF specifies "Usbser" as a lower filter driver in a device stack.
The INF also needs to specify the device setup class as Modem to use mdmcpq.inf. Under the Version section of the INF, specify the Modem and the device class GUID. for details, see System-Supplied Device Setup Classes.
For more information, see How to use or reference the Usbser.sys driver from universal serial bus (USB) modem .inf files.
Configure selective suspend for Usbser.sys
Starting in Windows 10, Usbser.sys supports USB Selective Suspend. It allows the attached USB-to-serial device to enter a low power state when not in use, while the system remains in the S0 state. When communication with the device resumes, the device can leave the suspend state and resume the working state. The feature is disabled by default and can be enabled and configured by setting the IdleUsbSelectiveSuspendPolicy entry under this registry key:
To configure power management features of Usbser.sys, you can set IdleUsbSelectiveSuspendPolicy to:
Additionally, if your machine is online at the time, you should be able to get Windows to download the driver through Windows Update when you connect to a switch for the first time.
I would suggest you get the above download as it also has the registry change required to stop the drive creating a new serial port for every switch you connect.
That entry can be added in one of two ways:
With the reg change made (and a reboot), windows will keep reusing the Serial port number you first get when you swap from switch to switch.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise.
Develop Windows applications for a USB CDC device
If you install Usbser.sys for the USB CDC device, here are the application programming model options:
Starting in Windows 10, a Windows app can send requests to Usbser.sys by using the Windows.Devices.SerialCommunication namespace. It defines Windows Runtime classes that can use to communicate with a USB CDC device through a serial port or some abstraction of a serial port. The classes provide functionality to discover such serial device, read and write data, and control serial-specific properties for flow control, such as setting baud rate, signal states.
In Windows 8.1 and earlier versions, you can write a Windows desktop application that opens a virtual COM port and communicates with the device. For more information, see:
Win32 programming model:
.NET framework programming model: