Windows10: Update KB4058258 causes error 0x80073715

[German]Microsoft released the cumulative update KB4058258 for Windows 10 Fall Creators Update on January 31,2018. It looks like this update causes the installation error 0x80073715 on some systems. Addendum: It seems we have identified the root cause.


I’ve addressed this update within my blog post Windows 10 V1709: Updates KB4058258, KB4074608, KB4077735, KB4078128 and KB4057790. Cumulative update KB4058258 for Windows 10 Fall Creators Update fixes issues with color rendering, multi monitor mode and shall fix boot issues on older AMD systems.

First reports of error 0x80073715

After I published a blog post within my German blog, I received a comment, that update KB4058258 stalls with install error 0x80073715. And I found a 2nd German site, where a user mentioned this error. Now there are more reports claiming issues with this update and install error 0x80073715 (see here or here). Also at tens-forum is a thread reporting this install error, and at I found this Thread.

What stands error 0x80073715 for?

Error code 0x80073715 indicates a corrupted or incorrect update file, and it stands for


A manifest file in the update package collides with an existing manifest file in the Update Component Store.


What you can try

To make sure that the problem is not on your own computer, you can check the component store (see Check and repair Windows system files and component store). You can also try to reset the Windows Update Component Store (see the section in the article Windows 10: Update Error 0x80248014). However, I’m afraid that doesn’t help. In the comments mentioned above, this did not work and in this tenforums article, the approach was not successful either.

Install the Servicing Stack Update KB4074608

Another approach you should try: Make sure, that the latest Servicing Stack Update KB4074608 has been installed successfully. Accoding to this comment in my German blog, it may help.

Try to download the update package

What you can do: Download the update package from Microsoft Update Catalog and try a manual installation.

The root cause Delta Update KB4056892

Addendum: Above I posted a link to a thread in this Dutch forum. A user noted, that he installed the delta update KB4056892 (January 3,2018). He wrote (free translated:

It turns out that this was caused by the installation of the delta patch update for Meltdown and Spectre. I installed this in early January immediately after the release of the leaks from the Microsoft Update Catalog. You have to remove such an update first. Unfortunately, however, this was no longer possible because a disk cleanup removed system files (including the Windows update files). It was therefore not possible to simply uninstall the delta patch.

Solution was therefore a reset by backup from January 3rd and then simply install the update via Windows Update. That went flawless right away.

Searching the Internet shows, that a couple of users already have had problems to install update KB4056892 and failing with error 0x80073715. I’ve seen some suggestions to do a disk cleanup, to enable KB4056892 installation. That was the reason, why the guy mentioned the disk cleanup thing. After I published my German article, a blog reader confirmed this root cause within this comment.

Another idea to fix error 0x80073715

Since the error does not affects all Windows 10 users, I guess that an existing component causes the collision. My tip to those affected would therefore be to uninstall all VC runtime libraries via control panel and try the update again. Afterwards, the VC runtime libraries could be reinstalled. Maybe it’ll help.

System wants restart, but remains unsuccessful

There is a second comment in the blog post that complains about error 0x80070bc2 = ERROR_SUCCESS_REBOOT_REQUIRED. The update prompts you to restart, but the update fails. Performing a system check for damage (see Check and repair Windows system files and component store) did not show any results.

The update will be installed again and again. The problem is also described in Microsoft Answers forum. In this case, however, the problem has bee solved, after the user manually removed the old update from the system (deinstalled), then manually downloaded the update package and reinstalled it.

Update KB4058258 breaks audio output

There is a Microsoft Answers forum entry mentions audio issues. But there isn’t a solution yet.

Norton Security damaged

Within this forum post at Symantec someone complains that an update destroyed and uninstalled Norton Security. It turns out there that it could have been update KB4058258 which caused the problems.

Update causes inaccessible boot device

Within this forum thread people reporting, that installing update KB4058258 on a PhenomII system is resulting in a “inaccessible boot device”.

This entry was posted in issue, Update, Windows and tagged , , , , . Bookmark the permalink.

7 Responses to Windows10: Update KB4058258 causes error 0x80073715

  1. fsr says:

    I have error 0x80073715 while trying to install KB4058258 online/offline. I checked sfc, no corruption, uninstalled KB4056892 (yep) per suggestion, system asked for a reboot which i did, aplied KB4074608 also per suggestion, again tried KB4058258 offline and again output was 0x80073715. Going to wait for official patch

  2. Wrzlbrmft says:

    I’m the user which reported the error on the other forum.
    Uninstalling KB4056892 did not help, the error 0x80073715 stays.
    I have invested some time and analysed CBS.log. The error seems to com from the servicing stack update KB4074608 which I have installed on Feb 1 before the KB4058258 was distributed. The SxS collision is in “Microsoft-Windows-BootEnvironment-Core-BootManager-EFI.Resources” which is also mentioned in the “amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.16299.212” in SxS. Uninstallation of the servicing stack is not possible, so I have to use a backup or new install :-(
    Lession learned: Do not install KB4074608 manually!

  3. Wrzlbrmft says:

    Hi again,
    the concolusion that the servicing stack is the problem was wrong!
    I missed the indication to failing ‘index 8’ in the CBS.log, the servicing stack is simply the last (index 255) follwed by the error message. Index 8 is ‘amd64_microsoft-windows-hvsi-csp-wim’ which contains “WindowsDefenderApplicationGuard.wim”.
    Im tempted to just erase the ‘old’ entry in SxS (folder and manifest) but I don’t know if there is a ‘database’ behind SxS (in a file or registry).
    Can I erase content in WinSxS?

  4. Advertising

  5. Wrzlbrmft says:

    Fond the solution! I uninstalled KB4056892 but did not clean afterwards. This leaves the contents of KB4056892 in the WinSxs folder.
    The working sequence is:
    Uninstall KB4056892
    Dism.exe /online /Cleanup-Image /StartComponentCleanup
    Install KB4058258

  6. Ricky says:

    Yes, you made it work:
    Uninstall KB4056892

    Dism.exe /online /Cleanup-Image /StartComponentCleanup

    Start the regular windows update, to let the os find its updates (it will reinstall ..892)

    Install KB4058258

Leave a Reply

Your email address will not be published. Required fields are marked *