Welcome to the FlexRadio Community! Please review the new Community Rules and other important new Community information on the Message Board.
Need the latest SmartSDR or 4O3A Genius Product Software?

SmartSDR v3.9.19 and the SmartSDR v3.9.19 Release Notes
SmartSDR v2.12.1 and the SmartSDR v2.12.1 Release Notes

The latest 4O3A Genius Product Software and Firmware
If you are having a problem, please refer to the product documentation or check the Help Center for known solutions.
Need technical support from FlexRadio? It's as simple as Creating a HelpDesk ticket.

wsjt stopped working after win 10 update on 6400

Options
Member ✭✭
edited December 2019 in FLEX-6000 Signature Series
wsjt worked fine before win update last night now the receive signal does not appear to get to wsjt in the green slider to left of wsjt page and have nothing on wsjt water fall. have checked all my setting they weem to be ok.

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In
Register

Answers

  • Member ✭✭
    edited December 2019
    Do a search on "DAX Devices after update"  Windows updates mess up the DAX Device names.  You can fix it yourself or start a ticket and have Tim or someone fix it in a few minutes.

    73 W4SG Dennis
  • Member ✭✭✭
    edited July 2019
    https://community.flexradio.com/flexradio/topics/dax-error-after-widows-update-1907-and-upgrade-to-2-5-1?utm_source=notification&utm_medium=email&utm_campaign=new_topic&utm_content=topic_link

  • Member ✭✭
    edited July 2019
    Dennis got a lot of duplicates in dax devices how do I correct and also how do i make a ticket?
  • Member ✭✭
    edited July 2019
    I've seen many, many posts reporting this problem with Windows updates. It must generate a lot of help tickets.

    Why doesn't Flex put together a routine to remove and reinstall the Dax drivers after a windows update as an option within SSDR 

    I know there's a procedure written down to manually do it but because it's happening so many times you'd think there would be a simple function to do the necessary fix without involving the help desk.

  • Member ✭✭✭
    edited July 2019
    The problem is the Windows update adds registry entries that the original installer did not create. That means the uninstaller will leave DAX-related cruft in the registry that it did not know to remove (because the installer did not put it there). You REALLY don’t want an uninstaller messing in the registry with things it was not responsible for - that’s a recipe for worse problems. Better to deal with this kind of problem with the best AI available - a knowledgeable human :-)
  • Member ✭✭
    edited July 2019
    Flex has a written procedure to manually uninstall and reinstall Dax drivers without messing up the registry. It works. I've used it before. Why can't that same procedure be made into a simple user  function?

    Is the plan to have endless help tickets for every update?
  • Member ✭✭✭
    edited July 2019
    Rather than screwing around with complex uninstalls and HelpDesk Tickets , the optimal solution is to create signed DAX drivers that are impervious to the vagaries of W10 updates. This is NOT a simple task as the driver designer has to anticipate many variable that updates will introduce. However it is possible as many signed drivers now survive most updates.

Leave a Comment

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In
Register

Quick Links

Categories