Windows 10 november update 1511 broke DAX...

  • 2
  • Problem
  • Updated 3 years ago
  • Solved
I did the Win 10 november update tonight. That broke my CAT ports and DAX drivers. Uninstalled SmartSDR 1.5.1, and made a new install. Now  CAT works, but DAX still broken. Se enclosed error window. 

73 de LB2EG Richard


Photo of Richard Saue

Richard Saue

  • 3 Posts
  • 1 Reply Like

Posted 3 years ago

  • 2
Photo of KM6CQ - Dan

KM6CQ - Dan

  • 173 Posts
  • 34 Reply Likes
Official Response
Okay, 
So I updated to win 10 a couple of months ago. I did not unistall SSDR. Everything worked as it normally does. Then Win 10 updated last week and broke all the VSP. 
So last night I did a complete uninstall of SSDR following the exact procedure by Tim Ellison here, https://helpdesk.flexradio.com/hc/en-us/articles/204975589-How-to-do-a-Complete-uninstall-of-SmartSD...
And it all works perfectly now. I thought it was interesting to see all of the greyed out ghost comports that were not in use. 
Photo of Wim

Wim

  • 95 Posts
  • 19 Reply Likes
Well since someone mentioned 3 times is a charm, me too did another round of full uninstall per guidelines plenty of reboots, then had to instal;l SmartSDR twice as the first time it complained about VSP not being loaded, another reboot and now smartCAT was showing a COM port in the 'connect 3rd party programs here'. Then I plugged in Flex Control, and created two more COM ports one for Digital programs CAT port and one for PTT CAT port.

So now I have Win 10 SP1 with SmartSDR 1.5.1 running but it sure is not a slam dunk install.
Photo of Jay / NO5J

Jay / NO5J

  • 1621 Posts
  • 235 Reply Likes
Wim
I find hard one successes, are usually more satisfying in the long run. 
Congratulations! Wim. You seem to have won this round. There will be "quite a few", "more" rounds
in the future.  If at first you don't succeed, Do the whole procedure over again and again, step by step, until the software learns it's not the boss. 

On to the next battle!
For we are warriors!


73, Jay - NO5J
Photo of Roy Laufer

Roy Laufer

  • 439 Posts
  • 45 Reply Likes
Wasn't Einstein erroneously quoted as saying:

"The definition of madness is a man who does the same thing over and over again, expecting a different outcome?"

Whoever really originated that line never had to deal with Microsoft Windows!

Roy AC2GS
Photo of Wim

Wim

  • 95 Posts
  • 19 Reply Likes
It sure was fun to go through this (not)... Can't wait for SP2 and do it again ;-)
July next year it is, I'll avoid the ham shack for a while then ...
Photo of Jay / NO5J

Jay / NO5J

  • 1621 Posts
  • 235 Reply Likes
They changed the definition a few years back to. "The definition of madness is Microsoft".

There's also a proposed redefinition, "The definition of madness is Microsoft, and it's repeat customers". Some of the customers objected, many just nodded in affirmation and shrugged.

73, Jay - NO5J 
Photo of Jerry - W2TXB

Jerry - W2TXB

  • 88 Posts
  • 17 Reply Likes
Count me in as one whose SSDR 1.5.1 presented with the OP's signs and symptoms, but also count me in as one who did a complete removal of SSDR, CAT, and DAX (using Win 10 Control Panel's "Uninstall" method) and reinstalled everything. I then loaded (imported) my settings, and it all works as it should. :)

Now that I have posted this, I am wondering if I jinxed myself and my SSDR... probably should not have posted this. ;)

My station setup is: Win 10 w/ latest updates, 6700, FLDigi (latest version, which I left as is); PC is a home built (recently rebuilt and upgraded) i5/3.5 gHz CPU, 16-gb RAM, and Wi-Fi connection to router.

Sincere thanks to all who have posted suggestions and experiences here. As always, the FlexRadio team and those "in the field" are an extraordinary crew.
(Edited)
Photo of k3Tim

k3Tim

  • 865 Posts
  • 170 Reply Likes
After Jay provided details of the 1511 update work he performed, I thought I'd have a go also. As expected, DaX broke. I noticed the Device Mgr showed two copies of each channel.  It appears Windows update somehow messed up those drivers. I uninstalled DaX and removed all the devices from the Dev Mgr, including several hidden ones.  Reinstalled Dax driver only (in admin mode) bringing DaX back to life.  FlDigi  was now working with Dax but not CAT.

CAT was more of a challenge. Again, an uninstall and removal of all CaT-TTY devices from the dev mgr and reinstall of VSP didn't work till about the third time (notice the # theme here).  Not sure if it was the magic of three or that the radio was connected at the 3rd try of the install.  Anyway - FLDIGI and SDR working well.

At no point was removal of SDR required or contemplated.  This makes sense (at least to me) since the only driver used by SDR is the OS built-in ethernet.  Other drivers had problems with the update, although the Flex Controller was 100% perfect.  The FC worked right off the bat.

An LG Blue Ray CD driver had to be removed / reinstalled to get working again.  Also noticed some BT devices that use a Com5 / Com6 port are acting up but will leave that for another day.

Good Luck to all who go for it.

k3Tim
Photo of Jay / NO5J

Jay / NO5J

  • 1621 Posts
  • 235 Reply Likes
I think it's more about what happens and when.

Windows "Normally??" (As If!), loads drivers and enumerates devices when it's restarted. The 1511 upgrade had no way of knowing that we had all of these software DAX and Com devices that needed special attention. It's better that our devices got ignored, instead of causing the upgrade process to blue screen and leave us with an unbootable mess.

My guess is if someone tried installing SSDR and set it up, with a brand new PC which was already update/graded with 1511. Then SSDR might install as it's supposed/intended too. Thus the need "this" time to start over with a clean slate. Complete removal and reinstall is just an easier/faster way to achieve that.

Does anyone remember  back when Windows used to insist on rebooting nearly anytime you installed software on it. It probably didn't need a reboot, but if it did, well they conned you into a reboot anyway didn't they. This still happens with some driver installs, where you can't use a feature until the driver gets loaded at boot. We could probably improve the Complete Removal and Reinstall SmartSDR document, as soon as we know where to insert the "After step X is complete you must reboot the PC "Now"before proceeding to Step X+1" steps. Every step matters and it matters what order they get done in. Skipping steps just means you might have to start over with step 1. Extra reboots don't hurt.

I just inserted reboot steps anytime a quick check of Device Manager failed to show the expected working devices. I tried to take notes as I went, about where the reboots were needed, but I got impatient the closer I got to finishing up, and the note taking got a little vague. I really hope that these Threshold/Service Pack upgrades aren't always go to end up, similar to running a "Windows Upgrade Disk" Install like this was.

One new feature is, after 1511, we should be able to perform a Clean Install using a valid Win7, 8, 8.1 key during the install so we won't need to install Win7 or Win8.1 first, in order to upgrade and only then validate Win10. Who wants to go first??

Clean Installs are always easiest, and you get the final say about any bloatware installation doing it that way. 

73, Jay - NO5J
   
(Edited)
Photo of Cal Spreitzer - N3CAL

Cal Spreitzer - N3CAL

  • 36 Posts
  • 3 Reply Likes
Since I'm currently without a radio (waiting on upgrade to Flex 6500)  I decided to do the upgrade to 1511.  I uninstalled SSDR1.5.1 and DAX first.  I did not uninstall Flex VSP.  The upgrade went okay but after it completed I noticed this:



So I went ahead and uninstalled Flex VSP.  I'll have to wait until my new 6500 arrives to install SSDR 1.5.1 again.  fingers crossed...

Cal/N3CAL
Photo of Jack - WA2OLZ

Jack - WA2OLZ

  • 15 Posts
  • 0 Reply Likes
Troglodyte that I am, my dedicated SDR-controlling computer will remain as a Win 8 machine with all access for the mobsters from Redmond blocked and locked - no patches, no updates, no Service Packs or Threshold of Pain permitted.
Photo of Jon - KF2E

Jon - KF2E

  • 651 Posts
  • 198 Reply Likes
I hope you don't allow the computer internet access if you aren't keeping it current with updates. It's the quickest way to get your computer infected.
Photo of Jack - WA2OLZ

Jack - WA2OLZ

  • 15 Posts
  • 0 Reply Likes
You are spot on, Jon. The computer is isolated for the web. I figure if it's not broke, no need to fix (update) it. I sometimes miss QRZ or the DX-Watch on the same system, but can live without them. After all, what did we do before Al Gore invented the Internet? Talk!

However, once the hackers figure a way to get to my computer via the Flex radio and RF my whole isolationist plan falls apart.
Photo of Chris DL5NAM

Chris DL5NAM

  • 637 Posts
  • 138 Reply Likes
... you forgot : Power Line :-)
Photo of Drax

Drax

  • 99 Posts
  • 13 Reply Likes

This is all I get with the Windows 10 November upgrade.  I had to roll back using a system image restore.

This conversation is no longer open for comments or replies.