Spin 3 repeatedly won't power on and fingerprint reader stopped working

GPS5

I have a 6 month old Spin3.  3 different times in last 2 months, computer would not power on.  Green power light shows on side, black screen, no fans running, no backlit keyboard lights.  I have removed power cord and eventually been able to get computer to start later in the day. 

This morning, would not power on.  This evening, after disconnected power and attempting to boot, holding down power button, finally coaxed it back on. 

Now fingerprint reader doesn't work.  In Device reader it showed an error however when I selected to update driver it stated it was using proper driver.  Have restarted multiple times and fingerprint reader no longer shows error but doesn't work.  I do not bet a message that the fingerprint reader couldn't match the fingerprint.  Just nothing happens. In Device Manager under 'events' it shows to have been deleted this morning at 2:10a (as I slept and computer not on or in use).  It also shows the windows update I completed at 6p today but still not working.

Appreciate advice on both problems.

Thread was edited to add model name to the title

Easwar

Hi GPS5,

# Power drain,

1)Unplug the AC power adapter.

2)Press and hold the Power button down until the unit goes off. 

3)Search for a pinhole on the backside of your laptop, insert a small paperclip in the battery reset pinhole, press and hold it down for 25 seconds. Then release the paperclip and try to turn on the unit and check.​

billsey

I believe you are looking at two different issues.

The problem with powering on is often traced to an app that doesn't like sleep mode. What happens is the OS tried to go into sleep but the app doesn't, and everything is stuck. Pressing and holding the power button to force a full power off bypasses the issue to allow you to power back on normally works, as does waiting for the app to shut down on it's own or allowing the battery to drop low enough to trigger a power off.

The problem with the fingerprint reader seems to be something Microsoft (and likely Intel) is doing with updates. The low level USB port that internally connects the reader to the rest of the system is either getting disabled or passing corrupt data. Usually they fix it again after a few weeks and sometimes you can just roll back the update for a while to bypass it. It sounds more like yours is passing corrupt data than it being a missing port...