Jump to content

Windows 10 forget folder view setting when ESS is installed


Recommended Posts

 
 
 
 

 

First of all, manual editing of the registry is not necessary - everything should be fixed automatically by means of the Cleaner module update. Apparently it doesn't fix the registry key on every system for some reason so we need to investigate further to find out what is causing it.

 

Hi

thanks Marcos!

about

Apparently it doesn't fix the registry key on every system for some reason

 

 

, could eset release a small tool to fix these 2 registry keys ? because many users have problems even to open regedit.exe , and change them

 

a small tool , to run as administrator that can fix these 2 keys would be really very helpful

 

i'm talking about the cases where the cleaner module updated  won't fix them

Edited by mantra
Link to comment
Share on other sites

Martin_B, on 25 Sept 2015 - 8:08 PM, said:snapback.png

 

Quote

 

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

 

Switched ESET to Test Updates, changed both registry values, ownership set back to system, rebooted. Keys stay at windows.storage.dll but icons keep switching positions to left side after every reboot.

Anything else i can do? Definitivly do not want to install windows from scratch.

 

Edit: Cleaner Module is 1112. Will check again in an hour or two if behaviour changed.

 

 

Waiting a bit longer fixed it for me.

A bit was playing a few hours :) Everything fine now.

 

Can we go back to normal updateing or will this uninstall 1112?

 

Martin

Link to comment
Share on other sites

 

Martin_B, on 25 Sept 2015 - 8:08 PM, said:snapback.png

 

Quote

 

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

and

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

 

Switched ESET to Test Updates, changed both registry values, ownership set back to system, rebooted. Keys stay at windows.storage.dll but icons keep switching positions to left side after every reboot.

Anything else i can do? Definitivly do not want to install windows from scratch.

 

Edit: Cleaner Module is 1112. Will check again in an hour or two if behaviour changed.

 

 

Waiting a bit longer fixed it for me.

A bit was playing a few hours :) Everything fine now.

 

Can we go back to normal updateing or will this uninstall 1112?

 

Martin

 

It brings you back to the OLD cleaner module!!!!!

Link to comment
Share on other sites

  • Administrators

I think Eset should provide to all us a AUTOFIX (EXE OR MSI).

 

Why to complicate things if the fix is distributed automatically via a module update? Just change to pre-release updates, wait until the update completes and then restart the computer. I assume 2 restarts may be needed - the first one to change the registry value and the second one for Windows to use that value as it starts.

Link to comment
Share on other sites

Issue fixed. According to procedure mentioned here. I manually changed those registry setting. Lovely. Many many thanks for those who helped. Users here and ok - thanks to Eset. I like Eset and I really do not want to change my security soft. I do not want to reinstall my Win 10 either. :)

Link to comment
Share on other sites

Issue fixed. According to procedure mentioned here. I manually changed those registry setting. Lovely. Many many thanks for those who helped. Users here and ok - thanks to Eset. I like Eset and I really do not want to change my security soft. I do not want to reinstall my Win 10 either. :)

 

I'm sorry to harp on but why aren't people backing up their systems? There's no real reason not to nowadays. It's not rocket science and the software is free. I find it unbelievable all this talk about reinstalling Windows, there's no need.

Link to comment
Share on other sites

Because I like may changes few minutes ago. And I like my system "go". Backup? Yes, but why. Why should I use my backup image "week ago". My backup "week ago" is ancient thing for me.I need my system running now with "now" configuration. And ok. The community here did fix my problem. Without need to go back. They are perfect here. Never forget.

Link to comment
Share on other sites

In my case windows10 and Eset SS 8.319.1

This value not work

%SystemRoot%\SysWow64\windows.storage.dll

I change value from

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

and

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

to %SystemRoot%\system32\windows.storage.dll

And yet all is ok

Link to comment
Share on other sites

 

Issue fixed. According to procedure mentioned here. I manually changed those registry setting. Lovely. Many many thanks for those who helped. Users here and ok - thanks to Eset. I like Eset and I really do not want to change my security soft. I do not want to reinstall my Win 10 either. :)

 

I'm sorry to harp on but why aren't people backing up their systems? There's no real reason not to nowadays. It's not rocket science and the software is free. I find it unbelievable all this talk about reinstalling Windows, there's no need.

 

 

I do backup, however I tend to delete old backups to save space, I actually backed up *after* an incorrect malware removal - bad luck eh? I only realised after a restart that it was borked...

 

Shoot me! :P 

Link to comment
Share on other sites

In my case windows10 and Eset SS 8.319.1

This value not work

%SystemRoot%\SysWow64\windows.storage.dll (Why @Marcos you tell to all to change to this value?)

I change value from

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

and

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

to %SystemRoot%\system32\windows.storage.dll

And yet all is ok

And dear @Marcos human who recognized that the issue is related to Eset and explained how to reproduce it is JAMESWT, and first human who found the regkey solutions is AREZCO.

And the issue in General was discovery by users from Eset forum and tenforums and i Thanks all People that contribute to the thread.

All users from forums was able to reproduce the issue at first trytime.. Only eset not.... But Thanks to do a update that sometimes solve the issue and Thanks to update eset SS 8 and 9 to solve the issue

Edited by JAMESWT
Link to comment
Share on other sites

 

In my case windows10 and Eset SS 8.319.1
 
This value not work
%SystemRoot%\SysWow64\windows.storage.dll (Why @Marcos you tell to all to change to this value?) 
 
I change value from
HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{42aedc87-2188-41fd-b9a3-0c966feabec1}\InProcServer32\
and
HKEY_CLASSES_ROOT\CLSID\{42aedc87-2188-41fd-b9a3-0c966feabec1}\InProcServer32\
 
to %SystemRoot%\system32\windows.storage.dll
 
And yet all is ok
 
 
And dear @Marcos the first human that understand issue is related to Eset And explain how reproduce it is JAMESWT and first human that Found the solution with regkey it is AREZCO.
 
And the issue in General was discovery by users from Eset forum and tenforums and i Thanks all People that contribute to the thread. 
 
All users from forums was able to reproduce the issue at first trytime..  Only eset not....  But Thanks to do a update that sometimes solve the issue and Thanks to update eset SS 8 and 9 to solve the issue 

 

 

 

I think the important thing is that Eset as a group managed to sort the issue out, I do however question the apologists, that blamed everything other than the generally brilliant Eset software - however I can see from that reasoning why they would.

Edited by daveiw
Link to comment
Share on other sites

Hereby the registry file you need to restore your icon positions on your desktop, see attachment.

Extract the rar file somewhere and dubbleclick on  "Windows10 with Esset - Restore Icons Positions.reg"

 

Let me know if this was easy  :D

 

 

Regards,

Bocky Wocky

Windows10 with Esset - Restore Icons Positions.rar

Link to comment
Share on other sites

Huge thanks to all contributors to resolve this issue.

 

Still, as average user I couldn't find way to force registry change (if this justify forum level criteria I admit that I am fairly stupid). 

Also, showing deeper level of ignorance I couldn't update Cleaner or CM (and have no idea how to do it) from 1110 to 1112. 

Furthermore, my version of SS 8.0.312.3, which seems not to ne the latest one and it doesn't update further.

 

Now, as I believe that few other users my suffer from same mental deficiency to resolve what is apparently simple, self-explanatory and straightforward solution, may I kindly beg someone to ENLIGHTEN us, intellectual inferiors, as reading through pages on forum just ends up with frustration.

 

Thank you for attention.

Link to comment
Share on other sites

To Eset team - please, will You let us now, when we can use normal update mode instead of prerelease one? When it's safe. And module 1112 stays still. Thanks ladies and gentlemen.

Link to comment
Share on other sites

Copy and paste this in notepad and save as blabla.reg
Dubble click on it and ready.

 
Windows Registry Editor Version 5.00
 
[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{42aedc87-2188-41fd-b9a3-0c966feabec1}\InProcServer32]
@=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\
  00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,77,00,69,00,\
  6e,00,64,00,6f,00,77,00,73,00,2e,00,73,00,74,00,6f,00,72,00,61,00,67,00,65,\
  00,2e,00,64,00,6c,00,6c,00,00,00
"ThreadingModel"="Apartment"
 
[HKEY_CLASSES_ROOT\CLSID\{42aedc87-2188-41fd-b9a3-0c966feabec1}\InProcServer32]
@=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\
  00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,77,00,69,00,\
  6e,00,64,00,6f,00,77,00,73,00,2e,00,73,00,74,00,6f,00,72,00,61,00,67,00,65,\
  00,2e,00,64,00,6c,00,6c,00,00,00
"ThreadingModel"="Apartment"

Link to comment
Share on other sites

Copy and paste this in notepad and save as blabla.reg

Dubble click on it and ready.

 

Windows Registry Editor Version 5.00

 

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

@=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\

  00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,77,00,69,00,\

  6e,00,64,00,6f,00,77,00,73,00,2e,00,73,00,74,00,6f,00,72,00,61,00,67,00,65,\

  00,2e,00,64,00,6c,00,6c,00,00,00

"ThreadingModel"="Apartment"

 

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

@=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\

  00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,77,00,69,00,\

  6e,00,64,00,6f,00,77,00,73,00,2e,00,73,00,74,00,6f,00,72,00,61,00,67,00,65,\

  00,2e,00,64,00,6c,00,6c,00,00,00

"ThreadingModel"="Apartment"

 

How about to get permissions to edit registry keys?

It stopped me on any of previous attempts.

 

Also, is it so difficult to make patch that will do that (with admin rights enabled) instead?

Link to comment
Share on other sites

  • Most Valued Members

Huge thanks to all contributors to resolve this issue.

 

Still, as average user I couldn't find way to force registry change (if this justify forum level criteria I admit that I am fairly stupid). 

Also, showing deeper level of ignorance I couldn't update Cleaner or CM (and have no idea how to do it) from 1110 to 1112. 

Furthermore, my version of SS 8.0.312.3, which seems not to ne the latest one and it doesn't update further.

 

Now, as I believe that few other users my suffer from same mental deficiency to resolve what is apparently simple, self-explanatory and straightforward solution, may I kindly beg someone to ENLIGHTEN us, intellectual inferiors, as reading through pages on forum just ends up with frustration.

 

Thank you for attention.

the latest version is 8.0.319 go to this link select the version of your OS and language and download it.

hxxp://www.eset.com/int/download//home/detail/family/5?installer=offline

(if you dont know what bit is your OS, the wrong downloaded file will give you an error during install so dont worry.)

 

To Eset team - please, will You let us now, when we can use normal update mode instead of prerelease one? When it's safe. And module 1112 stays still. Thanks ladies and gentlemen.

in a few weeks it will be ready and released to regular updates servers.

Link to comment
Share on other sites

I have the exact same problem.

 

Desktop icon positions are no more remembered after logoff (auto arrange is disabled). All icons shift to the left after logon.

It happened the first time after ESS had blocked a "potentially unwanted application" during a download attempt.

 

My system is Win10 Home 64 Bit - German version !!!

 

I have opened a trouble ticket with ESET support last Thursday but didn't get  any response as yet.

 

ESET team, please advise!  This is very frustrating!!!

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...