Re: [libusb] OT: Stuck at "Device was not migrated due to partial or ambiguous match."

[RisingEdgeIndustries <su...@ri...>]

So I have actually done some removal with the following paths, but I'm
pretty new so not sure how much is missing or if one of these is
unnecessary.

Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbstor
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags

In flags folder the subfolders are VIDPID and I deleted all the entries in
there.  This allowed my device to re-enumerate fresh or at least it looked
that way for me to do testing.

Robbie Valentine
Electrical Engineer
RisingEdgeIndustries
(256) 244-4091


On Tue, Jul 4, 2023 at 5:23 AM Kustaa Nyholm <Kus...@pl...>
wrote:

> Thank Tim, re hacking the registry.
>
>
>
> This is a semi hobby project for me and the users so I'm not sure the user
> is against hacking his machine.
>
>
>
> So, what keys should/could be removed from registry?
>
>
>
> Definitely my systems should not care if the device settings are migrated
> or not (I was not even aware there
>
> were device settings related to a simple generic HID device where (as far
> as OS is concerned) the only
>
> functionality is that the device is capable to send and receive 64 byte
> chunks of bytes.
>
>
>
> wbr  Kusti
>
>
>
>
>
>
>
>
>
> *From: *Tim Roberts <ti...@pr...>
> *Date: *Monday, 3. July 2023 at 21.16
> *To: *lib...@li... <
> lib...@li...>
> *Subject: *Re: [libusb] OT: Stuck at "Device was not migrated due to
> partial or ambiguous match."
>
> Hmm.  I don't understand that at all.  If you do an "uninstall", that
> should remove the vestiges of the old installation and start over.  If I
> had the system, I would hack the registry to remove the old instance, but
> that's not acceptable on a customer system.
>
>
>
> Does the device work?  You probably don't care if the device settings were
> migrated, as long as it operates.  Is this just an annoying warning?
>
>
>
> Perhaps the [NTDEV] folks can give you a clue.
>
> --
>
> Tim Roberts, ti...@pr...
>
> Providenza & Boekelheide, Inc.
>
>
>
>
>
> Kustaa Nyholm wrote:
>
>
>
>
>
> *From: *Tim Roberts <ti...@pr...> <ti...@pr...>
> *Date: *Monday, 3. July 2023 at 3.19
> *To: *lib...@li...
> <lib...@li...> <lib...@li...>
> *Subject: *Re: [libusb] OT: Stuck at "Device was not migrated due to
> partial or ambiguous match."
>
> There are two device objects involved here, and hence two listings in
> Device Manager.  There is a USB device, which has the format
> USB\VID_xxxx&PID_xxxx&REV_0100\....  That should have automatically loaded
> usbhid.sys, which then creates more devices for your top-level collection,
> which should have th format HID\VID_xxxx&PID_xxxx&REV_xxxx&COL_01.  If your
> device has a yellow bang icon in Device Manager, which one is it?
>
> This what my user reported when I asked your question:
>
>
>
> Yes, 2 new items appear when Toad4 is plugged in.
>
> The first one is "HID-compliant vendor-defined device", Information is:
>
>
>
> Device settings for HID\VID_1D50&PID_6020\6&2801700&1&0000 were not
> migrated from previous OS installation due to partial or ambiguous device
> match.
> Last Device Instance Id: USB\VID_17EF&PID_6019\5&2059b984&0&2
> Class Guid: {745a17a0-74d3-11d0-b6fe-00a0c90f57da}
> Location Path:
> Migration Rank: 0xF000FFFFFFFFF120
> Present: false
> Status: 0xC0000719
>
>
>
> The second one is "USB Input Device", Information is:
>
>
>
> Device settings for USB\VID_1D50&PID_6020\0000363 were not migrated from
> previous OS installation due to partial or ambiguous device match.
> Last Device Instance Id: USB\VID_17EF&PID_6019\5&2059b984&0&2
> Class Guid: {745a17a0-74d3-11d0-b6fe-00a0c90f57da}
> Location Path:
> Migration Rank: 0xF000FFFFFC00F130
> Present: false
> Status: 0xC0000719
>
>
>
> There is no yellow icron showing.
>
> It looks like both USB\VID and HID\VID are not quite right.
>
>
>
>
>
> This e-mail may contain confidential or privileged information and is
> intended solely for the person to whom it is addressed. If you have
> received this e-mail in error, please notify the sender immediately and
> destroy this e-mail. Any unauthorized copying, disclosure or distribution
> of the material in this e-mail is strictly forbidden. We will not be liable
> for direct, indirect, special or consequential damages arising from the
> alteration of this e-mail, or as a result of any virus being passed on or
> as of transmission of this e-mail in general.
>
>
> _______________________________________________
>
> libusb-devel mailing list
>
> lib...@li...
>
> https://lists.sourceforge.net/lists/listinfo/libusb-devel
>
>
> This e-mail may contain confidential or privileged information and is
> intended solely for the person to whom it is addressed. If you have
> received this e-mail in error, please notify the sender immediately and
> destroy this e-mail. Any unauthorized copying, disclosure or distribution
> of the material in this e-mail is strictly forbidden. We will not be liable
> for direct, indirect, special or consequential damages arising from the
> alteration of this e-mail, or as a result of any virus being passed on or
> as of transmission of this e-mail in general.
> _______________________________________________
> libusb-devel mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-devel
>