The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    NP780Z5E-S01UB Touchscreen Not working

    Discussion in 'Samsung' started by DRatJr, Mar 17, 2016.

  1. DRatJr

    DRatJr Notebook Enthusiast

    Reputations:
    0
    Messages:
    37
    Likes Received:
    0
    Trophy Points:
    15
    Hello all!

    I own a Samsung Series 7 Chronos (NP780Z5E-S01UB) and the touchscreen recently stopped working. I had installed Linux on the machine, dual booting it, and the touch functionality was working fine on Linux, even though in the Samsung Settings App on the Windows side had it turned off. Fast forward some time, I uninstalled Linux, wiped HDD, and reinstalled Windows 10.

    Now, the touch screen isn't working at all. In the Samsung Settings App I have even lost the category on the left side for touch devices (turning off touchpad and touch screen). I have tried using SW Update, but there are no drivers for it on Win8 (came with this), Win 8.1, or Win10.

    When I go to device manager I just see a HID Compliant Touchscreen driver that's installed, but nothing else.

    Does anyone know how I can fix this?

    Thanks!
     
  2. John Ratsey

    John Ratsey Moderately inquisitive Super Moderator

    Reputations:
    7,197
    Messages:
    28,841
    Likes Received:
    2,165
    Trophy Points:
    581
    I wonder if the touchscreen has become deselected at the BIOS / NVRAM level. For example, if the touchscreen is turned off in Settings, then Windows gets reinstalled and the new Settings doesn't bother to provide the option because it can't see the touchscreen. There might be a value in the registry which would re-enable the control in Settings. I wouldn't know where to look but this could be the first line of attack.

    You can see if resetting the BIOS to defaults followed by reinstalling Settings might clear the problem. If not, reloading the BIOS with the clear NVRAM switch (details are in one or more of the unbricking threads) would be my next step.

    John
     
    DRatJr likes this.
  3. DRatJr

    DRatJr Notebook Enthusiast

    Reputations:
    0
    Messages:
    37
    Likes Received:
    0
    Trophy Points:
    15
    I have tried reinstalling settings. But this information is farther than I have been able to get! So I will google around a bit to see if they touchscreen can be toggled in the registry, and if not I'll look in the unbricking threads. Thanks so much man! You actually helped me years ago with some problems too haha. I'll report back
     
  4. DRatJr

    DRatJr Notebook Enthusiast

    Reputations:
    0
    Messages:
    37
    Likes Received:
    0
    Trophy Points:
    15
    Thank you so much John! Editing the registry worked!

    I used these two sources:
    http://answers.microsoft.com/en-us/...keyboard/b757f349-a128-4c7e-9230-6a5ad14a5c86
    http://www.eightforums.com/tutorials/43561-touch-screen-enable-disable-touch-finger.html

    Essentially, they told me to look in the HKEY_CURRENT_USER\SOFTWARE\Microsoft\wisp\Touch folder, but the keys they told me to edit were different.
    One was "Touchgate" and the other was "TouchUI", changing the values to 1 instead of 0. I did this to both to be safe.

    But do you know the difference between the two? Looking on Microsoft's website for both, they both seem to be for the same thing but for different Windows versions?
    https://technet.microsoft.com/en-us/library/ff716012.aspx
    https://technet.microsoft.com/en-us/library/cc766207(v=ws.10).aspx
     
  5. John Ratsey

    John Ratsey Moderately inquisitive Super Moderator

    Reputations:
    7,197
    Messages:
    28,841
    Likes Received:
    2,165
    Trophy Points:
    581
    Thanks for the update. I'm happy to hear that you managed to locate the cause of the problem. :)

    I haven't a clue about the reason for the two different registry keys. Probably Microsoft haven't a clue either but, as you suggest, it may be related to different Windows versions (perhaps wanted to add more options so created a new key).

    John