Windows 10: Hp Envy x360 M6 no keyboard or mouse after Creators update

I can confirm that this situation is a super tricky driver issue.

Yesterday I tried the "reset my PC" option offered by windows 10. This did not help. Then I tried the "Refresh" option that has been available from Windows Defender since the last big update. It took a while to complete so I left the computer alone and went out. When I came back, it was finished and TA-DA the builtin touchpad and keyboard were working. I was happy with that and went to bed. This morning they did not work again! I checked and yeah! Windows had installed three updates between now and then, one of them being the large cumulative June 2017 update. So I missed my time window of trying to make Windows not update oem drivers automatically. Sigh.

So I tried Refresh again. And disabled networking (by making Windows forget all the WiFi passwords) to make sure it will not auto update anything. This time it did not help! And when it was done, the windows update history says that the June 2017 cumulative update "kb4022405" is already applied and furthermore it cannot be removed!

At this point I am no closer to finding out which driver is the issue (and i believe i have tried reinstalling any and all that seem even remotely relevant). My only remaining option is to restore the backup I did just before I started all these excercises, and then do the "Refresh" again, in a hopeful attempt to repeat the success I enjoyed last night - and this time be 101% sure the computer cannot do any automatic updates....

Of course my wife goes for another business trip in a day so as I probably don't manage to fix this by then, it will be another few weeks when I will have the opportunity to try again ....

 

This gets weirder! Last night Microsoft pushed an update to my wife's machine and in the morning the keyboard and touchpad were working. Great, awesome! ... however, by this evening they had stopped functioning again.

 

Open administrative command prompt and type or copy and paste:
1) sfc /scannow
2) dism /online /cleanup-image /restorehealth
3) chkdsk /scan

When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

4) msconfig (in the pop up system configuration > move the dot from normal startup to selective startup > uncheck load startup items > click service tab > in left lower corner check hide all Microsoft services > in the lower right side click disable all > click apply or ok > do not reboot)

5) taskmgr (in the pop up task manager > click on the start up tab > click on status so that the column sorts with enable rising to the top > right click on each row with enable and change to disable)

https://support.microsoft.com/en-us/...oot-in-windows

How to perform a Clean Boot in Windows 10 - TechNet Articles - United States (English) - TechNet Wiki

6) shutdown /r (you will reboot the computer so that it is in clean boot)

Evaluate the performance on your computer in clean boot during typical use.
Are the boots faster or slower?
Are the shutdowns faster or slower?
How has the audio and video performance changed? Is it better, worse, or the same?
How has the use of the keyboard changed? Is it better, worse, or the same?
How has the use of the mouse changed? Is it better, worse, or the same?
Continue using clean boot indefinitely to monitor performance.

8) type control in the left lower corner search > click on control panel > click on large or small icons > click on troubleshooting > on the left pane click on view all > run the following windows troubleshooter:

Hardware and Devices

9) View the detailed information for the troubleshooter. If it fixes something or is unable to fix something please use the Microsoft snipping tool or a camera to post an image into the thread.

 

I suffered through this same issue and after multiple reinstalls I found out what the issue was; it turns out that the Intel Integrated Sensor Solution was the culprit. If you go into Device Manager>System Storage and disable Intel Integrated Sensor Solution it should fix the issue after a restart.