Some icons are not displayed

[terrytw]

Hi I have found that some icons in the start menu folders do not show up (they show up in the start menu, just not in the folder when opened in XYplorer), please see attached picture.

Also just to make sure it is not the system's problem, I installed a brand new Windows 10 LTSC 2021 in virtualbox, and installed a brand new XYplorer from the latest official release. No settings were changed.

These are shortcuts, and their original exe files do not display icon either. Some of the executable have correct icon like mstsc (remote desktop), while others like snipping tool does not.

[jupe]

viewtopic.php?p=140258#p140258

[terrytw]

viewtopic.php?p=140258#p140258

Thanks for the help. It is not related to that thread you mentioned, since it is not a "Program File(x86)" and "Programs Files" issue, the shortcuts are pointed towards windows/system32 folder.

[jupe]

It's the same issue, just different path, you need to change those to %WINDIR%\Sysnative or similar to see them in XY

[terrytw]

It's the same issue, just different path, you need to change those to %WINDIR%\Sysnative or similar to see them in XY

Sorry this is really not a path related issue, because the original executable is not displaying icon either. Please see updated screenshot in the original post.

And, if it is a path related issue, why does mstsc (remote desktop) shows icon while snipping tool does not? They are both in the same path.

[jupe]

I am not sure if the dev can create some sort of special voodoo behind the scenes and add workarounds to mitigate the icon issue, he'll reply to that, but I'll try and quickly explain what you are seeing since you asked. The icons show for some files, because they exist in a 32bit version too, you can run a quick check by looking at the the contents of the 32bit System32 directory after disabling this:

Configuration | Other | Shell Integration | 64-bit Windows | Show the real System32 directory

and check the bitness (Shift+Enter) of the mstsc.exe file with that setting enabled and disabled (also take notice of the Path: field), the other files without icons are sort of redirection links between bitness's, that don't exist in both locations, you can read up on WOW64 here if you want to know more.

https://www.itechguides.com/syswow64-fi ... explained/

[terrytw]

I am not sure if the dev can create some sort of special voodoo behind the scenes and add workarounds to mitigate the icon issue, he'll reply to that, but I'll try and quickly explain what you are seeing since you asked. The icons show for some files, because they exist in a 32bit version too, you can run a quick check by looking at the the contents of the 32bit System32 directory after disabling this:

Configuration | Other | Shell Integration | 64-bit Windows | Show the real System32 directory

and check the bitness (Shift+Enter) of the mstsc.exe file with that setting enabled and disabled (also take notice of the Path: field), the other files without icons are sort of redirection links between bitness's, that don't exist in both locations, you can read up on WOW64 here if you want to know more.

https://www.itechguides.com/syswow64-fi ... explained/

Thanks for the patience, I think you are right, this is a 32-bit problem.

The dev has done a lot of mitigation (voodoo as you called it lol) that some of the symptoms like unable to run executable from shortcut do not exist anymore. Now it feels like simply a cosmetic problem. I still have not found any way to make the icon appear, (tried editing path in property to no avail) but at least I can sleep well knowing it won't affect anything else.

Thanks again!