From: RussellMc <apptechnz@gmail.com>
To: Microcontroller discussion list - Public. <piclist@mit.edu>
CC: ApptechNZ <apptechnz@gmail.com>, "ken@elecsyn.com" <ken@elecsyn.com>
Sender: "piclist-bounces@mit.edu" <piclist-bounces@mit.edu>
Date: Mon, 9 Aug 2021 19:59:58 -0700
Subject: Re: [OT] Windows 10 Networking Change
Thread-Topic: [OT] Windows 10 Networking Change
Thread-Index: AdeNlYq89vLRukcNTOqsYZ9NotnOFA==
Message-ID:
 <CACZQxzNsX1+fwSgRWpSp06i+CbyjUyApGJhat_yKY23_2L9HCQ@mail.gmail.com>
References: <95c60a46-382b-89d9-7462-dbcffb93c376@amulvey.com>
In-Reply-To: <95c60a46-382b-89d9-7462-dbcffb93c376@amulvey.com>
Reply-To: Microcontroller discussion list - Public. <piclist@mit.edu>
Accept-Language: en-US
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 gmail.com designates
	209.85.167.52 as permitted sender) receiver=protection.outlook.com;
	client-ip=209.85.167.52; helo=mail-lf1-f52.google.com;
dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com;
 s=20161025;
	h=mime-version:references:in-reply-to:from:date:message-id:subject:to	:cc;
 bh=kGzH3kLC5OKsy+jdUl4VX/OiJakWFIuubcy3qG6Roag=;
	b=EwBjf9UR9FQDp9uougfAEfuoU1U07ZGOfTEKXuZulJVjEizy8Gi49JZ1XsdrLpzIN8
	nbGm+nPEaD9yHhrkQeJJQTqA54lVue3UNXejdRH6f0FLl29c2l+9oJyQyQqrVhFwut9+
	++j9nElKgdzTO+8s7I89hdpQELS8AITitl3hmNM9vuhixRgoa/btcmEHH++WWqJL4Wwz
	giCnW8Sw3W9ffluzhU9IxOP40YUXCj19LEWlYblzXzfGniFF3rcQLt53Mo+j4hQixhKC
	AvVSbAQXFm8pqQyqGlKUF/cZX8TUyYQlOb1JfDv/cSaFgf7utWfFfGo/nRchv3UybkbY	2JPQ==
authentication-results: spf=pass (sender IP is 209.85.167.52)
	smtp.mailfrom=gmail.com; mit.edu; dkim=pass (signature was verified)
	header.d=gmail.com; mit.edu;	dmarc=pass action=none header.from=gmail.com; 
errors-to: piclist-bounces@mit.edu
list-id: "Microcontroller discussion list - Public." <piclist.mit.edu>
list-post: <mailto:piclist@mit.edu>
x-beenthere: piclist@mit.edu
x-mailman-version: 2.1.6
x-received: by 2002:a05:6512:2294:: with SMTP id
	f20mr10509429lfu.557.1628564436579; 	Mon, 09 Aug 2021 20:00:36 -0700 (PDT)
x-topics: [OT]
x-content-filtered-by: Mailman/MimeDel 2.1.6
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

On Tue, 10 Aug 2021 at 13:41, Allen Mulvey <allen@amulvey.com> wrote:

> I have an access control system for my home which uses a central
> controller with Wiegand RFID scanner/keyboards at the access points. It
> has worked well for many years. The software was made pre-Windows 10
> but, until last April, it worked fine on Windows 10 Pro. It worked fine
> on Windows 10 pro in April 2020.
>

There was a change in Win10 earlier this year which "broke" many WIN
systems running on old network hardware.
As usual in such case uSoft did not issue a statement about this or any
form of 'apology'.
What they did do was to make a change in the update rollout that said ~~
"This update is not suitable for your system - you will be notified when
the update can be installed."

After a while an updated update was supplied.
Systems that had had the update attempted remained broken. The internet
networking did not work (at all in the systems that I saw as far as I
knew).
I tried to fix one without success and then found that installing a newer
network card worked - in this case I added a USB interfaced card which
"just worked".

I'd suggest that there is  a reasonable likelihood that you are in this
position.
If so either a trial with new hardware (external USB easy) or manually
adding a more recent update may help. Or not.

It's even p[ossible that a system updated via a temporary new network card
will then work on the old card.

I'd be interested to hear if this works.


 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
.