I've tried this several times already, as well as the powershell commands, sfc commands, DISM commands, and running associated troubleshooters.

Performing a clean boot does not fix this issue.