After someone said on one of the many threads about surface update issues that another update was out I gave it a try. It took around 8 hours to process the updates often sticking at 21% for hours before slowly moving on. The final result is nothing, no improvement, typecover still detected as HID Keyboard device complete and utter tosh. I have spent hours on this and now I have sold the working type cover and bought a bluetooth cover.
I don't know what sequence of events is causing these issues or even if microsoft can fix them, but as far as I can see ever from the very launch of surface devices they have had problems. If you have never encountered issues then lucky you, but there are some scenarios of hundreds of use cases where updates fail. This is down to MS trying to automate fixes and rolling them up into windows update so they cannot be rolled back. In the old days before over the air updates were easy, product testing was more in depth as the quick get it out the door if there is a problem we can just update it mentality didn't exist. In fact if products never got updated and were working to start with they would never then subsequently break with some improvement update that is just thrown out there. Offset this though with telemetry from busted updates and MS must have a good idea of how many device they are shafting. It a lot I bet and these figures are hidden away else no one would buy an expensive device that is unreliable. Poor form indeed.