Windows 10 (1903 Update Audio Changes)

Discussion in 'Computers, Hardware, and Operating Systems' started by G0KDT, Nov 13, 2019.

ad: L-HROutlet
ad: l-rl
ad: L-MFJ
ad: Left-2
ad: Subscribe
ad: Left-3
  1. G0KDT

    G0KDT Ham Member QRZ Page

    Hi people

    Ignore this note if you wish. I am posting it because the update changes recently resulted in me having to completely reinstall windows, all software and data to my laptop.

    I run a Kenwood TS590SG and like a lot of rigs it utilises a USB port for comms and audio. The audio feature is good because in theory it simplifies hooking the rig to WSJT-X or MMTTY of FLDigi etc... all good ( even if the art of configuring everything can be a bit testing ).

    You will note that when the rig is connected to the USB then its relatively easy to select the USB Codecs (which you can rename) to provide the audio to such software, indeed windows 'itself' does tend to default to the usb device when its plugged in. So now your playback audio volume setting will affect the modulation to the rig (like changing mic gain against ALC settings), so pretty critical.

    The update added a facility to associate applications eg. WSJT-X with audio devices and volume settings so that they can be consistent. That sounded great until I actually tried it The result was that it disconnected the audio from the rig into WSJT-X and each time I started WSJT-X it said 'USB Audio Device - An Error Opening the Audio Input Device has occurred'. I wasted many hours trying to recover the situation including looking at the USB device logs which can be accessed from the device driver application and then the device itself. The logs showed something had gone on as follows with 3 logged items;

    Looking at the device events, there are three as follows;

    The first:

    Device USB\VID_08BB&PID_29B3&MI_00\7&1175028a&1&0000 was not migrated due to partial or ambiguous match.

    Last Device Instance Id: SW\{97ebaacc-95bd-11d0-a3ea-00a0c9223196}\{53172480-4791-11D0-A5D6-28DB04C10000}
    Class Guid: {4d36e96c-e325-11ce-bfc1-08002be10318}
    Location Path:
    Migration Rank: 0xF000FFFFFFFFF132
    Present: false
    Status: 0xC0000719

    The Second:

    Device USB\VID_08BB&PID_29B3&MI_00\7&1175028a&1&0000 was configured.

    Driver Name: wdma_usb.inf
    Class Guid: {4d36e96c-e325-11ce-bfc1-08002be10318}
    Driver Date: 03/18/2019
    Driver Version: 10.0.18362.1
    Driver Provider: Microsoft
    Driver Section: USBAudio
    Driver Rank: 0xFF2002
    Matching Device Id: USB\Class_01
    Outranked Drivers:
    Device Updated: false
    Parent Device: USB\VID_08BB&PID_29B3\6&354118f7&0&1

    The Third:

    Device USB\VID_08BB&PID_29B3&MI_00\7&1175028a&1&0000 was started.

    Driver Name: wdma_usb.inf
    Class Guid: {4d36e96c-e325-11ce-bfc1-08002be10318}
    Service: usbaudio
    Lower Filters:
    Upper Filters:

    No matter what I could do I could not clear these or restore the audio function without a complete reinstall of windows and all my software, office and mail clients etc. etc. some 24 Hrs later I think I am back and operational.

    So this is just a warning that you may find suffer such problems it you try to use the new feature. Shame because it does mean that I have to go through and check the setting each time I want to use the radio with audio etc. via the pc. Incidentally none of this affected the Virtual comm port and the laptop ability to remote the rig itself with commands via the rig software JUST the Audio.

    Hope it helps and sorry if you have experienced similar, I feel your pain.
    Phil GOKDT
    KA9JLM likes this.


    Well.....a lot of water under the bridge..
    dont you just love computers and windows
    you stick to your data i remember your dull set tones on the radio
    hope alls well your end

Share This Page