New version of Zentimo is available for beta testing. In this beta we have fixed several minor issues and significantly improved forced stopping mechanism. Now the forced stop will unlock the device in all cases where earlier versions failed: svchost, an NTFS issue (so called $Extend\$RmMetadata\$TxfLog isue), when some low level program like antivirus, backup locked the drive etc. If you had problems with safe removal in previous versions feel free to try the beta and report us if it works for you or not.
Zentimo 2.0 beta 1 available
May 6th, 2017
What are the changes besides the improved forced stopping?
To go from v1.10 to v2.0 normally indicates major improvements.
Or is this a marketing move?
There are no major changes between version 1.10 and 2.0 except mentioned ones. But there are huge changes between version 1.x and 2.0 therefore we decide that it’s time to increase the version number.
Just tried, get an 404 instead of a download page… oO
I’m sorry, there was a wrong link. Please try to download once again.
The link above is a 404, but the link in the email works.
The previous version solved all my forced stopping issues. Too infrequently updated for me to continually renew. I do so every couple of years or so when there is a deal on Bits du Jour.
This is a third update for the last year, I’m sorry we are so slow. And I think we will no more participate on BitsDuJour with our products.
With Windows 7 and the previous Zentimo version, I was having problems with the removal of my 3 & 4 tB external drives, and the “Forced Stop” did not work. With v2.0 beta 1, the Forced Stop now works.
Note that the previous version worked fine on my Windows 10 machine, and also worked for Windows 7 with drives 2 tB or smaller.
Thanks for your feedback!
Re: $Extend\$RmMetadata\$TxfLog issue: my way around this was to launch Disk Management and set the disk to offline. I could then stop and eject the drive using Zentimo. Of course this meant the drive was offline when I reconnected it, but at least it allowed me to eject the drive. I experimented and tried stopping all sorts of services but I never worked out exactly which one was keeping those files open.
AVG Internet Security created a separate file on the disk that also locked, and by temporarily disabling AVG, that removed the AVG lock file.
However, setting the disk to Offline in Disk Management then using Zentimo to stop the device gave me most success.
Unfortunately, there has been no consistency between drives – I have close to 20 x 3.5″ external desktop USB 3.0 drives and another 10 x 2.5″ portable drives – and the problem affects some but not others. The majority are Seagate, but I have some WD as well.
From my testing, as I am sure you have discovered, I am certain it is a NTFS issue rather than related to a particular manufacturer.
Anyway, I’m glad you have been able to address this issue in Zentimo 2.0b1 – I look forward to testing it and will report back my results.
Thanks for the detailed feedback. Yes, it’s a tricky bug in NTFS since the issue may happen even on newly installed system, but often it’s caused by thirdparty software. It would very interesting to know your results since you have so many drives.
I just found your email in my spam folder from a few weeks ago. I have a lifetime sub. to USB Safely Remove and a paid older version of Zentimo. Love your products. I did not have the success of others here with the new Beta version of Zentimo in safely shutting down a 4tb WD Ultra Passport I bought a few months ago. PID 4 error and the dreaded $Extend\$RmMetadata\$TxfLog issue.
I just set it up for quick removal which I would have preferred not to do. But I can’t safely remove it without a shutdown. I am using Norton Security Suite (Latest Version), latest firmware on the WD drive. I also see efasidat\Symefa.da which i believe is related to Norton.
Can you send us the report from the program. In order to send the report you should proceed to “Main menu -> Help -> Report a bug”, and in the opened dialog enter your e-mail and a short description of the problem. This helps us to investigate the problem more detailed.
By the way what email service are you using (that places our messages to spam)?