Windows 10 version 1703

  • 3
  • Problem
  • Updated 1 year ago
My PC accidentally rebooted and upgraded from 1607 to 1703 and it broke DAX drivers and forced m to revert to 1607.   If you use Windows 10, you'd better defer the upgrade.  Upgrade and revert process takes time.

Photo of Takeshi Yamada

Takeshi Yamada

  • 170 Posts
  • 48 Reply Likes

Posted 1 year ago

  • 3
Photo of Alex - DH2ID

Alex - DH2ID, Elmer

  • 894 Posts
  • 166 Reply Likes
You can try the last posting by N3CAL in this thread: 

https://community.flexradio.com/flexradio/topics/windows-10-update-strikes-again?topic-reply-list%5B...

or deinstall and reinstall the latest SSDR version.

Reverting to an earlier Win10 version is only a short-term measure, as Win10 will update again.

This is Cal's official response:

"...Following Flex Support Advise all I had to do was repair the FlexVSP program.  Under installed programs you right click on FlexVSP and select repair..."

73, Alex - DH2ID
(Edited)
Photo of Takeshi Yamada

Takeshi Yamada

  • 170 Posts
  • 48 Reply Likes
I tried deinstall/reinstall several times, but it did not help.  Also, CAT worked OK in my case.  It was DAX and in some case it looked OK at installation, but it gives "Driver error" when SmartSDR is started and  connected to Flex6XXX.

73, Ken - JI1BNU/JA2IYJ
Photo of Alex - DH2ID

Alex - DH2ID, Elmer

  • 894 Posts
  • 166 Reply Likes
Ken, did you try to repair FlexVSP as described above?
Photo of K3DCW

K3DCW

  • 55 Posts
  • 17 Reply Likes
Not that it helps you with your problem, but I've had no problem running the Windows 10 1703 update here. Everything worked fine before and after the update.  
Photo of N5LB - Lionel B

N5LB - Lionel B

  • 131 Posts
  • 23 Reply Likes
I experienced numerous  issues with the upgrade to 1703 and eventually did a clean install.  All of my apps had to be re-installed.  Then FlexVSP had to be installed and repaired one more time before it became stable.  No issues with DAX.  No error messages at W10 install. 

Just what a "clean install" of W10 means is unclear to me and I suspect some registry entries remain orphaned.   Nevertheless, it seems to have done the trick.  Ah, the ol'days - format C, so last century. 

I burned my boat on the beach - deleted 1607 revert. 

I have had one 6300 lock up since, corrected by SD of SSDR and restart of SSDR.  Some proficiency in using Event Viewer seems like it might be useful - I am at the bottom staring up at a steep hill, but still. 

I have always allowed W10 updates and only been burned once by a reboot.

This computer is dedicated to SSDR and some other ham apps and all unneeded apps uninstalled (to the extent that MS will allow). 

Clean install seems important.

W10x64 
SSDR 1.10.16.174
AMD A10
Photo of Larry: KE2YC

Larry: KE2YC

  • 66 Posts
  • 5 Reply Likes
Hi all,

Just a comment.  Tried updating to 1703 with no luck.  Tried different setups and deleting different drivers still no go.  Have to stay with 1607 for now. 

Larry
ke2yc
Photo of Michael Coslo

Michael Coslo

  • 812 Posts
  • 195 Reply Likes
I have just adopted the habit of uninstalling and reinstalling SmartSDR and components after every W10 update. 
Photo of Rick Hadley - W0FG

Rick Hadley - W0FG

  • 579 Posts
  • 120 Reply Likes
My system wouldn't take 1703 either. It was also an unplanned upgrade, as I've so far been able to defer them until I have everything shut down. Don't know if it was related to the update or not, but at the same time, something happened to my 6500, which was running at the time, that caused it to crowbar my power supply., and the spare supply I tried next. The 6500 is on the bench in Austin as we speak. Windows-wise, I finally got it to revert to 1607 and will stay there for the foreseeable future.
Photo of Bob Kozlarek

Bob Kozlarek

  • 10 Posts
  • 0 Reply Likes
No problem here with the last update I just made sure that the flex software was not running.
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9149 Posts
  • 3467 Reply Likes
If the problem persists, I highly recommend that you open a HelpDesk support ticket (http://helpdesk.flexradio.com) so we can investigate this issue further.