That is not the same thing as what I posted. An in place upgrade repair will fix any Windows problems you have, it will not remove any programs that you have or any personal filed. All you need to do is download the ISO usion the Windows Upgrade tool and follow the directions in the Tut that I posted.
Repair Install Windows 10 with an In-place Upgrade Windows 10 Tutorials
Performed the Dsim and sfc was clean. Doing a in-place now. For the record this happened on a HP Spectre x360 15-b1XX. Also tried an unplug everything and a install of the catalogued KBxx913 package from MSFT update catalogue in SAFE mode with same results.
Seems KB4090914 is updated 1st and correctly but then hanging KB4090913. Hung in a loop with 0x80070bc2 error. Gets to 98% on the KBxx913, restarts and then the oops couldn't complete message and an undo.
03/09/2018 UPDATE. Did a in-place last night and it successfully updated KBxx913 and KBxx914.
However this morning it downloaded KBxx913 again now awaiting restart.
==> Windows 10 Cumulative Update KB4090913 Fails to Install, Causes Other Issues
Cumulative Update KB4090913 Windows 10 v1709 Build 16299.251 - Mar. 5 - Windows 10 Forums
I got both via Windows Update and have had no issues.Performed the Dsim and sfc was clean. Doing a in-place now. For the record this happened on a HP Spectre x360 15-b1XX. Also tried an unplug everything and a install of the catalogued KBxx913 package from MSFT update catalogue in SAFE mode with same results.
Seems KB4090914 is updated 1st and correctly but then hanging KB4090913. Hung in a loop with 0x80070bc2 error. Gets to 98% on the KBxx913, restarts and then the oops couldn't complete message and an undo.
03/09/2018 UPDATE. Did a in-place last night and it successfully updated KBxx913 and KBxx914.
However this morning it downloaded KBxx913 again now awaiting restart.
==> Windows 10 Cumulative Update KB4090913 Fails to Install, Causes Other Issues
Cumulative Update KB4090913 Windows 10 v1709 Build 16299.251 - Mar. 5 - Windows 10 Forums
I did the suggested inplace upgrade repair and as soon as Windows Update ran, KB4090913 was downloaded and would not install as MarkDS posted. I also used Microsoft's guide to clear the contents of the software distribution folder, which got rid of the pending KB4090913 update, but as soon as Windows Update ran again, the offending KB4090913 update was back and will not install. Since it's not causing any issues at this moment, I'll wait for a fix from MS.
I'm still tilting at windmills on this issue. I found the following MS web page on trouble shooting Windows Update problems. Pretty good tutorial, but it left me with no resolution. The SFC Scannow generated a CBS.log that shows that the analyticsevents.dat files on my system are corrupt and the only fix the tutorial offers is to do an inplace repair, which I've done to no avail. The log says the hash for the file and the one in the store do not match. Not sure if the files would be rebuilt if deleted and I can't find any information on them, yet.
https://support.microsoft.com/en-us/...-update-errors
It appears that this issue is fixed now. Yesterday (03/13/18), KB4088776, KB4088785, & KB890830 downloaded automatically; but would not install due to the corruption from KB4090913. That trashed my hopes that a new cumulative or version would correct things. I have been laboring under the belief that this problem started with an 03/05/18 update gone awry, but looking at the downloaded packages for KB40090913 I discovered that it started on 03/02/18. I found over 1,800 KB4090913 files from 03/02/18 spread across several hours. I have a 57Mb internet connection, so downloads don't take much time. I also found some from 03/05/18. I had tried previous fixes based on 03/04/18 restore points and backups. Last night, I did a system restore from an 02/26/18 system image. The KB4090913/KB4090914 updates disappeared and when the system booted up after the restore, WU automatically downloaded and installed the three updates that showed up on 03/13/18. Thank goodness I had multiple system images (father/son). I am going to add another level with the new 1TB drive I just added for system backup. Had I realized when the corruption initially occurred, this problem could have been corrected much sooner and with a lot less labor. Now I can look forward to April's version update.
Last edited by jamis; 14 Mar 2018 at 08:32. Reason: added text
I had the same issue nd the following fixed it for me:
In the search box on the taskbar, type cmd.
Right-click Command Prompt in the search results and select Run as administrator. (Select Yes, when prompted by the User Account Control.)
In the Administrator: Command Prompt window, type the following command and press Enter:
SC config trustedinstaller start=auto
Restart the PC.
In some cases, a second restart may be required. If you look under Settings > Update & security and you see the message Status: Awaiting restart, restart the PC a second time to complete the installation.
I found these steps as a fix for a similar issue for the 0x80070bc2 error while attempting to install KB4074588.
Quote
