Thanks for the suggestion. I completely forgot that I had this same issue in February and had to do the repair updates solution back then. Looks like the Refresh Updates might have worked this time.
