![](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)
My issues seem to only be getting worse. I thought the February firmware update would finally be the fix, but alas it was not. Now I'm experiencing an issue where the keyboard (type 1) is connected but not fully detected, so when I start my SP1, it's stuck at the login screen. I can't type anything with the keyboard, but I also can't get the onscreen keyboard to come up, suggesting that it knows the type1 is connected. The only way to fix this is to restart the SP1 several times, or disconnect and reattach the keyboard repeatedly. It's worth noting that simply disconnecting the keyboard won't allow me to access the on screen keyboard, as if the keyboard driver is just frozen or something. I'm also still experiencing all the random reboots from before.
It is simply astounding that Microsoft obviously introduced this killer bug with the 8.1 update, and somehow can't figure out how to reverse it after all this time, and all these angry customers.