Corrupted IconCache?

collector wrote on 2020-08-04, 20:56:

Corrupted IconCache?

I tried deleting the cache and letting the system rebuild it, but that didn't fix it.

I posted a question on the windows help site. I think this issue may be related to the new version update of windows 10 that I installed last week. It was then that the issue with DOSBox started.

I noticed that STEAM and GOG both include DOSBox in their game installations for the Wolfenstein 3D and Spear of Destiny games, but neither one is version 0.74-3. In the case of STEAM, it is version 0.74-2, and in the case of GOG it is version 0.74-0. In both cases the DOSBox executable shows the DOSBox icon in the Properties window, so I uninstalled 0.74-3 and ran the installer again. Again, the executable did not display the DOSBox icon in the Properties window, but did display the generic document icon. I have a feeling it is the way it is being installed that is the problem. I am going to try re-downloading the installer and reinstalling DOSBox again to see if anything changes.

I uninstalled 0.74-3 and reinstalled it using a fresh copy of the installer I just downloaded. The same thing happens. The application does not display the correct icon in the Properties window, even though it does display the correct icon in the explorer window, and the desktop shortcut displays the correct icon on the desktop, but shows the generic document icon in the Properties window. Running any game that uses DOSBox shows the generic document icon in the taskbar instead of the DOSBox icon. I can't say that it's definitely the installer, because I don't know that, but I can't see it being my system with two other versions of DOSBox in existence on my drive and they display the correct icon both in the Properties window and on the taskbar. In case someone asks, 0.74-3 was on my hard drive long before I installed STEAM or GOG GALAXY.

Did you reinstall 0.74-3 in the same path as before?
Maybe something on your system is broken in that specific path.

I'll have to look at that. The installer puts it in Program Files (x86), and I wasn't aware you could change the installation path.

Well, I'll be switched! That fixed it. There's something about the folder name DOSBox-0.74-3 that breaks it. I installed it again to DOSBox-0.74-3a in the Program Files (x86) folder and it fixed it. I uninstalled the DOSBox-0.74-3 copy and renamed DOSBox-0.74-3a to DOSBox-0.74-3 and it was broken again. Changing it back to DOSBox-0.74-3a fixed it again. so, I can't explain it, but apparently the DOSBox-0.74-3 folder name on my computer has an issue in Windows 10 64-bit. Thanks for the suggestion. I would have never thought of it.