Windows 10: Windows 10 not saving my folder view options.

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 !!




Originally Posted by chimera8888


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."

 

FOLLOW THIS LINK :

https://support.microsoft.com/en-us/kb/929135

Full Answer HERE : ( In Arabic) :



WORKED FOR ME !!!!!!!!