Looks like the culprit was another .NET Security update. The fix was the same as what I posted in the above link... Change the master page back to default go to the root, then change back to the custom master page. This isn't the best fix, so I'll look into
why it errors out after these updates in the first place.
updates to server:
Related KB articles:
Anyone else run into this issue and know how to permanently fix?