Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by klubnl.pl (8.14.4/8.14.4/Debian-8+deb8u2) with ESMTP id w42FbJY4002458 for ; Wed, 2 May 2018 17:37:20 +0200 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1fDtid-0001qb-2l for rs_out_1@blacksheep.org; Wed, 02 May 2018 16:30:59 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1fDtiC-0001qQ-Bo for rsgb_lf_group@blacksheep.org; Wed, 02 May 2018 16:30:32 +0100 Received: from omr-m019e.mx.aol.com ([204.29.186.18]) by relay1.thorcom.net with esmtps (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.89) (envelope-from ) id 1fDti8-0006yH-BS for rsgb_lf_group@blacksheep.org; Wed, 02 May 2018 16:30:30 +0100 Received: from mtaomg-mbc01.mx.aol.com (mtaomg-mbc01.mx.aol.com [172.26.221.143]) by omr-m019e.mx.aol.com (Outbound Mail Relay) with ESMTP id 4275038000BA for ; Wed, 2 May 2018 11:30:26 -0400 (EDT) Received: from core-mdc05f.mail.aol.com (core-mdc05.mail.aol.com [172.27.97.15]) by mtaomg-mbc01.mx.aol.com (OMAG/Core Interface) with ESMTP id 09BF738000089 for ; Wed, 2 May 2018 11:30:26 -0400 (EDT) Received: from 74.111.172.145 by webjas-vae164.srv.aolmail.net (10.96.23.167) with HTTP (WebMailUI); Wed, 02 May 2018 11:30:25 -0400 Date: Wed, 2 May 2018 11:30:25 -0400 From: wa3tts@verizon.net To: rsgb_lf_group@blacksheep.org Message-Id: <1632179df88-c8d-333ba@webjas-vae164.srv.aolmail.net> In-Reply-To: <1204118172.20180502102453@gmail.com> References: <1204118172.20180502102453@gmail.com> MIME-Version: 1.0 X-MB-Message-Source: WebUI X-MB-Message-Type: User X-Mailer: JAS STD X-Originating-IP: [74.111.172.145] x-aol-global-disposition: G x-aol-sid: 3039ac1add8f5ae9d992444d X-Spam-Score: 0.0 (/) X-Spam-Report: Spam detection software, running on the system "relay1.thorcom.net", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Chris: Seems like I had a similar issue last fall. At the time, the Win 10 upgrade turned the internal mic back on, and the mic signals were combining with the USB sound card input. I did not lose the USB sound card connection though....I just turned the mic off and check it now and then. [...] Content analysis details: (0.0 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 0.0 HTML_MESSAGE BODY: HTML included in message X-Scan-Signature: 17343f7e400f1005b5081acbd4115359 Subject: Re: LF: For anyone on Windows 10 with a broken USB set up since MS "Upgrade" Content-Type: multipart/alternative; boundary="----=_Part_273831_929394240.1525275025287" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.8 required=5.0 tests=HTML_20_30,HTML_MESSAGE, NO_REAL_NAME autolearn=no version=2.63 X-SA-Exim-Scanned: Yes Sender: owner-rsgb_lf_group@blacksheep.org Precedence: bulk Reply-To: rsgb_lf_group@blacksheep.org X-Listname: rsgb_lf_group X-SA-Exim-Rcpt-To: rs_out_1@blacksheep.org X-SA-Exim-Scanned: No; SAEximRunCond expanded to false ------=_Part_273831_929394240.1525275025287 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Chris: Seems like I had a similar issue last fall. At the time, the Win 10 = upgrade turned the internal mic back on, and the mic signals were combining= with the USB sound card input. I did not lose the USB sound card connection though....I just turned the mi= c off and check it now and then. By the way, I saw what could=C2=A0 have been a few light 2E0ILY traces on t= he waterfall the other evening around 0312, 0324, and 0336...just a dB or s= o shy of signal capture strength.... 73 Mike wa3tts -----Original Message----- From: Chris Wilson To: rsgb_lf_group Sent: Wed, May 2, 2018 5:26 am Subject: LF: For anyone on Windows 10 with a broken USB set up since MS "Up= grade" Hello LF'ers, It seems Microsoft's Spring upgrade for Win10 has caused some grief in the USB audio department and WSPR and other audio USB connected apps have stopped communicating. I avoid 10 like the plague due to updates breaking stuff and stick with Win7, but was asked to look at a friend's PC yesterday that had lost USB audio comms with WSJT-X since the auto update. I searched all over the place until I spotted this mischievous change MS added to modify his microphone setting, which may not actually be being used as a microphone in some applications of course...... Try going to settings/privacy/microphone and set it to "allow applications = to access your (my?) microphone" Hope it helps, seems a lot have been caught out by this nefarious activity :) --=20 Best regards, Chris mailto:dead.fets@gmail.com ------=_Part_273831_929394240.1525275025287 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Chris: Seems like I had a similar issue last fall. At the tim= e, the Win 10 upgrade turned the internal mic back on, and the mic signals = were combining with the USB sound card input.

= I did not lose the USB sound card connection though....I just turned the mi= c off and check it now and then.

By the way, I= saw what could  have been a few light 2E0ILY traces on the waterfall = the other evening around 0312, 0324, and 0336...just a dB or so shy

of signal capture strength....

=
73 Mike wa3tts


-----Original Message-----
From: Chris = Wilson <dead.fets@gmail.com>
To: rsgb_lf_group <rsgb_lf_group@b= lacksheep.org>
Sent: Wed, May 2, 2018 5:26 am
Subject: LF: For any= one on Windows 10 with a broken USB set up since MS "Upgrade"

=

Hello LF'ers,

It seems Microsoft's Spring upgrade for Win10 = has caused some grief in
the USB audio department and WSPR and other aud= io USB connected apps
have stopped communicating. I avoid 10 like the pl= ague due to updates
breaking stuff and stick with Win7, but was asked to= look at a
friend's PC yesterday that had lost USB audio comms with WSJT= -X since
the auto update. I searched all over the place until I spotted = this
mischievous change MS added to modify his microphone setting, which=
may not actually be being used as a microphone in some applications of<= br>course......

Try going to settings/privacy/microphone and set it = to "allow applications to
access your (my?) microphone"

Hope it = helps, seems a lot have been caught out by this nefarious
activity := )




--
Best regards,
Chris = mailto:dead.fets@gmail.com<= br>

------=_Part_273831_929394240.1525275025287--