Touch components does not work for the first two minutes after logon with custom shell RRS feed

  • Question

  • If I run windows with a custom shell, i.e. without explorer.exe running, the touch components in windows (wisptis.exe?) doesn't seem to do anything for the first two minutes. After that time has passed, it all works as it should.

    So it would seem that explorer.exe is doing something when it starts that gets wisptis.exe to do it's stuff.

    Having a look in process monitor shows that after the two minutes, wisptis.exe starts a thread and reads a bunch of settings from the registry. Not sure how I would find out what triggers this though.

    I've also noticed that the Shell Hardware Detection service seems to start when I logon, and stop after the two minutes, exactly when touch starts working. Although, disabling the Shell Hardware Detection service makes no difference.

    Does anyone have any idea what's going on here?



    Monday, March 2, 2015 8:39 PM