System restore to pre KB install resolve the issue but looking at the time stamps of other KB CU install's and the fact I had to use a restore point two back it maybe that it was another KB causing the issue. And FYI forced driver update that seems to have been the fix for others didn't work in this case.
this however is the third time in 30 days that this machine has been bricked by different windows update not very good is it?...
1 x AV related
1 x HDD boot sector issue
And now this..
Current working winver is 16299.192
Now unfortunately this is a windows home PC so I can't defer / pause updates unless I decide to break win updates (which sucks, this shouldn't be necessary)
So I've created a restore point and we'll see if it happens again after the next install of updates hopefully MS can fix there s**ty updates..
To many tickets relating to 1709 upgrade QC has to be improved at MS!
So the update re applied itself again as the deferred timeout period had been reached, I has hoping you might have fixed the underlying issues but alas the issue persists.
I have submitted the data as requested, I'll remove the update and try to stop its for coming back..
Another week another bug report.. :(
20 years I've been in IT and this last year I've reported more bugs to MS than in the 19 years before it..
Whoever is in charge of QC at MS needs taking outside and chaining to the dog house!
Better still bring back versioning so we can all avoid these new 'features' which seem to be causing no end of issues..
I can see the windows 10 name being so poisonous soon that you'll have to bring in windows 11 just to stop the rot..
[Moved from: Windows / Windows 10 / Windows update, recovery, & backup ]