This issue seems to crop up from time to time in virtually every iteration of Windows since XP, maybe before even.
In past versions of Windows, I've ran the various Troubleshooters, the FixIt(s) programs that Microsoft publishes from time to time that are suppose to address such problems, I've even gone so far as manually attempting to fix the issues which involves renaming various directories and re-registering multiple .dlls that are involved in the update process.
Sometimes that works, but a lot of times it doesn't.
The only method that I've found that seems to work reasonably reliably (high 90 percentile) is to perform an in-place upgrade repair. That is..... upgrade Windows by installing it over top of itself.
It's a reasonably simple process but does take some time to perform.
The upside is that it is normally non-destructive and generally will leave all your programs, drivers and data intact and unharmed.
I would still backup all my critical data as well as create a disk image before doing it, just to be on the safe side.
Neosmart has a pretty good article describing the process here
https://neosmart.net/wiki/windows-10-repair-installation/
If you need the installation media to perform the in-place upgrade / repair
The installation media can be obtain through either of these two resources.
https://www.microsoft.com/en-us/software-download/techbench
OR
http://www.microsoft.com/en-us/software-download/windows10
Once you have the ISO, you can use ImgBurn to burn it to a DVD or Rufus to burn it to a USB ThumbDrive or simply mount the ISO from within Windows 10.