viBoot official release was on Friday, I am writing this on Monday night. We here at Ten Forums were first to notice that latest Windows Insider builds caused an issue with Macrium's virtual SCSI adapter
required for viBoot to run.
Kudos to Macrium, they started working on the issue on weekend. On Monday I received an email from them telling they have identified the culprit:
We have identified that issue lies with a change in the driver certification logic with newer technical preview kernel builds. The reason that the original viBoot release works is that this was signed by a 'legacy' authenticode certificate; binaries signed using this method are exempted from strict validation to maintain compatibility.
I am sure an updated installer will be available soon. Until that happens, please unselect Run viBoot
when installer is ready before closing it!
Before launching viBoot first time download this small ZIP archive from my OneDrive: viBoot SCSI drivers
. The ZIP archive is safe to download, it comes directly from Macrium, I received it in an email from their support.
Extract the archive, copy all three files and paste them in C:\Program Files\Macrium\viBoot
folder replacing existing files with same name:
Select Do this for all current items
and click Continue
to paste the files:
Now you can launch viBoot, it will work perfectly