Running a windows defender scan didn't flag it this time, so it was probably an issue of a backlogged patch being installed before the more current one.
