Windows explorer won't remember folder and icon settings?

Here is my problem:
I keep my folders in different settings, some with large icons, some with details view.

Today they are all reset to details view,
and items are listed by name. Every folder is reset to the same settings.
when I try to change they always defaults to details view.
Even when I go to another folder and press back, the settings are already reset.

Also, icons on desktop are keep returning to default state (big icons),
I keep them smaller, when I hold ctrl and scroll mouse wheel they become smaller, but next time I reset windows they return to default (big icons) view. I already cleaned shellbag in regedit, reset windows but it is still the same.

I saw this other theme with similar problem, but I am not using Eset, I use Kaspersky.
Also I don't have this key in my registry :
HKEY_CURRENT_USER\Software\Microsoft\Windows\Shell\Bags\1\Desktop

Any solution?

Hello, two threads above yours - please read thru this very long thread on this topic.
Solved Windows 10: Folder View Settings and Desktop Icon Positions Not Saving - Windows 10 Forums

This is not a Win 10 exclusive issue, and has been reported over several versions of Windows- there may be more than one cause. This thread has a lot of discussion about ESET and two particular registry locations with a fix.

Hello, I've just realised I missed your point on ESET, some have reported registry permissions problems too. I think I posted a couple of other things in that thread, so read thru carefully for any other clues.

Especially as you don't have that key, you could consider copying it from another working PC if available, with appropriate backup.
it's basically worth searching

I think you're looking for sthg similar to this:
https://support.microsoft.com/en-us/kb/813711
- it doesn't specifically cover Win 10 of course, but appears to address your issue.

Provided you back up carefully you could try what it suggests, although I believe I remember that the entry specifying the limit was removed in Win 7, although Windows still tried to read it... (someone checked using Process Monitor).