Skip to main content

How to prevent 2012 stopping safe disc removal

Thread needs solution

Since installing 2012 my removable drives can’t be removed from Safe to remove”. I am told something is using them. It must be something from true image as there was no problem before. I have disabled Aconis Nonstop Backup service, Scheduler 2 service and Sync Agent from service and TrueImageMoniter and Scheduler Helper from Start-up.
As all I do is images I don’t need all these add ones running and they something is causing a lot of problems making safe removal difficult.
What else can I do other than remove the program which is a likely candidate?

0 Users found this helpful

If you stop scheduler2 and schedhp you won't be able to make any images.

Are you positive this has only happened upon installation of TIH? You have had no Windows updates or other software updates in the meantime?

I have one drive that never allows the safe removal to work, but my other 3 do with or without TIH installed.

Have you checked in the drive properties under device manager to see if somehow their attachment setting has changed?

**edited spelling errors***

One drive is a few months old, the other new yesterday (firest used just before downloading 2012, but it was a replacement for the identical one that failed). I have found the new one (as eSATA can only have one working at a time) allowed safe removal AFTER I just unplugged it and replaced it. I have done the same for the older one as well and it also now allows safe removal. I have opened the image on both but not created a new one which is what I did on both before I found the problem before (I closed laptop and removed drives then rebooted to see if safe removal was working (with this it wasn’t). So it may be something creating the images caused the “lock” or something else!
When I have the time I will recreate a new image and see if that does it again and reopen this post if so.

Are these USB connections? This is a recurring problem with how Win handles USBs and it's aggravated by something in ati. I don't know eaxctly how this works but I'd put omoney on it.

1) You can wait and see if the drive can be ejected later.
2) You can use something like unlocker.exe (free program) to see if any program is holding an open file handle on the file, and then "unlock" the file. However, you might find that no program is holding the file open.
3) You can temporarily disable cidaemon service (the windows file indexer) in case it's reservinglocking the file for indexing operations. Doing 1) or 2) will also, usually, solve this.

4) You can wait until you are sure that any delayed writes to the drive have completed and then just disconnect the drive by hand. The only problem with disconnecting a USB is doing it while there are still writes to be completed or the recyle bin hasn't completed being updated.

These are eSATA drives, W7 has endless issues with eSATA and no idea when/is MS will ever sort them out. They use the same auto recognition etc. as USB as far as I know though. Yes my graphics is ATI. Will get unlocker and use it if/when it returns.

Thanks

John7 wrote:

These are eSATA drives, W7 has endless issues with eSATA and no idea when/is MS will ever sort them out. They use the same auto recognition etc. as USB as far as I know though. Yes my graphics is ATI. Will get unlocker and use it if/when it returns.

Thanks

Yes, six of one, half dozen. . ..

unlocker is free, small and very unobtrusive so it can't hurt. However, in most cases you likely will have to resort to the other workarounds; this has been my expereince on various machines.