Reply to post:

Don't worry guys - just skip the individual KB that causes the issue and wait for a rerelease! I guess it's the CVE-2018-0885 HyperV fix!

Ohhhh!! Hang on! Damn.. can't even do that anymore! All or none approach now!