Directory Opus 11.15.5666 (x64) is installed and running. (Same issue with at least the prior DO version.)
I create a file or folder on the desktop; the correct icon for the object type is visible.
I move the file or folder to another folder opened in DO on drive C; the object is moved but shows no icon
I move the file or folder to another folder opened in Windows Explorer on drive C; the object is moved and shows the correct icon for the object type
I copy the file or folder to another folder opened in DO on drive C; the object is copied and shows the correct icon for the object type
I move or copy the file to the root or folder on any drive except C opened in DO; the object is either moved or copied and shows the correct icon for the object type
I create a file or folder in a folder on drive C (not the desktop); the correct icon for the object type is visible
5) I move or copy the file or folder to the root or folder on any drive opened in DO; The object is either moved or copied and shows the correct icon for the object type
6) I move the file or folder to the desktop and subsequently move the file or folder to any folder on drive C; the object is moved but no icon is visible
7) I move the file or folder to the desktop and subsequently copy the file or folder to any folder on drive C; the object is copied and shows the correct icon for the object type
Notes:
The above occurs routinely with PDF files (Adobe Acrobat Reader DC) and TXT files (Edit Plus 3, set as the default TXT editor), with folders and other, but not all, files. It does not occur with, for instance, Microsoft Word files.
I have rebuilt the icon cache but that has had no affect on this problem.
I've looked everywhere except, of course, the right place... help me find that "right place," please. Thank you in advance for your help.
Test 1: Folder created on the desktop, moved here
New Microsoft Document.docx: Created on the desktop, moved here
::: NOTE: "Usually," the icon shows when Word files are created on, then moved from, the desktop!!
New Microsoft Document-2.docx: Created on the desktop, copied here
New Text Document.txt: Created here
Test 2.txt: File created on the desktop, moved here
Test 3.pdf: File created on the desktop, moved here
Test 4.txt: File created on the desktop, copied here
Yes, very strange. Further:
Create a file on the desktop, then move it to C:\temp; no icon Move the file back to the desktop Copy the file to C:\Temp; icon appears Move the same file again from the desktop to C:\temp; the icon disappears
Ramblings:
I just moved a newly created file from the desktop to C:\temp. In "details" view, the icon is missing. I changed the view to "details + thumbnails" and then to "thumbnails." In every view, the icon is missing, i.e., blank. The problem may be with the resource from which the icon is recovered.
The issue seems to be caused by DO at the destination folder (and perhaps the resource where the icon is stored) rather than the origin folder. When a DO window opens the origin location and Windows Explorer has opened the destination folder, there is no problem.
I just learned this:
File created on the desktop then moved to C:\temp
In a DO window, the file exists at C:\temp without an icon
In a Windows Explorer window, the file has its expected icon.
Give the Clear Icon Cache tool a try as ktbcrash suggests. Failing that I would guess it's caused by a shell extension; you could try using ShellExView to disable all the shell icon extension handlers and see if that makes a difference.
Ran ClearIconCache_1002; no change.
Grabbed ShellExView and started looking at shell icon extension handlers.
Then ka-boom; I saw the problem. Working in the fog which surrounds me, through a crack in the clouds, I saw a bunch of DropBox entries and remembered that several years ago I had the same problem. I posted a message here and someone told me the DropBox handlers were probably the problem. I disabled them and viola! the problem was fixed. At that time I switched to Google Drive but for lack of use, deleted it. Recently I had to get some files to an associate in a hurry and grabbed DropBox. Incidentally, the old, previously disabled entries were still there. If only I had remembered all of this a few weeks ago.
Thanks for the help everyone! Really, thank you very much!!
One more thing: Note the faint "X" overlaid on the icons in the image below. That comes up when a object is:
[ul]created on the desktop and then moved to a folder on drive C, or;
created anywhere, moved to the desktop and then moved to a folder on drive C, but;
the object looses the faint "X" if it's moved off of C, and;
it stays lost until it gets back to the desktop.
[/ul]This is only a nit... but, if anyone knows the cause, I'd appreciate your sharing your knowledge with me. Thank you!
I'm experiencing the same or similar issue. However, mine is more specific to my OneDrive and SharePoint folders. The screenshots provided above are very much the same.
I will have a look around and attempt the "fix". However, I have a clean install and no other cloud based program other than Adobe and Microsoft. I would much rather wait on the developers responses before doing the bandaid since the issue is not persistent on Explorer only Dopus.
Jon, please see my exchange with HPDelaney, above. He has a very similar to my DropBox problem--which is solved--but does not have DropBox installed. = Ron
Jon, please see my exchange with HPDelaney, above. He has a very similar problem to my DropBox problem--which is solved--but does not have DropBox installed. = Ron
Okay. I've attempted using ShellExView and there are way too many components and I'm not really sure what I'm looking for. With that said, my attempt was to focus at the Type: Icon Overlay Handler. Disabling them one at a time and then all at once yield no effect in Windows Explorer, but varied within Dopus. Unless someone on your end can recommend something that is less time consuming, I'm not doing anything further and we can wait when others will start to report on the same issue.
The best approach is to disable all the Icon Overlay Handlers, reboot and then see if the issue is fixed in Opus. If not then obviously it's not the cause and we can investigate other ideas. If disabling them all does fix the issue then you need to progressively re-enable them to work out which one is causing it. You can take a binary approach to this - re-enable half, if that doesn't fix it re-enable half again and so on. Unfortunately there's not really any other way of finding out where the problem lies.
