I would have though that it wouldn't have had an effect, as there would be no direct change of ashMaiSv.exe, that should be the only reason comodo might block and it should first challenge for any change.
So it is more likely to be a coincidence that this happened after windows update and this is the same issue (problem with comodo blocking) as before, so take the same action as before.