Midi fighter classic on windows 10 : device not recognized (after windows update)
Results 1 to 10 of 10
  1. #1
    Tech Student
    Join Date
    Mar 2011
    Posts
    4

    Default Midi fighter classic on windows 10 : device not recognized (after windows update)

    Using the device every week. Suddenly today after a windows 10 update, the device manager says 'invalid device descriptor' for the midi fighter usb device.

    Tried all the tricks already that I could find on the internet. Tried a different cable.

    Anyone else has this problem? Maybe the device is dead, also possible.

  2. #2
    Tech Student
    Join Date
    Mar 2011
    Posts
    4

    Default

    Device USB\VID_0000&PID_0005\6&b9bc6fb&0&1 was configured.

    Driver Name: usb.inf
    Class Guid: {36fc9e60-c465-11cf-8056-444553540000}
    Driver Date: 06/21/2006
    Driver Version: 10.0.15063.0
    Driver Provider: Microsoft
    Driver Section: BADDEVICE.Dev.NT
    Driver Rank: 0xFF0000
    Matching Device Id: USB\DEVICE_DESCRIPTOR_VALIDATION_FAILURE
    Outranked Drivers: usb.inf:USB\DEVICE_DESCRIPTOR_VALIDATION_FAILURE:0 0FF2000
    Device Updated: false
    Parent Device: USB\VID_0451&PID_8142\MSFT20090A00814048

  3. #3
    Tech Student
    Join Date
    Mar 2011
    Posts
    4

    Default

    Tested in linux and got the same result. So it's not windows update that did it. RIP midifighter ... . Don't know what I could still do.

    ..
    [11334.582307] usb 1-2.1: new full-speed USB device number 23 using xhci_hcd
    [11334.603342] usb 1-2.1: device descriptor read/8, error -61
    [11334.731267] usb 1-2.1: device descriptor read/8, error -61
    [11334.838458] usb 1-2-port1: unable to enumerate USB device

  4. #4
    DJTT Administrator del Ritmo padi_04's Avatar
    Join Date
    Nov 2009
    Location
    Argentina
    Posts
    6,448

    Default

    Opened a support ticket for you to try and solve the issue.

  5. #5
    Tech Convert
    Join Date
    Feb 2010
    Location
    Costa del Sol, Spain
    Posts
    6

    Default

    Was there ever a resolution to this?

  6. #6
    DJTT Administrator del Ritmo padi_04's Avatar
    Join Date
    Nov 2009
    Location
    Argentina
    Posts
    6,448

    Default

    The device was bricked and needed replacing.

  7. #7
    Tech Convert
    Join Date
    Feb 2010
    Location
    Costa del Sol, Spain
    Posts
    6

    Default

    Yeah, that's cool, but there's no reason for my devices to be bricked. They were working perfectly fine the last time I used them and now they aren't.

    Two DIY kits, with the rubber surrounds, sat on the shelf for a couple years and now when I plug them in they aren't recognized by the utility.

    Am I simply forgetting something? Do I need to put them in a special mode for them to be recognized? I think I'm missing something... forgive me, it's been awhile.

  8. #8
    DJTT Administrator del Ritmo padi_04's Avatar
    Join Date
    Nov 2009
    Location
    Argentina
    Posts
    6,448

    Default

    What exactly isn't working with your devices? Each case is different since you are using different hardware. I'm not saying the only solution to Classic issues on W10 is getting a new Midi Fighter.

  9. #9
    Tech Convert
    Join Date
    Feb 2010
    Location
    Costa del Sol, Spain
    Posts
    6

    Default

    They simply are not recognized by the utility. I plug them in, they light up and go through the usual light dance that happens, but the utility says there's no Midifighter recognized and to plug one in.

  10. #10
    DJTT Administrator del Ritmo padi_04's Avatar
    Join Date
    Nov 2009
    Location
    Argentina
    Posts
    6,448

    Default

    If the unit plays it's initial animation and it sends MIDI to other software then it's most likely alright. Send an email to support@djtechtools.com and we'll help you out.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •