Jump to content

Bainge

Members
  • Posts

    5
  • Joined

  • Last visited

Posts posted by Bainge

  1.  

     

    The update did not fix the issue for me (or I didn't wait long enough), but changing the mentioned registry value did seem to do the trick.

    BUT I had to change the value from both

    HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{42aedc87-2188-41fd-b9a3-0c966feabec1}\InProcServer32\

    and

    HKEY_CLASSES_ROOT\CLSID\{42aedc87-2188-41fd-b9a3-0c966feabec1}\InProcServer32\

    Changing from Wow6432Node alone was not engouh.

    As Marcos mentioned, both registry keys are owned by SYSTEM and neither regular users nor admins can edit them by default. I first had to change the ownership of the keys, then edit permissions to allow modifications, change the values, and finally change the ownership back to SYSTEM. So try this at your own risk...

     

    Can you explain how to make admin permission on these keys ? I try to bring a admin permission but I have a message with "access refused" :(

     

     

    You have to change the ownership of the folder from "system" to your account and then grant full control on them. (and after the modify return it back to system)

     

    EDIT: Btw I managed to fix it, thanks for the quick fix!!!

     

     

    Ok thanks :)

  2. The update did not fix the issue for me (or I didn't wait long enough), but changing the mentioned registry value did seem to do the trick.

    BUT I had to change the value from both

    HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{42aedc87-2188-41fd-b9a3-0c966feabec1}\InProcServer32\

    and

    HKEY_CLASSES_ROOT\CLSID\{42aedc87-2188-41fd-b9a3-0c966feabec1}\InProcServer32\

    Changing from Wow6432Node alone was not engouh.

    As Marcos mentioned, both registry keys are owned by SYSTEM and neither regular users nor admins can edit them by default. I first had to change the ownership of the keys, then edit permissions to allow modifications, change the values, and finally change the ownership back to SYSTEM. So try this at your own risk...

     

    Can you explain how to make admin permission on these keys ? I try to bring a admin permission but I have a message with "access refused" :(

  3. I'm still searching for a solution and the only thing I can say is that it seems that only Windows 10 in English is affected by this problem.

    I cannot find any French or Italian  forum with people speaking about this.

     

    As Brehon wrote, we are discussing for this problem in Tenforum: HERE and HERE.

     

    Personally, I'm not sure about an interaction between Eset and Win 10, but it seems that almost all those who have this problem use Eset Smart Security.

    I wrote to Customer Care opening a ticket and I'm waiting for an answer.

     

    It should be a good choice if all of you does the same thing.

     

    Hello,

     

    I have the same problem since 23/09/15 with Windows 10 french version and I have Eset french version 8.0.319.1 ... :(

×
×
  • Create New...