Type Cover not Working but ...

While my Type Cover issues still exists thanks to a Firmware update in September that I've previously identified, I've had to put a new battery in my SP4 pen that came with it. This battery may or may not have expired before the MS Technician reinstalled Windows remotely. So, while the pen is recognized and the top button works to open various applications, the screen does not interact with the pen at all.

I'm so close to putting 'something heavy' through this device's screen - this is how frustrated I've become, having no Type Cover, now a half-functioning Pen, and having to manually switch between Desktop and Tablet mode, just so I'm able to type using the software keyboard.

If the device is out of warranty as the MS Technician was happy to point out - STOP PROVIDING ME WITH UPDATES - ESPECIALLY THOSE THAT BREAK IT!

This is so, so, so very frustrating. 'Disappointed with you Microsoft.

I wonder, if they can't figure out what is the problem, why couldn't they just get the old firmware source, update the firmware version number, and let us download the update to fix the type cover issue? (I don't really mind it if I have to manually download it, or even ask a Microsoft Representitive to give the link to download it like the "service hotfixes".)

I use the SP3 in my home or at work, so I can accept the risk to run it without the Intel security patch. I just want it to be something fully usable and not an expensive brick.

I finally received a repaired SP4 from Microsoft. No explanation about the problem. But it works.

When you do a windows latest update on this repaired surface, does the same keyboard disconnection problem appears again ?

I spoke to a Microsoft trade-in partner. He suspect it's due to motherboard, which I believe it is caused by firmware updates, since the symptoms are the same for us. But, Microsoft support team does not think it's due to updates, as their support website says no issues found. This is so frustrating. I think whoever is affected by this same issue should voice out at Microsoft social media platform (eg. Instagram, FB, etc..), so that the support team can focus and quickly resolve this issue for all of us.

Hi Br0mZ,

Although in your post, you have indicated that you're not sure if it happened after an update. In my earlier post, I confirmed it categorically happened 'because' of the update - and posted an image of (most of) the drivers / firmware it loaded.