Jump to content

massih majidi

  • Posts

  • Joined

  • Last visited

About massih majidi

  • Rank

Profile Information

  • Location
  1. I think tha problem happens when Eset serches after windows registerys that are wrong. the fillowing regisrty value (HKEY_CLASSES_ROOT\CLSID\{42aedc87-2188-41fd-b9a3-0c966feabec1}\InProcServer32\) in windows 8.1 (and older) are shell32.dll. and Eset thinks that registery value in windows 10 still refers to shell32.dll , and the value is mischanged to windows.storage.dll (the defualt value).
  2. There's no need to do anything manually. The fix was already distributed via an automatic module update as stated above. Excuse me, but the problem on my PC happend 5 hours ago, and my ESS V8 cleaner module version is 1113. the latest update is for 8 hours ago, so problem have happend infront of cleaner.
  • Create New...