Windows 10: 802.1x authentication issue after computer resume from sleep mode post upgrade to 1909 OS

Hi Folks,


I've seen several threads active on this on Internet but couldn't find a working solution amidst all of them.


I've a ticket open with Microsoft to troubleshoot this issue but thought to ask this here because there is lot less response/action on the case we are working with MS.


we have WPA2-Enterprise/802.1x network auth in our environment. After computer resume from sleep mode, the machine won't respond to the EAP request from Switch. We have started noticing this issue post upgrade to OS 1909. all our machines on 1809 are still authenticationg OK. it's just the 1909 machines which when put to sleep mode and wake up won't auth


here is the wireshark snip where switch send the EAP request asking for identity and there is no response from machine.


175 105.717173 Cisco_c2:xx:xx Nearest-non-TPMR-bridgeEAP 60 Request, Identity
265 115.990242 Cisco_c2:xx:xx Nearest-non-TPMR-bridgeEAP 60 Request, Identity
277 126.255543 Cisco_c2:xx:xx Nearest-non-TPMR-bridgeEAP 60 Failure


We have matched the sleep settings are same on 1809 and 1909 build and using the same NIC, same version and everythingeven tinyest of detail


powercfg.exe state = S3

NIC = DriverVersion : 12.17.8.7

DriverDescription : IntelR Ethernet Connection 4 I219-LM

FullDuplex : True

DeviceWakeUpEnable : False


There are no logs generated under Application and services logs > Microsoft > Windows > Wired-AutoConfig after computer resume from sleep mode. Not even failure because like I said machine won't respond to EAP request and thus auth flows do not start itself.


Wired-AutoConfig service status is


Name : dot3svc

RequiredServices : {RpcSs, Eaphost, Ndisuio}

CanPauseAndContinue : False

CanShutdown : True

CanStop : True

DisplayName : Wired AutoConfig

DependentServices : {}

MachineName : .

ServiceName : dot3svc

ServicesDependedOn : {RpcSs, Eaphost, Ndisuio}

ServiceHandle : SafeServiceHandle

Status : Running

ServiceType : Win32OwnProcess, Win32ShareProcess

StartType : Automatic

Site :

Container :






almost all the discussion on Internet are after upgrade to 1903. because we have jumped from 1809 to 1909, we are marking it as post 1909 issue


Microsoft support call:

REG:120091821001028

Please share anything you can :

:)

 

Windows 10 Upgrade 1903 64 bit Sleep Wakes Up on Multiple Computers

Someone suggested I look at all the drivers list before and after the upgrade. I did, nothing found/changed in drivers.

What I did discover was that after the KB4503327 upgrade, if I put the computer to sleep mode (via power menu,) I discovered the computer wakes up after the minutes set in the "turn off screen".
So, if the screen shutoff were five minutes and I put the computer to sleep, it would wake up after that amount of time, then turn the screens off after another time period of five minutes.

At this point, I have set the screen turn-off to "never" and any other sleep mode to "never".
Then, when I put the computer to sleep, it stays asleep.

This issue was never seen until this OS upgrade was installed in the system.

My next step is to upgrade the video adapter (something from 2007) to a new and different model adapter to see if that corrects this issue, or not. For now, my work-around is to set "never" in "sleep mode".

 

Issue with Fingerprint Scanner when Resuming from Sleep Mode

Hi,

I ran the Power troubleshooter, and then restarted the computer.

After the initial login, I put the system into sleep mode, and then woke it. Upon resuming, I get the Hello screen, and after several seconds (It doesn't matter if I touch the fingerprint scanner or
not) I get, "Sorry, something went wrong. Please try again." If I then touch the fingerprint scanner, Hello recognizes me, and I'm logged in. So, this doesn't appear to have made any difference.

Any suggestions on a next step?

 

Sleep mode resume

Hi Tyler,

Disabling some of the startup programs normally aids a slow response time when resuming from sleep mode. The concern you're experiencing may continue to happen due to some incorrect power settings. Aside from the steps mentioned above, may we know the specific
procedures that you have tried to rectify the issue? You can also indicate other changes made on your device before this issue occurred.