Windows 10: Folder View Settings and Desktop Icon Positions Not Saving

Gunner Youri said:

Hi all, I'm experiencing similar problems as you guys. Only, here it's just the order of the desktop icons resetting after every reboot. And also, they even moved back when I was using the computer a couple of times. I have deleted ESET, didn't help. I have changed those registry things, that didn't work either. Is it possible that I'm having a different problem than you guys?

Hi, if you have eliminated ESET Nod32 and the registry settings, but still have a problem with desktop icon rearrangement, (but not folder view settings as I understand it) it is possible you have a separate cause. Many people have reported this through several versions of Windows.

For example, this is what one person found: (reported for an earlier version of Windows but should be applicable)
Desktop icons that rearrange themselves on reboot or a refresh or when a program starts seems quite common.

The usual workaround is to use microsoft's layout.exe or a third party program (eg Iconoid) to save and restore icon positions but this is not a solution.

After much time I tracked the problem down to a registry with corrupted 'permissions':
HKEY_CURRENT_USER\Software\Microsoft\Windows\Shell\Bags\1\Desktop
I could not get into Bags\1 - 'Error on opening' message but I could get into permissions which I reset including the 'owner' tab.
I imported a copy of another computers bags\1 settings although it had no similarity regarding icon settings. Made sure the icons were how I wanted them positioned and rebooted. Problem solved.

Searching for
"desktop icons rearranging" yields many results. Perhaps one might point you in the right direction.

dalchina said:

After much time I tracked the problem down to a registry with corrupted 'permissions':
HKEY_CURRENT_USER\Software\Microsoft\Windows\Shell\Bags\1\Desktop
I could not get into Bags\1 - 'Error on opening' message but I could get into permissions which I reset including the 'owner' tab.
I imported a copy of another computers bags\1 settings although it had no similarity regarding icon settings. Made sure the icons were how I wanted them positioned and rebooted. Problem solved.

Hi, thank you for your reply! I find this bit interesting but I can't understand it perfectly what he did.
What exactly did he reset and how do you import that "Bags\1" settings?

Gunner Youri said:

Hi, thank you for your reply! I find this bit interesting but I can't understand it perfectly what he did.
What exactly did he reset and how do you import that "Bags\1" settings?

Clearly that user had access to another PC and seems to have copied the key and applied the same permissions settings.

Searching for the string
HKEY_CURRENT_USER\Software\Microsoft\Windows\Shell\Bags\1\Desktop
yields lots of interesting comment on this whole matter..
Where does Windows store icon positions? - Super User
https://support.microsoft.com/en-us/kb/813711
for example.

It's an issue many have grappled with, and registry permissions seems to be an aspect to explore.

vkaraoke said:

Hi everyone,

I seem to be having 2 issues with Windows 10 Pro x64 that occur simultaneously. The 2 issues are that my desktop icon positions are not being remembered (always shifting to the left after reboot - auto align is off) and my folder view settings are not being saved (change folder preference to thumbnail view -> close window -> reopen same folder but always displays list mode).

The things I have tried so far is:
- Rebooting into safe mode and typing in sfc /scannow in the command prompt (did not fix)
- Rebuilding my Windows 10 icon cache using the .bat file and methods found here (did not fix)

It seems the only way to fix these issues to to format and perform a clean install of Windows or recovering from a previously working cloned Windows 10. However, regardless of the approach, after a few days the 2 issues will emerge simultaneously after some point.

I was wondering if anyone else was/is experiencing these issues or if there are any fixes I could try? Thanks.



Edit: 9/22/2015

It seems to be reported by a majority of folks here in the forums that there is a strong correlation between Windows 10 (any version) and ESET (antivirus or security suite - doesn't matter which version). Essentially, if/when ESET detects a virus and proceeds to remove or quarantine the virus, the result afterwards is that ESET does something to the windows registry that *borks* the registry and thus will result in the 2 issues being discussed.

Several members have attempted various approaches to fix the problem to no avail. It has been suggested that the only way to permanently fix the problem is to completely reformat Windows 10 (clean install) and use a different antivirus program (do not install ESET after the clean installation).
*It is important to note that uninstalling ESET AFTER experiencing these issues will not fix the problem as the damage is already done*

In addition, a thread has been created in the official ESET forums which brings up the 2 issues can be found here:
https://forum.eset.com/topic/6033-wi...-is-installed/

I'll update the OP when new development arises.



Edit: 9/27/2015 [Manual Fix] [For Auto Fix Scroll Further Down]

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.

If you are receiving a message saying that you do not have permission to modify your registry keys then follow the steps in the section below. After giving yourself permission to modify the registry keys proceed to modify the registry keys in the two locations stated above. When both of the registry keys have been changed restart your computer and see if the issues have been resolved.

On another note, for people who feel uncomfortable or don't know know to modify their registry files, you can download and install these files which were created by forum resident chimera8888 which will automatically apply the registry fixes stated above. However, you will still need to give yourself permission to edit the registry keys (see section below).



How To Give Yourself Permission To Edit The Registry Keys

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



**For people who feel uncomfortable or don't know know to modify their registry files, you can download and install these files which were created by forum resident chimera8888 which will automatically apply the registry fixes stated above. However, you will still need to give yourself permission to edit the registry keys (see paragraph above).**





Edit: 9/27/2015 [Auto Fix]

Forum user Zash has provided an auto fix which can now be used. You must reboot into safe mode first and then proceed to run the applicable version depending on which version of Windows 10 you are using (32 bit or 64 bit). If you are unsure how to boot into safe mode then visit http://www.7tutorials.com/4-ways-boo...ode-windows-10

This for me is not working. I tried both options and the next day we returned to its original state - all the icons on the left side. When I go into regedit and see what is in both the key and see that sitting back to back situation, which is the extension * Shell32.dll. As shown ESET constantly checks the keys. I do not know what bidalo still do.

Seriously people, it's not necessary to quote the whole post when it's long like the one above

From the moderator on the Eset forum

We've found out that the issue continues to occur with Cleaner module 1113 if an ESET product not supporting Windows 10 is installed. With the latest version installed, it shouldn't occur. We've made one more fix to prevent the issue from occurring even if an older version of an ESET product is installed. A Cleaner module with this fix (1114) is now available on pre-release update servers.
Is there anybody with a Windows 10 compatible version installed (the latest one available on the web) who is experiencing the issue despite having Cleaner module 1113 installed?

You can find all the discussion HERE

Lio said:

From the moderator on the Eset forum
You can find all the discussion HERE

hi
thanks Lio
does somebody tried the new module 1114 with for example eicar malware test file ?

Tested with



Detected, cleaned, quarantined, deleted. Rebooted twice, everythings OK.

I registered just to say thank you guys for all of this. I was banging my head against this issue for months revisiting it with no luck.

I had no idea it was tied to ESET, but lo and behold it was the issue. I had previously tried numerous "fixes" regarding {42aedc87-2188-41fd-b9a3-0c966feabec1} -- many of which asked to delete it.

I got my desktop back and I'm as happy as a clam. Thanks again!