I was getting this in 4.25.2 and I was also still getting it in 4.25.3 despite also having updated the MS plugin through Bridge. Bummer!

...