abort
function. Since Explorer doesn't rely on the MS C runtime the most logical conclusion is that you have a misbehaving shell extension. Shell extensions are loaded into the Explorer process and can quite easily wreak havoc like this. I would try this disk on a different machine to test out that theory. Or find a tool that disables shell extensions.