I ran SFC on powershell and it was able to fix the problem. The update was successfully installed. It must have been a fluke. Thanks.
