Bummer.
Do you know the name/number/date of the problematic MS Update? Perhaps Microsoft would have a solution if I can identify the MS Update.
Is this MS Update just an issue with Avast?
Thanks.