This message just showed up, again, a few days ago. Does anyone know if another "bad" release caused this like it did in the November 2018. Dave-H's solution worked for me back then, but cannot duplicate it since I no longer have KB4461552 listed as a "currently installed program". Is anyone else having this problem? Or is there something else I could do to try and remedy this?