Surface Type keyboard not working after upgrade to Win 10

 it is Windows 10 that has screwed up Type driver.

I don't think that that is clear.  There have been firmware updates to consider too.  Check to see if the firmware thinks that there is still a Touchcover device to connect to.   E.g. what do you see with this WMIC query?

wmic  sysdriver where (DisplayName like "%Surface%") list brief

C.f.

BTW I once had a similar effect in my Surface 2 Pro regarding Network devices.  Device Manager apparently could not detect any, even with Show hidden... requested.  What finally worked for me to correct that was doing an ISO Upgrade Repair procedure using a (sufficiently appropriate) ISO file I fortunately happened to have previously downloaded.  Unfortunately at the time I didn't think to try using a WMIC query too to see if it was also blind to those devices.

FYI

Robert Aldwinckle

---

I have also tried manually entering my serial number, but still only provides me with a Windows 10 recovery download.

I receive this error. 

I receive this error. 

[PowerShell syntax message]

When you use PowerShell certain command line syntax needs to be escaped by the PowerShell command line escape string  (--%).   I mentioned this in the post I linked to.   

Alternatively, you can open  WMIC  itself by just entering that portion and then entering the rest of the query as a subcommand in it, without causing PowerShell any confusion.

These are my results. 

These are my results. 

That list of drivers will be most interesting to someone else who has a working Surface 3 Pro, perhaps particularly since SurfaceTouchCover and SurfaceTypeCover are not there.  Meanwhile I used them to try to find a more complete list and got this

https://blogs.technet.microsoft.com/surface/2015/01/16/firmware-and-driver-updates-to-get-more-from-your-surface-devices/ 

anonymouscommenter says:

Why aren't all of the drivers signed by WHQL?

which then prompted me to do a scan of my  %windir%\Inf  to compare (remember, I only have Surface 2 Pro to look with)

PS>cd windows\inf
PS>LS -Fi *.inf |? {(gc $_.FullName) -match "Surface"}  | sort LastWriteTime | ft FullName -AutoSize -Wrap

which are mostly  OEMnnn.inf  things?   OK.  I just added the sort stage and found something that could be helpful.  There is an errata.inf which mentions Surface 3 Pro and then two more OEM .inf files which seem insignificant to me but (as they say) YMMV.  I'm not sure where else this may be leading us, so I'll stop here for now.

In fact, I had one last idea which seems to produce even more useful results:  make the above pattern match for "SurfaceT" and see what you get.   Errata.inf gets dropped from that list but instead there are some interesting hits in it by using this Regular Expression in a Find:  Surface.*T  (e.g. in ISE).

HTH

Robert

---

 /something in the update process kills these type covers, not the update itself/

 

Perhaps; nevertheless I think there are clues about how it happened in those .inf files.  So perhaps if someone understands .inf files well enough they could see better what had caused support for older devices to be dropped and then even find a workaround to have theirs added again.

You'd see things like

 

Surface Pro 4 Type Cover Integration Service  SurfacePro4TypeCoverIntegration  T

RUE     Running  OK

 

Thanks for mentioning that one in particular.  It was not in the (evidently partial) list that I found.

But knowing this info won't lead to a fix.

 

Again, I would agree but only because I am mainly interested in understanding how it happened.  As I mentioned above, better knowledge may lead to someone figuring out a workaround; otherwise I can easily imagine that MS would stay mum and unresponsive.

What would be interesting is to see if a SP4 typecover or newer worked on this

SP3 (anything newer than the SP3 typecover) or if in fact the customer has an

SP4 typecover.

  

Absolutely.  This is the first time that I have been aware of such an option.  In fact, now I am wondering if there may be OEM keyboards/adapters  which have the right attachment but present themselves as newer models which are still supported?

Robert

---