Most Common Fix for DAX Driver errors in Windows Spring Update (1803) (You can do this!)

Neal - K3NC

As we continue to see high ticket rates related to the Windows Spring Update (often referred to as 1803), we can better recommend actions for our customers to take for fixing the problems.

The Most Common Problem

The most common problem is that the DAX Sound Device names are being mangled during the Spring Upgrade. The diagram below shows what a correct configuration of DAX should look like in the Device Manager:


After the Spring Update, here is what happened to one of my computers:

To list the problems with my installation, highlighted by the boxed entries, we find:

1. We are missing 2 DAX IQ devices, that are present in the correct list. These are DAX IQ RX 2 and DAX IQ RX 4. Some of the mangled named devices are actually these two devices.
2. We are missing 2 RESERVED IQ RX devices, DAX RESERVED IQ RX 2 and DAX RESERVED IQ 4. Again, some of the mangled named devices are actually these two devices.
3. This system is one that I use PowerSDR on to test my Flex-3000 and use Virtual Audio Cables. You can see two of the VAC cables have been mis-named to DAX Audio TX and DAX MIC Audio.

Let's Fix This System!

If you see many multiple devices with the same name, feel uncomfortable in doing this procedure or just cannot figure out what to do, STOP! Create a trouble ticket and let Flex Technical Support work on your system.

Before we begin fixing these issues:

1. Terminate SmartSDR and DAX. I know it sounds simple but I usually forget to do this! Double-check before you begin.
2. Defeat your antivirus and malware software (as much as you can) during this process. Sometimes they will 'sandbox' these actions so they appear to be fixed but once you reboot, no changes are made.

To fix these, I will first right-click on the DAX Audio TX device that is a Virtual Audio Cable and select Uninstall Device. I will get the warning below, but will accept the risk and click Uninstall.


I will repeat this action for DAX Mic Audio device.

To fix the remaining items, I will open the Sound control panel app. When the Sound window opens, right click on it and you will see two items that are usually checked, 'Show Disabled Devices' and 'Show Disconnected Devices'. Uncheck them so we do not see these devices in our list (it will only confuse things!).


Now, click on the Playback tab in case it doesn't automatically open and scan for the name of the first erroneously titled device, which is DAX RESERVED AUDIO RX 2 which has the descriptor 'FlexRadio Systems DAX IQ'. Here you can see two of the mangled named devices in this window:



I will double-click on DAX RESERVED AUDIO 2 and see the property page below:


You notice that the device name is highlighted. I can now rename it to the proper name. Since I am missing a device that should be titled DAX RESERVED IQ RX 2 and this partially matches this device, I will assume its the one I am missing and rename it.


Press Apply, then press OK. You probably only need to press OK but I am a guy who wears belts and suspenders!

Look thru your list and see if any other devices are present that are mis-labeled. If so, repeat this procedure. You will see that the named device is partially correct, you only need to fix the part that isn't. I had a device called DAX RESERVED AUDIO RX 2 and renamed it DAX RESERVED IQ RX 2, for instance.

While you are in this window, make sure no DAX device is designated as the defaul playback device (green cirle with a white check-mark). If so, find the device for your speakers or headset and right-click on it, then select Default Device.

Now, click on the Recording Tab and perform the same action. By the picture below, I found DAX Audio RX 2 that is labeled as an IQ device:


Based on our approach from before, double-click it and rename it to DAX IQ RX 2.


Press Apply and OK and you have fixed another one!

Repeat for all the other misnamed devices you discovered in your examination of the Audio Inputs of the Device Manager.

Now, you have to reboot your system. If you do not, it will not work!

Once you reboot, go to the Device Manager control app and look under audio inputs and outputs, comparing it to the first picture above. It should be identical. If not, try the process again (we have had one customer report it took two tries to work on his system). After that, if it doesn't work, contact Flex Technical Support!

See you on the bands!

Greg N8GD

Neal,

Hiring you was one of the smartest moves FlexRadio has made (not that Tim and others aren't competent).  Your extended knowledge of Windows and how it interfaces with Flex programs has proved to be an invaluable resource for all of us.  Thanks for providing this info to those of us who feel comfortable working "under the hood" of Windows.  I know it will greatly reduce the support load on the Flex organization.

K1UO Larry

I would be happy to second that thought Greg.

Tim - W4TME

Who do you think is teaching him? ;-)

Greg N8GD

Yeah, Tim.  That's why I put the disclaimer in parentheses regarding competency.  I know you're happy to have Neal's help, especially when things like the Win 10 1803 debacle come along.  Don't worry, you'll always be the "Mayor" here on the Community!

Matt NQ6N

Does anyone know how these devices are being renamed or why Windows would decide to rename them to a different name than the one that was configured when they were installed?  Is there an identifier (other than the name) that remains correct/constant even when the update screws up the names? 

Greg N8GD

Boy, if we knew that I'm sure Flex would have had it fixed by now.  I have certain files that have been corrupted in Windows 10 during updates (or as a normal course of operation) that I have made read only.  For those simple cases, it tends to work.  Other files I just make backup copies and replace them after Windows mangles them.  I know this isn't an option for DAX - what Windows 10 does to it is far too complex!  Sometimes Windows 10 updates just like to remove entire apps, drivers, etc. for whatever reason.  I guess Microsoft sees them as security or compatibility risks.  Typically I just reinstall them and they work just fine (until maybe next time - or not).

Tim - W4TME

I am the Exalted Grand PoohBah!  No lowly "mayor" for me :-D 

Tim - W4TME

What and why did Microsoft do what they did?  This is a question that is akin to knowing what is happening inside a black hole.  Seriously, they have code that is designed to "migrate" kernel mode drivers during an update.  These Win10 updates are in reality more like an operating system upgrade and if anyone has done Windows OS upgrades before, you know how brilliantly successful that went.

This is the new "normal" of having an operating system as a service; these updates will continue to mangle stuff and I'll be optimistic, eventually, fingers crossed, they will get better at it.  What we can do is what we have done and that is to mobilize our support resources, find workarounds and fix broken updates as fast as we can.  I know it isn't perfect, and it is frustrating for you as the user and several orders of magnitude more frustrating for FlexRadio Support and Engineering.

Mike-VA3MW

Be aware that the Grand BooBah and his cronies haven't had much sleep in the last week.  And, no, I am not making this up. 

Imagine if this was mission critical applications, as that is the type of service they are providing.  As someone who has been in the Data Protection and Data Recovery business for decades, my hat is off to all of them.

Thanks guys!

Gary L. Robinson

Amen!

Bill W2PKY

Does anyone know why an Uninstall and Reinstall does not correct the the names?
Sorry if I missed it.
I had several other issues with 1803; Printer driver and Meinberg needed to be reinstalled.

Jerry W2TXB

Does the latest (i.e., yesterday's) update affect this problem in any way? I installed this update, and will, when time becomes available) check to see if anything (else) has changed with respect to SmartSDR, DAX, and VSP.


"May 8, 2018—KB4103721 (OS Build 17134.48) Applies to: Windows 10 version 1803

Improvements and fixes

This update includes quality improvements. No new operating system features are being introduced in this update. Key changes include:

• Addresses an issue with the April 2018 Windows Servicing update that causes App-V Scripts (User Scripts) to stop working. 

• Addresses an issue that may cause some devices to stop responding or working when using applications, such as Cortana or Chrome, after installing the Windows 10 April 2018 Update.

  
  
• Addresses an issue that prevents certain VPN apps from working on builds of Windows 10, version 1803. These apps were developed using an SDK version that precedes Windows 10, version 1803, and use the public RasSetEntryProperties API.
• Addresses additional issues with updated time zone information. 
• Addresses an issue that may cause an error when connecting to a Remote Desktop server. For more information, see CredSSP updates for CVE-2018-0886.
• Security updates to Windows Server, Microsoft Edge, Internet Explorer, Microsoft scripting engine, Windows app platform and frameworks, Windows kernel, Microsoft Graphics Component, Windows storage and filesystems, HTML help, and Windows Hyper-V.

If you installed earlier updates, only the new fixes in this package will be downloaded and installed on your device.

For more information about the resolved security vulnerabilities, see the Security Update Guide.

Known issues in this update

Microsoft is not currently aware of any issues with this update."

Rick Hadley - W0FG

I installed this morning's update on both computers with no apparent corruption of the drivers, but I did have to do an additional reboot on both the computer and the radio to get DAX-IQ to recognize the panadaptors for CW Skimmer and DAX-AUDIO to WSJT-X.  Following the reboots all appears normal on both radios and computers.

Tim - W4TME

Yes.  As part of the 1803 Update, Windows tries to "migrate" the DAX kernel-mode drivers and in doing so add a bunch of registry entries that were not added by the installer, so when the uninstaller runs, it does not remove entries that it does not know about.  It is the vestige of registry entries that have to be removed before the installer can re-install the DAX drivers correctly.

Tim - W4TME

I installed the patches yesterday and DAX and CAT are still working just fine on my test machine.  In general, these minor patches do not do the mayhem that an Update does.

AA0KM

Best explanation thanks Tim. It all makes sense now.

Joe - KC2TN

Thanks to everyone for posting their experiences here. After experiencing my own set of problems, these posts helped me recover from a frustrating “NO TX AUDIO” problem when using WSJT-X. Everything else seemed to be OK exception that one driver. I wound up completely removing ALL versions of SSDR and WSJT-X and then “Unhiding” ALL hidden device drivers and then deleting ALL FLEX/DAX related drivers. After reinstalling SSDR and WSJT-X everything worked fine. Took about 30 minutes to fix. However, that was after days of on and off again troubleshooting trying to figure out why my TX audio wasn’t working even though ALL my settings looked OK. Great group here!

Neil N4FN

Good job... Exalted Grand PoohBah!  The only thing better is "Sublime Wizard" and that is reserved for Mack W4AX and Chuck AE4CW

W2PP

OK, I have had some trouble with DAX channels not working right.  I followed the above suggestions and discovered under sound...recording....numerous copies of DAX channels.  How do I know which ones to delete they all look correct, its just their are multiple copies of of the DAX channels, especially 2,3,4 the ones I had problems with??????

Should I just open a support ticket??

Peter

Jay Nation

Peter

First take a look in Device Manager, and  not under Sound ... recording, etc, which serves a different function entirely, it's used to modify the properties of installed devices, not add or remove them.

For me the correct number of DAX devices is a total of 28. That's 8 DAX Audio RX devices, 8 DAX Reserved Audio RX devices, 4 DAX IQ RX devices, 4 DAX Reserved IQ RX devices, 1 DAX Audio TX device, 1 DAX Reserved Audio TX, 1 DAX Mic Audio device and 1 DAX Reserved Mic Audio device.

All of them are required, but depending on your radio model some may never be used. but SmartSDR expects all of them to be there.

If you're missing any of those, or have any that are duplicated, you will eventually have problems with DAX.

Also, occasionally Windows Updates, fail to update, occasionally SmartSDR DAX when installed has failed to cleanly remove all of them and after reinstalling SmartSDR, you may find broken, misnamed, or duplicated "Ghosted" DAX devices. 

So yes, you can end up with the wrong number of devices. 

If you see that trouble performing a Full Clean, Removal and Reinstall of SmartSDR, should result in the correct 28 devices.

https://helpdesk.flexradio.com/hc/en-us/articles/204975589-How-to-do-a-Complete-uninstall-of-SmartSDR-for-Windows-from-your-PC 

Doing so can return your PC back to the state it was in before the first installation of SmartSDR, allowing you to reinstall it correctly.

Just about anything else you try to do, is unlikely to improve the problem.


Windows call these DAX devices Audio Endpoints, think of them as the RCA connectors on the ends of an audio patch cable, a total of 14 virtual audio patch cables, the Reserved devices are the ends that are virtually connected at the radio end of the cable, the other end is the end that virtually connects to digital software, you will run on the PC. 

Removing any of the required Endpoint devices is like Virtually snipping off the RCA connectors from the virtual audio patch cables. They can't be repaired, only replacement will work. Think of any Ghosted endpoints as virtual RCA connectors with the virtual cable wire Damaged, Destroyed, or removed too. Just like any other damaged/destroyed connector you find in your Junk Box, they are Virtually useless. 

#FlexRadio IRC chat

   73, Jay - NO5J

Michael Pfaeffle (K3FEF)

WOW!  I was struggling with the old scripts for the driver errors - rebooting at each step - nothing.  Then I found this and.... BINGO!  It worked.  Thank you!

David Martin

Thanks Jay for your very informative text, especially the link that I haven’t seen before. I have been unable to get all the Dax drivers successfully installed on Windows 10 - and neither can I get them uninstalled. The uninstallation stalls at: Processing HWID FlexRadioSystems_DAX_IQ That is as far as uninstallation progresses. I’m confident that if I can ever uninstall, I’ll be able to,install correctly! Any comments or suggestions would be appreciated. Dave WA5KCP

Jay Nation

Dave
If you drop in to the IRC channel, maybe I can get you sorted out. the link to the webchat client is in my signature below.  Fill in your callsign as your nickname and hit enter.

    #FlexRadio IRC chat

For real-time discussions

        SDRgadgets

User created documentation.
           Volunteer!!

         73, Jay - NO5J

K5CG

This site can’t be reached

www.sdrgadgets.com took too long to respond.

Jay Nation

Danny

OOPs, I had a power glitch yesterday.
SDRgadgets should be back online now.

    #FlexRadio IRC chat

For real-time discussions

        SDRgadgets

User created documentation.
           Volunteer!!

         73, Jay - NO5J

Neal Pollack, N6YFM

Tim mentioned that the reason an uninstall/reinstall cycle does not fix it is because MickySoft with their windows update migrated the entries to a new name and created registry entries that the Flex installer did not create.   Hence the Flex installer package did have that list of registry entries to uninstall.

As someone both cost conscience and also all about customer satisfaction, I still maintain the point
I made earlier;   If Flex wants to save money and reduce both user frustration and time spent on
support calls, they need to add an optional click-box on the installer package prompt screen that
lets the user select "Deep Clean, Re-Install", which will warn the user to backup profiles, then
proceed to scan the registry, purge ANY entry with Flex's keywords (This is what Norton
Uninstaller/cleaner does), and then after that proceed to reinstall.     With coding, it is very easy to
match/find the registry entries that MickySoft migrated with their update.   The risk is low in doing that.   The rewards are huge, both financially and customer frustration wise.

Work Smart, Not Hard.

Neal

ON7NQ - Danny

Still having an issue I can't seem to resolve..
On 1 PC all audio devices are ok but on the 2nd PC I still get an error.
At first look I don't have an "ghost" devices but when you look into detail it says :

Device SWDMMDEVAPI{0.0.1.00000000}.{ad21fc8f-b2b5-45ef-bd3a-995c7fa845ee} was not migrated due to partial or ambiguous match.

Last Device Instance Id: SWDMMDEVAPI{0.0.0.00000000}.{c62aa6db-c543-4e0d-a6a2-c6fbcdb31852}
Class Guid: {c166523c-fe0c-4a94-a586-f1a80cfbbf3e}
Location Path:
Migration Rank: 0xF00000000000F120
Present: false
Status: 0xC0000719

I'm guessing this could be a Realtek driver issue...I did an update of the drive prior to installing SmartSDR..Anyone have a clue ?Thanks..
73 - ON7NQ Danny

OK disregard ! Found the problem...ugh

John - K3MA

IF you are having trouble figuring out if a DAX device is the right name or not or what name to correct it too.  You can find out the correct name before Windows changed it by going to the Level tab and you will see the old correct name above the level bar.  Seems that Windows missed changing that also.

KC9EI - Dave

Jay is stellar and spent hours working with me on the issue a short time ago. I don't think I properly thanked him then so I will here.. Thank you Jay for sticking with me!!!
 

Chuck - KJ6HT

John,
Many thanks, your tip on finding the correct name on the level tab really helped.