Hi, since a few weeks, changes in DOpus stopped refreshing when a change is made. New files do not appear, file rename still show the old one, etc. I did check the FAQ about Changes to folders are not being detected but nothing apply to the current problem. The problem happen both on local drive and NAS drives, but it was all working properly some times ago. The latest update didn't help with this problem
I cannot really pinpoint when this started to happen. I tried logging(as suggested in the FAQ), but I do not see anything related to the folder I do changes in, so I tried the "change" tool, and it does report the renaming correctly
Notified with 138 bytes.
FILE_ACTION_RENAMED_OLD_NAME "D:\Users\kinwo\OneDrive\Pictures\20200518_151631.jpg"
FILE_ACTION_RENAMED_NEW_NAME "D:\Users\kinwo\OneDrive\Pictures\20200518_15163a1.jpg"
Notified with 28 bytes.
FILE_ACTION_MODIFIED "D:\Users\kinwo\OneDrive\Pictures"
Notified with 70 bytes.
FILE_ACTION_MODIFIED "D:\Users\kinwo\OneDrive\Pictures\20200518_15163a1.jpg"
The renaming reported above was actually made using DOpus, but the change wasn't reflected in DOpus itself.
Any ideas?
I am running on Windows 11 Pro 21H2 with Dopus 12.27
Do you see any changes for other folders in the log?
Does the problem only happen below the OneDrive folder?
Are you in D:\Users\kinwo\OneDrive\Pictures itself, or is it a special folder that points to it (like OneDrive at the top of the folder tree)? Try going to C:\ and then typing D:\Users\kinwo\OneDrive\Pictures into the path field and pushing return, to test what happens when in the real folder instead of a virtual folder, in case that's involved somehow.
Hi, for the example above I was in Libraries\Pictures, which translate to D:\Users\kinwo\OneDrive\Pictures for windows , so, yes, a special folder in Dopus.
Try going to C:\ and then typing D:\Users\kinwo\OneDrive\Pictures into the path field and pushing return
Ah, I think we are on the right path. Doing this, and doing a rename, it works fine every time indeed. So the problem seems to be when using a special folder?
I was seeing change in the log, yes, just nothing on the folder touched. I'll redo that step in the evening and post the logs here tomorrow morning. Thanks
Hmm, I went to redo the debug steps and here is what I did:
I went in Preferences - Miscellaneous - Advanced and turned "no_external_change_notify" and "shellchange_debug" to True (I know, I made an error on the first one, it's not the right setting to change, but I noticed that error later on, keep reading .)
I restarted Dopus like asked(that was my first cue I made a mistake since I remembered it never asked me that the first time I did the debug steps)
I then started DebugView++ but nothing was logged. That's when I saw my error, so I put back "no_external_change_notify" back to false, turned "notify"debug" to True , restarted Dopus completely and...
No more problem... I even see correctly the change/rename made in a library reported in DebugView++(it wasn't reporting those rename yesterday)
So, dunno, maybe changing the status of "no_external_change_notify" to True then False did something. In all case, I am happy that changes are seen once more!
Argh, the problem is back and the previous workaround doesn't work anymore. I have made a small video to show the problem. In the video, you can see I zip a small folder and the file doesn't appear in the lister unless I refresh manually by clicking on the folder name.
If that's the full debug output, you're still not seeing any change notifications at all in the output, which means either something is blocking dopus.exe from receiving all change notifications or the debugging isn't set up right.
I would try with the C:\ drive first, to keep things simple. Once you see some debug events for that, move on to the K:\ drive.
(The ShellChange disk rename events also seem strange, unless you were renaming your drives during the test?)
Hi, yes, I found the shellchange message weird since I didn'T rename any drives, but those are network drives, so probably unrelated(and they are working properly in dopus too, except for the refresh thing of course)
So, I redid the test on the C drive and I have the same result. I am zipping a file in c:\temp and Dopus does not show the resulting zip file unless I refresh. And there is nothing in the debugview either.
The changetest utility detect them correctly, and if I do the same operation in windows explorer, the file appear right away. So, only Dopus seems to be having the problem.
|0.000000|2022/05/03 13:11:26.951|0|DebugView++.exe|File Identification Header, DebugView++ Format Version 1|
|---|---|---|---|---|
|0.000000|2022/05/03 13:11:13.487|30220|dopus.exe|DesktopDock_ContextMenu::Initialize|
|0.000482|2022/05/03 13:11:13.487|30220|dopus.exe|DesktopDock_ContextMenu::Initialize Finished - DesktopObject, Ignoring (C:\temp)|
|0.000499|2022/05/03 13:11:13.487|30220|dopus.exe|DesktopDock_ContextMenu::Initialize Finished|
|0.000651|2022/05/03 13:11:13.488|30220|dopus.exe|DesktopDock_ContextMenu::QueryContextMenu|
|0.000691|2022/05/03 13:11:13.488|30220|dopus.exe|DesktopDock_ContextMenu::QueryContextMenu - Ignored|
|0.029430|2022/05/03 13:11:13.516|48088|ACDSeePicaView.exe|PIM: Loading am_cab.apl|
|0.030233|2022/05/03 13:11:13.517|48088|ACDSeePicaView.exe|PIM: Loading am_cab.apl|
|0.031240|2022/05/03 13:11:13.518|48088|ACDSeePicaView.exe|PIM: Loading AM_Encryption.apl|
|0.031784|2022/05/03 13:11:13.519|48088|ACDSeePicaView.exe|PIM: Loading AM_Encryption.apl|
|0.032471|2022/05/03 13:11:13.519|48088|ACDSeePicaView.exe|PIM: Loading AM_TGZ.apl|
|0.032999|2022/05/03 13:11:13.520|48088|ACDSeePicaView.exe|PIM: Loading AM_TGZ.apl|
|0.033680|2022/05/03 13:11:13.521|48088|ACDSeePicaView.exe|PIM: Loading AM_ZIP.apl|
|0.034205|2022/05/03 13:11:13.521|48088|ACDSeePicaView.exe|PIM: Loading AM_ZIP.apl|
|0.034912|2022/05/03 13:11:13.522|48088|ACDSeePicaView.exe|PIM: Loading ax_arj.apl|
|0.035377|2022/05/03 13:11:13.522|48088|ACDSeePicaView.exe|PIM: Loading ax_arj.apl|
|0.035993|2022/05/03 13:11:13.523|48088|ACDSeePicaView.exe|PIM: Loading AX_RAR.apl|
|0.036472|2022/05/03 13:11:13.523|48088|ACDSeePicaView.exe|PIM: Loading AX_RAR.apl|
|0.037107|2022/05/03 13:11:13.524|48088|ACDSeePicaView.exe|PIM: Loading CX_Archive.apl|
|0.041519|2022/05/03 13:11:13.528|48088|ACDSeePicaView.exe|PIM: Loading CX_Archive.apl|
|0.045172|2022/05/03 13:11:13.532|48088|ACDSeePicaView.exe|PIM: Loading CX_Email.apl|
|0.047288|2022/05/03 13:11:13.534|48088|ACDSeePicaView.exe|PIM: LoadLibrary failed on CX_Email.apl|
|0.047288|2022/05/03 13:11:13.534|48088|ACDSeePicaView.exe| : The specified module could not be found.|
|0.047318|2022/05/03 13:11:13.534|48088|ACDSeePicaView.exe|PIM: Loading CX_Email.apl|
|0.049086|2022/05/03 13:11:13.536|48088|ACDSeePicaView.exe|PIM: LoadLibrary failed on CX_Email.apl|
|0.049086|2022/05/03 13:11:13.536|48088|ACDSeePicaView.exe| : The specified module could not be found.|
|0.049289|2022/05/03 13:11:13.536|48088|ACDSeePicaView.exe|PIM: Loading CX_Flickr.apl|
|0.051616|2022/05/03 13:11:13.539|48088|ACDSeePicaView.exe|PIM: LoadLibrary failed on CX_Flickr.apl|
|0.051616|2022/05/03 13:11:13.539|48088|ACDSeePicaView.exe| : The specified module could not be found.|
|0.051646|2022/05/03 13:11:13.539|48088|ACDSeePicaView.exe|PIM: Loading CX_Flickr.apl|
|0.053874|2022/05/03 13:11:13.541|48088|ACDSeePicaView.exe|PIM: LoadLibrary failed on CX_Flickr.apl|
|0.053874|2022/05/03 13:11:13.541|48088|ACDSeePicaView.exe| : The specified module could not be found.|
|0.054077|2022/05/03 13:11:13.541|48088|ACDSeePicaView.exe|PIM: Loading CX_Ftpuploader.apl|
|0.057897|2022/05/03 13:11:13.545|48088|ACDSeePicaView.exe|PIM: Loading CX_Ftpuploader.apl|
|0.061615|2022/05/03 13:11:13.549|48088|ACDSeePicaView.exe|PIM: Loading CX_SmugMug.apl|
|0.064184|2022/05/03 13:11:13.551|48088|ACDSeePicaView.exe|PIM: LoadLibrary failed on CX_SmugMug.apl|
|0.064184|2022/05/03 13:11:13.551|48088|ACDSeePicaView.exe| : The specified module could not be found.|
|0.064215|2022/05/03 13:11:13.551|48088|ACDSeePicaView.exe|PIM: Loading CX_SmugMug.apl|
|0.066141|2022/05/03 13:11:13.553|48088|ACDSeePicaView.exe|PIM: LoadLibrary failed on CX_SmugMug.apl|
|0.066141|2022/05/03 13:11:13.553|48088|ACDSeePicaView.exe| : The specified module could not be found.|
|0.066344|2022/05/03 13:11:13.553|48088|ACDSeePicaView.exe|PIM: Loading CX_Zenfolio.apl|
|0.067915|2022/05/03 13:11:13.555|48088|ACDSeePicaView.exe|PIM: LoadLibrary failed on CX_Zenfolio.apl|
|0.067915|2022/05/03 13:11:13.555|48088|ACDSeePicaView.exe| : The specified module could not be found.|
|0.067947|2022/05/03 13:11:13.555|48088|ACDSeePicaView.exe|PIM: Loading CX_Zenfolio.apl|
|0.069587|2022/05/03 13:11:13.557|48088|ACDSeePicaView.exe|PIM: LoadLibrary failed on CX_Zenfolio.apl|
|0.069587|2022/05/03 13:11:13.557|48088|ACDSeePicaView.exe| : The specified module could not be found.|
|0.069792|2022/05/03 13:11:13.557|48088|ACDSeePicaView.exe|PIM: Loading ID_AFPH.apl|
|0.070360|2022/05/03 13:11:13.557|48088|ACDSeePicaView.exe|PIM: Loading ID_AFPH.apl|
|0.070399|2022/05/03 13:11:13.557|48088|ACDSeePicaView.exe|PIM: Unloading ID_AFPH.apl|
|0.070634|2022/05/03 13:11:13.558|48088|ACDSeePicaView.exe|PIM: Loading ID_APD.apl|
|0.074460|2022/05/03 13:11:13.561|48088|ACDSeePicaView.exe|PIM: Loading ID_APD.apl|
|0.074497|2022/05/03 13:11:13.561|48088|ACDSeePicaView.exe|PIM: Unloading ID_APD.apl|
|0.075036|2022/05/03 13:11:13.562|48088|ACDSeePicaView.exe|PIM: Loading ID_Brush.apl|
|0.079898|2022/05/03 13:11:13.567|48088|ACDSeePicaView.exe|PIM: Loading ID_Brush.apl|
|0.079935|2022/05/03 13:11:13.567|48088|ACDSeePicaView.exe|PIM: Unloading ID_Brush.apl|
|0.080709|2022/05/03 13:11:13.568|48088|ACDSeePicaView.exe|PIM: Loading ID_Canvas.apl|
|0.081320|2022/05/03 13:11:13.568|48088|ACDSeePicaView.exe|PIM: Loading ID_Canvas.apl|
|0.081358|2022/05/03 13:11:13.568|48088|ACDSeePicaView.exe|PIM: Unloading ID_Canvas.apl|
|0.081611|2022/05/03 13:11:13.569|48088|ACDSeePicaView.exe|PIM: Loading ID_DCRaw.apl|
|0.085923|2022/05/03 13:11:13.573|48088|ACDSeePicaView.exe|PIM: Loading|
|0.085947|2022/05/03 13:11:13.573|48088|ACDSeePicaView.exe|PIM: LoadLibrary failed on|
|0.085947|2022/05/03 13:11:13.573|48088|ACDSeePicaView.exe| : The parameter is incorrect.|
|0.086012|2022/05/03 13:11:13.573|48088|ACDSeePicaView.exe|Plug-in certificate could not be loaded:|
|0.086383|2022/05/03 13:11:13.573|48088|ACDSeePicaView.exe|PIM: Loading ID_DCRaw.apl|
|0.086430|2022/05/03 13:11:13.573|48088|ACDSeePicaView.exe|PIM: Unloading ID_DCRaw.apl|
|0.086446|2022/05/03 13:11:13.573|48088|ACDSeePicaView.exe|PIM: Unloading ID_DCRaw.apl|
|0.087112|2022/05/03 13:11:13.574|48088|ACDSeePicaView.exe|PIM: Loading ID_DjVu.apl|
|0.087793|2022/05/03 13:11:13.575|48088|ACDSeePicaView.exe|PIM: Loading ID_DjVu.apl|
|0.087835|2022/05/03 13:11:13.575|48088|ACDSeePicaView.exe|PIM: Unloading ID_DjVu.apl|
|0.088084|2022/05/03 13:11:13.575|48088|ACDSeePicaView.exe|PIM: Loading ID_Font.apl|
|0.088634|2022/05/03 13:11:13.576|48088|ACDSeePicaView.exe|PIM: Loading ID_Font.apl|
|0.088673|2022/05/03 13:11:13.576|48088|ACDSeePicaView.exe|PIM: Unloading ID_Font.apl|
|0.088904|2022/05/03 13:11:13.576|48088|ACDSeePicaView.exe|PIM: Loading ID_GoPro.apl|
|0.092118|2022/05/03 13:11:13.579|48088|ACDSeePicaView.exe|PIM: Loading ID_GoPro.apl|
|0.092155|2022/05/03 13:11:13.579|48088|ACDSeePicaView.exe|PIM: Unloading ID_GoPro.apl|
|0.092171|2022/05/03 13:11:13.579|48088|ACDSeePicaView.exe|PIM: Unloading ID_GoPro.apl|
|0.092683|2022/05/03 13:11:13.580|48088|ACDSeePicaView.exe|PIM: Loading ID_HEIC.apl|
|0.096651|2022/05/03 13:11:13.584|48088|ACDSeePicaView.exe|PIM: Loading ID_HEIC.apl|
|0.096688|2022/05/03 13:11:13.584|48088|ACDSeePicaView.exe|PIM: Unloading ID_HEIC.apl|
|0.097246|2022/05/03 13:11:13.584|48088|ACDSeePicaView.exe|PIM: Loading ID_ICN.apl|
|0.097857|2022/05/03 13:11:13.585|48088|ACDSeePicaView.exe|PIM: Loading ID_ICN.apl|
|0.097893|2022/05/03 13:11:13.585|48088|ACDSeePicaView.exe|PIM: Unloading ID_ICN.apl|
|0.098140|2022/05/03 13:11:13.585|48088|ACDSeePicaView.exe|PIM: Loading ID_ICO.apl|
|0.103224|2022/05/03 13:11:13.590|48088|ACDSeePicaView.exe|PIM: Loading|
|0.103248|2022/05/03 13:11:13.590|48088|ACDSeePicaView.exe|PIM: LoadLibrary failed on|
|0.103248|2022/05/03 13:11:13.590|48088|ACDSeePicaView.exe| : The parameter is incorrect.|
|0.103317|2022/05/03 13:11:13.590|48088|ACDSeePicaView.exe|Plug-in certificate could not be loaded:|
|0.103380|2022/05/03 13:11:13.590|48088|ACDSeePicaView.exe|PIM: Loading ID_ICO.apl|
|0.103416|2022/05/03 13:11:13.590|48088|ACDSeePicaView.exe|PIM: Unloading ID_ICO.apl|
|0.104868|2022/05/03 13:11:13.592|48088|ACDSeePicaView.exe|PIM: Loading ID_Media2.apl|
|0.114671|2022/05/03 13:11:13.602|48088|ACDSeePicaView.exe|PIM: Loading ID_Media2.apl|
|0.115150|2022/05/03 13:11:13.602|48088|ACDSeePicaView.exe|PIM: Unloading ID_Media2.apl|
|0.116078|2022/05/03 13:11:13.603|48088|ACDSeePicaView.exe|PIM: Loading ID_PICT.apl|
|0.116702|2022/05/03 13:11:13.604|48088|ACDSeePicaView.exe|PIM: Loading ID_PICT.apl|
|0.116740|2022/05/03 13:11:13.604|48088|ACDSeePicaView.exe|PIM: Unloading ID_PICT.apl|
|0.116990|2022/05/03 13:11:13.604|48088|ACDSeePicaView.exe|PIM: Loading ID_PSP.apl|
|0.117539|2022/05/03 13:11:13.605|48088|ACDSeePicaView.exe|PIM: Loading ID_PSP.apl|
|0.117597|2022/05/03 13:11:13.605|48088|ACDSeePicaView.exe|PIM: Unloading ID_PSP.apl|
|0.117832|2022/05/03 13:11:13.605|48088|ACDSeePicaView.exe|PIM: Loading IDE_ACDStd.apl|
|0.121742|2022/05/03 13:11:13.609|48088|ACDSeePicaView.exe|PIM: Loading IDE_ACDStd.apl|
|0.121789|2022/05/03 13:11:13.609|48088|ACDSeePicaView.exe|PIM: Unloading IDE_ACDStd.apl|
|0.121806|2022/05/03 13:11:13.609|48088|ACDSeePicaView.exe|PIM: Unloading IDE_ACDStd.apl|
|0.122344|2022/05/03 13:11:13.609|48088|ACDSeePicaView.exe|PIM: Loading IDE_JP2.apl|
|0.123346|2022/05/03 13:11:13.610|48088|ACDSeePicaView.exe|PIM: Loading IDE_JP2.apl|
|0.123389|2022/05/03 13:11:13.610|48088|ACDSeePicaView.exe|PIM: Unloading IDE_JP2.apl|
|0.123406|2022/05/03 13:11:13.610|48088|ACDSeePicaView.exe|PIM: Unloading IDE_JP2.apl|
|0.123671|2022/05/03 13:11:13.611|48088|ACDSeePicaView.exe|PIM: Loading IDE_PSD.apl|
|0.124646|2022/05/03 13:11:13.612|48088|ACDSeePicaView.exe|PIM: Loading IDE_PSD.apl|
|0.124962|2022/05/03 13:11:13.612|48088|ACDSeePicaView.exe|PIM: Unloading IDE_PSD.apl|
|0.124980|2022/05/03 13:11:13.612|48088|ACDSeePicaView.exe|PIM: Unloading IDE_PSD.apl|
|0.125331|2022/05/03 13:11:13.612|48088|ACDSeePicaView.exe|PIM: Loading IDE_WEBP.apl|
|0.125872|2022/05/03 13:11:13.613|48088|ACDSeePicaView.exe|PIM: Loading IDE_WEBP.apl|
|0.125914|2022/05/03 13:11:13.613|48088|ACDSeePicaView.exe|PIM: Unloading IDE_WEBP.apl|
|0.125930|2022/05/03 13:11:13.613|48088|ACDSeePicaView.exe|PIM: Unloading IDE_WEBP.apl|
|0.126157|2022/05/03 13:11:13.613|48088|ACDSeePicaView.exe|PIM: Loading IE_DNG.apl|
|0.127327|2022/05/03 13:11:13.614|48088|ACDSeePicaView.exe|PIM: Loading IE_DNG.apl|
|0.128644|2022/05/03 13:11:13.616|48088|ACDSeePicaView.exe|PIM: Unloading IE_DNG.apl|
|1.146802|2022/05/03 13:11:14.634|48088|ACDSeePicaView.exe|<process started at 13:11:13.499 has terminated with exit code 0>|
If notify_debug = True when making that then something's broken at a lower level than Opus.
It would usually be something like antivirus if the entire change notification mechanism is broken for the whole process, but it could also be something that's being loaded into the process and is patching APIs (or similar) within the process.
Hi, I have uninstalled the antivirus(bitdefender) and rebooted. Still same result. Is there any other kind of software that can cause a conflict like this?
sigh It was set to "True" , setting it to false solved it. But I don't get why it was set to true, I haven't touched those options at all, beside for the debugging yesterday and today.