Well, the code in question is still the same, so if you have some kind of error situation where attaching the volume fails, the exception will still get masked as DeviceIsBusy, whatever the original error may be.
Well, the code in question is still the same, so if you have some kind of error situation where attaching the volume fails, the exception will still get masked as DeviceIsBusy, whatever the original error may be.