Received: from PCH.mit.edu (18.7.21.50) by mail.efplus.com (192.168.0.8) with Microsoft SMTP Server (TLS) id 8.3.485.1; Wed, 8 Jul 2020 09:23:26 -0700 Received: from PCH.MIT.EDU (localhost.localdomain [127.0.0.1]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 068GApmJ024992; Wed, 8 Jul 2020 12:11:26 -0400 Received: from outgoing-exchange-5.mit.edu (OUTGOING-EXCHANGE-5.MIT.EDU [18.9.28.59]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 068EisW0009178 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Wed, 8 Jul 2020 10:44:54 -0400 Received: from oc11exedge1.exchange.mit.edu (OC11EXEDGE1.EXCHANGE.MIT.EDU [18.9.3.17]) by outgoing-exchange-5.mit.edu (8.14.7/8.12.4) with ESMTP id 068EieZX027435 for ; Wed, 8 Jul 2020 10:44:49 -0400 Received: from w92expo16.exchange.mit.edu (18.7.74.70) by oc11exedge1.exchange.mit.edu (18.9.3.17) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Wed, 8 Jul 2020 10:43:49 -0400 Received: from oc11exhyb4.exchange.mit.edu (18.9.1.100) by w92expo16.exchange.mit.edu (18.7.74.70) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Wed, 8 Jul 2020 10:44:42 -0400 Received: from NAM10-MW2-obe.outbound.protection.outlook.com (104.47.55.105) by oc11exhyb4.exchange.mit.edu (18.9.1.100) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Wed, 8 Jul 2020 10:44:41 -0400 Received: from MWHPR19CA0082.namprd19.prod.outlook.com (2603:10b6:320:1f::20) by MWHPR0101MB3200.prod.exchangelabs.com (2603:10b6:301:36::15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3153.28; Wed, 8 Jul 2020 14:44:40 +0000 Received: from CO1NAM03FT055.eop-NAM03.prod.protection.outlook.com (2603:10b6:320:1f:cafe::3d) by MWHPR19CA0082.outlook.office365.com (2603:10b6:320:1f::20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3174.21 via Frontend Transport; Wed, 8 Jul 2020 14:44:40 +0000 Received: from mulvey.us (24.169.71.174) by CO1NAM03FT055.mail.protection.outlook.com (10.152.81.162) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.3174.21 via Frontend Transport; Wed, 8 Jul 2020 14:44:39 +0000 Received: from Win10ProDT ([192.168.100.55]) by mulvey.us with MailEnable ESMTPA; Wed, 8 Jul 2020 10:44:36 -0400 From: Allen Mulvey To: 'Microcontroller discussion list - Public.' Sender: "piclist-bounces@mit.edu" Date: Wed, 8 Jul 2020 07:44:36 -0700 Subject: [OT] WIN10 upgrade de-internets a zillion older PCs. Thread-Topic: [OT] WIN10 upgrade de-internets a zillion older PCs. Thread-Index: AdZVM4b0G8SOys3iT4uNlJKtVv1ZVw== Message-ID: <000001d65536$4d36cbc0$e7a46340$@amulvey.com> List-Help: List-Subscribe: , List-Unsubscribe: , Reply-To: Microcontroller discussion list - Public. Accept-Language: en-US Content-Language: en-US X-MS-Exchange-Organization-AuthAs: Anonymous X-MS-Exchange-Organization-AuthSource: TS500.efplus4.local X-MS-Has-Attach: X-Auto-Response-Suppress: All X-MS-Exchange-Organization-SenderIdResult: Pass X-MS-Exchange-Organization-PRD: mit.edu X-MS-TNEF-Correlator: received-spf: Pass (protection.outlook.com: domain of amulvey.com designates 24.169.71.174 as permitted sender) receiver=protection.outlook.com; client-ip=24.169.71.174; helo=mulvey.us; dkim-signature: v=1; c=relaxed/relaxed; h=from:to:subject:date:message-id:mime-version:content-type:content-transfer-encoding; d=amulvey.com; s=amulvey; a=rsa-sha256; bh=JrRziekwJ5+J7lVeUatTQeZgd5U4jHTHqYBg8mqI+ns=; b=JdPMaSq4pn5KbZlw1JbQXClorZamDRND3NrR6pBx/x3mX5ZR8mcgRgPO/Vd06u1D2 WpLXsTs85D5+1qwFJKDJGy5UT2lBnzfRcneyqttZ+Si7PyIzCJMzytIVtZHmZ5HNX8u lFO+BDhFYmOUJ07+7Xly96HE8Kujs6Gn1jAPaVU=; authentication-results: spf=pass (sender IP is 24.169.71.174) smtp.mailfrom=amulvey.com; mit.edu; dkim=pass (signature was verified) header.d=amulvey.com;mit.edu; dmarc=bestguesspass action=none header.from=amulvey.com; errors-to: piclist-bounces@mit.edu list-id: "Microcontroller discussion list - Public." list-post: x-beenthere: piclist@mit.edu x-mailman-version: 2.1.6 x-topics: [OT] x-mailman-approved-at: Wed, 08 Jul 2020 12:10:50 -0400 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 I'm surprised no one has commented on this so far. I think the problem of "Updates" trashing hardware is pretty common. Not all updates are improvements. I have a primary rack in the basement, a secondary rack in the attic, and a "play" rack next to my desk. (I like to play with hardware.) All are interconnected by fiber, as are the servers and my desktop. Some time ago m= y desktop suddenly lost network connectivity. I switched over to copper while I tried to figure out why the fiber was dead. Several days later the same thing happened on my servers (at the time Hyper-V Server Core 2012). I was using Mellanon ConnectX-2 interface boards. They were not certified for Windows 10 but they were very cheap and worked quite well. I switched the servers over to copper and ordered the "proper" but more expensive ConnectX-3 boards. When they arrived I put one in my desktop and it was good. I then went to the servers where I had left the old boards in place and discovered that they were now working. Apparently a lot of other people with a louder voice than me had the same problem and I failed to notice tha= t a fix had been pushed out. Allen -----Original Message----- From: piclist-bounces@mit.edu [mailto:piclist-bounces@mit.edu] On Behalf Of RussellMc Sent: Saturday, July 4, 2020 7:56 AM To: Microcontroller discussion list - Public. Cc: VHome; RossGMail; ApptechNZ; Iain; ken@elecsyn.com Subject: [CAUTION: Failed DKIM Test][OT] WIN10 upgrade de-internets a zillion older PCs. This may be of value to some whose older PCs suddenly lost internet connectivity in the last few months. Summary: Older PCs that lose their Internet connectivity after a recent rolling automatic WIN10 update (from about May on) MAY be able to be re-interneterised by adding a modern USB-LAN or USB-Wifi adaptor. It seems likely but not certain that drivers used with some older hardware has been rendered fatally inoperable by the upgrade. Others may wish to put this in better technical-speak, but ... _________________________________ In May a friend's old desktop PC running WIN10 (initially WIN7) lost it's internet connectivity. My days of spending countless hours attempting to unravel PC woes are generally long past. Every now and again I forget the pain and .... Here is the gist of an email I sent to another friend: _____________ Martin After multiple attempts to persuade Rena's PC to 'see' the internet I achieved this in a manner which I now know that I could have done near instantly and for $20 many weeks ago. While there is much on the internet about the events that de-interneted a very large number of PCs worldwide I have seen nothing which identifies what appears to be the cause in many cases. It appears that a WIN10 update which started to be rolled out in May (maybe earlier in some locations) removed the ability for drivers for many older network devices to function. The devices may be - "missing" or - visible to the system but declared faulty or inoperational. - WiFi adaptors may be visible but report "No networks available". On Rena's PC with various devices I managed examples of all of the above :-= ) *The solution was to buy current network adaptors *- in this case I tried a USB to wired LAN and a USB to WiFi adaptor and both worked instantly. Both cost about $20 at PBTech. (Guess: I suspect that the old drivers were 16 bit and that the system stopped recognising these. Old 16 bit WIN apps have long not been supported). In the interim I had obtained a latest WIN10 image and reinstalled it twice, with no gain but with the loss of the original installation. (I have a copy of all files, so nothing actually lost). The USB to WiFi Dongle that worked prior to the May upgrade will presumably function on WIN7 or before PCs. Russell --=20 http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist --=20 http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .