We have seen a TONNE of Windows BFs related to persistent EBUSY conditions with random WiredTiger data files – the turtle file, metadata, and data files have all been impacted. (See comment below.)

Historically, we've hand-waved these away a little. We tend to close these tickets saying things like "gone away", "it was probably another process", that sort of thing.

We can't fix Windows' fundamentally bad design choices, but we CAN improve the diagnostics when they bite us. A bit of googling has led me to believe that there are ways to figure out which process has a file open – if we can do this in, say, diagnostic mode we'd have a much better ability to do something useful with these BFs.