With an issue as critical as "will prevent your computer booting" (I just spent two days with sfc, dism, system restore, and all manner of other stuff before narrowing it down to WindowBlinds) wouldn't it be a good idea to somehow notify customers of this issue? I realise that's a little challenging, but not everyone updates their addon software the instant an update is available while Windows will transparently apply its own updates without your involvement - so people are going to run into issues like this.
I am sorry you had problems.
The update on Windows Update is an optional one (or certainly was when the WB update went out) which is why we have so few reports and the WB update should have been telling people every week about the update. In fact if your build was sufficiently old it prompted you every hour due to a small bug in the earlier releases update checking code. Unfortunately we have no ability in the builds to show a message other than there is an update out. In the future I believe this capability is being built in to the update system but that will require another WB update.
The instant we became aware of the issue we put out the update. On the one hand auto installing updates would be a good thing, on the other I know how irritating it is for apps to require a reboot all of a sudden. It is an exceptional event indeed for a Windows Update to trigger a compatibility issue of that nature with WindowBlinds, it was an unexpected change on the MS side which exposed a bug in some code in the 64 bit version which didn't correctly handle it.
For future reference if you hold down the ctrl key when logging in you will find WindowBlinds is disabled, or safe mode would also do the same thing.