Changes to files and folders are not being detected

Help & Support
1

DOPUS V11.19 x64 on Windows 10

Problem: Changes, file renames, copy file, delete file etc in any file window (Lister) are not immediately displayed. I have to refresh the Lister (F5 or press refresh icon) to view changes.

The same happens for all disks, local, network and removable.

Directory / Folder name change in the folder tree works and are shown immediately

Add or delete folder any where requires a refresh to be visible in DOPUS.

Windows File Explorer recognises ALL changes immediately with going to the dialog window or refresh.

A change made in File Explorer requires a refresh in DOPUS to see the change.

I have followed the instructions in 2006 post headed “Changes to folders are not being detected” .

When I Set Troubleshooting / notify_debug to True and shellchange_debug to True the debugview generates over 2000 lines per second. Mostly this;

[9548] dopus: Notify 00000238F6DE32D0 Returned 32 bytes, error 0

[9548] dopus: Notify 00000238F6DE32D0 Returned 288 bytes, error 0

[9548] dopus: Notify 00000238F6DE32D0 Returned 64 bytes, error 0

[9548] dopus: Notify 00000238F6DE32D0 Returned 128 bytes, error 0

[9548] dopus: Notify 00000238F6DE32D0 Returned 64 bytes, error 0

[9548] dopus: Notify 00000238F6DE32D0 Returned 128 bytes, error 0

[9548] dopus: Notify 00000238F6DE32D0 Returned 64 bytes, error 0

[9548] dopus: Notify 00000238F6DE32D0 Returned 128 bytes, error 0

[9548] dopus: Notify 00000238F6DE32D0 Returned 64 bytes, error 0

[9548] dopus: Notify 00000238F6DE32D0 Returned 128 bytes, error 0

[9548] dopus: Notify 00000238F6DE32D0 Returned 64 bytes, error 0

[9548] dopus: Notify 00000238F6DE32D0 Returned 128 bytes, error 0

[9548] dopus: Notify 00000238F6DE32D0 Returned 64 bytes, error 0

[9548] dopus: Notify 00000238F6DE32D0 Returned 128 bytes, error 0

[9548] dopus: Notify 00000238F6DE32D0 Returned 64 bytes, error 0

[9548] dopus: Notify 00000238F6DE32D0 Returned 128 bytes, error 0

[9548] dopus: Notify 00000238F6DE32D0 Returned 64 bytes, error 0

[9548] dopus: Notify 00000238F6DE32D0 Returned 128 bytes, error 0.

I would appreciate some help please. I have looked at a few similar posts but there is no solution posted.

I have applied all Windows updates and completely uninstalled and reinstalled DOPUS. SFC and DISM are all OK.

Thanks,
Ian

1 Like
2

As a quick test, can you try closing the folder tree and see if that makes a difference? That should change Opus from watching for changes everywhere in the system to only looking for them in the current folder.

3

Closed, relaunched fresh instance. Closed Folder Tree.

No difference.

5

I think we need to work out what's generating so many changes on your system, as 2000+ per second would certainly overwhelm Opus's ability to keep the folder displays up to date.

If you create a Process Monitor log following those instructions and send it to us we might be able to see what's happening. You probably don't need to record for more than a few seconds if there really are that many changes happening.

6

Logfile.zip (5.6 MB)

Here is a small log. thanks,

7

The only thing that stands out to me in the log is that something is causing Opus to keep accessing a network drive related to Wordpress.

Newer versions of Opus will output more information (and also have 8 years of improvements to how change notification and other things work in general), so they might be worth a try.

8

I have a tab that monitors my Website (wordpress) uploads. It's a small text file and a few jpgs once a minute from a Weather Station.

I have tried closing all tabs bar one but that makes no difference. I have been considering updating - may be a will trial the latest version to see if it works.

The double-click on the desktop has also stopped working now. The helper app is in the start up group and I've manually started it but it wont run. When I go to the Licence Manager to get the Reg Code I get an error "Registration of the UAC=helper component failed. Administrator access is not availble" - is this related?

9

I don't want to install v13 and discover it doesn't solve my issue so I tried to register for a trial - but I was declined. Can you advise please.

10

That suggests something is wrong, at least. Re-running the installer may fix it.

You can install it without a trial cert; the trial cert just lets you test it for longer. It should let you get one unless you already have one for version 13. Was there an error message or any other details about why it was declined?

11

Is this a problem that's just started occurring or have you always had it with this version?

12

It has just started this week. It has worked faultlessly for many years. Terrific piece of software, till now.

There is nothing that I know off that could have triggered it. I tried to even do a few system restores but it didn't make any difference.

I would really like it to just work. As feature rich as v13 is I just don't need it all.

Thans,
Ian