Why does Win 10 say update failed but then say system is up-to-date

Various computers (Win 10 Home and Pro, all 64 bit) have had updates that failed but then the system claims the system is up-to-date. Sometimes in days, sometimes in weeks, the system finally agrees with itself and performs the update. I have never been able to force them without manually downloading the udpate using the KB #.

On an as-needed computer the latest update from 1703 to 1709 has no KB # to look up. For the past week the computer has been left running. It has been manually restarted and shutdown/restart. However, checks for updates continue to claim it is up-to-date.

Since the updates are forced on us there must be a way to force an update when we want it!

Any suggestions?

I have seen cases were Windows figured out the update did not apply, or perhaps somehow had been installed already, or perhaps recalled, or something... In any case, this may trigger an "Update failed" message despite the fact that everything is well.

[Shrug] It's a product of the "new" Microsoft under Nadella and clowns like Joe Belfiore, so there's no, and I mean none at all, quality control of that stuff anymore

I apologize for the long delay but I didn't want to post until I was sure of how to correct *my* situation(s).

Caledon Ken, I thank you very much for your posts. Those will come in handy but I really wanted to find a way to get the update without having to reinstall applications. On the computer in question that would have been easy as only VLC and Malwarebytes (free version) were installed. Also, I could never find how to set the metered connection but found the netsh command to test and it was unrestricted.

Pirx, the OS still showed the older version so, in my case, that didn't seem to be the issue but I will keep that in mind!

After many, many, attempts the simplest solution for me was to delete the entire "%windir%\SoftwareDistribution" folder. (It was copied to the desktop.) I also ran an SFC scan which found no issues and a troubleshoot for windows update which, on the first computer performed some repairs.

After each step, SFC, troubleshoot, folder delete after coping, the update was executed. Only after deleting the folder did the first computer requiring a 1703 update get updated.

then, my Wife's computer needed to be updated to 1709. It failed. Neither SFC nor Troublshoot found isuues. I deleted MOST of the folder (only stopped wuauserv but forgot to stop bits), restarted the computer, shut down protection, and restarted the update. It worked!

This seems so wrong to have to go through on so many computers for various windows updates but, at least they are updated.

Thank you for all your help and comments.

Well, I was going to explain what I read and ask what I missed. Instead, I read the text past the video!

Well, I am glad I found a way that seens to work fairly well what you posted for everyone to see is great! That could solve a whole host of issues with only a minimal to moderate amount of pain.

Thank you for waking me up!