Windows 10: Desktop rearrange / registry change

Hello, I've got a problem with desktop. After reboot/restart or even refresh desktop all icons are moved to left side of screen.


I found this solution:


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


It worked fine but when I restart pc it happens again AND registry is as it was before (so "shell32.dll" instead of "windows.storage.dll").


So my question is - why changes in registry are undone after reboot?
I did it in safe mode. I have unchecked "autoarrange". I don't have any malware or virus. I'm running Win10 x64 (upgrade from 8.1). It's happening on Guest profile too.


Thank you for answers.

P.S.: I read thread about this but I made new because I have almost solved desktop part but there is a problem with saving change in registry

:)

 

Desktop Icons Keep Rearranging after screen resolution change

This seems to be a problem many people have.

I run windows 10, and everytime i plug HDMI cable into TV, changing the screen resolution, it resets my desktop configuration.

My desktop is not on auto align. Desktop theme is not allowed to make changes to icon layout

This is a problem multiple users seem to have.

Desktop icons keep rearranging - Page 11 - Windows 10 Forums with no solution other than registry edits.

There must be a better way to deal with this.

Can somebody please help ?

 

Desktop rearranged every update or Windows 10

Another round of rearranged desktop this morning. Anytime the update hangs up overnight the desktop is rearranged as I think the system resets itself instead of leaving the desktop build alone.

I really didn't think Microsoft could be this bad as to leave this blatant error so long with no correction. Either put some seasoned programmers on the problem or time for a change of project managers.