I can confirm that this particular update is not causing my problem.