New
#301
I solved it finally. Many thanks!
I'm from Poland so if anyone has the same issue let me know, I'll try help.
I solved it finally. Many thanks!
I'm from Poland so if anyone has the same issue let me know, I'll try help.
hi peoples
i had the same problem and i changed the registry values as mentioned before and all things become normal
after 2 days .. this morning started my PC and the problem come again
anyone faces this problem again ? .. and how can i resolve it ???
help plz
Hi, presumably as a workaround you can schedule a script to run as appropriate.
Naturally you want to understand the underlying cause - or in this case, that could be ESET's responsibility. However, we don't actually know if there are other things that do the same. The symptoms have been around through generations of Windows, perhaps with more than one cause.
Tools like Sysinternals procmon, with a highly selective filter, or a registry monitor tool, could identify when the keys are written.
So, I tried, (I think) everything:
W10 does not allow me to edit registry, as I have no permission, but also does not allow me to edit permission rights or add new user at permission.
I started it minimal mode, also does not allow as I have no permission XD
Tried to start the .bat x64 files, they could not make the change as there is no permission.
I am the only user with administration rights on this home computer.
What should I do further to solve that?
Maybe I am doing it wrong, should I remove ESET firstly?
this menthod doesnt work to me.. i've changed to
HKEY_CLASSES_ROOT\CLSID\{42aedc87-2188-41fd-b9a3-0c966feabec1}\InProcServer32
HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{42aedc87-2188-41fd-b9a3-0c966feabec1}\InProcServer32
and restart... but my desktop still arrange by it self...
please help me... im going crazy..
Hi Irvan, just follow the manual fix below. It worked for me. Have to do it both locations. you can then confirm it by running the script file given in this tread.
Edit: 9/25/2015 [Manual Fix]
A user from the ESET forums named AREZCO has posted a manual fix.
Run regedit (start menu > run/search > regedit) and go to these 2 destinations:
HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{42aedc87-2188-41fd-b9a3-0c966feabec1}\InProcServer32\
AND
HKEY_CLASSES_ROOT\CLSID\{42aedc87-2188-41fd-b9a3-0c966feabec1}\InProcServer32\
Double click on (Default) and replace "%SystemRoot%\SysWow64\shell32.dll" with "%SystemRoot%\system32\windows.storage.dll" in both file destinations.
Once done, restart your computer and see if the issues have been resolved.
**It is important to note that you need to have permission to change the value of these keys so in order to do that you must perform the steps stated below.**
Originally Posted by chimera8888
You need to give yourself permission to edit the registry keys
Originally Posted by chimera8888
Start by right-clicking on the last sub-key which in this case is InProcServer32 and click on Permissions the Advanced then change Ownership to yourself.
Assuming you're on Windows 10 click on Change -> Advanced again -> Find Now -> Administrators.
Then tick the "Replace owner on subcontainers and objects" and also "Replace all child object permission entries..."
Click OK
Then select "Administrators" in the Permissions window you first opened and tick "Full Control" then hit OK
Do that to the InProcServer32 folder and the {42aedc87-2188-41fd-b9a3-0c966feabec1} in both HKEY paths
As for the reg file itself that i uploaded Right Click -> Properties -> Security tab ->follow the general steps i wrote above
I tried to this thing you made but it doesn't work out. I can't even do it mannually, when I try to replace %SystemRoot%\SysWow64\shell32.dll to %SystemRoot%\system32\windows.storage.dll , it says thats an error in the writting. I don't understand why, i honestly don't know very much about computers.
When i try do use your thing, appears the next sentences in the end of the black sheet:
SetACL finished with error(s):
SetACL error message: The call to SetNamedSecurityInfo () failed
Operating system error message: Acesso negado. (in portuguese means denied access)
ERROR: Acesso negado. (in portuguese means denied access)
Can you help me out?
it doesnt work man.. and i've been use Attachment 39381Attachment 39382 but it doesnt work on me too..
pretty confused about this.