-->

Summary

I understand you're needing assistance with downloading Apple Mobile Device USB driver. I'd be happy to help out. The article below has the steps to download the Apple Mobile Device USB driver: If iTunes doesn't recognize your iPhone, iPad, or iPod - Apple Support Cheers! Android USB drivers are a necessary tool in your PC and Mac. They act as a bridge between your mobile device and your PC helping them to interact and communicate. The USB drivers help in connecting our phones to your computer and performing tasks like transferring photos and other data.

• Microsoft-provided in-box UCSI driver for a USB Type-C system with an embedded controller.

Last Updated

• October 2018

Windows version

• Windows 10 for desktop editions (Home, Pro, Enterprise, and Education)
• Windows 10 Mobile

Mobile Connector USB Devices Driver

Official specifications

Microsoft provides a USB Type-C Connector System Software Interface (UCSI) Specification-compliant driver for ACPI transport. If your design includes an embedded controller with ACPI transport, implement UCSI in your system's BIOS/EC and load the in-box UCSI driver (UcmUcsiCx.sys and UcmUcsiAcpiClient.sys).

If your UCSI-compliant hardware uses a transport other than ACPI, you need to write a UCSI client driver.

Drivers for supporting USB Type-C components for systems with embedded controllers

Here is an example of a system with an embedded controller.

In the preceding example, USB role switching is handled in the firmware of the system and USB Role Switch driver stack is not loaded. In another system, the driver stack may not get loaded because dual role is not supported.

In the preceding image,

• USB device-side drivers

  The USB device-side drivers service the function/device/peripheral. The USB function controller class extension supports MTP (Media Transfer Protocol) and charging using BC 1.2 chargers. Microsoft provides in-box client drivers for Synopsys USB 3.0 and ChipIdea USB 2.0 controllers. You can write a custom client driver for your function controller by using USB function controller client driver programming interfaces. For more information, see Developing Windows drivers for USB function controllers.

  The SoC vendor might provide you with the USB function lower filter driver for charger detection. You can implement your own filter driver if you are using the in-box Synopsys USB 3.0 or ChipIdea USB 2.0 client driver.

• USB host-side drivers

  The USB host-side drivers are a set of drivers that work with EHCI or XHCI compliant USB host controllers. The drivers are loaded if the role-switch driver enumerates the host role. If your host controller is not specification-compliant, then you can write a custom driver by using USB host controller extension (UCX) programming interface. For information, see Developing Windows drivers for USB host controllers.

  Note Not all USB devices classes are supported on Windows 10 Mobile.

• USB connector manager

  Microsoft provides a UCSI in-box driver with Windows (UcmUcsiCx.sys) that implements the features defined in the USB Type-C Connector System Software Interface Specification. The specification describes the capabilities of UCSI and explains the registers and data structures, for hardware component designers, system builders, and device driver developers.

  This driver is intended for systems with embedded controllers. This driver is a client to the Microsoft-provided USB connector manager class extension driver (Ucmcx.sys). The driver handles tasks such as initiating a request to the firmware to change the data or power roles and getting information needed to provide troubleshooting messages to the user.

UCSI commands required by Windows

See the UCSI specification for commands that are 'Required' in all UCSI implementations.

In addition to the commands marked as 'Required', Windows requires these commands:

• GET_ALTERNATE_MODES
• GET_CAM_SUPPORTED
• GET_PDOS
• SET_NOTIFICATION_ENABLE: The system or controller must support the following notifications within SET_NOTIFICATION_ENABLE:
  • Supported Provider Capabilities Change
  • Negotiated Power Level Change
• GET_CONNECTOR_STATUS: The system or controller must support these connector status changes within GET_CONNECTOR_STATUS:
  • Supported Provider Capabilities Change
  • Negotiated Power Level Change

For information about the tasks required to implement UCSI in the BIOS, see Intel BIOS Implementation of UCSI.

Example flow for UCSI

The examples given in this section describe interaction between the USB Type-C hardware/firmware, UCSI driver, and the operating system.

DRP role detection

1. USB Type-C hardware/firmware detects a device-attach event and the Windows 10 system DRP system initially becomes the UFP role.
   1. The firmware sends a notification indicating a change in the connector.
   2. The UCSI driver sends a ​ GET_CONNECTOR_STATUS request.
   3. The firmware responds that its Connect Status = 1​ and Connector Partner Type = DFP. ​
2. The drivers in the USB function stack responds to the enumeration.
3. The USB connector manager class extension recognizes that the USB function stack has loaded and hence the system is in the wrong state. It tells the UCSI driver to send Set USB Operation Role and Set Power Direction Role requests to the firmware.
4. USB Type-C hardware/firmware initiates the role-swap operation with the DFP​.

Detecting a charger mismatch error​ condition

1. USB Type-C hardware/firmware detects that a charger is connected and negotiates a default power contract. It also observes that the charger is not providing sufficient power to the system.

2. USB Type-C hardware/firmware sets the slow charging bit.

   1. The firmware sends a notification indicating a change in the connector.
   2. The UCSI driver sends a ​ GET_CONNECTOR_STATUS request.
   3. The firmware responds with Connect Status = 1​, Connector Partner Type=DFP, and Battery Charging Status = Slow/Trickle.

3. The USB connector manager class extension sends notification to the UI to display the charger mismatch troubleshoot message.

How to test UCSI

There are a number of ways to test your UCSI implementation. To test individual commands in your UCSI BIOS/EC implementation, use UCSIControl.exe, which is provided in the MUTT Software Pack. To test your complete UCSI implementation, use both the UCSI tests that can be found in the Windows Hardware Lab Kit (HLK) and the steps in the Type-C Manual Interop Procedures.

UCSIControl.exe

You can test individual commands in your UCSI BIOS/EC implementation by using UCSIControl.exe. This tool enables you to send UCSI commands to the firmware through the UCSI driver. It requires the driver to be loaded and running, and also have the test interface to the driver enabled. By default, this interface is not enabled so as to prevent it from being accessible to unauthorized users on a retail system.

1. Locate the device node in Device Manager (devmgmt.msc) named UCSI USB Connector Manager. The node is under the Universal Serial Bus controllers category.

2. Select and hold (or right-click) on the device, and select Properties and open the Details tab.

3. Select Device Instance Path from the drop-down and note the property value.

4. Open Registry Editor (regedit.exe).

5. Navigate to the device instance path under this key.

   HKEY_LOCAL_MACHINESystemCurrentControlSetEnum<device-instance-path>Device Parameters

6. Create a DWORD value named TestInterfaceEnabled and set the value to 0x1.

7. Restart the device by selecting the Disable option on the device node in Device Manager, and then selecting Enable. Alternatively, you can simply restart the PC.

You can view the help by running UcsiControl.exe /?.

Here are the common commands:

Related topics

If your computer doesn't recognize your connected device, you might see an unknown error or a '0xE' error. If you do, follow these steps and try to connect your device again after each step:

1. Make sure that your iOS or iPadOS device is unlocked and on the Home screen.
2. Check that you have the latest software on your Mac or Windows PC. If you're using iTunes, make sure you have the latest version.
3. Make sure that your device is turned on.
4. If you see a Trust this Computer alert, unlock your device and tap Trust.
5. Unplug all USB accessories from your computer except for your device. Try each USB port to see if one works. Then try a different Apple USB cable.*
6. Restart your computer.
7. Restart your device:
8. Try connecting your device to another computer. If you have the same issue on another computer, contact Apple Support.
   

For more help, follow the steps below for your Mac or Windows PC.

* Learn how to connect iPad Pro (11-inch) or iPad Pro 12.9-inch (3rd generation) to your computer.

Mobile Connector Usb Devices Driver Adapter

If you use a Mac

1. Connect your iOS or iPadOS device and make sure that it's unlocked and on the Home screen.
2. On your Mac, hold down the Option key, click the Apple menu, and choose System Information or System Report.
3. From the list on the left, select USB.
4. If you see your iPhone, iPad, or iPod under USB Device Tree, get the latest macOS or install the latest updates. If you don't see your device or still need help, contact Apple Support.
   

If you use a Windows PC

The steps differ depending on if you downloaded iTunes from the Microsoft Store or from Apple.

If you downloaded iTunes from the Microsoft Store

Follow these steps to reinstall the Apple Mobile Device USB driver:

1. Disconnect your device from your computer.
2. Unlock your iOS or iPadOS device and go to the Home screen. Then reconnect your device. If iTunes opens, close it.
3. Click and hold (or right-click) the Start button, then choose Device Manager.
4. Locate and expand the Portable Devices section.
   
5. Look for your connected device (such as Apple iPhone), then right-click on the device name and choose Update driver.
   
6. Select 'Search automatically for updated driver software.'
7. After the software installs, go to Settings > Update & Security > Windows Update and verify that no other updates are available.
8. Open iTunes.

If you downloaded iTunes from Apple

Follow these steps to reinstall the Apple Mobile Device USB driver:

1. Disconnect your device from your computer.
2. Unlock your iOS or iPadOS device and go to the Home screen. Then reconnect your device. If iTunes opens, close it.
3. Press the Windows and R key on your keyboard to open the Run command.
4. In the Run window, enter:
   %ProgramFiles%Common FilesAppleMobile Device SupportDrivers
5. Click OK.
6. Right-click on the usbaapl64.inf or usbaapl.inf file and choose Install.
   You might see other files that start with usbaapl64 or usbaapl. Make sure to install the file that ends in .inf. If you’re not sure which file to install, right-click a blank area in the File Explorer Window, click View, then click Details to find the correct file type. You want to install the Setup Information file.
7. Disconnect your device from your computer, then restart your computer.
8. Reconnect your device and open iTunes.

If your device still isn't recognized

Kinds Of Usb Devices

Check Device Manager to see if the Apple Mobile Device USB driver is installed. Follow these steps to open Device Manager:

Mobile Connector Usb Devices Driver Updater

1. Press the Windows and R key on your keyboard to open the Run command.
2. In the Run window, enter devmgmt.msc, then click OK. Device Manager should open.
3. Locate and expand the Universal Serial Bus controllers section.
4. Look for the Apple Mobile Device USB driver.
   

If you don't see the Apple Mobile Device USB Driver or you see Unknown Device:

• Connect your device to your computer with a different USB cable.
• Connect your device to a different computer. If you have the same issue on another computer, contact Apple Support.

If you see the Apple Mobile Device USB driver with an error symbol:

If you see , , or next to the Apple Mobile Device USB driver, follow these steps:

Mobile Connector Usb Devices Drivers

1. Restart the Apple Mobile Device Service.
2. Check for and resolve issues with third-party security software, then restart your computer.
3. Try to install the usbaapl64.inf or usbaapl.inf file again.