I have the same problem as well. Very annoying. Happened since two days ago. And win 10 just suddently don't remember my folder settings. When set it larger, then open a folder n go back, it goes to default again, don't remember larger setting. Setting order same same ... OMG.
Same here, instead I've been using the compatible version of eset smart security 8 the first time I installed windows 10 that would be august and works fine, but then 2 days ago I installed some cumulative updates and bang... the stupidest defect ever and don't be silly I tried uninstall the updates but there's one updates that windows don't let me to uninstall.
There's no way eset cause the problem, it's obviously windows stupid defect AGAIN, still though I need solution.
The only thing I can tell now it's that Eset is collecting data on the problem.
They replied to my Customer care ticket and I collected all the data by a program (Eset Log Collector).
And now ... we can only wait....
Thanks,
We had the grandchildren for the weekend so I gave them my attention.
Yes, oppps! and old age
- bad eyes, stiff fingers, difficult breathing and sometimes wandering thinking
I must have been reading another thread when I spoke of search. Please accept my apology.
Thank you for contacting ESET, but as long as you've already updated, that probably is not the cause. The issue was reported against an earlier ESET release, but please post their response.
It seems as though most people reporting the issue on this thread say that it started about the same time - a few days ago - it might well be one of the updates. It will take me another day to recover from the time spent with the young ones, then I'll take a look at the steps recorder that your posted - thanks.
Bill
No Lio it's not only related to the english version of windows 10/ess as i have both windows 10 and ESS 8 and i had the exact same issue.
I've tried to troubleshoot a little and experiment with registry changes but i was unable to fix the issue, i ended up doing a system restore to before i've installed ESS and everything got back to normal. I'll stay away from eset until the issue is fixed.
Oh and it's surely not an issue with windows 10 updates, as comparing my system before/after the system restore, there's no updates removed.
As i said on the eset forums it's probably some privileges that eset removes when a new potentially harmful file is found, as there are no more reads/writes in the bags registers.
I agree with you.
Unfortunately, I cannot restore because my system restore was turned off because of I use Paragon. But my image with Paragon was done at the first beginning of my Windows 10 setup and I was setting up my program when the problem occured.
The new image for system restore would be done after installing the essential software.
Hey Lio, since now i don't feel like to reproduce the issue again as i'm staying away from eset until the issue is fixed,I agree with you.
Unfortunately, I cannot restore because my system restore was turned off because of I use Paragon. But my image with Paragon was done at the first beginning of my Windows 10 setup and I was setting up my program when the problem occured.
The new image for system restore would be done after installing the essential software.
please try to reset registry administrator rights by following this guide:
Solving setup errors by using the SubInACL tool to repair file and registry permissions - Aaron Stebners WebLog - Site Home - MSDN Blogs
Let me know if it works
Just a quick update.
The Eset forum HERE with all the users and the Tenforums HERE, found a solution.
The problem was really generated by Eset and it can be fixed with a workaround.
Originally Posted by chimera8888
A FIX WAS FOUND ON THE ESET WEBSITE
I will provide the FIX here and walk you through it
FIX was found by AREZCO
In regedit go to those 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 then restart your PC and everything should work fine !!
You need to give yourself permission to edit the registry keys
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
Thanks Lio, this looks interesting, and is explored more fully here:
windows 7 - Cant find the BagMRU Size value, my folder settings are getting lost - Super User
where it seems in later versions of Windows "bagsize" doesn't exist as such, yet at least in Win 7, there was an attempt to read "bagmru size" (which sets a limit on the number of folders) from the registry- a seeming leftover.
If, in later versions of Windows, there is an assumed value hard coded (since it is not read from the registry) then some people could have these symptoms (desktop icons/explorer folder view settings not kept) on that score, and the solution suggested (add value to define it) might be relevant.
extract from that page:
"Analysis
Using Process Monitor on Windows 7 x64 I see the following when I restart explorer and randomly browse:
- Access under
HKCU\Software\Classes\Local Settings\Software\Microsoft\Windows\Shell\Bags
- Access under
HKCU\Software\Microsoft\Windows\Shell\Bags
- Access at
HKCU\Software\Classes\Local Settings\Software\Microsoft\Windows\Shell\BagMRU Size
(This does not exist on my computer, but it is requested)- Access under
HKCU\Software\Classes\Local Settings\Software\Microsoft\Windows\Shell\BagMRU- Access under
HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\Directory\OpenWithList\MRUList
(This does not exist on my computer, but it is requested)
Conclusion
So, our %WINDIR%\Explorer.exe only accesses the 64-bit keys for our Bags.
However, the Wow6432Node keys are accessed when you use %WINDIR%\SysWOW64\explorer.exe,
there might be some contexts where the 32-bit explorer is used so take caution. For example, when it is launched from a 32-bit context or maybe when you launch Windows Explorer from a File Dialog.
To clear the Bag information, it is indeed sufficient to recreate the Bags and BagMRU folders under:
- HKCU\Software\Classes\Local Settings\Software\Microsoft\Windows\Shell\
And although it is less used it might help to recreate the Bags folder under:
- HKCU\Software\Microsoft\Windows\Shell\
The value of BagMRU Size is requested, so it's not really good that the key is absent. It could result in undefined behavior but I'm taking a wild guess that it just uses the default instead in the code. To be sure and run less fast into the limit you could define the DWORD value with a large number in the following key:
- HKCU\Software\Classes\Local Settings\Software\Microsoft\Windows\Shell\BagMRU Size
The last key that is accessed is when you would open a MRUList with Explorer.exe, I don't think that this is ever needed as there is no such thing as opening a Most Recently Used List other than to showing that in something like the Start Menu. So it's not necessary to create that key.
Any suggestions to increase the cache size for view settings without completely resetting the entire explorer folder settings?I would say that you could solely create and increase the BagMRU Size setting under the assumption that your Bags settings aren't corrupt... I've answered the other question under your question."
Quote
