This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Windows 10 home, new computer with CPU Intel 8700K working well, version 1709 installed.
I noticed that windows update gives error 0x80070bc2 when trying to install 2017-11 Cumulative update for Windows Version 1709 for amd64-based systems KB4048955 (and before KB4043961) ... getting a sort of a loop as it requires a restart to finish installing but at any restart gives the same message and does not install.
Tried various things such as sfc scan, dism, troubleshooting windows update, manual install etc. Nothing works. Other updates such as KB4048951 and KB4051613 installed correctly in the last few days. Can someone help?
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
This seems to have worked for me:
SC config wuauserv start= auto
SC config bits start= auto
SC config cryptsvc start= auto
SC config trustedinstaller start= auto
Все делал, как у Вас написано не помогло ...
Что еще можно сделать?
13 февраля 2018 г. - KB4074588 (сборка ОС 16299.248)
Thank you for the detailed account of your experience that is interesting and helpful. My own experience is somewhat different – not unusual where MS is concerned! It might be helpful to others if I recount this.
Back on 25 February 2018 I made a backup of my Win10 Pro system and recovered this to a spare HDD. This was to prove my backup and recovery regime.
I used this spare HDD system drive rather than my normal SSD system drive in case of further problems arising from my attempts to overcome the 0x80070bc2 error.
Although the HDD should have been an exact copy of the SSD I was surprised to find that - Settings | Update & Security | View installed update history - showed a completely blank history although the SSD system had 0x80070bc2 errors from weeks ago!
The scan for available updates returned with Cumulative Update for Windows 10 Version 1709 for x64 based systems KB4090913 instead of the usual KB4056892 !!
I proceeded to install this using the commands advised by DevonBasson – (to whom, many thanks)
SC config wuauserv start= auto
SC config bits start= auto
SC config cryptsvc start= auto
SC config trustedinstaller start= auto
(Note for those too young to know DOSKEY which is now built in to the command line entry facility – the UP arrow cursor key restores the previous command line entry that can then be edited. This can save quite a lot of typing.)
The installation proceeded very much as IranMach1’s experience with numerous cycles of updating and restarting.
Eventually KB4090913 installed – Control Panel | Programs and Features | View installed updates – confirms that this update was installed on 06/03/2018.
However if I look in - Settings | Update & Security | View installed update history – it says that Cumulative Update for Windows 10 Version 1709 for x64 based systems KB4090913 failed to install with error 0x80070bc2 Consequently it needs to install again!
How can I convince Windows that the installation does not need to be repeated?
Next I shall recover the system backup to my HDD again and repeat the exercise, observing carefully throughout. I am not going to “touch” my SSD until I have a reliable updating methodology.
Has anyone else come across KB4090913 ? How does it differ from KB4056892 ?
Kapil Arya MVP. Thanks man. İ have just formated new ssd and face this problem. Try to fix it like 2-3 hour. 2-3 hour means a lot these days. fixed the problem. We are living in 2018 and windows still cant fix these kind of thinks.
You have one or more typos.
