Once you havepurchased Virtual Serial Port Driver, the activation code will be e-mailed to you shortly. Delivery time may vary depending on your purchase options. The next step is to activate your copy of VSPD:
- Configure Virtual Serial Port Driver Registration Code Windows
- Configure Virtual Serial Port Driver Registration Code For Windows 7
May 18, 2020 Configure Virtual Serial Port Driver Registration Code. All virtual serial ports work and behave exactly like real ones, emulating all their settings. You can create as many virtual port pairs as you want. Virtual copies, each of them sending this data to a connected serial app.”. This software consist a “Serial Splitter” module who. ScreenShots: Software Description: Virtual Serial Port Driver creates virtualserial ports and connects them in pairs via virtual null modemcable. Applications on both ends of the pair will be able toexchange data in such a way, that everything written to the firstport will appear in the second one and backwards.All virtual serial ports work and behave Read more →.
- Launch Virtual Serial Port Driver if it is not running yet.
- Select Help → Activate from the Main Menu.
- In the invoked window, enter the activation code you’ve received from us:
4. Click the Activate button to finish the activation process.
If you don’t have Internet access on your PC:
You can activate Virtual Serial Port Driver manually (offline). You will need to use another PC that is online to get a special activation file.
Do the following:
1. Repeat steps 1-3 of the instructions above.
2. You will get the following message:
3. Click the “Activate manually” button.
4. In the invoked window, read the instructions and click the “Save activation file” button:
5. Save the activation info to a file (it will have the extension .activate).
6. Then bring this file (on a USB flash drive, for example) to any computer which has Internet access.
7. Go to https://activate.electronic.us. Click the “Browse” button to load the file and click “Submit”.
8. Download the file and bring this file to your PC (where Virtual Serial Port Driver is installed). Repeat steps 1-3 of this instruction to invoke the following window and click the “Load activation file” button:
9. Once activation is successfully completed, you will get a confirmation message.
Notes:
- Virtual Serial Port Driver may be occasionally reactivated in the background to ensure a smooth and uninterrupted license compliance check. This will require an Internet connection as well. If there is no access to the Internet available on your PC, you can reactivate Virtual Serial Port Driver manually (offline) by following the instructions above.
- The trial version of Virtual Serial Port Driver performs activation in the background without your interference. No activation code is needed! Activation of the trial version is required for statistics only.
- No personal information is collected during activation. Check our Privacy Policyfor details.
-->Versions supported
- Windows 10
- Windows 8.1
Applies to
- Device manufacturers of CDC Control devices
Microsoft-provided in-box driver (Usbser.sys) for your Communications and CDC Control device.
In Windows 10, the driver has been rewritten by using the Kernel-Mode Driver Framework that improves the overall stability of the driver.
- Improved PnP and power management by the driver (such as, handling surprise removal).
- Added power management features such as USB Selective Suspend.
In addition, UWP applications can now use the APIs provided by the new Windows.Devices.SerialCommunication namespace that allow apps to talk to these devices.
Usbser.sys installation
Load the Microsoft-provided in-box driver (Usbser.sys) for your Communications and CDC Control device.
Note
Configure Virtual Serial Port Driver Registration Code Windows
If you trying to install a USB device class driver included in Windows, you do not need to download the driver. They are installed automatically. If they are not installed automatically, contact the device manufacturer. For the list of USB device class driver included in Windows, see USB device class drivers included in Windows.
Windows 10
In Windows 10, a new INF, Usbser.inf, has been added to %Systemroot%Inf that loads Usbser.sys as the function 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.
USBClass_02
USBClass_02&SubClass_02
- If you want to load Usbser.sys automatically, set the class code to 02 and subclass code to 02 in the Device Descriptor. For more information, see USB communications device class. With this approach, you are not required to distribute INF files for your device because the system uses Usbser.inf.
- If your device specifies class code 02 but a subclass code value other than 02, Usbser.sys does not load automatically. Pnp Manager tries to find a driver. If a suitable driver is not found, the device might not have a driver loaded. In this case, you might have to load your own driver or write an INF that references another in-box driver.
- If your device specifies class and subclass codes to 02, and you want to load another driver instead of Usbser.sys, you have to write an INF that specifies the hardware ID of the device and the driver to install. For examples, look through the INF files included with sample drivers and find devices similar to your device. For information about INF sections, see Overview of INF Files.
Note
Microsoft encourages you to use in-box drivers whenever possible. On mobile editions of Windows, such as Windows 10 Mobile, only drivers that are part of the operating system are loaded. Unlike desktop editions, it is not possible to load a driver through an external driver package. With the new in-box INF, Usbser.sys is automatically loaded if a USB-to-serial device is detected on the mobile device.
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
Configure Virtual Serial Port Driver Registration Code For Windows 7
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 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:
'0x00000001': Enters selective suspend when idle, that is, when there are no active data transfers to or from the device.
'0x00000000': Enters selective suspend only when there are no open handles to the device.
That entry can be added in one of two ways:
Write an INF that references the install INF and add the registry entry in the HW.AddReg section.
Describe the registry entry in an extended properties OS feature descriptor. Add a custom property section that sets the bPropertyName field to a Unicode string, 'IdleUsbSelectiveSuspendPolicy' and wPropertyNameLength to 62 bytes. Set the bPropertyData field to '0x00000001' or '0x00000000'. The property values are stored as little-endian 32-bit integers.
For more information, see Microsoft OS Descriptors.
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: