These downloads cover most Intel® Ethernet Adapters and install the latest drivers when you run them. The network adapter property sheet in Windows® 10 provides information about the network adapter and driver on the computer. Follow these steps to open the adapter properties: Right-click the Start button. Click Device Manager from the list. Device Manager is the program you need to manage drivers and see whether there’s a problem. Photograph: Samuel Gibbs/The Guardian. If a reboot doesn’t make Windows renew its USB drivers, you.
-->Windows versions
- Windows 10 for desktop editions (Home, Pro, Enterprise, and Education)
- Windows 10 Mobile
Common points of discussion for OEMs who want to build Windows systems with USB Type-C connectors.
USB Type-C connector features
Symmetric and reversible design
- The connector is symmetric. The cable has a USB Type-C connector on each end allowing the host and function device to use USB Type-C connectors. Here is an image that compares the connectors:
- The connector is designed to be reversible. Traditional connectors had to be connected the 'right-side-up'. With the reversible design, the connector can be flipped.
Supports all USB device speeds
The connector can support USB devices that are low-speed, full-speed, high-speed, SuperSpeed (including SS+).
Alternate modes
The connector can support alternate modes. The alternate mode feature allows non-USB protocols to run over the USB cable, while simultaneously preserving USB 2.0 and charging functionality. Currently, the most popular alternate modes are DisplayPort/DockPort and MHL.
DisplayPort / DockPort
This alternate mode allows the user to project audio/video to external DisplayPort displays over a USB connector.
MHL
The MHL alternate mode is allows the user to project video/audio to external displays that support MHL.
Billboard error messages
If a user connects a USB Type-C alternate mode device or adapter that is not supported by the attached PC or phone, the device or adapter can expose a Billboard device that contains information about the error condition to help the user troubleshoot issues.
Increased power limits
A system with USB Type-C connectors has higher power limits, it can support up to 5V, 3A, 15W.
In addition, the connector can optionally support the power delivery feature as defined by the USB Power Delivery OEM . If the connector supports power delivery, a USB Type-C system can be a power source provider or a consumer and support up to 100W.
Supports USB dual roles
Peripheral devices can connect to a mobile system with USB Type-C connectors, changing the traditional role of a mobile system from function to host. When the same system is connected to a PC, the system resumes the role of a function and PC becomes the host.
Operating system input into which alternate mode needs to be negotiated, such as DP 2-lane vs. DP 4-lane
No. The operating system (or any Microsoft-provided software component) plays no part in selecting an alternate mode. The decision is made by the driver for the connector, specifically the USB connector manager (UCM) client driver. The driver does so by communicating with the connector's firmware by using hardware interfaces.
Pre-OS charging with Type-C and PD
Enabling pre-OS charging is owned by the OEM. You can choose to not implement USB Power Delivery, and charge at USB Type-C power levels until you boot into the operating system.
Charging the phone when it is a USB host to enable docking scenarios like Continuum
Here are a few things to consider:
You must to implement USB Power Delivery, so that power and data roles can be swapped independently.
Your dock’s upstream port should be implemented as a Charging UFP, defined in the USB Type-C specification. For details, see section 4.8.4, version 1.1.
Your dock should request a DR_Swap if it resolved to a DFP, or a PR_Swap if it resolved to a UFP.
The initial DFP is the power source, so you must change the data role. The initial UFP is the power sink, so you must change the power role. You can perform those operations in your implementation of these callback functions:
Windows 10 Mobile support of USB billboard devices
Yes, if you connect the phone to a device that supports a USB Billboard, as per the USB Device Class Definition for Billboard Devices specification, the user is notified. Your USB connector manager (UCM) client driver is not required to handle the notification. If your system does not recognize the alternate mode, do not enter the mode.
Support for USB Type-C on earlier versions of Windows
USB Type-C is not supported on versions of Windows prior to Windows 10.
UCSI support on earlier versions of Windows
UCSI is not supported on versions of Windows prior to Windows 10.
How to test an implementation of UCSI
To test your implementation, follow the guidelines given in USB Type-C manual interoperability test procedures. We recommend running USB tests in Windows Hardware Lab Kit (HLK) for Windows 10. These tests are listed in Windows Hardware Certification Kit Tests for USB.
Conditions and UI for the different errors
Windows 10 can show a set of USB Type-C error messages to help educate users about the limitations with different combinations of USB Type-C hardware and software. For example, the user might get 'Device is charging slowly' message if the charger connected to the USB Type-C connector is not powerful enough, not compatible with the system, or is connected to a non-charging port. For more information, see Troubleshoot messages for a USB Type-C Windows system.
Connecting a non-PD port to a PD provider and a PD consumer to a system that is not a PD provider
The non-PD port attempts to charge the system by using USB Type-C current levels. For more information, see USB 3.1 and USB Type-C specifications.
Connecting Thunderbolt, SuperMHL, or PCI express to a PC that does not support those capabilities
The alternate mode feature allows non-USB protocols (such as Thunderbolt, SuperMHL) to run over the USB cable, while simultaneously preserving USB 2.0 and charging functionality. If a user connects a USB Type-C alternate mode device or adapter that is not supported by the attached PC or phone running Windows 10, an error condition is detected and a message is shown to the user.
- If the device or adapter exposes a Billboard device, the user sees information about the error condition to help the troubleshoot issues. Windows 10 provides an in-box driver for a Billboard device and notifies the user that an error has occurred.
- The user might see an error notification, 'Try improving the USB connection'. For more information, see Fix USB-C Problems.
For the best results, make sure that the alternate mode device or adapter’s requirements are met by PC or phone or cable.
Support and limitations for MTP over USB Type-C in Windows
Windows 10 for desktop editions supports MTP in the initiator role; Windows 10 Mobile supports MTP in the responder role.
How downstream devices and hubs connect and communicate with USB Connector Manager (UCM)
UCM is its own device stack (see Architecture: USB Type-C design for a Windows system). Windows 10 support for USB Type-C includes the required plumbing to make sure that the different class drivers know how to communicate with the different USB Type-C connectors. In order to get Windows 10 support for USB Type-C, you must plug into the UCM device stack.
USB Type-C MUTT requirements for HLK tests
The Windows HLK for Windows 10 contains tests for USB host and function controllers. To test your system, use a USB C-A adapter. These tests are listed in Windows Hardware Certification Kit Tests for USB.
Microsoft support for P2P data transfer between the same Windows 10 SKU
This is not a valid connection.
- You cannot connect two PCs running Windows 10 for desktop editions.
- You cannot connect two mobile devices running Windows 10 Mobile.
If the user attempts to make such a connection, Windows shows an error message. For more information, see Error messages for a USB Type-C Windows system.
The only valid connection is between a Windows Mobile device and Windows desktop device.
UCM class extension (UcmCx) communication with PMIC or battery driver to get/set charging status
On software-assisted charging platforms, UcmCx communicates with PMIC and the battery subsystem. The client driver may determine the charging levels by communicating with the hardware through hardware interfaces. On hardware-assisted platforms, the embedded controller is responsible for charging. UcmCx takes no part in the process.
HLK support for USB Type-C
In Windows HLK for Windows 10, there are no USB Type-C specific tests. We recommend running USB tests in Windows HLK for Windows 10. These tests are listed in Windows Hardware Certification Kit Tests for USB.
UCSI
USB Type-C Connector System Software Interface (UCSI) Specification describes the capabilities of the USB Type-C Connector System software Interface (UCSI), and explains the registers and data structures, for hardware component designers, system builders, and device driver developers.
Microsoft provides an in-box driver with Windows, UcmUcsi.sys, that implements the features defined by the specification. This driver is intended for systems with embedded controllers.
Test a UCSI implementation running on Windows 10
We recommend running USB tests in Windows HLK for Windows 10. These tests are listed in Windows Hardware Certification Kit Tests for USB.
Test a UCMCx client driver on Windows 10
We recommend running USB tests in Windows HLK for Windows 10. These tests are listed in Windows Hardware Certification Kit Tests for USB.
VBus/VConn control and role switch operations handled by the UCM class extension
The UCM class extension might get requests from the operating system to change data or power direction of the connector. When it gets those requests, it invokes client driver's implementation of EVT_UCM_CONNECTOR_SET_DATA_ROLE and EVT_UCM_CONNECTOR_SET_POWER_ROLE callback functions (if the connector implements PD). In the implementation, the client driver is expected control the VBUS and VCONN pins. For more information about those callback functions, see Write a USB Type-C connector driver.
-->This section describes the class-of-device (CoD) registry subkeys and entries that apply to the Bluetooth driver stack.
'COD Major' and 'COD Type' Values
Original equipment manufacturer (OEMs) can use the COD Major and COD Type values to indicate the Class of Device for a Bluetooth-enabled Windows device. After the Bluetooth class installer sets the Class of Device based on these registry values, a remote device can determine whether it is connecting to a portable computer, a desktop computer, a phone, and so on.
The registry path to the COD Major and COD Type values is:
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesBTHPORTParameters
Note that setting these values changes the Bluetooth Class of Device for the system, regardless of which Bluetooth radio may be attached. You can set the COD Major and COD Type to DWORD values as defined for the Class of Device field values in the Bluetooth SIG Assigned Numbers.
The Bluetooth profile driver, BthPort.sys, reads the COD Major and COD Type values to determine how it should respond to a device inquiry. These values affect only the COD_MAJOR_XXX and COD_XXX_MINOR_XXX bits of the Class of Device. The COD_SERVICE_XXX bits are not affected by this registry entry.
If the COD Major and COD Type values are not set or are set to invalid values, the Bluetooth class installer will set these values to COD_MAJOR_COMPUTER and COD_COMPUTER_MINOR_DESKTOP, respectively.
Scanning Parameterization Settings
Profile drivers can specify scanning parameters settings for their device(s) in their profile driver's INF file to tailor to the specific needs of a given device scenario.
You can override the default system scanning parameters by providing one or more of the following scanning parameters listed below into the AddReg directive. More information on how to use this directive can be found in INF AddReg Directive.
| Value Name | Type | Min Value | Max Value |
|---|---|---|---|
| HighDutyCycleScanWindow | DWORD 0x10001 | 0x0004 | 0x4000. Shall be equal or smaller than the HighDutyCycleScanInterval parameter |
| HighDutyCycleScanInterval | DWORD 0x10001 | 0x0004 | 0x4000 |
| LowDutyCycleScanWindow | DWORD 0x10001 | 0x0004 | 0x4000. Shall be smaller than the LowDutyCycleScanInterval parameter |
| LowDutyCycleScanInterval | DWORD 0x10001 | 0x0004 | 0x4000 |
| LinkSupervisionTimeout | DWORD 0x10001 | 0x000A | 0x0C80 |
| ConnectionLatency | DWORD 0x10001 | 0x0000 | 0x01F4 |
| ConnectionIntervalMin | DWORD 0x10001 | 0x0006 | 0x0C80. Shall be smaller or equal to ConnectionIntervalMax |
| ConnectionIntervalMax | DWORD 0x10001 | 0x0006 | 0x0C80 |
Ioline Port Devices Driver Windows 10
Note
Ioline Port Devices Driver Scanner
Changes to scanning parameters make a global impact on the performance of the Bluetooth stack. Making changes to scanning parameters programmatically is not permitted. Using Low Duty Cycle scanning parameters that are too aggressive can not only have a negative impact to the available bandwidth for other Bluetooth Low Energy connections, but also for Bluetooth BR/EDR connections.