Windows 10: Pin doesnt work. Finger print doesnt work. Has your latest security update screwed...

My fingerprint scanner no longer works. > If I try to reset the reader does nothing.

My pin no longer works > If I remove and add again it makes no difference, when I log out and in I face the same message every-time > something happened your pin is not available.


I have rolled back to a previous save point > no use. I have installed new drivers > no use.


This happened out of the blue. However my internet was also dropping regularly that day. Perhaps a hack of sorts. Who knows, but this is a pain.


Whats the steps to take?

:)

 

security code doesnt work and doesnt come

security code doesnt work and then another one cannot be sent. security system is broken I cant download anything and couldnt even create an account, I had to sign in with google

 

security code doesnt work and doesnt come

We don't know what security code does not work, what security system is broken, where you are trying to create an account or where you had to sign in with google.

 

Touch screen doesnt work after latest update

Hi,

What I have:

• Porsche Book One.
• Running: Win 10 Pro
• Version: 1803
• Build: 17134.228

Problem 1: After latest update (1803) the touchscreen doesnt work anymore, like it is non-responsive whatsoever

Problem 2: Touchpad doesnt turn off. There is a shortcut key to disable the touchpad (F7) but it doesnt respond at all anymore.

I have had the exact same issues before when there was a larger Win10 update (just cant remember which one). I did work with the Porsche support but since we tested with the same HW, but different OS versions, and the one that didnt upgrade OS version had
no issues and the other one had issues, we concluded that it has to do with the MS update.

Then came another OS update and all of the sudden both problems were gone. No FW updates between that period that could have affected the change.

So, now its back....again. The manufacturer cant do anything, but to wait for MS to fix in the next release I guess?

Anyhow, I thought atleast I could post it here and hope that an MS representative would read and send the feedback back to the correct team to fix this.

Sincerely