Unable to lock the disk for exclusive use [Bug in v5]

[kamcm]

Hello,

I would like to tell you I am using the 4.71 standard version [giveaway version] since last year and really happy with it.
Therefore, I purchased a pro license for a upgrade yesterday.

However, the version 5 is broken, I tried the 5.01.7 pro and 5.01 pro version. Both of them will showed up an error msg - "Unable to lock the disk for exclusive use"when I try to do a surface write test.

I am really disappointed with it. I downgrade to 4.71 PRO and everything worked as expected.

I had attached the screenshot for your reference.

Please fix this serious bug ASAP.

Thanks!
=========
Working in 4.71 PRO
http://kamserver.com/upload/2017-9/HDD1.jpg
Not working in 5.01.7 PRO [Bata version]
http://kamserver.com/upload/2017-9/HDD2.jpg
Not working in 5.01 PRO
http://kamserver.com/upload/2017-9/HDD3.jpg

[hdsentinel]

Thanks for your message and excuse me for the possible troubles.

This seems so interesting. I can confirm that generally there is no difference in this field between 4.71 and 5.01 (and 5.01.7) versions: all versions generally attempt to lock the drive for exclusive use when the write test started. This is the first step to be performed in order to properly overwrite the drive.

When any other application is using the drive, it is failed to lock the drive. An open file, folder may cause this too. If the drive is just connected with USB dock or similar, an antivirus software may automatically perform scan (which can prevent locking too).

Do you have any partition(s) on the drive? While generally not required (as automatically erased) I'd suggest to please check in Windows Disk Management and delete it prior starting the test, just to verify if there may be any difference.
Or do you see this on a clean, empty drive too, where no partition(s) defined?

I tried to check the images - but all the same (captured with 4.71).

I suggest to please use Report menu -> Send test report to developer option in the latest 5.01.7 version, as then it is possible to check the actual situation, verify what can be wrong, what may happened and why you receive this error.
Maybe somehow related to disk controller / connection - so would be nice to examine with more details.

Excuse me for the delayed answer - in the meantime I attempted to reproduce the issue: tried with 5.01 and 5.01.7 to overwrite such high capacity drives. I used 6 TB and 8 TB drives (WD80EFZX, slightly similar to your) under Win7, Win8, Win10 - and both versions performed to overwrite as should, without any warnings, messages, errors. This is why I generally see no bug (if there would be a bug, then other users would surely report similar) - and curious what happened on your system.

Excuse me again - hopefully by the developer report I can see things better and can check what can cause the issue on your system.