Laptop keyboards broken/double key after Windows updates - Hell Corner  

** This is an informative post , if you are just trying to help you can just skip this post unless you want to add to contents .

I have had a problem losing 2 laptop keyboards to 2 consecutive windows updates where I attempted to tackle the issue and here are my findings (since I am starting to see this problem escalating to so many users of the forum and online) :

1 - If you are like me with the habit of leaving laptop running over night for downloads , encoding , etc there might rise issue of overheat for prolonged times after windows updates resulting from re-indexing files / search optimization (Superfetch) , unscheduled defrags , re-optimizing executable files (Prefetch / Superfetch) , creating a restore point , antivirus getting all spooky from the massive system change ... The result is , your system keeps running at extreme heat condition for like a couple of days after the update , where the keyboard being placed right above the CPU/HDD would undergo similar condition to the pancake while heating on the pan where eventually your keyboard gets fried . Fried keyboards do not end up 100% dead but they may - well - just act bizarcal like skipping keys or double keying where you may notice that most keys with problems are the ones right above heat spots (CPU / Sink Rod / HDD / SSD) .

2 - So yes your keyboard is lets say "busted" hardware wise , changing it would instantly solve the problem , however the problem may rise again if you did not manage to clear the heat issue .

3 - Having a cooling pad / vacuum fan does not save you , just makes it take a little longer while .

So bottom line is :

I suggest you disable superfetch / prefetch / system restore / defrag schedule / microsoft experience program (from task scheduler) and try to run them manually one at a time later to avoid the "Pan Effect" Microsoft Windows updates have .

Cheers

windows updates resulting from re-indexing files /

- would suggest you don't add operating system files to your indexing options. Doing so could also significantly increase the size of your index database.

Further, indexing, when it's working properly, backs off (stops) with just a little use.

I can't see why System Restore would add significantly to the workload.