Not what you are looking for? Ask the experts!
SYMEFA.DB causes sharing violation on handle.
I was double checking our ReFS support for backup and find Norton is interfering. Basically, We can lock the volume and force the handle off the volume. But we need to use some FSCTL_ calls that won't work on a dismounted / locked volume. So typically we open the volume with sharing mode 0, that fails now due to SYMEFA.DB. We we willing to move to FILE_SHARE_READ since volume will still be protected from changing, but that didn't work either, still sharing violation. Using both FILE_SHARE_READ|FILE_SHARE_WRITE works, but we can't chance volume changes. I have a couple other ideas I'm going to try to fudge around it, not sure if it will work. But be helpful if you guys wouldn't open handles on the volume that aren't needed, or at least read-only mode until you need to write, or maybe delay opening so if we lock / unlock open quickly, we can get the handle before you take it.