This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I don't know what happened. I turned my Surface Pro 4 on the other day and the type cover is dead. No lights. No response. No indication that it's working at all. I rarely take my surface anywhere.
This started on July 9th 2018. My system information is below. I've gone through all of the steps in the "Troubleshoot your Surface Type Cover or keyboard" page. I've tried to manually download and install the latest firmware and drivers from the "Download firmware and drivers for surface" page. I picked SurfacePro4_Win10_16299_1801701_1.msi. My device manager does not show the "Surface Touch Cover Filter Device" under keyboards or anywhere. It only shows the HID keyboard and cannot detect my type cover. The type cover is completely unresponsive. Also, my windows updates are completely up to date. I've provided the links to the troubleshooting pages I used below.
AGAIN, WTH
Troubleshoot your Surface Type Cover or keyboard
Download drivers and firmware for Surface
Edition
Windows 10 Professional
Version
1803
OS Build
10.0.17134.165
Serial #
035060755053
Processor
Intel(R) Core(TM) i5-6300U CPU @ 2.40GHz
Graphics card
Intel(R) HD Graphics 520
System
OSType64BitX64
RAM
8 GB
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.
The upside of my Surface is that it's been wiped/reinstalled multiple times in futile attempts to correct the Type Cover issue, then angrily shoved in a closet, so there's nothing to lose. :)
I'll try that. And if that fails, I may just start hacking in the registry with best guesses. Of course, the MS download link for SP4 drivers/frimware (below) has been dead all day, so they may be onto us trying to fix this. :)
https://www.microsoft.com/en-us/download/details.aspx?id=49498
The only thing I can think of trying would be to remove those firmware devices from device manager and delete the drivers. Scan for new devices to pick up the firmware again and it should reinstall the drivers. At that point it might reinitialize that section of the registry. Only do this on a machine where you have full backups and don't mind reimaging if something goes wrong - the usual "this worked on my machine, but yours might be different" caveat applies :)
Version is W10Pro v1903. Yes, everything is there as expected in Device Manager (except that I have 6 total items under Firmware)...
On my Surface I had to add the Policy REG_DWORD.
However, on the screenshot you shared I don't see any GUIDs beneath Firmware Resources. That's not something I saw on my end - normally they should be there. Not sure what to suggest. What build/version of Windows are you running and if you go into Device Manager do you see the firmware resources there?
- Open Registry Editor, go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FirmwareResources. You should see four GUIDs, one for each firmware resource. Inside each GUID, create a REG_DWORD named "Policy" and set it to a value of "1". This enables firmware rollbacks and downgrades.
- Open HKEY_LOCAL_MACHINE\HARDWARE\UEFI\ESRT. You should see four GUIDs, one for each firmware resource. Inside each GUID, review the "LowestSupportedVersion" value. This is the oldest firmware version you'll be able to downgrade to. For me, the EC was 0x340100 (34.01.00) and the UEFI was 0x30b0a28 (3.11.2600).
On my SP4 (with a dead Type Cover), my reg entries for step 1 are completely blank. Should I just add each GUID with a REG_DWORD of "Policy" = "1"?
Editorial: I can't fathom why MS hasn't addressed this with a "fixall" tool or a firmware update that once and for all corrects all these issues. This is the most blatant lack of ownership of a manufacturer-induced user issue that I can remember.
