Surface Pro7 touch screen issue with Windows 11

Anonymous
2021-11-07T14:03:55+00:00

Recently installed Windows 11 on my Surface pro7. The touchscreen stop working every time I lock machine after usage or if it goes on sleep. Also, face recognition stops working and only way to login is through pin.

If i restart machine, it works fine - both face recognition and touch screen works but the moment it goes for sleep or get locked, both things stop working again. Appreciate any help to resolve issue.

Surface | Surface Pro | Display and screen

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

48 answers

Sort by: Oldest
  1. Anonymous
    2021-12-06T08:04:25+00:00

    You mean it's not in Device Manager? Have you tried to enable all devices and Scan for Hardware?

    If that doesn't work, download the drivers here.

    https://www.microsoft.com/en-us/download/details.aspx?id=100419

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2021-12-17T21:07:58+00:00

    I'm having exactly the same issue. After upgrading to windows 11 on my Surface Pro 7, whenever I put my device to sleep by closing typecover, both the camera for face recognition does not come on, and the touchscreen is unresponsive. When I put my surface to sleep via software or the power button, the problem does not occur. It however might occur again if the typecover is closed after putting the device to sleep by either of these 2 methods.

    This seems to be clearly related to the opening and closing of the typecover. That is all-the-more clear because of the fact that the issue of the unresponsive camera and touchscreen can be resolved by closing and immediately opening the typecover, although this might take a few tries. It would be good to have this issue resolved instead of having people waste their time reinstalling drivers. The fact that the unresponsive touchscreen and the camera/ face recognition issue always occur together indicates a software issue in Windows 11 rather than anything involving the drivers of the camera or touchscreen.

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2021-12-20T03:48:24+00:00

    Indeed, I just found out a few days ago that opening and closing the Type cover revived the cameras and touchscreen and it is inconsistent at best.

    It seems like the Type cover open event is slow in triggering the Face camera because I often get stuck at the login screen where it is waiting for the Face Camera to initialise and doesn't go into the Pin screen like when the camera driver fails or is unloaded completely.

    My SP7 is about a year old and I've never encounter this exact problem on Win10. At worst, it will fail to PIN if the camera fails to turn on. My 3 year old SP5 and its Type Cover doesn't exhibit this issue as well.

    We know that the Windows Shell is slow in certain areas, so maybe it's a performance issue?

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2021-12-30T06:38:08+00:00

    Hi John

    I'm having the same problem with my SP7 after updating to Windows 11 - face recognition login isn't working and touchscreen not responsive. A reboot "restores" functionality but as soon as the SP7 goes to sleep we start all over again.

    Has there been a solution identified?

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2021-12-30T07:30:08+00:00

    Yes Brett, if you close the Type Cover and then open it immediately, the camera and touchscreen will reactivate.

    I have noticed that when Type Cover is closed, the camera switches on occasionally so the issue may have started as early as the Type Cover close event.

    Still waiting for MS to release firmware update for SP7 & Type Cover.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments