In case the two conventional system file checkers (DISM and SFC) aren’t able to fix the issue for you, the final solution would be to refresh every OS component by doing a repair install (in-place repair).
However, in the event that you’re dealing with an advanced case of system file corruption, you might need to initiate a system-wide system corruption scan (using the SFC and DISM utilities). If that doesn’t work, move towards resetting the Windows Update component – You can either use the automated agent to do this or you can do the steps yourself (manually) from an elevated Command prompt. In case you want to fix the underlying problem that’s causing the KB4464218, start simply by running the Windows Update Troubleshooter and see if the utility is capable of isolating the culprit and fixing it automatically. Since the issue is somehow facilitated by some corrupted files that are stored locally, one way to circumvent the issue altogether is to use the Microsoft Update Catalog to install the update manually instead of relying on the Windows Update client – However, this will not allow you to discover the root cause of the issue.
