As soon as I start ChangeTest it's working, even in folders that are not monitored.
I also found that restarting Opus may help with changes made in Opus. It still doesn't refresh on changes made by external tools.
EDIT: But changes made before I started ChangeTest are not refreshing in Opus.
If change detection starts working in Opus after running a separate piece of software that uses the same API, then something is wrong outside of Opus. The problem must be in the components that implement/intercept that API (the OS itself, antivirus or filesystem/drivers).
Some part of the API is getting stuck, by the sound of it. Since it started happening recently and only to people on Windows 11, it may be a recently added bug in Windows 11, unfortunately.
It'd be interesting to keep ChangeTest running to see if it starts to see problems as well. I suspect it will, unless the API only goes wrong when a process requests monitoring of multiple folders, perhaps.
I have had the problem for years and it started with windows 10. I only find it annoying enough lately to dig deeper after I accidentally lost files Opus showed the wrong location for. The thread starter also has windows 10.
And if other software can see the changes while Opus can't how could a stuck API be the cause? This thing is extremely hard to troubleshoot because I don't know how to trigger the issue, I can only wait... I'll keep the ChangeTest running.
My mistake about Win11; I was getting confused with a different thread.
The Windows Desktop often misses changes as well (particularly if a sequence of changes are done to a single file, and more often when it's done via a command line program, for some reason; I often have to push F5 to get it to stop showing icons for files that no longer exist). Those bugs in the Desktop have been there for over 10 years with no sign of a fix.
Change notification in Windows is not always reliable, even in Microsoft's hands.
But what you're seeing isn't usual in Opus, either.
One thing which can be a factor is if there are so many events that the buffer for storing them overflows, at which point some or all may be dropped. Increasing Preferences / Miscellaneous / Advanced [Troubleshooting]: notify_max_time and notify_min_items could be worth a try, although that is a long shot.
Nothing that Opus does can really explain why things start working after you run another program (ChangeTest.exe) which also use the same API. That points to an issue outside of Opus, since Opus and the other program have no connection other than both using that API, and do not communicate with each other in any way. For the API to stop sending events until a second program asks points to a problem in the API itself. Unfortunately, we have no way of seeing inside Windows to understand what it's doing or how that could happen.
I also see this on the desktop an until now I thought this is the same issue but I just realized that I don't sync the desktop to Onedrive. To get to the bottom of this I'll test the settings you mentioned. I'll also check if the ChangeTest is indeed reliably fixing the issue or if this is a coincidence. I'm still not convinced that the problem lies outside of Opus if I let's say extract a folder with 7-zip and Windows Explorer sees the change but Opus doesn't. Also if ChangeTest pushes Opus to work why doesn't Explorer do the trick? I'll have to try everything that comes to mind...
Testing with Opus added to Defender's whitelists (there are two of them) is also worth a try:
I'll try whitelisting. It would be pretty disturbing though if ChangeTest would be able to override Defender, LOL
Thank you for your support btw! Much appreciated!
ChangeTest can't override Defender, but what Defender does is based on a lot of heuristics and can vary a lot between programs.
Today the issue re-appeared for the first time after I did the tests. I whitelisted dopus in defender and the problem was gone immediately. I don't know if this is really the solution because the problem was also solved by running the ChangeTest tool. Since I don't know what triggers the issue I can only wait a few weeks.
PS: removing the whitelisting doesn't reinstate the error, so...
I also have the problem with the updating issue in onedrive synced folders by using directory opus. Does it matter if I set other drive which is not the system drive? It is very annoying I have to refresh manually after copy/pasting, deleting and unziping. I am using win 11 and latest Opus.
It doesn't matter. I tried other volumes and other drives.
Whitelisting didn't help. The issue appears again after some time.
There's discussion of how to debug the issue above. We need those logs to see anything useful.
@Leo Thanks for the feedback. Please help to check the enclosed debugview file, I repeat the steps as the above video does.
DebugView++.zip (1.8 KB)
There's no change notification entries in the log (only ShellChange ones, which are secondary and not what matters here).
If notify_debug was on (not just shellchange_debug) then that indicates change notification is being blocked or broken by something on the system. Most likely antivirus.
Which antivirus are you using?
Have you tried the suggestions above to whitelist Opus to see if it makes a difference?
Running ChangeTest.exe may also be worth a try to see if your machine is also only sending change notifications when a second program also requests them. I don't know what the solution is to that (it's something going wrong in the OS or with low-level components like antivirus that can interfere with the OS) but it would mean you're seeing the same issue as the OP rather than something different.
I double-checked and found out what you described for the "change notification" stuff. I can see the "change notification" in other driver except the onedrive synced folder as below:
And I have tried to add to the whitelist as below, but I am not sure if what I set was correct/working.
I also tried the changetest, but seems not working except in the default location. Maybe I am not use it correctly 
If ChangeTest.exe can't see any changes happening to the drive / folder, the Windows change notification system is broken on that drive/machine. I don't know how to fix that, sorry.
