Further to my previous post: before I started experimenting with those updates yesterday morning, my system crashed at first boot with a SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (VeloSSDd.sys) BSOD. Fascinating, is this pure co-incidence or is there a relationship with the appearance of updates the same day?
My partition was unbootable. I offline removed the VeloSSDd.sys driver from the crashed system's registry, as well as all (boot) references to the driver, to VeloSSD and to elitebytes. There were no traces of VeloSSD on the system anymore. Still, it crashed with the same message.
Even replacing the hidden Windows partitions with "clean" ones from before the Velo days didn't work. Neither did restoring a full, known good image which had worked before. This leads me to believe that there is a secret boot procure hidden somewhere on the disk.
Only restoring a full image without Velo worked. I could easily live with that and re-install VeloSSD. Yet I won't. VeloSSD effectively hijacks my system and like a virus, it resists all attempts to get rid of it. This should normally not be a problem. Yet it is fatal when VeloSSD persistently keeps crashing, preventing the system from booting and even preventing repairs. I have no time to randomly get stuck with an unbootable system and no possibility to repair. My image backups are useless.
I can fully understand that such a highly complex product like VeloSSD can run into trouble on some systems. I can live with that. But Elitebytes should at least make it possible to get a crashed system working again by restoring a full image backup. Because in the Windows world, things tend to crash.
Thank you for your attention.