Surface Pro 4 type cover suddenly not working.

I'm having the same problem, type cover is not working since July. But I did not know because most of the time I use my SF4  with the docking station and use external keyboard. I have tried every possible way available on the internet. I tried to do the WINDOWS RECOVERY and it DIDN'T WORK!!! So I want to send my SF4 for replacement but my SF4 have a dent (had it long time ago and and it was working fine), they said I can't get a replacement because I have physical damage to my SF4. So they recommend me to buy a Bluetooth keyboard, if so, I will lose the mobility function of my SF4 (so what's the point of having SF4 at all). Seems like I'm not the only one with this problem and Microsoft is denying and not trying to responsible for it.

I just booked my appointment to go to the MS store to see if they have a remedy before reading this post. I am now going to cancel my appointment due to reading the horror stories of them trying to charge you guys $450 to replace the unit. My warranty just ended last month!

I guess this thing will collect dust because there is no way I am forking over $450 to replace my system that may have the same issues once the July update installs!

Couldn't argue with anything you've said there and my expectation of how Redmond will handle this is in no way an endorsement of it. 

It is a shame that the large, but in overall terms, limited number of devices affected will probably never be officially acknowledged. But it is the way of things and from car recalls to bungled updates, it is often how large corporations approach these situations. 

As I said, in my years of using these things I've enjoyed a high level of reliability, especially when on the road. So it is particularly

egregious that this situation has so limited the device. I have the luxury of being able to wait for a fix, many don't and I can only wonder at how frustration that must be. 

In the mean time, I'll shout form the rooftops about it, though it is getting some mainstream traction: https://www.theregister.co.uk/2018/08/24/surface\_pro\_4\_devices\_update/

If you think it will be done on the hush hush and this is good enough, its not. For such a high profile expensive line of kit its understandable why they don't want bad PR hence not stating there is a problem to even be fixed. Why would they publicly announce they did an update that bricked type covers. No one would ever update their SP. My Sp was a few updates behind so I did a big roll up. I think what caused mine to screw up is that it did it on battery power. It did most of the updates ok then the battery dropped below 40% and failed the last bios updates. (It would even start the bios updates before you ask until it was powered from mains.) I plugged it in, it updated and bam end of type cover. Fantastic. 

If they do finally either secretly release an update then great but until then I am using a normal laptop. Imaging typing this on screen, err no thanks. So in terms of using my surface for productivity then its game over.  I won't be recommending them to anyone unless all they want to do is read stuff or watch movies. That being the case get a cheap android tablet or an Ipad.  I haven't bought a bluetooth cover for it yet and its now in the cupboard gathering dust. I could sell it without the typecover and then sell that desperately but that's plain wrong. Just like Microsoft's behaviour now.

To a certain extent, I have to disagree. I've used the Pro line since its very first as my main work machine, often with the previous generation as a home machine. In all cases, bar one (SPro3 with the yellow line screen), I've found them to be very robust and easily withstood the rigors of the road as well as desktop usage. 

This is the first time I've experienced this level of issue and it is very disappointing that it is being dealt with in this manner. 

To simply not acknowledge what is obviously a fairly widespread fault is unforgivable. 

I'm not going to rush off to get the SPro4 replaced, as I do have the luxury of another machine in the meantime, but I suspect that an update will be quietly rolled out in the near future that addresses the specific issue without acknowledging it further, which is not good, but par for the course in such circumstances.