Windows 10: Error 0x80073715 in kb4058258

Page 1 of 3 123 LastLast
  1.    02 Feb 2018 #1

    Error 0x80073715 in kb4058258


    I can not install the update kb4058258 from windows update, I have also tried to download the update from Microsoft Update Catalog giving me the same error.
      My ComputerSystem Spec


  2. Posts : 1
    Windows, CentOS
       02 Feb 2018 #2

    While I have successfully installed this on a couple of PCs; I'm having this issue on several different machines. I'm seeing these two errors in the Event Viewer:

    System Log: "Installation Failure: Windows failed to install the following update with error 0x80073715: 2018-01 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4058258)."

    Setup Log: Windows update "Update for Windows (KB4058258)" could not be installed because of error 2147956501 "The identities of the manifests are identical but their contents are different."

    I have tried:

    • Windows Update Troubleshooter
    • Windows Update Component Reset
    • Installation via Windows Update
    • Installation via manual download
    • DISM.exe /Online /add-package /packagepath:"E:\Windows 10 Updates\KB4058258.cab"
    • DISM.exe /Online /RestoreHealth
    • SFC /ScanNow

    The only interesting common thread I can think of on these machines is that, at one point or another, I've run:

    DISM /Online /Cleanup-Image /StartComponentCleanup /ResetBase
      My ComputerSystem Spec

  3.    03 Feb 2018 #3

    I have tried:
    • Executed the Windows Update Troubleshooter.
    • Tried via Windows Update.
    • Tried via manual download.


    Unsuccessfully.
      My ComputerSystem Spec


  4. Posts : 29
    Windows 10 Home x64 (Build 16299)
       04 Feb 2018 #4

    Same here. If you search the internet for kb4058258 and 0x80073715 you'll see a lot of people are having the same issue. And there is no workaround.

    While there’s no official workaround available, you can try to download the offline installers from Microsoft’s Update Catalog website and manually perform the update. You can also install the latest Service Stacking Update (SSU) from here and retry the update.

    If nothing works, we would advise you to wait for the official fix and keep watching this space for more updates.
    https://www.windowslatest.com/2018/0...or-0x80073715/
      My ComputerSystem Spec

  5.    04 Feb 2018 #5

    Try this and report your findings.

    Download the offline installers for all the patches KB4048955 (2017-11), KB4054517 (2017-12), KB4056892 (2018-01) & KB4058258 (2018-01). (It's up to you as to if you choose Delta Updates or Cumulative Updates or download both).

    Uninstall updates or 'Refresh My PC' to revert to base version 16299.15

    Take the machine offline and install the updates in sequence.

    If successful, document whether you chose the Cumulative or the Delta of each patch. I used Cumulatives.

    I have one machine that installed Deltas via WU (no issues) and one that failed 16299.192 (manual patch applied) that refused 16299.214 until I rolled back and did this.

    YMMV.
      My ComputersSystem Spec


  6. Posts : 347
    Windows 10 PRO
       04 Feb 2018 #6

    Got it just now... and no issues! :)
      My ComputerSystem Spec


  7. Posts : 29
    Windows 10 Home x64 (Build 16299)
       04 Feb 2018 #7

    winactive said: View Post
    Try this and report your findings.
    I was not successful.

    So here goes:

    I created a thumb drive with the Windows Media Creation tool to be able to work offline and I downloaded the updates onto the thumb drive. All cumulative, no deltas.

    Still, online, i.e. in Windows, I removed the relevant updates with dism /online /remove-package . This way I successfully reverted to 16299.15

    Working offline, invoking command shell (shift F10), during booting Windows setup from the thumb drive, I tried to apply the Updates in the order of release date: Nov, Dec, Jan KB4056892 and Jan KB4058258, like so:

    Code:
    X:\Sources>dism /scratchdir:c:\scratchdir /image:c:\ /add-package /packagepath:"d:\Updates\2017-11 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4048955)\windows10.0-kb4048955-x64_f214597fd57cd8284a363ada825a3d8ca16bf632.msu"
    
    Deployment Image Servicing and Management tool
    Version: 10.0.16299.15
    
    Image Version: 10.0.16299.15
    
    Processing 1 of 1 - Adding package d:\Updates\2017-11 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4048955)\windows10.0-kb4048955-x64_f214597fd57cd8284a363ada825a3d8ca16bf632.msu
    [==========================100.0%==========================]
    The operation completed successfully.
    
    X:\Sources>
    This works for Nov and Dec. Both Jan updates fail with error 0x80073715

    Code:
    X:\Sources>dism /scratchdir:c:\scratchdir /image:c:\ /add-package /packagepath:"d:\Updates\2018-01 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4058258)\windows10.0-kb4058258-x64_69f87cf7f2ea83509d5e61ba2d525a103a6d64f9.msu"
    
    Deployment Image Servicing and Management tool
    Version: 10.0.16299.15
    
    Image Version: 10.0.16299.125
    
    Processing 1 of 1 - Adding package d:\Updates\2018-01 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4058258)\windows10.0-kb4058258-x64_69f87cf7f2ea83509d5e61ba2d525a103a6d64f9.msu
    [==========================100.0%==========================]
    d:\Updates\2018-01 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4058258)\windows10.0-kb4058258-x64_69f87cf7f2ea83509d5e61ba2d525a103a6d64f9.msu: An error occurred applying the Unattend.xml file from the .msu package.
    For more information, review the log file.
     Error: 0x80073715
    
    Error: 14101
    
    The identities of the manifests are identical but their contents are different.
    
    The DISM log file can be found at X:\windows\Logs\DISM\dism.log
    
    X:\Sources>
    Note that the build version goes from 16299.15 to16299.125 but not higher.
      My ComputerSystem Spec

  •    04 Feb 2018 #8

    Ben Hastings said: View Post
    I was not successful.

    So here goes:

    I created a thumb drive with the Windows Media Creation tool to be able to work offline and I downloaded the updates onto the thumb drive. All cumulative, no deltas.

    Still, online, i.e. in Windows, I removed the relevant updates with dism /online /remove-package . This way I successfully reverted to 16299.15

    Working offline, invoking command shell (shift F10), during booting Windows setup from the thumb drive, I tried to apply the Updates in the order of release date: Nov, Dec, Jan KB4056892 and Jan KB4058258, like so:

    Code:
    X:\Sources>dism /scratchdir:c:\scratchdir /image:c:\ /add-package /packagepath:"d:\Updates\2017-11 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4048955)\windows10.0-kb4048955-x64_f214597fd57cd8284a363ada825a3d8ca16bf632.msu"
    
    Deployment Image Servicing and Management tool
    Version: 10.0.16299.15
    
    Image Version: 10.0.16299.15
    
    Processing 1 of 1 - Adding package d:\Updates\2017-11 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4048955)\windows10.0-kb4048955-x64_f214597fd57cd8284a363ada825a3d8ca16bf632.msu
    [==========================100.0%==========================]
    The operation completed successfully.
    
    X:\Sources>
    This works for Nov and Dec. Both Jan updates fail with error 0x80073715

    Code:
    X:\Sources>dism /scratchdir:c:\scratchdir /image:c:\ /add-package /packagepath:"d:\Updates\2018-01 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4058258)\windows10.0-kb4058258-x64_69f87cf7f2ea83509d5e61ba2d525a103a6d64f9.msu"
    
    Deployment Image Servicing and Management tool
    Version: 10.0.16299.15
    
    Image Version: 10.0.16299.125
    
    Processing 1 of 1 - Adding package d:\Updates\2018-01 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4058258)\windows10.0-kb4058258-x64_69f87cf7f2ea83509d5e61ba2d525a103a6d64f9.msu
    [==========================100.0%==========================]
    d:\Updates\2018-01 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4058258)\windows10.0-kb4058258-x64_69f87cf7f2ea83509d5e61ba2d525a103a6d64f9.msu: An error occurred applying the Unattend.xml file from the .msu package.
    For more information, review the log file.
     Error: 0x80073715
    
    Error: 14101
    
    The identities of the manifests are identical but their contents are different.
    
    The DISM log file can be found at X:\windows\Logs\DISM\dism.log
    
    X:\Sources>
    Note that the build version goes from 16299.15 to16299.125 but not higher.
    Then you need the ValueCompat registry key set. Install the Trial version of Malwarebytes Anti-Malware if you don't fancy the reg file and try the remaining patches.

    (You may wish to temporarily uninstall your current AV if it is not on this list.)
      My ComputersSystem Spec


  • Posts : 29
    Windows 10 Home x64 (Build 16299)
       04 Feb 2018 #9

    winactive said: View Post
    Then you need the ValueCompat registry key set. Install the Trial version of Malwarebytes Anti-Malware if you don't fancy the reg file and try the remaining patches.

    (You may wish to temporarily uninstall your current AV if it is not on this list.)
    It is set. I use Windows Defender. I manually installed the delta of, I believe, KB4056892 in early January (the first Meltdown/Spectre mitigation patch). I noticed the registry entry was already in place then.

    I believe installing the Jan 3rd delta update is somehow connected with this issue.
      My ComputerSystem Spec

  •    04 Feb 2018 #10

    Ben Hastings said: View Post
    It is set. I use Windows Defender. I manually installed the delta of, I believe, KB4056892 in early January (the first Meltdown/Spectre mitigation patch). I noticed the registry entry was already in place then.

    I believe installing the Jan 3rd delta update is somehow connected with this issue.
    I installed my patches in .exe mode not from Powershell or the Command Window. I believe advice from MS is to stop wuauserv and cryptsvc using net stop but being offline they can't do much.
      My ComputersSystem Spec


  •  
    Page 1 of 3 123 LastLast

    Related Threads
    Source: https://support.microsoft.com/en-us/help/4058258 Direct download links for KB4058258 MSU file from Microsoft Update Catalog: :arrow: Download KB4058258 MSU for Windows 10 v1709 32-bit (x86) - 364.1 MB :arrow: Download KB4058258...
    The Meltdown patch has not been offered so far for update on my Win10 Pro (build 1709) laptop. It also fails the PowerShell script that MS provided to check if your system is vulnerable. It is NOT an AMD system, and I'm using Windows Defender for...
    Hello, My wife has a new computer with Windows 10 and we're trying to activate Office 2010. The error we get every time we try to activate is "a communication error has occurred 0x80072EE7." I saw some posts about syncing the time and date but...
    During Windows backup, which wants to backup the 'C' drive and my games drive 'E' (for some reason), I get the following error message after the 'C' backup has completed but not the 'E': 'The backup operation that started at...
    I am on my 4th SSD in my Windows 10 laptop that has been getting SMART error 2000-0151. We have replaced the motherboard, the SSD, and the connector cable between the SSD and motherboard. One thing is that I've been using Macrium Reflect to clone...
    Our Sites
    Site Links
    About Us
    Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

    © Designer Media Ltd
    All times are GMT -5. The time now is 23:37.
    Find Us