They recently acknowledged and fixed this issue. I can personally confirm it hasn't happened to me since the update.
https://www.pcmag.com/news/microsoft-fixes-update-and-shut-d...
https://www.pcmag.com/news/microsoft-fixes-update-and-shut-d...
According to the link, it "only" took them 5 years to solve the bug. Better late than ever though, I guess :)