• Surface turns on
• Surface reaches login screen
• Surface logs in and is on home screen
• Surface is in UEFI bios
• Surface is in Advanced startup options.

In none of these scenarios does the keyboard work. No lights are on. No signs of life. However after a reset of windows it does work but then small things do trigger it to stop working again.

I have tried literally everything from cleaning the contacts to even (repeatedly) turn on and off the type cover port in the UEFI bios with absolutely 0 luck at all.

Pls help as this is a machine used on an everyday basis.

Thanks.

So, after going back and forth with Microsoft, the only solution they had was to send me a new keyboard, which now works fine.

⟐ Commented October 11, 2023 at 1:57 MST

⟐ Answered October 04, 2025 at 16:12 MST

⟐ Commented March 17, 2023 at 2:01 MST

⟐ Commented October 20, 2025 at 2:28 MST

⟐ Answered September 17, 2025 at 8:39 MST

⟐ Answered March 26, 2024 at 5:10 MST

I would need your advice. I have a Surface Pro 7+ (core i7, 32GB, 1TB SSD) that was bought 2,5 years ago. A month ago it started to have blue screen than, it restarted and after that worked fine for a few days. After that it had the same error message and restarted again and worked again for a few days. However at once, after restarting I had the message

I searched on the internet and after several attempt to recover the computer or unlock the bitlocker I stated that probably my SSD is dead, I have to replace it. I put the device aside for a few weeks and when I checked it, it is worked again fine. I could log in, windows loaded perfectly several times, I could read and write the SSD (of course I made a backup save to have all my important files), but now it came back again to the same error message: couldn't find a bootable... It is important, that not the windows is broken as when I try to make a recovery with a surface image, it doesn't find the SSD itself, so I had the hint that maybe it is a hardver, SSD connection issue. While I could login into the windows and it worked fine I could also checked and repair corrupted files, software updates and SSD maintenance. OP system should work properly.

Therefore, I bought a simple NVMe, PCI-e (M.2, 2230) SSD enclosure and attached the SSD to another computer. I could read and write the SSD. As I put back to the Surface Pro 7+, it had the same error message and don't let recovery with an image because don't find the SSD. This is consequent, every time I test it (I did it 5-7 times), it remains the same. Externally I can read and write the SSD and internally there is no access. So I think that finally not SSD is broken, but the connection within the computer?

Do you have any idea how could I repair it or test it more? What could be a solution? Is there any other software solution? Is there any replacement part for it or it is integrated into the motherboard... I don't know.

Thank you in advance!

Br,

Tibor

⟐ Commented December 12, 2023 at 7:54 MST

⟐ Answered October 26, 2023 at 8:01 MST

I recently succeeded in replacing the inflated battery in my surfacepro5 intact, but (foolishly) I am about to get my hands on a junk pro7+ next. So my question is, is the screen of the pro5 compatible with the pro7 in order to use it for operational testing, etc.? I know that the location of the terminals may be different depending on the production lot.

⟐ Answer accepted October 11, 2022 at 22:36 MST

• Serial number: 007793213553
• Surface model: Surface Pro 7+ Model 1960 i7
• SAM: 12.206.139.0
• UEFI: 16.101.141.0
• Touch driver: 5.141.139.0
• Wi-Fi driver: 22.40.0.7
• App Version: 61.1034.139.0

Thank you

⟐ Answered March 05, 2022 at 15:21 MST

Although the documentation keeps referring to running the SDT software and choosing "Repair setup and validation" and entering TDM Replacement Mode.

Initially, we could not find this option on any version of the SDT software that we could find. We did finally find some software that had a technician mode that did allow for TDM Replacement Mode.

Now, however, we are getting the error:

Running Test: The type initializer for 'NCPTransport.AccessNcpTransportFactory' threw an exception.

With no further error information. We've updated drivers on the computer, but we're still getting the error. We can't find anything on the internet about this error or how to resolve it.

Any idea what this means and how we can get around this? We haven't even started the hard part yet, but we seem stymied by this software error.

⟐ Commented October 10, 2023 at 1:03 MST

Is there a possibility of running out of control terminal ports?