Same thing happened to me this week-end and we are not alone [1]. The worst is that it's actually the second time on this computer (Kaby Lake i3 on a MB with Intel B250 Chipset). I had the same issue in December last year (exact same behaviour with probably an earlier version of that hotfix).
I'm running with Windows Update service disabled till this is fixed for good !
[1] https://answers.microsoft.com/en-us/windows/forum/windows_10...