3 ms·
> Combine this with Windows Defender that scans every file that your application creates, and now you have no reliable way of deleting or moving your files. Th
by smileybarry 4y ago
> Combine this with Windows Defender that scans every file that your application creates, and now you have no reliable way of deleting or moving your files.
This doesn't happen for years now due to "opportunistic locks" -- when you open a file being used by an app which support oplocks (i.e.: usually antiviruses), they get a blocking notification and can release the file. They can hold the notification (and stall the requesting application) until they're done, close their handle, and the other app's open succeeds.
- cma 4y agoIs this where all the stalls during big compiles come from?
- indrora 4y agoThat's probably your disks cache catching up with what you've done. NTFS likes making sure that disks flush their caches regularly, and congestion caused by cache bloating makes it harder. Getting an nvme (or better, while you can, Optane) SSD for compilation on is a good start for improving your build times.
- xwolfi 4y agoSweet child, he reads the documentations but doesnt use it. I concur with op, to this day, deleting a fucking file in Windows is an unbelievable chore compared to all their competitors. I tried today, nope, couldn't. But you dont care, obv you dont use it.
- kevin_thibedeau 4y agoUse Shift-Del to bypass the performance shitshow that is the recycle bin.
- smileybarry 4y agoI use Windows Defender on several PCs, and have used for years. All are kept up to date on Windows 11 (and prior, Windows 10) and not “modded” to disable telemetry etc. I haven’t had a “locked by Defender” error in at least 5 years, and I would say more if I could remember the last time I did. I’m also developing a(n existing) product that actually uses oplocks, so I’m speaking from experience here.