Win 10 Creators version update ...

  • 2
  • Praise
  • Updated 1 year ago
The Windows Creator update was a VERY long update BUT all went well.  No problems or glitches with SmartSDR, associated programs, or the 6300.  Of all the Windows updates I have had - I ONLY had one (several months ago) that caused a problem which was with the DAX program.  I uninstalled and reinstalled the SmartSDR software and all was well.

All the myriad of other updates have had no effect which is amazing to me ...
Photo of Gary L. Robinson

Gary L. Robinson

  • 218 Posts
  • 42 Reply Likes

Posted 1 year ago

  • 2
Photo of Duane, AC5AA

Duane, AC5AA

  • 384 Posts
  • 84 Reply Likes
Same here - just did it tonight.  An hour of updating, and all worked when it was all over.  I'm shocked!  :-)
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9052 Posts
  • 3435 Reply Likes
It could be a driver signing issue.

It is not.

It appears that Windows doesn't handle upgrading virtual drivers for things that are usually hardware centric, like sound devices and serial ports.
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9052 Posts
  • 3435 Reply Likes
The best practice is to remove SmartSDR and all of its components (dax drivers) prior to doing any major Win10 update.  It only takes a few moments and then re-install after the update is done.  I have never experienced an issue using this method. 
Photo of Peter K1PGV

Peter K1PGV, Elmer

  • 541 Posts
  • 315 Reply Likes
>Windows doesn't handle upgrading virtual drivers
>for things that are usually hardware centric, like
>sound devices and serial ports.

Yup.

You (Tim) have seen and thought about this problem far more than I have.  But I think the problem isn't keeping the drivers running through the upgrade so much as it is re-establishing the settings that driver uses after the upgrade.

We know, for example, that the sound device settings (which is your default audio device) can change when you add or remove a sound device.  Windows tries to be clever and choose a new default audio device based on... something.  And it varies based on the order the devices are installed in (or, after an update, the order in which the device are discovered).

That's my best guess as to what's going wrong.  Things like COM port numbers and audio devices have external numbering dependencies... and those dependencies get scrambled during the upgrade.

Does that make sense given your experience, Tim?  Or am I down the wrong path?

Peter
K1PGV
Photo of Michael Coslo

Michael Coslo

  • 753 Posts
  • 172 Reply Likes
Remove before or after seems like the same thing. I have had some updates that warned me that it was going to automatically shut down and reboot in the middle of the night, so I guess if I hadn'r seen it, it would have just happened. 

And everyone should remember that this is not a SSDR only issue. I've dealt with a lot of NBEMS people who suddenly lose their audio, and occasionally a few other controls after an update. 

It's our penance. 8^)
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9052 Posts
  • 3435 Reply Likes
Remove before or after seems like the same thing.

Not really.  The upgrade may mess with settings that could prevent the clean uninstall of the SmartSDR software.  It is always best to uninstall SmartSDR it before the upgrade if at all possible.  It has worked flawlessly for me.
Photo of Ross - K9COX

Ross - K9COX

  • 335 Posts
  • 101 Reply Likes
You are not alone
Photo of Steven G1XOW

Steven G1XOW

  • 277 Posts
  • 116 Reply Likes
Installed W10C on my home machine over a month . No problems whatsoever, even SSDR had no issue, that was a nice surprise!

At work we've installed (or updated to it) more than 140 times already, not seen any problems so far, except that the media creation tool (makes a bootable USB W10 installer) does not work anymore. No big deal as we still remember how to use DVDs.
Photo of Peter K1PGV

Peter K1PGV, Elmer

  • 541 Posts
  • 315 Reply Likes
> If we knew why it was happening

I'd be happy to know WHAT's happening.

The problem reports seem to only ever say "the install borked my copy of SSDR and I had to remove/reinstall 3 times before it worked again"

To be able to diagnose the problem (the first step to finding a fix) we'd need a very specific description of what that problem is.

>My thoughts are that it is the individual computer's hardware related

Me too.  I have *long* suspected an issue with the serial port database -- which is ancient and very prone to problems.  And, if SSDR/CAT isn't the only thing that's synthesizing serial ports on a system (Michael's hardware-specific aspect maybe), there's a reasonably high likelihood of problems (due to carrying forward serial port numbers, and  the random ordering of how those drivers start).

But THAT is a Big Giant Dumb-Assed  Guess, is what that is...

Peter
K1PGV
Photo of Mike Hoing

Mike Hoing

  • 243 Posts
  • 38 Reply Likes

The install that came out 2 weeks ago caused all kinds of Havoc in the DAX audio drivers that were virtually unfixable with out a windows rebuild. 


I waited until I had time and the update that came out this week seemed to fix it with a uninstall and reinstall.  I wish I knew what caused it as well.  It seemed to be a rights issue for the DAX directory as near as Dudley and I could tell.

Its is fixed now so all is well

Mike

N9DFD

(Edited)
Photo of Michael Coslo

Michael Coslo

  • 753 Posts
  • 172 Reply Likes
I empathize with ya Tim. This is a nuisance for all of us. 
Photo of Michael Coslo

Michael Coslo

  • 753 Posts
  • 172 Reply Likes
Okay - I have gone through my error logs. Now one thing to keep in mind is that I'm a UNIX guy, so I could be reporting something way off, so be gentle!

I'm watching the Pens Sens game right now, so I'll do the log reportage tomorrow.
(Edited)
Photo of Michael Coslo

Michael Coslo

  • 753 Posts
  • 172 Reply Likes
Okay, here's the skinny. my creators update came in on the 21st. I have saved the error logs from then to this morning. I saved them in all of the formats allowed. Now what to do? 
Photo of Steven G1XOW

Steven G1XOW

  • 277 Posts
  • 116 Reply Likes
ps. Microsoft recently made a statement to the effect that W10 was the ONLY O/S that was entirely immune from the WannaCry ransomeware. More shockingly was that W7 was in fact the worst affected.

Needless to say we've spent weeks updating the 900 x W7 PCs we still have on contracts.
Photo of David Warnberg

David Warnberg

  • 538 Posts
  • 56 Reply Likes
HAHA, I can not get my computer to accept the creators update from windows.. go figure
Photo of Peter K1PGV

Peter K1PGV, Elmer

  • 541 Posts
  • 315 Reply Likes
I *did* want to advise people that it's (almost) always better to *wait* for major upgrades (like Creators) to be pushed to you by Microsoft, than it is to pro-actively seek and download the upgrade at your first opportunity.  This is true even after Microsoft announces the upgrade has been officially released.

While the result of waiting may be that it takes you a few weeks longer to get the upgrade, you'll also be getting an upgrade that's been updated/fixed to avoid problems experienced by earlier adopters.  In addition, other updates/fixes that may be useful/helpful/pertinent to your specific system are more likely to be ready.

In this case, patience is indeed a virtue. OTOH, after the upgrade has been out for several weeks, and you haven't gotten it, but you're aware of it being pushed to friends and relatives, you should feel free to go ahead and pull it down and install it.

Now, whether that does anything to solve Flex driver issues during upgrade or not is anyone's guess.

I hope that helps,

Peter
K1PGV
Photo of Gary L. Robinson

Gary L. Robinson

  • 206 Posts
  • 42 Reply Likes
Interestingly,  I waited until Windows forced the Creators update on me.  So, you may be giving out valuable good advice about waiting for the updates to be pushed out to you.  And I regularly do that.  I seldom "go looking for trouble" hihi

---Gary WB8ROL
Photo of VE7ATJ

VE7ATJ

  • 106 Posts
  • 20 Reply Likes
Well, I guess I'm one of the outliers, cuz I've had two major problems with the upgrade to Win10 1703 (aka Creators).  There were both on the same machine, so there may be something to the hardware supposition.  But it's a relatively new (3 mos) high-end Dell laptop, so I wouldn't have expected any issues.

One was the Intel driver problem I reported in another thread.  Apparently, the default WiFi drivers included had fatal flaws which caused them to crash. (fix is to download revised ones from Intel) And the other now, is an inability to load drivers for my HP printers -- either USB connected or via WiFi!  Sheesh.. talk about making life difficult.  the flex works fine tho...
Photo of VE7ATJ

VE7ATJ

  • 106 Posts
  • 20 Reply Likes
Just to update everyone on this... the laptop went back to the 'geeks' who had exactly the same difficulties installing printer drivers.  After a week, their solution was to completely install Win10 1703 (Creators) from scratch.  Don't know why but 'voila' -- printer drivers install correctly and everything is working fine (so far :-))
Photo of K4MT

K4MT

  • 22 Posts
  • 9 Reply Likes
Update was done on my computer and it didnt even mess with all my PowerSDR or 5000A virtual audio and serial ports. I was very surprised.
Photo of John AE5X

John AE5X

  • 27 Posts
  • 5 Reply Likes
My Creator update occurred this morning and all was well except DAX. Uninstalled SSDR per Tim's guideline, reinstalled and all is well.

Surprisingly, all my profiles were there without me having to import them into the new installation - I would have thought they would have been deleted with the very specific 11 step uninstall procedure.

John AE5X
Photo of Wim

Wim

  • 88 Posts
  • 17 Reply Likes
Just got the creators update... only issue was DAX driver crashing now 

will uninstall and re-install smartSDR ...
Photo of Mike Hoing

Mike Hoing

  • 243 Posts
  • 38 Reply Likes
Try reading this and uninstall, running the cleaner then reinstall. It was one of the steps I used and worked

Mike N9dfd

https://helpdesk.flexradio.com/hc/en-...
Photo of Wim

Wim

  • 88 Posts
  • 17 Reply Likes
yes, had to do full uninstall, then re-install, then only the VSP driver would complain, after re-installing that again got it running again. Then had to mess with windows soundcard channels a bit. Now all back ok ...
Photo of Mike Hoing

Mike Hoing

  • 243 Posts
  • 38 Reply Likes
Good to hear