BIG PROBLEM across all Surfaces. In my recent months of troubleshooting, I've found many others recently having this same issue. It seems to apply to Surface Pro 1/2/3/4 and possibly the latest models. This link is just one example of the complaints: Surface Pro 4 Jul 2017 Update - Type Cover not working My efforts copy/pasted below. Add Surface Pro 2 Type/Touch Covers to the list: Same issue here. Worked fine for 2 years, then noticed on my Surface Pro 2 around April 2018 off and on, then by May 2018 my Touch Cover 2 was completely bricked. After trying all kinds of remedies, I bought a "new" Type Cover 2, same issue. Cleaned the connector pins on Surface, did all the steps and realized that it's a Firmware issue. Somewhere along the way, these updates made either the Surface Pro (2/3/4) firmware and/or the Type/Touch Cover firmware incompatible. It's almost as if something in the Surface BIOS is telling the pins not to send power to the Covers (no LEDs, no Caps lock, nothing). My type and touch covers are not recognized in the UEFI. I'm finding HUNDREDS maybe thousands of others having this issue, especially recently. I've wasted around 1 week of my life trying to fix this, even looking at new computers to buy. And I'm an experienced MS tech! Why can't MS release a new firmware update or downgrade to fix all of the Surfaces and covers? I called MS support today, and their solution was to bring it to an MS store (3 hours drive), where they MIGHT give me a discount on a newer system. My system was perfectly fine before these updates this year, I shouldn't be forced to buy a new computer because of MS's firmware mistake. 20+ years MS user and tech supporter, this is ridiculous. If this is their quiet way of pushing users to buy new hardware, that would be a new low for any company. MS needs to realize that no keyboard/mouse on any Surface basically BRICKS it, and defeats the purpose of the once amazing device. I spent about 10 hours today researching all of the ways to try to fix this. This is my post before I try resetting/refreshing/clean install tomorrow - which I'm afraid may not fix it due to all the other stories I've read. I'm glad I don't have to explain this to a client if it were an enterprise computer! Good luck to all with this issue. MS, you can do so much better, easily. It's got to be something with the USB internals and of course the firmware all need to play nice together (and have a way to restore older firmware for issues like this).