Cumulative Update failing

nvm

Hi everyone,

I'm back ....lol I am still trying to figure out why I can't install KB40134209 on my Windows 10 Home v1607 Build 14393.693. I will keep searching until the next Cumulative Update is released and then if I can't install that one I will do some kind of repair to my system

Last night I ran the three DISM scans (CheckHealth, ScanHealth and RestoreHealth) The end result is it found repairable corrupted files in my store (whatever that is) but it couldn't find the source.

Meanwhile, while checking my updates page last night I noticed when I went to Settings > Update > uninstall updates there is a KB3213986 listed and it is being shown as installed on March 20, 2017 (yesterday).

However, it is not listed as a Successful Install on my Installed update page. To further boggle my mind it is my understanding that this Microsoft Windows Security Update was released as a Cumulative Update on Jan. 10, 2017 which brought my computer to its current build (14393.693)

My question is if my System has had this build # for the last two months why is this update now showing as having been installed on March 20, 2017 in a listing for updates I could uninstall if I wanted and why wasn't its Successful installation listed under my Installed update listing?

Hope I made this clear enough.

Thanks and regards,
2harts4ever

SOLVED SOLVED SOLVED

Howdy everyone, :) :) :)

Just wanted to let everyone who has been responding to my problem that it is now solved.

Everyone who posted on this thread helped with the final solution.

However, what really tipped the scales was this post from this past October when I had a similar problem (USB Flash Drive - Create to Install Windows 10?).

The very first answer 'Navy LCDR' suggested to me is what I tried today. In a nutshell I was looking for a way to solve my update problems, because of corrupted files, but still manage to hang on to all my apps and files. So I did as he said again today and after installing Windows 10 on a Flash Drive I launched its 'setup' with Windows running and after sweating bricks for about an hour and a half this method proved successful and my computer is back to normal and I just ran 'sfc /scannow' and it shows no problems. I think I now have a fully updated computer. I now show v1607 with Build # 14393.969.

The one change I did make when I ran this method this time is I chose not to install updates until the end of the installation. The last time when I tried the same thing I selected install updates as soon as it started up.

Regardless I am one happy camper because last time when this same method failed I ended up doing a clean install. This method when it works eliminates all that hassle ....lol

So in closing I once again want to thank everyone who helped me, not only on this post, but the one I referenced above.

Thanks and regards,
2harts4ever

Pleased you found a solution to the mysterious world of MS updates - well done and thanks for posting.

Couldnt get the update to take, so updated straight to

Windows 10.0.15063.0 Version 1703 RS2.
Done