On Sat, Mar 6, 2021 at 2:36 PM Michael Paquier <michael@xxxxxxxxxxx> wrote: > On Fri, Mar 05, 2021 at 07:36:37PM +0200, Andrus wrote: > > Then turned real-time protection off: > > > > Problem persists. New entry is written after every 10 seconds. > > On which files are those complaints? It seems to me that you may have > more going on in this system that interacts with your data folder than > you think. Suggestion received off-list from my colleague Bevan Arps, when I was complaining about this general variety of problem: maybe we should look into using Windows' RestartManager[1][2] API to find out which processes (at least the pids, maybe also names) currently have a file open? Then, if it is indeed a sharing violation that's causing the problem, we might at least be able to log message that says who's blocking us once we reach that dreaded retry loop. There are other ways to get that information too, I believe, no idea which API would be best, but this one looks to be the best documented. I'm unlikely to work on this myself as a card carrying Unix hacker, so I'm just passing on this insight in case it's useful... Another thought: if it's not a sharing violation, I wonder if we should consider dumping more raw Windows error information in the messages we log, because, if I recall correctly, we're converting many Windows error codes into few Unix-style error numbers and thereby throwing away valuable clues. It makes it a bit more confusing when trying to ask a Windows expert what might be happening. [1] https://docs.microsoft.com/en-us/windows/win32/rstmgr/restart-manager-portal [2] https://devblogs.microsoft.com/oldnewthing/20120217-00/?p=8283
