Macrium Support Forum

Incremental Consolidate leaves Disk Locked?

By larrymcg - 30 September 2017 7:04 PM

Using Reflect v7.0.2199 on Win10 64bit backing up to an external Backup Disk

I'm not 100% sure about this but it seems to me that after using Macrium Incremental Consolidate the disk can not be Safely Removed and Ejected. Stopping everything in sight does not help. Stopping explorer.exe (Windows Explorer) works but I don't really like to do that.  LockHunter shows which tasks have the disk locked but it can not unlock it.  So, I just power the disk down.  I have the disk set for quick removal so that should be OK but I'd be happier if it wasn't left locked.

So, do others experience Incremental Consolidate leaving the disk locked?

-- Larry

By Nick - 1 October 2017 12:34 PM

Hi Laryy

It's the file Windows system cache that's preventing the disk from being ejected. 

Check the setting in Device Manager.

Device Manager > Select disk > Right Click and choose 'Properties' > 'Quick Removal'
By larrymcg - 1 October 2017 4:21 PM

Nick,  My original post stated that the disk is set for quick removal.  I checked again and it is set for quick removal.  Both my external backup disks are set that way and they both are often locked after using Macrium Increment Consolidate.  On some occasions the backup disk is left locked after doing a backup but that is rare.

-- Larry

By jphughan - 1 October 2017 4:40 PM

Unrelated to Reflect usage, I’ve had disks set for quick removal that Windows would sometimes hang onto. In those cases, sometimes closing folder windows or applications and reattempting fixes it, and sometimes just doing nothing other than trying again does, but in the cases where Windows is tenacious, I just remove the device anyway. The only time I’ve ever seen a problem has been on a tiny FAT16 partition where I store a UEFI NTFS driver on certain flash drives, but even that’s rare. For other file systems, occasionally I’ll see a warning that it should be checked for errors when I first use it again after a dirty removal, but the scans never detect any problems. I’ve never figured out what accounts for the varying behaviors I’ve seen, although in fairness it’s never bothered me enough to investigate, but if it’s not happening consistently with Reflect, it may not be something Reflect can fix.