FileSystemWatcher stops reacting to deletions

[IlyaRabyy]

I was trying to start new thread, but this new website dinna wanna take "FileSystemWatcher glitch" as a thread title... I miss the old Tek-Tips website!
But it let me in on this second attempt. (Forgive me my nostalgia for the ol' good Tek-Tips wbsite!)

BTOM:
1. FSW reacts dutifully to renaming and modification (excerpt from the log file):
================================================================================
2024-10-31 13:21:00: FileWatcher2_C started on [Machine Name]
================================================================================
2024-10-31 13:21:41: File C:\Temp\New Text Document - Copy (3).txt was modified on [Machine Name]
2024-10-31 13:23:08: File C:\Temp\New Text Document (4).txt was renamed to
C:\Temp\New Text Document 4.txt on [Machine Name]
2024-10-31 13:23:21: File C:\Temp\New Text Document 4.txt was modified on [Machine Name]

However,

2. After reacting to (registering) one or two deletions, it stops reacting to any deletion (single or multiple) at all!

What might cause this behavior?

TIA!

 

[strongm]

>What might cause this behavior?

Can't answer that at the moment (not least because something has broken my Visual Studio installation), but

>FileSystemWatcher glitch

Can't see any restrictions on this. I was able to create a thread with that title