Not really. I haven’t looked into why it caused the issue it did. Presumably it is not actually intentional by MS, and there is some conflict going on that’s causing it. I’ll eventually get around to trying to let it install that update again, but life has been busy :)