Hi,
I have a faulty IPad Pro which apple shop say can't be repaired. However I wanted to try myself as I noticed that whenever the Ipad Pro failed to communicate was when two drivers come in NCM Data and NCM Control.
I am getting rather confused regarding the the correct driver for my windows Pc when I connect it to my Apple IPad Pro. It would appear that windows have removed the driver for this device at some point in time and I just can't find any usbNCM driver on the PC. I have reloaded ITunes sever times and bought a copy of an IPAD fixing tool on line, However it always says this problem is down to windows.
Now I'm not saying I am going to fix this Ipad, it could be a hardware problem, however I suspect the problem was more than likely caused by an upgrade to 17.2 as both myself and wife had the same upgrade on our phones the day this Ipad failed. but I would like to go or at least get it to communicate through the NCM drivers.
So after all the background my question is what driver do I need? I just don't want to get the wrong one, I've already done that once, but managed to recover from it.
My PC is
Device name DESKTOP-L6C1UG3
Processor AMD Ryzen 5 2400GE with Radeon Vega Graphics 3.20 GHz
Installed RAM 8.00 GB (7.69 GB usable)
Device ID 1701CDE6-74CD-46B8-8970-A1D4DBC90052
Product ID 00325-96311-95575-AAOEM
System type 64-bit operating system, x64-based processor
Pen and touch No pen or touch input is available for this display
Examples of what I get from Event Manager are,
The drivers for this device are not installed. (Code 28)
There are no compatible drivers for this device.
To find a driver for this device, click Update Driver.
Events
Device USB\VID_05AC&PID_12AB&RESTORE_MODE&MI_01\7&3343f50&0&0001 was configured.
Driver Name: null
Class Guid: {00000000-0000-0000-0000-000000000000}
Driver Date:
Driver Version:
Driver Provider:
Driver Section:
Driver Rank: 0x0
Matching Device Id:
Outranked Drivers:
Device Updated: false
Parent Device: USB\VID_05AC&PID_12AB\00008027-001661623E84402E
NCM Data
Device USB\VID_05AC&PID_12AB&RESTORE_MODE&MI_01\7&3343f50&0&0001 was configured.
Driver Name: null
NCM Control
Device USB\VID_05AC&PID_12AB&RESTORE_MODE&MI_00\7&3343f50&0&0000 was started.
Driver Name: oem68.inf
Class Guid: {88bae032-5a81-49f0-bc3d-a4ff138216d6}
Service: WINUSB
Lower Filters:
Device USB\VID_05AC&PID_12AB&RESTORE_MODE&MI_01\7&3343f50&0&0001 was not migrated due to partial or ambiguous match.
Last Device Instance Id: USB\VID_17EF&PID_608C&MI_01\8&bc4f0bc&0&0001
Class Guid: {745a17a0-74d3-11d0-b6fe-00a0c90f57da}
Location Path: PCIROOT(0)#PCI(0801)#PCI(0004)#USBROOT(0)#USB(1)#USB(1)#USBMI(1)
Migration Rank: 0xF000FFFFFFFF0023
Present: false
Any help greatly appreciated
Reply: It seems that this issue is caused by the system upgrade, and it is unrelated to the Windows system. I suspect that after the upgrade, there might have been a change in the communication protocol, leading to hardware communication failures.