Everything you wrote related to 100% same background: Hard Disk Sentinel started, attempted to access the disks/controllers and detect the status information. It needs to wait for the devices - and if there is no response, you may see what you wrote:
> HDS started but HDS didn't display anything. No notification icons.
> And when I try to start HDS from the desktop nothing was happening.
> And similar to now the HDS task couldn't be killed using the Process Explorer.
This is completely independent from Hard Disk Sentinel. Hard Disk Sentinel does not "protect" itself of course: during normal operation, it can be any time "killed" from Task Manager if really required. If it is not possible - then it means some device is "locking" the software which attempted to access it - Hard Disk Sentinel in this case.
It is completely independent from the versions - expect that older versions of HDS may not support the newest hardware, so older versions did not attempt to detect VROC, Adaptec RAID and so. Maybe you did not see similar with old versions - exactly because they did not attempt to detect the disk status information.
> Why is it not possible to kill the HDS process?
Because a device is not responding and somehow locking the software which attempted to access it. It is completely independent from Hard Disk Sentinel but more related to the device driver.
> Anyway, when I reboot (I usually do this only once in a month)
> I will send a test report to developer. Hopefully, you can find something which can be further analyzed.
From the developer report, I'd surely see things more clearly. Actual disk configuration, the drivers used for the controller(s) can give ideas, thoughts and by that, it is possible to examine if
- a driver update
- or some changes in the software
can help to minimise issues.
> You say that HDS is waiting for a device. But all disks are fully functional.
> When I open the Intel VROC GUI all disks are visible and in a normal state.
> When I open Adaptec maxView Storage Manager again every disk is in optimal state.
> Everything is OK.
It does not mean anything. It only means that at a LATER stage the disks/controllers work properly - but not immediately after wake up.
I'm sure the same would happen if you'd manually close Hard Disk Sentinel before hibernation and then later restart it manually after wake up, when the disks/controllers are already working/responding properly.
Maybe it is only a question time: HDS may need to apply some delay on wake up before attempting to detect/update the status. Probably it happens too quickly after wake up on your system.
> So, I wonder for what device HDS is waiting for?
I'm so curious about it too. The developer report can help to check and also we can examine the behaviour specifically for your RAID controllers/disks.