Failing updates: KB3032655 and KB3023215

dmitriyv

New member
Joined
Oct 10, 2015
Posts
4
I need some assistance. Updates KB3032655 and KB3023215 keep failing, errors are 80073712 and 800B0100 respectively.

I have run the System Update Readiness tool and updates still fail.

Here is the information from ChekSUR:


=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2015-10-11 07:43

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_2_for_KB3032655~31bf3856ad364e35~amd64~~6.1.1.0.mum Line 1: INDX(

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f) CSI Manifest and S256H Do Not Match 0x00000000 winsxs\Manifests\amd64_af0f05c36620bfcaf625f971aca3e637_b77a5c561934e089_6.1.7601.18763_none_f882e877bc679904.manifest amd64_af0f05c36620bfcaf625f971aca3e637_b77a5c561934e089_6.1.7601.18763_none_f882e877bc679904
(f) CSI Manifest and S256H Do Not Match 0x00000000 winsxs\Manifests\amd64_993649d11959fa44591493cffc511455_b77a5c561934e089_6.1.7601.22970_none_65a49c77c42aea8e.manifest amd64_993649d11959fa44591493cffc511455_b77a5c561934e089_6.1.7601.22970_none_65a49c77c42aea8e
(f) CSI Manifest and S256H Do Not Match 0x00000000 winsxs\Manifests\amd64_9fd546f7781e332a7b0e6ea7651c325a_b03f5f7f11d50a3a_6.1.7601.18763_none_a4906b0690a1cfd3.manifest amd64_9fd546f7781e332a7b0e6ea7651c325a_b03f5f7f11d50a3a_6.1.7601.18763_none_a4906b0690a1cfd3

Summary:
Seconds executed: 622
Found 4 errors
CSI Manifest and S256H Do Not Match Total count: 3
CBS MUM Corrupt Total count: 1

Unavailable repair files:
winsxs\manifests\amd64_af0f05c36620bfcaf625f971aca3e637_b77a5c561934e089_6.1.7601.18763_none_f882e877bc679904.manifest
winsxs\manifests\amd64_993649d11959fa44591493cffc511455_b77a5c561934e089_6.1.7601.22970_none_65a49c77c42aea8e.manifest
winsxs\manifests\amd64_9fd546f7781e332a7b0e6ea7651c325a_b03f5f7f11d50a3a_6.1.7601.18763_none_a4906b0690a1cfd3.manifest
servicing\packages\Package_2_for_KB3032655~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_2_for_KB3032655~31bf3856ad364e35~amd64~~6.1.1.0.cat


Please let me know if you need anymore information.
 
Some more information:

SFCFix version 2.4.5.0 by niemiro.
Start time: 2015-10-11 11:56:36.396
Microsoft Windows 7 Service Pack 1 - amd64
Not using a script file.


AutoAnalysis::
WARNING: Manifest damage on component "amd64_993649d11959fa44591493cffc511455_b77a5c561934e089_6.1.7601.22970_none_65a49c77c42aea8e". See CBS logfile for more details.


SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 5
CBS & SFC total unimportant corruption count: 0
CBS & SFC total fixed corruption count: 0
SURT total detected corruption count: 4
SURT total unimportant corruption count: 0
SURT total fixed corruption count: 0
AutoAnalysis:: directive completed successfully.


Successfully processed all directives.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2015-10-11 12:01:06.844
----------------------EOF-----------------------

Also, Components file: Microsoft services
And CBS.log: Microsoft services
 
Hello and welcome

Due to the precise nature of your corruption, you will receive help from a user named LiquidTension. He's one of our senior trainees here who's in his final phrase of his studies and needs to gain some real world experience in specific areas of Windows Update. This means that he'll be assisting you, but that I will first need to double check and approve his fixes before he posts them to you. If anything this is a good thing for you because it means that you've got at least two of us watching over your thread, but it will unfortunately add a slight delay between each reply. I hope that you understand and can accept the need for us to train up new members in this way in order to carry on doing what we do here, however, if for any reason you object to this setup, I will happily take on your thread myself.

Thank you very much for your understanding. We'll be with you very shortly.
 
Hello,

Please do the following:

IGJdB0T.png
System Update Readiness Tool (SURT) Package Replacement

Warning: This fix is intended for use on this particular machine. Do not use this fix on any other machine; doing so may cause damage to your Operating System. If you are not the original poster and require assistance, please start your own topic.

  • Download View attachment Packs.zip and save this file to your Desktop.
  • Right-click the file and click Extract All....
  • Place a checkmark next to Show extracted files when complete and click Extract.
  • A window will open showing two folders, Manifests and Packages.
  • Open the Manifests folder and copy the files into the following folder:

    C:\Windows\Temp\CheckSur\Winsxs\Manifests

  • Open the Packages folder and copy the files into the following folder:

    C:\Windows\Temp\CheckSur\Servicing\Packages

  • Re-run the System Update Readiness Tool (SURT) as you did before.
  • Upon completion, copy the contents of the SURT log found at C:\Windows\Logs\CBS\CheckSUR.log and paste in your next reply.
 
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2015-10-13 07:26
Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_2_for_KB3032655~31bf3856ad364e35~amd64~~6.1.1.0.mum Line 1: INDX(
Checking Package Watchlist
Checking Component Watchlist
Checking Packages
Checking Component Store
(f) CSI Manifest and S256H Do Not Match 0x00000000 winsxs\Manifests\amd64_af0f05c36620bfcaf625f971aca3e637_b77a5c561934e089_6.1.7601.18763_none_f882e877bc679904.manifest amd64_af0f05c36620bfcaf625f971aca3e637_b77a5c561934e089_6.1.7601.18763_none_f882e877bc679904
(f) CSI Manifest and S256H Do Not Match 0x00000000 winsxs\Manifests\amd64_993649d11959fa44591493cffc511455_b77a5c561934e089_6.1.7601.22970_none_65a49c77c42aea8e.manifest amd64_993649d11959fa44591493cffc511455_b77a5c561934e089_6.1.7601.22970_none_65a49c77c42aea8e
(f) CSI Manifest and S256H Do Not Match 0x00000000 winsxs\Manifests\amd64_9fd546f7781e332a7b0e6ea7651c325a_b03f5f7f11d50a3a_6.1.7601.18763_none_a4906b0690a1cfd3.manifest amd64_9fd546f7781e332a7b0e6ea7651c325a_b03f5f7f11d50a3a_6.1.7601.18763_none_a4906b0690a1cfd3
Summary:
Seconds executed: 570
Found 4 errors
CSI Manifest and S256H Do Not Match Total count: 3
CBS MUM Corrupt Total count: 1
Unavailable repair files:
winsxs\manifests\amd64_af0f05c36620bfcaf625f971aca3e637_b77a5c561934e089_6.1.7601.18763_none_f882e877bc679904.manifest
winsxs\manifests\amd64_993649d11959fa44591493cffc511455_b77a5c561934e089_6.1.7601.22970_none_65a49c77c42aea8e.manifest
winsxs\manifests\amd64_9fd546f7781e332a7b0e6ea7651c325a_b03f5f7f11d50a3a_6.1.7601.18763_none_a4906b0690a1cfd3.manifest
servicing\packages\Package_2_for_KB3032655~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_2_for_KB3032655~31bf3856ad364e35~amd64~~6.1.1.0.cat
 
Hello,

It does appear the files were replaced. We can use a different method.

bMTzsQ3.png
SFCFix Script (.zip)

Warning: This fix is intended for use on this particular machine. Do not use this fix on any other machine; doing so may cause damage to your Operating System. If you are not the original poster and require assistance, please start your own topic.

  • Download View attachment SFCFix.zip and save this file to your Desktop.
  • Note: Ensure this file is named SFCFix.zip. Do not rename the file.
  • Close all open windows.
  • SFCFix.exe
    bMTzsQ3.png
    and SFCFix.zip
    49i66Jv.png
    should both be present on your Desktop.
  • Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  • SFCFix will now process the script. Upon completion, a file (SFCFix.txt) will be created on your Desktop.
  • Copy the contents of the file and paste in your next reply.

After doing the above, please rerun a scan with SURT (as you did in your very first post). Upon completion, copy the contents of C:\Windows\Logs\CBS\CheckSUR.log and paste in your next reply.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top