OEM Multifunction Devices Driver

In Portable Devices, right-click the name of the device you connected, and then select Update Driver Software. In the Hardware Update wizard, select Browse my computer for driver software and click Next. Click Browse and then locate the USB driver folder. For example, the Google USB Driver is located in androidsdk extras google usbdriver.
Its products include printers, multifunction printers, desktop computers, sewing machines, large machine tools, label printers, typewriters, fax machines, and other computer-related electronics. Brother distributes its products both under its own name and under OEM agreements with other companies.
The device features a lightweight mechanical enclosure and is bus powered for easy portability. You can easily connect sensors and signals to the USB‑6008 with screw-terminal connectivity. The included NI‑DAQmx driver and configuration utility simplify configuration and measurements.

Oem Multifunction Devices Driver Download
Oem Multifunction Devices Driver Update

An original equipment manufacturer (OEM) provides the components in another company's product, working closely with the seller of the finished product, known as the value-added reseller (VAR).

-->

This article describes the steps to add Original Equipment Manufacturer (OEM)-supplied drivers to Windows installations.

Original product version: Windows Server 2003
Original KB number: 254078

Summary

This article only includes drivers that are typically installed during graphical user interface (GUI)-mode Setup or after Setup by Plug and Play enumeration. This lets you pre-load OEM Plug and Play drivers that you can use if the associated hardware is added to the system later.

This article describes how to add OEM Plug and Play drivers in the following situations:

Unattended Setup
Sysprep Setup
Remote Installation Service (RIS) installations
Riprep images
Existing Windows installations

More information

Drivers that are installed during the 'Installing Devices' part of GUI-mode Setup have to be found in certain locations. At this point, Setup is installing the devices by using Plug and Play IDs that have been enumerated by Windows Plug and Play. Setup searches a predefined path on the drive, looking in .inf files to find the best match for the Plug and Play ID of the device. By default, this path is defined in the following registry location and is set to %SystemRoot%Inf:
HKEY_LOCAL_MACHINESoftwareMicrosoftWindowsCurrentVersionDevicePath: REG_EXPAND_SZ:%SystemRoot%Inf
Setup uses this path to locate .inf files for device installation. After Setup, this path is also used for any new hardware that is found and installed. If you modify this key during Setup by using the Sysprep.inf file or the Unattended answer file, the value is saved and is also used after Setup.

The following sections contain steps to add OEM-supplied drivers to unattended or Sysprep Setup installations of Windows.

For Microsoft Windows 2000

Unattended setup

When you add drivers to unattended Setup, follow these steps. If the OEM-supplied drivers are not digitally signed, you may receive a message about the drivers during Setup.

Create your distribution share on a server by copying the contents of the Windows installation disc I386 folder. You can use the Setupmgr.exe program to create this share and the Unattended.txt file. You can find the Setupmgr.exe program on the Windows installation disc in the SupportTools folder in the Deploy.cab file and the Unattend.doc file that contains information about Windows unattended Setup.
Create a $oem$$1Drivers folder in the I386 folder. You may want to create additional folders in the Drivers subfolder, depending on the hardware that you want to install. For example, you may install a network adapter, a modem, or a video. The $1 folder resolves to %SystemDrive%. During text-mode Setup, these folders and files are copied to the %SystemDrive%Drivers folders as follows:
i386
$oem$
- - $1
- - - Drivers
- - - - - network adapter
- - - - - MODEM
- - - - - VIDEO
Copy all the OEM-supplied driver files for the device in the folders that you created in the previous step.
Add the OemPnPDriversPath = Driver_Paths entry in the [Unattended] section of the Setup answer file. You can list multiple paths in this key by separating them with a semicolon (;). For example, add the following entry.
[Unattended]
OemPnPDriversPath = 'Driversnetwork adapter;DriversModem;DriversVideo'
Note
The %SystemDrive% environment variable string is automatically inserted before each of the listed search paths.
Save the answer file.

During GUI-mode Setup when the system is searching .inf files for Plug and Play IDs, it also looks in the paths that are noted in the OemPnPDriversPath and the standard default path of %WinDir%Inf. The %WinDir%Inf path is listed first in the search order, but if you have a device that is supported by more than one .inf file, Setup continues to search all paths that are specified in the OemPnPDriversPath entry. ((Windows may include a driver that offers generic functionality.) Although it may find multiple matches, Plug and Play uses the .inf file that has the best match, and then installs the associated device driver to support the device.

Sysprep setup

The steps to add OEM-supplied drivers to a Windows Sysprep Setup resemble the steps in the 'Unattended Setup' section, except that you do not have to create the distribution share. To add drivers to the mini-wizard of Sysprep, follow these steps.

Note

To add OEM third-party mass-storage drivers to the Sysprep image that you use to start the computer, you require at least version 1.1 of Sysprep. There have been many updates to the Sysprep tool and to the deployment tools that include Sysprep. Therefore, we recommend that you use the latest version of the Sysprep tool and the deployment tools that are specific to the operating system that you deploy.

On the root of the volume where the %WinDir% folder is located, create a folder structure to hold the OEM-supplied drivers as follows:
Drivers
- - network adapter
- - VIDEO
Sysprep
WINNT
Copy the OEM-supplied drivers to their appropriate subfolders.
Add the OemPnPDriversPath = Driver_Paths entry in the [Unattended] section of the Sysprep.inf file. You can list multiple paths in this key by separating them with a semicolon (;) as shown in the following example.
[Unattended]
OemPnPDriversPath = 'Driversnetwork adapter;DriversVideo'
Note
The %SystemDrive% environment variable string is automatically inserted before each of the listed search paths.

If you do not want the OEM-supplied drivers to remain on the volume after the mini-wizard is completed, you can add the folder structure that you created in the previous step under the Sysprep folder. You have to adjust the OemPnPDriversPath = key appropriately. The Sysprep folder and its subfolders are automatically removed after Setup is complete.

Save the Sysprep.inf file in the Sysprep folder, and then run Sysprep.exe. Any Plug and Play devices are automatically installed during the mini-setup wizard on the target computers. (These files include those found by using the OEM driver .inf files.)

Note

You do not have to specify the -pnp command-line switch unless there are earlier (ISA) devices on the target computers. If you use the -pnp command-line switch, a full Plug and Play re-enumeration of all devices is performed that adds 5-10 minutes to the Sysprep mini-wizard process. Also, if you specify additional mass-storage controllers by using Sysprep version 1.1 or later versions, the -pnp command-line switch may cause some additional hard disk controllers to appear in Device Manager.

If the OEM-supplied drivers are not digitally signed, the mini-wizard postpones the installation of the device until an administrator logs on to the computer. This is referred to as client-side versus server-side installation that occurs during mini-wizard Setup.

RIS installations

Adding OEM Plug and Play drivers to RIS installations involves the same steps that are listed in the 'Unattended Setup' section, with two small adjustments:

Put the $oem$ folder at the same level as the I386 folder of the RIS image. For example, use the following folder structure:
RemoteInstallSetup%languageImages%dir_name%i386
RemoteInstallSetup%languageImages%dir_name%$oem$$1Drivers
network adapter
MODEM
VIDEO
Modify the RIS image default template (Ristndrd.sif). In the [Unattended] section, change the OemPreinstall = key value from No to Yes, and then add the OemPnPDriversPath = Driver_Path entries. You can list multiple paths in this key by separating them with a semicolon (;) as shown in the following example.
[Unattended]
OemPreinstall = Yes
OemPnPDriversPath = 'Driversnetwork adapter;DriversModem;DriversVideo'
Note
The %SystemDrive% environment variable string is automatically inserted before each of the listed search paths.
If one of the OEM-supplied drivers is for a network adapter device, the RIS server must have this file available when it restarts in text-mode Setup.
If you copy the additional network adapter or mass-storage drivers to the i386 folder as described in Knowledge Base article 246184, stop and restart the BINL service on the RIS server. To stop and restart the BINL service, type the following commands at the command prompt, and then press ENTER after each command:
- net stop 'boot information negotiation layer'
- net start 'boot information negotiation layer'

Riprep images

Riprep and Sysprep share much of the same functionality. Therefore, adding OEM Plug and Play drivers to computers that will be imaged involves steps that resemble those that are used for Sysprep. Before you run Riprep against the image computer to copy it to the RIS server, follow these steps:

Create a folder named Sysprep on the %SystemDrive% folder. (This is most likely drive C because Riprep.exe can only copy one volume/partition.)
On the root of the same volume, create a folder structure to hold the OEM-supplied drivers as follows:
Drivers
- - network adapter
- - VIDEO
Sysprep
WINNT
Copy the OEM-supplied drivers to their appropriate subfolders.
Create a Sysprep.inf file in the Sysprep folder, and then add the [Unattended] and OemPnPDriversPath = Driver_Path entries. You can list multiple paths in this key by separating them with a semicolon (;). For example:
[Unattended]
OemPnPDriversPath = 'Driversnetwork adapter;DriversVideo'
Note
The %SystemDrive% environment variable is automatically inserted before each of the listed search paths that are specified.
If the device has already been recognized by the operating system as a known or unknown device, you must remove the device by using Device Manager before you run Sysprep or the updated drivers are not installed on startup during mini-Setup.
Run the Riprep.exe program from the RisServer ReminstAdminI386 folder on the client computer to copy the image to the selected RIS server. Riprep looks in the Sysprep folder for a Sysprep.inf file, reads the OemPnPDriversPath= key, and then updates the following registry subkey:
HKEY_LOCAL_MACHINESoftwareMicrosoftWindowsCurrentVersionDevicepathThen, Riprep copies the registry up to the server so that it can be used during the mini-Setup wizard.
Note
The default Riprep.sif file that is created during this process is not affected by the entry in the Sysprep.inf file that was created in the previous steps.
Note
If one of the OEM-supplied drivers is for the primary network adapter, the RIS server must also have this file available from a typical RIS flat image before the Riprep image is downloaded.
If the image is already created and you want to add OEM-supplied Plug and Play drivers, we recommend that you use RIS to download the image to a computer, follow the steps listed in the previous 'Riprep Images' section, and then Riprep the image back to the RIS server.
One side effect is that the driver paths are entered two times in the SoftwareMicrosoftWindowsCurrentVersionDevicePath key.

Existing Windows installations

You may have to add new hardware devices to existing Windows-based computers that require OEM-supplied drivers. Although this process requires that you install the new device, you may want the OEM-supplied drivers to be distributed in a controlled manner or to be centrally located on one server. To do this, follow these steps:

Decide whether you want to copy the drivers locally or if you want to store them on a central distribution server. If you want to store the drivers locally on the computer's hard disk, you must have a procedure to copy the drivers to the computer. (For example, use logon scripts, Microsoft Systems Management Server (SMS) batch jobs, or other methods.)
After the distribution method is determined, obtain the path for the device drivers. If you want to copy them locally, the path may be C:Driversnetwork adapter. If you want them copied to a centrally located server, the path may be ServerNameDrivers network adapter (where Drivers is a shared folder).
The DevicePath key in the local computer's registry has to be updated to reflect the new OEM driver locations. You must have an automated method of remotely updating the registry key. You can use Regedit files together with logon scripts or with an SMS batch job. The default value is located in the following registry key:
HKEY_LOCAL_MACHINESoftwareMicrosoftWindowsCurrentVersionDevicePath: REG_EXPAND_SZ:%SystemRoot%Inf
Edit the DevicePath key by using Regedt32.exe so that path where the drivers are located is included in the search path.
Important
This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base: 322756 How to back up and restore the registry in Windows
For example, if the drivers are copied locally to the root of the drive where the %WinDir% folder resides (Driversnetwork adapter), the DevicePath final value must read:
DevicePath: REG_EXPAND_SZ:%SystemRoot%Inf;%SystemRoot%Driversnetwork adapterIf the drivers are kept on a centrally located server or distribution point, you have to add the UNC path to the OEM-supplied drivers. For example:
DevicePath: REG_EXPAND_SZ:%SystemRoot%Inf;ServerNameShareNameDriversnetwork adapter
Note
%SystemRoot% is not automatically appended because the Setup process does not add the values. You must manually type the value of %SystemRoot% if you edit the registry.

After you have completed these steps and new hardware is installed, when a user logs on, Plug and Play locates the new hardware and searches the device paths you specified to locate the OEM-supplied drivers. Notice that all the rules that apply to signed/unsigned drivers also apply to devices that are installed after Setup. If the OEM-supplied drivers for the new device are not digitally signed and a non-administrator user logs on to the computer after the new hardware is installed, the user cannot complete the installation of the device until an administrator logs on to the computer.

Note

If the device has already been recognized by the operating system as a known or unknown device, you must remove the device through Device Manager before you run Sysprep or the updated drivers are installed on startup during mini-setup.

For Windows Server 2003

Unattended setup

When you add drivers to unattended Setup, follow these steps. If the OEM-supplied drivers are not digitally signed, you may receive a message about the drivers during Setup.

Create your distribution share on a server by copying the contents of the Windows installation CD-ROM I386 folder. You can use Setupmgr.exe to create this share and your Unattended.txt file. You can find Setupmgr.exe on the Windows or service pack CD-ROM in the SupportTools folder in the Deploy.cab file and the deploy.chm and ref.chm Help files that contain information about Windows unattended Setup. You can also download the latest files from the Microsoft Web site.
Create a $oem$$1Drivers folder in the I386 folder. You may want to create additional folders in the Drivers subfolder, depending on the hardware that you want to install (for example, network adapter, modem, or video). The $1 folder resolves to %SystemDrive%. During text-mode Setup, these folders and files are copied to the %SystemDrive%Drivers folders. For example:
i386
$oem$
- - $1
- - - Drivers
- - - - - network adapter
- - - - - MODEM
- - - - - VIDEO
Copy all the OEM-supplied driver files for the device in the folders that you created in the previous step.
Add the OemPnPDriversPath = Driver_Paths entry in the [Unattended] section of the Setup answer file. You can list multiple paths in this key by separating them with a semicolon (;). For example:
[Unattended]
OemPnPDriversPath = Driversnetwork adapter;DriversModem;DriversVideoUpdateInstalledDrivers = Yes | No
Note
The %SystemDrive% environment variable string is automatically inserted before each of the listed search paths.
Save the answer file.

During GUI-mode Setup when the system is searching .inf files for Plug and Play IDs, it also looks in the paths that are noted in the OemPnPDriversPath and the standard default path of %WinDir%Inf. The %WinDir%Inf path is listed first in the search order, but if you have a device that is supported by more than one .inf file (Windows may include a driver that offers generic functionality), Setup continues to search all paths that are specified in the OemPnPDriversPath entry. Although it may find multiple matches, Plug and Play uses the .inf file that has the best match, and then installs the associated device driver to support the device.

Sysprep setup

Note

We recommend that you use the latest version of Sysprep that is available for your operating system.

On the root of the volume where the %WinDir% folder is located, create a folder structure to hold the OEM-supplied drivers. For example:
Drivers
- - network adapter
- - VIDEO
Sysprep
WINNT
Copy the OEM-supplied drivers to their appropriate subfolders.
Add the OemPnPDriversPath = Driver_Paths entry in the [Unattended] section of the Sysprep.inf file. You can list multiple paths in this key by separating them with a semicolon (;). For example:
[Unattended]
OemPnPDriversPath = Driversnetwork adapter;DriversVideoUpdateInstalledDrivers = Yes | No
Note
The %SystemDrive% environment variable string is automatically inserted before each of the listed search paths.

If you do not want the OEM-supplied drivers to remain on the volume after the mini-wizard is complete, you can add the folder structure that you created in the previous step under the Sysprep folder. You have to adjust the OemPnPDriversPath = key appropriately. The Sysprep folder (and its subfolders) is automatically removed after Setup is finished.

Save the Sysprep.inf file in the Sysprep folder and run Sysprep.exe. Any Plug and Play devices (including those found by using the OEM driver .inf files) are automatically installed during the mini-setup wizard on the target computers. Notice that you do not have to specify the -pnp command-line switch unless there are earlier (ISA) devices on the target computers. If you use the -pnp command-line switch, a full Plug and Play re-enumeration of all devices is performed, that adds 5-10 minutes to the Sysprep mini-wizard process. Also, if you specify an additional mass-storage controller, the -pnp command-line switch may cause some additional hard disk controllers to appear in Device Manager.

Note

RIS installations

Adding OEM Plug and Play drivers to RIS installations involves the same steps that are listed in the 'Unattended Setup' section, with two small adjustments:

Put the $oem$ folder at the same level as the I386 folder of the RIS image. For example, use the following structure:
RemoteInstallSetup%languageImages%dir_name%i386
RemoteInstallSetup%languageImages%dir_name%$oem$$1Drivers
network adapter
MODEM
VIDEO
Modify the RIS image default template (Ristndrd.sif). In the [Unattended] section, change the OemPreinstall = key value from No to Yes, and then add the OemPnPDriversPath = Driver_Path entries. You can list multiple paths in this key by separating them with a semicolon (;) as follows:
[Unattended]
OemPreinstall = Yes
OemPnPDriversPath = 'Driversnetwork adapter;DriversModem;DriversVideo'
UpdateInstalledDrivers = Yes | No
Note
The %SystemDrive% environment variable string is automatically inserted before each of the listed search paths.
Note
If one of the OEM-supplied drivers is for a network adapter device, the RIS server must have this file available when it restarts in text-mode Setup.
If you copy the additional network adapter or mass-storage drivers to the i386 folder as described in Knowledge Base article 246184, stop and restart the BINL service on the RIS server. To stop and restart the BINL service, type the following commands at the command prompt, and then press ENTER after each command:
- net stop 'boot information negotiation layer'
- net start 'boot information negotiation layer'

Riprep images

Create a folder named Sysprep on the %SystemDrive% folder. (This is most likely drive C because Riprep.exe can only copy one volume or partition.)
On the root of the same volume, create a folder structure to hold the OEM-supplied drivers as follows:
Drivers
- - network adapter
- - VIDEO
Sysprep
WINNT
Copy the OEM-supplied drivers to their appropriate subfolders.
Create a Sysprep.inf file in the Sysprep folder, and then add the [Unattended] and OemPnPDriversPath = Driver_Path entries. You can list multiple paths in this key by separating them with a semicolon (;) as follows:
[Unattended]
OemPnPDriversPath = Driversnetwork adapter;DriversVideoUpdateInstalledDrivers = Yes | No
Note
The %SystemDrive% environment variable is automatically inserted before each of the listed search paths that are specified.
Note
If the device has already been recognized by the operating system as a known or unknown device, you must remove the device through Device Manager before you run Sysprep or the updated drivers are not installed on startup during mini-Setup.
Run the Riprep.exe program from the RisServerReminstAdminI386 folder on the client computer to copy the image to the selected RIS server. Riprep looks in the Sysprep folder for a Sysprep.inf file, reads the OemPnPDriversPath= key, and then updates the following registry subkey:
HKEY_LOCAL_MACHINESoftwareMicrosoftWindowsCurrentVersionDevicepath
Then, Riprep copies the registry up to the server so that it can be used during the mini-Setup wizard.
Note
The default Riprep.sif file that is created during this process is not affected by the entry in the Sysprep.inf file that was created in the previous steps.

Existing Windows installations

Decide whether you want to copy the drivers locally or if you want to store them on a central distribution server. If you want to store the drivers locally on the computer's hard disk, you must have a procedure to copy the drivers to the computer. For example, use logon scripts, Microsoft Systems Management Server (SMS) batch jobs, or other methods.
After the distribution method is determined, obtain the path for the device drivers. If you want to copy them locally, the path may be C:Driversnetwork adapter. If you want them copied to a centrally located server, the path may be ServerNameDriversnetwork adapter. (Drivers are a shared folder.)
The DevicePath key in the local computer's registry has to be updated to reflect the new OEM driver locations. You must have an automated method of remotely updating the registry key. You can use Regedit files together with logon scripts or with an SMS batch job. The default value is located in the following registry subkey:
HKEY_LOCAL_MACHINESoftwareMicrosoftWindowsCurrentVersionDevicePath: REG_EXPAND_SZ:%SystemRoot%Inf
Edit the DevicePath key by using Registry Editor so that path where the drivers are located is included in the search path.
Important
This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base: 322756 How to back up and restore the registry in Windows
For example, if the drivers are copied locally to the root of the drive where the %WinDir% folder resides (Driversnetwork adapter), the DevicePath final value must read as follows:
DevicePath: REG_EXPAND_SZ:%SystemRoot%Inf;%SystemRoot%Driversnetwork adapterIf the drivers are kept on a centrally located server or distribution point, you have to add the UNC path to the OEM-supplied drivers. For example:
DevicePath: REG_EXPAND_SZ:%SystemRoot%Inf;**ServerName****ShareName**Driversnetwork adapter
Note
%SystemRoot% is not automatically appended because the Setup process does not add the values. You must manually type the value of %SystemRoot% if you edit the registry.

Assume that you have completed these steps and new hardware is installed. When a user logs on, Plug and Play locates the new hardware and searches the device paths that you specified to locate the OEM-supplied drivers. Notice that all the rules that apply to signed and unsigned drivers also apply to devices that are installed after Setup. Assume that the OEM-supplied drivers for the new device are not digitally signed and a non-administrator user logs on to the computer after the new hardware is installed. In this case, the user cannot complete the installation of the device until an administrator logs on to the computer.

Note

If the device has already been recognized by the operating system as a known or unknown device, you must remove the device by using Device Manager before you run Sysprep or the updated drivers are installed on startup during mini-Setup.

-->

This topic is intended for OEMs who want to build a Windows 10 system with USB Type-C connector and want to leverage OS features that allow for faster charging, power delivery, dual role, alternate modes, and error notifications through Billboard devices.

A traditional USB connection uses a cable with a USB A and USB B connector on each end. The USB A connector always plugs in to the host side and the USB B connector connects the function side, which is a device (phone) or peripheral (mouse, keyboard). By using those connectors, you can only connect a host to a function; never a host to another host or a function to another function. The host is the power source provider and the function consumes power from the host.

The traditional configuration limits some scenarios. For example, if a mobile device wants to connect to a peripheral, the device must act as the host and deliver power to the connected device.

The USB Type-C connector, introduced by the USB-IF, defined in the USB 3.1 specification, addresses those limitations. Windows 10 introduces native support for those features.

Feature summary

Allows for faster charging up to 100W with Power Delivery over USB Type-C.
Single connector for both USB Hosts and USB Devices.
Can switch USB roles to support a USB host or device.
Can switch power roles between sourcing and sinking power.
Supports other protocols like DisplayPort and Thunderbolt over USB Type-C.
Introduces USB Billboard device class to provide error notifications for Alternate Modes.

Official specifications

Hardware design

USB Type-C connector is reversible and symmetric.

The main component are: the USB Type-C connector and its port or PD controller that manages the CC pin logic for the connector. Such systems typically have a dual-role controller that can swap the USB role from host to function. It has Display-Out module that allows video signal to be transmitted over USB. Optionally it can support BC1.2 charger detection.

Consider recommendations for the design and development of USB components, including minimum hardware requirements, Windows Hardware Compatibility Program requirements, and other recommendations that build on those requirements.Hardware component guidelines USB

Choose a driver model

Use this flow chart to determine a solution for your USB Type-C system.

If your system...	Recommended solution...
Does not implement PD state machines	Write a client driver to the UcmTcpciCx class extension. Write a USB Type-C port controller driver
Implements PD state machines in hardware or firmware and support USB Type-C Connector System Software Interface (UCSI) over ACPI	Load the Microsoft provided in-box drivers, UcmUcsiCx.sys and UcmUcsiAcpiClient.sys. See UCSI driver.
Implements PD state machines in hardware or firmware, but either does not support UCSI, or support UCSI but requires a transport other than ACPI	Write a client driver for the UcmCx class extension. Write a USB Type-C connector driver Write a USB Type-C Policy Manager client driver
Implements UCSI but requires a transport other than ACPI	Write a client driver to the UcmUcsiCx class extension. Use this sample template and modify it based on a transport that your hardware uses. Write a UCSI client driver

Bring up drivers

USB Function driver bring-up is only required if you support USB Function mode. If you previously implemented a USB Function driver for a USB micro-B connector, describe the appropriate connectors as USB Type-C in the ACPI tables for the USB Function driver to continue working.
For more information, see instructions about writing a USB Function driver.
USB Role-Switch driver bring-up is only required for devices that have a Dual Role controller that assumes both Host and Function roles. To bring-up the USB Role-Switch driver, you need to modify the ACPI tables to enable the Microsoft in-box USB role-switch driver.
For more information, see the guidance for bringing up the USB Role Switch Driver.
A USB Connector Manager Driver is required for Windows to manage the USB Type-C ports on a system. The bring-up tasks for a USB Connector Manager driver depend on the driver that you choose for the USB Type-C ports: The Microsoft in-box UCSI (UcmUcsiCx.sys and UcmUcsiAcpiClient.sys) driver, a UcmCx client driver, or a UcmTcpciCx client driver. For more information, see the links in the preceding section that describe how to choose the right solution for your USB Type-C system.

Test

Perform various functional and stress tests on systems and devices that expose a USB Type-C connector.