Windows 10: In need of a Windows driver expert. COM ports/ambigious device name/Not migrated.

I've cross posted to .Net in case a programmer there knows what's going on.

I've marked this as a bug as Windows gives no way of fixing this issue. (probably because it's so rare)

The details: https://www.reddit.com/r/dotnet/comments/13ffkk6/writing_a_program_systemioports_the_ports/

From the little I could glean.. I updated Windows 7 to 10 a few years ago, and this message is something about the driver subsystem needing to update Win 7 drivers to the Win 10 core - EVERY TIME it's plugged in. (WTH!?!?!? That's some research for another day - not that I can find anything useful! )

That's fine - it's always done that, but since I added some new USB hardware it started failing for all my other COM devices.

How do I diagnose and correct an "Device not migrated" error? Properly? I expect I need a tool.

......

I clicked on the "Events" to see why there were no drivers now for my vitual COM port devices I plug in , and found some "Not migrated" errors....

Device USB\VID_10C4&PID_EA60\01DAB3FA was not migrated due to partial or ambiguous match.

Last Device Instance Id: USB\VID_10C4&PID_EA60\6&a4f55e&0&4

Class Guid: {4d36e978-e325-11ce-bfc1-08002be10318}

Location Path: PCIROOT(0)#PCI(1A00)#USBROOT(0)#USB(1)#USB(4)

Migration Rank: 0xF000000000000132

Present: false

Status: 0xC0000719

--------------------------

I DID "resolve" this by rolling back using a restore point. I learned NOTHING!

That's like using a hammer to fix a switch.

The stock answers online are not what I'm after..... uninstall device, reinstall device, reboot windows, run sfc /scannow.... blindly crashing through settings and files.

Also of these reasons often given in "fixit" pages, the top one is relevant but 4 years ago!:

• Windows Upgraded from an older version.
• Corrupted System files
• Outdated driver
• Dual boot system
• Windows not up-to-date
• Issues with internal components
• Peripheral device not supported

I want to know what's going on - via diagnoses, and gentle manipulation of the environment.

I've learned there's a service involved in this "Device Setup Manager service" (DsmSvc), and there's a cache of previously added USB hardware:%programdata%\Microsoft\Windows\DeviceMetadataCache\dmrccache\

But I've found no software that can show what is ambiguous about the hardware names recently added.



I get a tingly feeling I'm on the write track with THIS software, but I lack the skills to use it:

https://www.nirsoft.net/utils/usb_devices_view.html

Is this the KEY to solving ambiguous device ID?





submitted by /u/SarahC
[link] [comments]

:)

 

Device could not be migrated....

Hi Henrik,

For us to isolate the issue and better assist you regarding your concern, we would like to ask some additional information:

• Does it happen every time you use video call on Skype?
• Have you done any changes on your computer prior to the issue?
• Have you tried updating any drivers?

We suggest that you try the troubleshooting steps provided by AntonyJose on this

link.

We will wait for your response.

 

Device not migrated

Hi, lots of results if you search for
device not migrated due to partial or ambiguous match

- suggest uninstalling the root hubs and let them reinstall on reboot.

Did this occur after a Windows update was applied? (See Update History).

 

USB Port Oddities


Ok, let's see it with pictures step-by-step. First right-click on the USB device and select Update driver software:





Then select Browse my computer for driver software (LAST option) :





The select Let me pick from a list of device drivers on my computer (LAST option) :





Then select the standard driver from the list and click next:





Click next/OK as required to complete installation. Repeat the steps for all Intel USB devices. Finally click on each USB root device and press DEL to delete it, reply YES when asked. After deleting all USB root devices restart the computer.

I hope this is detailed enough...