Cumulative Update KB4058258 Windows 10 v1709 Build 16299.214 - Jan. 31

My version is now 16299.214.

IUTLPS said:

Hello
I have an installation problem with the new update KB4058258. The error is 0X80073715.
Same issue with olds KB4073291 or KB4056892. Only the KB4056892 Delta worked and the previous cumulative patch too.
I have downloaded this updates manually after KB4050258 failed with WU.
I have tried by installing the MSU file and the CAB file with DISM.
I have tried troubleshooter, deleted Softwaredistribution folder, removed Kaspersky, removed Virtualbox, updated drivers, restarted computer, SFC and DISM checks (no errors).

Someone have an idea ?
Here is an extract of the CBS.LOG.
2018-02-02 11:36:54, Info CBS Not able to add pending.xml to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2018-02-02 11:36:54, Info CBS Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2018-02-02 11:36:54, Info CBS Not able to add SCM.EVM to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2018-02-02 11:36:55, Error CSI 0000000b (F) STATUS_SXS_MANIFEST_IDENTITY_SAME_BUT_CONTENTS_DIFFERENT #520257# from CCSDirectTransaction::OperateEnding at index 8 of 256 operations, disposition 2[gle=0xd015001c]
2018-02-02 11:36:55, Error CSI 0000000c (F) HRESULT_FROM_WIN32(ERROR_SXS_MANIFEST_IDENTITY_SAME_BUT_CONTENTS_DIFFERENT) #512447# from Windows::ServicingAPI::CCSITransaction::ICSITransaction2_AddComponents(Flags = 4, a = @0x25115c5b090, mp = @0x25115c5b890, disp = 0)[gle=0x80073715]
2018-02-02 11:36:55, Info CBS Failed to add one or more deployment [HRESULT = 0x80073715 - ERROR_SXS_MANIFEST_IDENTITY_SAME_BUT_CONTENTS_DIFFERENT]
2018-02-02 11:36:55, Info CBS Failed to bulk stage deployment manifest and pin deployment for package:Package_1859_for_KB4058258~31bf3856ad364e35~amd64~~10.0.1.17 [HRESULT = 0x80073715 - ERROR_SXS_MANIFEST_IDENTITY_SAME_BUT_CONTENTS_DIFFERENT]
2018-02-02 11:36:55, Info CBS CommitPackagesState: Started persisting state of packages
2018-02-02 11:36:55, Info CBS CommitPackagesState: Completed persisting state of packages
2018-02-02 11:36:55, Info CSI 0000000d@2018/2/2:10:36:55.692 CSI Transaction @0x25118e1f420 destroyed
2018-02-02 11:36:55, Info CBS Perf: Resolve chain complete.
2018-02-02 11:36:55, Info CBS Failed to resolve execution chain. [HRESULT = 0x80073715 - ERROR_SXS_MANIFEST_IDENTITY_SAME_BUT_CONTENTS_DIFFERENT]
2018-02-02 11:36:55, Error CBS Failed to process single phase execution. [HRESULT = 0x80073715 - ERROR_SXS_MANIFEST_IDENTITY_SAME_BUT_CONTENTS_DIFFERENT]
2018-02-02 11:36:55, Info CBS WER: Generating failure report for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.214.1.17, status: 0x80073715, failure source: Resolve, start state: Absent, target state: Installed, client id: WindowsUpdateAgent
2018-02-02 11:36:55, Info CBS Not able to query DisableWerReporting flag. Assuming not set... [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

I have the same problem with the update kb4058258 and the error 0X80073715.

Hello,

Installed it last night and all seemed well, shutdown the computer. Turned it on this morning and my main monitor wouldn't come up. I log into Windows and the ThunderboltEX 3 adapter that my main monitor is hooked up to is not showing up in the Device Manager > System Devices... It does look like its showing in the USB controller section, of course its with the little yellow triangle. Going to try checking the BIOS etc... Anyone else having TB issues?

JMTH said:

Hello,

Installed it last night and all seemed well, shutdown the computer. Turned it on this morning and my main monitor wouldn't come up. I log into Windows and the ThunderboltEX 3 adapter that my main monitor is hooked up to is not showing up in the Device Manager > System Devices... It does look like its showing in the USB controller section, of course its with the little yellow triangle. Going to try checking the BIOS etc... Anyone else having TB issues?

Now is really the time to become very friendly with backing up. With all the shebang going on with Spectre & Meltdown, microcode update not working and retrieved, the only thing that can truly save one from getting trapped is to backup, backup and backup your system whenever it is working normally and before making any big change with a MS Update or any other update for that matter.
All I am trying to say is to try to revert your system back with the last good system image backup you have made. I cannot count how many times my backup plan has saved my bacon. MR has always been my best bet when it comes to backing up.

Hi,

Igor Strongers said:

I have the same problem with the update kb4058258 and the error 0X80073715.

After a restart of the machine the CU may well show as installed correctly and winver updated to .214.

https://support.microsoft.com/en-au/...date-kb4058258





Cheers,

IronZorg89 said:

Now is really the time to become very friendly with backing up. With all the shebang going on with Spectre & Meltdown, microcode update not working and retrieved, the only thing that can truly save one from getting trapped is to backup, backup and backup your system whenever it is working normally and before making any big change with a MS Update or any other update for that matter.
All I am trying to say is to try to revert your system back with the last good system image backup you have made. I cannot count how many times my backup plan has saved my bacon. MR has always been my best bet when it comes to backing up.

Heh yeah, I tried uninstalling KB4058285 first. It worked (which surprised me) and of course the TB3 card came right back. So now ill have to wait for Intel then ASUS to update the drivers yet again hehe.

JMTH said:

Heh yeah, I tried uninstalling KB4058285 first. It worked (which surprised me) and of course the TB3 card came right back. So now ill have to wait for Intel then ASUS to update the drivers yet again hehe.

I don't have a clue about what actions were taken on your machine before you installed KB4058258, but if you look at @Brink's article (First page):

• Resolves the issue reported by some customers on a small subset of older AMD processors where the processor entered an unbootable state after installing January 3, 2018—KB4056892 (OS Build 16299.192).

& @f14tomcat (post #56), some prerequisites are needed beforehand in order to install this update.
At any rate, I am glad that uninstalling the update worked for you and that you are back on track (TB3 card came right back). Again, remember to backup...and also verify the backup is working. I always programmed my backups to "verify" right after finishing the task. :)

IronZorg89 said:

I don't have a clue about what actions were taken on your machine before you installed KB4058258, but if you look at @Brink's article (First page):

• Resolves the issue reported by some customers on a small subset of older AMD processors where the processor entered an unbootable state after installing January 3, 2018—KB4056892 (OS Build 16299.192).

& @f14tomcat (post #56), some prerequisites are needed beforehand in order to install this update. In my case, I didn't have to install it since I am not concerned.
At any rate, I am glad that uninstalling the update worked for you and that you are back on track (TB3 card came right back). Again, remember to backup...and also verify the backup is working. I always programmed my backups to "verify" right after finishing the task. :)

I have an Intel processor so it did not apply. Yeah I verify hehe I use AOEMI Pro with a incremental scheduled backup. Along with iDrive on a scheduled and continuous backup. Cant have too many backups!