Icon Overlays not visible since recent Windows update

[Adequat]

Since a recent Windows update (I can't say which one, this is a few weeks old, I have now Windows 10, version 1709, build 16299.248)
icon overlays are not visible anymore. I have done some researches, and my registry settings are ok (I have not more than 10 icon overlay registered, while 15 are allowed). Apparently, this is not the fault of XYPlorer, as other 32 bit application also have the problem, while 64 bit applications don't have the problem.

Maybe unrelated (???) but I think my earlier Windows had a HKEY_LOCAL_MACHINE32 key while it is no longer present in the today version.
Hence this is whether a bug introduced in a recent Windows update, or this is about Microsoft reducing its support for 32 bit applications.

Do you have a solution around the problem for XYPlorer, or when do we get a XYPlorer 64 bit?

[jupe]

Try these settings:

Configuration | General | Refresh, Icons, History | Icons | Show icon overlays

Configuration | General | Refresh, Icons, History | Icons | Show shortcut overlays

And if still not working, read this topic viewtopic.php?f=2&t=17041&p=146358

[admin]

Maybe unrelated (???) but I think my earlier Windows had a HKEY_LOCAL_MACHINE32 key while it is no longer present in the today version.

HKEY_LOCAL_MACHINE32 is long deprecated. It's also missing from e.g. Win8.1. Instead Wow6432Node is where it's at.

[Adequat]

Thanks
viewtopic.php?f=2&t=17041&p=146358
but did not help.
Not a XYPlorer problem I am sure. Except that if XYPlorer was 64 bit, this would not happen

[admin]

Check out this:
https://www.xyplorer.com/faq-topic.php?id=iconoverlays

[Adequat]

After experimenting here and there, I finally could solve the problem executing the instructions found there:

"Solving setup errors by using the SubInACL tool to repair file and registry permissions"
https://blogs.msdn.microsoft.com/astebn ... rmissions/

This blog basically instructs to run a script (run a long time!). And after that, the problem is solved.

Note #1: running this script also had a couple of side-effects, such as resetting the default application (explorer, media player...)
Note #2: the blog is dated 2006... to solve a Windows 10 problem in 2018!

[admin]

Wow.

But in the comments on that page some more side effects are mentioned: like "After changing that my computer became very strange." ...

So use with care...