New
#11
have to use the DISM via CMD in troubleshooting to find the most recent KB installed....
mine was a C++ but was able to roll back a few days on that one only... ~10/11th jan 2018 - still never checked which KB though and paused updates until mid Feb.
our AV is Vipre 10 Endpoint - which is compatible with all new cpu patches... supposedly.
figure ms should just use google approach to fixing their packages.. think NIX systems are using the opensource fix vs the MS performance impacting fix, but we'll see.
beyond that I have a lot of different packages loaded on this system - could be any one of them installed that "could" conflict with an update... but inaccessible boot - and non of the fixboot commands were fully working, nice work MS...