Surface Pro 5 - no touch screen after N&P

[Blue House Computer Help]

Bit of a strange one. Had a Surface Pro 5 with a long dead battery that stopped booting (when plugged in). We opted for a nuke and pave. Drivers from Snappy Driver, windows update etc...

Everything seems to work except the touch screen. There is a missing driver in Device Manager.... Elan EzTouchFilter. But I downloaded drivers for it and tried to install them, then update from Device Manager, but it just has the Microsoft default drives and doesn't accept any new ones. The touch screen works when you go into the BIOS so it feels like it's a Windows driver issue but I don't know how to get the right one installed.




Oh and all 4 processors have Yellow exclamation mark triangles next to them.




What's going on? Should I have installed from a Surface specific image?

 

[ThatPlace928]

Update your BIOS, then run Windows updates again, and re-install driver(s). I would uninstall previous drivers first, in case there's a conflict.

 

[frase]

Have you disabled "automatically download drivers from manufacturer" with System Properties>Advanced?

 

[Blue House Computer Help]

No, so it seems straneg that they don't pull down from windows update like usual

 

[Markverhyden]

It sounds like you did the N&P the old fashioned way. Boot from a USB stick, N&P with stock W10, then go from there.

I do know the bangs on the processor cores means the OS is missing instruction sets. Seen that a handful of times on newer laptops and servers. While I've not had to work on a Surface all instructions indicate that you should use the built in methods or at least download a serial number specific image.

Creating and using a USB recovery drive for Surface - Microsoft Support

Learn how to reset your Microsoft Surface and solve problems using a USB recovery drive or Surface recovery image.

support.microsoft.com

 

[Blue House Computer Help]

Thanks Mark... that was what I was thinking I might need. Will do.

 

[johnrobert]

Try driver updater Snappy that always works for me