Gotta pipe in here on John’s behalf. There is absolutely no question whatsoever that updating Windows whenever microsoft decides to assault the world with their next disaster is a terrible idea unless there is some special driving need to do so. This forum and countless others along with endless news and journal articles over the last several years recount horror story after horror story brought on by updates from the flaming idiots at microsoft. The fact that some people have been lucky so far doesn’t negate that fact that very very many haven’t. It just is what it is. And trying to pretend it isn’t doesn’t help anyone.
However, from what I can see, allowing just the routine security updates that, for example, refresh WD’s database don’t seem to cause these problems and probably can be be performed safely. So “performing updates” can mean several things. And I think the case most people are advising against here are version updates.
There are many guidelines on-line and some on Dave Bernstein’s excellent DXLab Suite website for “dealing with Windows”. They can be easily googled up. For my own part I’ve been successful at preventing version updates and allowing routine security updates for the nearly two years I’ve been forced to use microsoft garbage for ham radio purposes. It is also possible to disable just the device portion an update might have which, at least for me, spared me the port scramble/loss misery being described once I decided enough “fix our last screwup” updates had occurred that a particular version update might finally be safe (still always a risk).
Anyway, I just wanted to weigh in with some support for the “avoid the microsoft morons whenever possible” side of the discussion because it is very real.
On Mar 25, 2020, at 2:59 PM, JP Tucson, AZ <samcat88az@...> wrote:
Hassan,
Perhaps I wasn't completely clear, when win10 updated, it blew out my profiles, my saved passwords, etc.
It took me nearly 5 freaking hours just to get back to where I was!
Sorry, but you and others are wrong! Recent win10 upgrades have proven to be nearly complete disasters that even MS "experts" are dumbfounded by...
Just like the recent time after time screwups by Boeing!
Frankly, I think it's just more proof that Washington state's pot(head) acceptance is just stupid!
Let me be more clear... the last "good" & working version of Windows was XP Pro! 7 was workable but not as good. Office 2003 worked great, and since then MS has done everything wrong & screwed up the works.
Seriously, I would still use XP Pro today, except most of the software writers stopped supporting it.
FYI, Yes! I still have an HP & two other computers that run XP Pro! The HP gas only had to have the failed hard drive replaced, and that took 8 minutes, not 5 hours! (I kept an up to date spare HD on the side).
Turning off Windows Updates is a Terrible Idea
If a person doesn't have the technical competence to make Windows Audio Devices work properly after an Update munges them, just how well do they think they are going to do avoiding getting and giving virus's and Trojans when their Security Patches are so out of date that they become a nesting area for the bad actors?
Work through the audio setup from top to bottom. If needed, uninstall all your audio devices and start over. Windows audio can be very daunting.
Simply plugging and unplugging something from the Sound Card inputs and outputs can drive you crazy!
However, turning off Windows Updates is NOT the solution, unless you are quite accomplished with the O/S in the first place. ...and if you are, then you shouldn't need to turn off Updates to solve and audio device or serial port enumeration issues.
Worst case, uninstall all the audio devices (non-motherboard ones) and disconnect them. Then reboot. Plug the audio devices in one at a time and find them in Device Manager when Windows recognizes them. Test them one at a time. Rename them once you have identified them.
If that doesn't work, uninstall even the motherboard audio device....you won't lose it.
Shut the computer down, power back up and Windows will find the motherboard audio. Test it out. Unless it's gone bad, it will work. Then add each additional device one at a time. Review them in Device manager and then test them. Eventually you will have them all working again.
If you are using another audio device besides the motherboard one (and you should be for WSJT-X), then once you get it working, RENAME it, so you won't get confused next update. I have not had Update change an Audio Device Name that I changed, and I get updates nearly weekly.
Windows Update is a PITA, to be sure, I have had it brick a laptop, but most of the time I don't have those kinds of issues. With Audio Devices since I renamed them, and also wrote out notes on every serial port (plus labled the cables on both ends), my problems become very easy to solve.
When things get messed up, it's a big help.
Good luck!
73, N0AN
On Wed, Mar 25, 2020 at 9:32 AM Gilbert Baron < w0mn00@...> wrote: Turning off update is NOT the answer. You will be sad about this when you miss something critical ,especially a security thing. Find out what the real -problem is. I have ZERO problems with audio after update. Outlook Laptop Gil W0MN Hierro candente, batir de repente 44.08226N 92.51265W EN34rb From: WSJTX@groups.io <WSJTX@groups.io> On Behalf Of Andrew O'Brien
Sent: Wednesday, March 25, 2020 07:45
To: WSJTX@groups.io
Subject: Re: [WSJTX] WSJT-X suddenly deaf? John, I argue ... always update Windows Ted - did your Windows 'update'? (Never update Windows!) Win10 updates have a nasty habit of screwing up your audio mixer & your codec settings! Recheck those & TURN OFF Win10 update; by going into the windows icon in bottom left corner - type ser(vices); which brings up a list; go down to Windows update & disable it! NOTE: you have to check it on a regular basis because update will turn itself back on... (stupid windows & microsoft) (seriously, we need to all file a class action lawsuit against MS to force them to provide a permanently turn off windows/stop "forced" updates!) On Wed, Mar 25, 2020, 12:30 AM K7RA Tad Cook <k7ra@...> wrote: I've been using the software on FT8 with a Tigertronics SignalLink, but suddenly a few days ago it has gone deaf. Nothing appears in Band Activity, and the Receiving nomograph stays at zero, which is odd because normally in the past even when the USB connection from the SignalLink hardware was not attached, the Receiving field is jumping around. For instance, right now I am not at the radio and on another computer, and when I run WSJT here with no audio input, that Receiving window acts as if there are signals present. I*'ve been through everything. I am able to transmit OK. Any suggestions? Everything worked fine til very recently.
--
--
W0MN EN34rb 44.08226 N 92.51265 W
Hierro candente, batir de repente
HP Laptop
|
