Evdev is an Xorg input driver for Linux's generic event devices. It therefore supports all input devices that the kernel knows about, including most mice, keyboards, tablets and touchscreens. Evdev is the default driver on the major Linux distributions. The evdev driver can serve as both a pointer and a keyboard input device. USB Input Device: hidclass.sys, hidparse.sys, hidusb.sys When I plug the same keyboard and mouse combo in my laptop (Dell E7440) running the very same version of Windows 7, it tells me it is an 'Unknown Device' for which it is unable to find drivers, even though I can see the six.sys files mentioned above under C: Windows system32 drivers. In addition to dividing the device input value by the maximum capability of the device, the driver scales the device input value by 0xFFFF: LastX = ((device input x value). 0xFFFF ) / (Maximum x capability of the device) LastY = ((device input y value). 0xFFFF ) / (Maximum y capability of the device).
-->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
Download hidalgo port devices driver win 7. 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.
This release brings the 1st Generation Scarlett Range, iTrack Solo and Saffire 6 USB 2.0 up to the same driver versions as the 2nd and 3rd Generation Scarlett ranges and the Clarett USB range. 1st Generation Scarlett 6i6, 8i6, 18i6, 18i8 and 18i20 continue to be supported by Scarlett Mix Control 1.10. Why am I seeing a selection of brands? We are a family of brands, all committed to removing barriers to creativity. You’ll find the products you own from all of our brands in one place, streamlined to get you what you need, as fast as possible, with a single sign-on for all. Focusrite 1394 driver download. Pick your download for product by type Software Focusrite Control 3.6.0. Focusrite Control 3.6.0 - Windows. Download Focusrite Control 3.6.0 - Mac (macOS 10.12 or newer) Download Release Notes. Download Focusrite Control - 3.4.6 (OS X 10.10-10.11). Focusrite Control Scarlett 3rd Gen - ユーザーガ.
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. Harnett driver download 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.
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.
-->Find information on known issues and the status of the rollout for Windows 10, version 20H2 and Windows Server, version 20H2. Looking for a specific issue? Press CTRL + F (or Command + F if you are using a Mac) and enter your search term(s).
Windows 10, version 20H2 is available for users with devices running Windows 10, versions 1903 and higher who manually seek to “Check for updates” via Windows Update. The recommended servicing status is Semi-Annual Channel. Note We are slowly throttling up availability over the coming weeks to ensure a reliable download experience. As a result, the update may not be offered to you right away. For more details, see How to get the Windows 10 October 2020 Update. |
| Windows 10, version 20H2 is now available Find out how to get the update > | What’s new for IT pros Explore the latest features and servicing innovations in Windows 10, version 20H2 > |
Known issues
| Summary | Originating update | Status | Last updated |
|---|---|---|---|
| Some games might fail to open, or you might receive an error You might have issues with some Direct3D games when using in-game overlay feature of Discord. | OS Build 19042.1000 KB4598291 2021-02-02 | Resolved External | 2021-02-08 19:16 PT |
| Errors or issues during or after updating devices with Conexant ISST audio drivers Devices with affected Conexant ISST audio drivers might receive an error or have issues with Windows 10, version 2004. | N/A | Confirmed | 2021-01-22 13:43 PT |
| Errors or issues during or after updating devices with certain Conexant audio drivers Devices with affected Conexant or Synaptics audio drivers might receive a stop error with a blue screen. | N/A | Confirmed | 2021-01-05 17:37 PT |
| Automatic input of Furigana might not work as expected In certain circumstances, the automatic Furigana input/conversion feature may not work as expected in apps. | N/A | Mitigated | 2020-12-10 18:24 PT |
Issue details
February 2021
Some games might fail to open, or you might receive an error | ||
| Status | Originating update | History |
| Resolved External | OS Build 19042.1000 KB4598291 2021-02-02 | Last updated: 2021-02-08, 07:16 PT Opened: 2021-02-08, 06:29 PT |
Microsoft and Discord have found incompatibility issues with some games using Direct3D 12 when the in-game overlay feature of Discord is enabled. When attempting to open affected games you might receive an error, or the game might close silently. Affected platforms:
Workaround: To mitigate this issue, you can turn off the in-game overlay in settings within the Discord app. Resolution: This issue is now resolved in an update to the Discord app. To verify you're on the latest version, right click on the Discord icon in the notification area and select 'Check for updates..'. If there are updates to install, it should install automatically but you might need to select the arrow icon in the upper right corner of the app to install the updated version. There is no update for Windows needed to resolve this issue. | ||
December 2020
Automatic input of Furigana might not work as expected | ||
| Status | Originating update | History |
| Mitigated | N/A | Last updated: 2020-12-10, 06:24 PT Opened: 2020-12-03, 12:29 PT |
When using the Microsoft Japanese Input Method Editor (IME) to enter Kanji characters in an app that automatically allow the input of Furigana characters, you might not get the correct Furigana characters and might need to enter them manually. Note for developers: Affected apps are using the ImmGetCompositionString function. Workaround: To mitigate this issue, please follow the instructions in Revert to a previous version of an IME (Input Method Editor). Affected platforms:
Next steps: We are working on a resolution and will provide an update in an upcoming release. | ||
May 2020
Errors or issues during or after updating devices with Conexant ISST audio drivers | ||
| Status | Originating update | History |
| Confirmed | N/A | Last updated: 2021-01-22, 01:43 PT Opened: 2020-05-27, 12:22 PT |
Synaptics and Microsoft have found incompatibility issues with certain versions of drivers for Conexant ISST audio driver and Windows 10, version 2004 (the Windows 10 May 2020 Update). Windows 10 devices with affected Conexant ISST audio driver might receive an error or experience issues while installing the update or after the device has updated. The affected driver will be named Conexant ISST Audio or Conexant HDAudio Driver under Sound, video and game controllers in Device Manager and have file name uci64a96.dll through uci64a231.dll and a file version of 7.231.3.0 or lower. To safeguard your update experience, we have applied a compatibility hold on Windows 10 devices with affected Conexant or Synaptics audio drivers installed from being offered Windows 10, version 2004 or Windows Server, version 2004 until the driver has been updated. If your organization is using Update Compliance, the safeguard ID is 25178825. Affected platforms:
Workaround: To mitigate the safeguard, you might need to check with your device manufacturer (OEM) to see if an updated driver is available and install it. If updated drivers are not available for your device and you are offered Windows 10, version 2004 or Windows 10, version 20H2, a small number of devices might roll back to the previous version of Windows 10 when attempting to update. If this occurs, you should attempt to update to Windows 10, version 2004 or Windows 10, version 20H2 again. Next steps: Microsoft and Synaptics are working on a resolution and will provide an update in an upcoming release. As of January 14, 2021, we are adjusting this safeguard to allow certain devices with the affected driver to update to Windows 10, version 2004 or Windows 10, version 20H2. Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved. | ||
Errors or issues during or after updating devices with certain Conexant audio drivers | ||
| Status | Originating update | History |
| Confirmed | N/A | Last updated: 2021-01-05, 05:37 PT Opened: 2020-05-27, 12:20 PT |
Synaptics and Microsoft have found incompatibility issues with certain versions of drivers for Conexant or Synaptics audio devices and Windows 10, version 2004 (the Windows 10 May 2020 Update). Windows 10 devices with affected Conexant or Synaptics audio drivers might receive a stop error with a blue screen during or after updating to Windows 10, version 2004. The affected driver will be named Conexant HDAudio Driver under Sound, video and game controllers in Device Manager and have versions 8.65.47.53, 8.65.56.51, or 8.66.0.0 through 8.66.89.00 for chdrt64.sys or chdrt32.sys. To safeguard your update experience, we have applied a compatibility hold on Windows 10 devices with affected Conexant or Synaptics audio drivers installed from being offered Windows 10, version 2004 or Windows Server, version 2004 until the driver has been updated. If your organization is using Update Compliance, the safeguard IDs are 25702617, 25702660, 25702662, and 25702673. Affected platforms:
Next steps: Microsoft and Synaptics are working on a resolution for safeguard IDs 25702617 and 25702660, and will provide an update in an upcoming release. Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved. Resolution: This issue was resolved for safeguard IDs 25702662 and 25702673. The safeguard hold has been removed for these safeguard IDs as of December 11, 2020. Please note, if there are no other safeguards that affect your device, it can take up to 48 hours before the update to Windows 10, version 2004 or Windows 10, version 20H2 is offered. | ||
Generic Dvd Driver