[SOLVED] sfc has corruption cannot fix

RalphG · Aug 20, 2016

Hi, have run sfc/scannow on windows 7 ultimate sp1 32 all files are upto date but says some files corrupted and could not be fixes , ran sfxfix and says I need help I have attached the sfcfix file and hopefully will send you the cbs file.
Regards

LogBot · Aug 20, 2016

Logfile submission from RalphG

Logfile submission from RalphG.

The logfiles are available at: https://www.sysnative.com/niemiro/fileDistribution/2016-08/30506.zip

zcomputerwiz · Aug 22, 2016

Hello and Welcome!

System Update Readiness Tool (SURT)

Download and run the System Update Readiness Tool for your version of Windows here: System Update Readiness Tool

NOTE: If you aren't sure if your Windows installation is 32-bit or 64-bit, check here: How to determine whether a computer is running a 32-bit version or 64-bit version of the Windows operating system

This tool will take some time to complete - when it has finished, attach C:\Windows\Logs\CBS\CheckSUR.log with your reply.

RalphG · Aug 23, 2016

zcomputerwiz said:
Hello and Welcome!

System Update Readiness Tool (SURT)

Download and run the System Update Readiness Tool for your version of Windows here: System Update Readiness Tool

NOTE: If you aren't sure if your Windows installation is 32-bit or 64-bit, check here: How to determine whether a computer is running a 32-bit version or 64-bit version of the Windows operating system

This tool will take some time to complete - when it has finished, attach C:\Windows\Logs\CBS\CheckSUR.log with your reply.

RalphG · Aug 23, 2016

Hi, thanks for your reply, I ran the system rediness tool and hopefully it has attached to this reply

zcomputerwiz · Aug 23, 2016

Please download and install the following update: http://www.microsoft.com/downloads/details.aspx?FamilyId=6879be29-5693-4f45-b9e7-18df905219c0

Once installed, run SURT again and attach CheckSUR.log when it completes.

RalphG · Aug 24, 2016

Windows update say not applicable to your computer

zcomputerwiz · Aug 25, 2016

Does KB123456 appear in the list of installed updates?

Control Panel -> Programs and Features -> Installed Updates

If so, try uninstalling it and then run SURT again.

RalphG · Aug 25, 2016

can you confirm the kb number please as it appears to be for microsoft office
Regards
Ralph

zcomputerwiz · Aug 26, 2016

Although suspiciously numbered, that is the KB # indicated in the SURT log.

Code:

Checking Package Manifests and Catalogs
(w)    CBS Catalog Expired    0x800B0101    servicing\Packages\Microsoft-Management-Odata-Package~31bf3856ad364e35~x86~en-US~7.3.7601.933.cat        
(w)    CBS Catalog Expired    0x800B0101    servicing\Packages\Microsoft-Management-Odata-Package~31bf3856ad364e35~x86~~7.3.7601.933.cat        
(w)    CBS Catalog Expired    0x800B0101    servicing\Packages\Microsoft-NetworkSwitch-Management-Package~31bf3856ad364e35~x86~en-US~7.3.7601.933.cat        
(w)    CBS Catalog Expired    0x800B0101    servicing\Packages\Microsoft-NetworkSwitch-Management-Package~31bf3856ad364e35~x86~~7.3.7601.933.cat        
(w)    CBS Catalog Expired    0x800B0101    servicing\Packages\Microsoft-Windows-PowerShell-Client-WTR-Package~31bf3856ad364e35~x86~en-US~7.3.7601.933.cat        
(w)    CBS Catalog Expired    0x800B0101    servicing\Packages\Microsoft-Windows-PowerShell-Client-WTR-Package~31bf3856ad364e35~x86~~7.3.7601.933.cat        
(w)    CBS Catalog Expired    0x800B0101    servicing\Packages\Microsoft-Windows-PowerShell-WTR-Package~31bf3856ad364e35~x86~en-US~7.3.7601.933.cat        
(w)    CBS Catalog Expired    0x800B0101    servicing\Packages\Microsoft-Windows-PowerShell-WTR-Package~31bf3856ad364e35~x86~~7.3.7601.933.cat        
(w)    CBS Catalog Expired    0x800B0101    servicing\Packages\Microsoft-Windows-WinMan-WinIP-Package-MiniLP~31bf3856ad364e35~x86~en-US~7.3.7601.933.cat        
(w)    CBS Catalog Expired    0x800B0101    servicing\Packages\Microsoft-Windows-WinMan-WinIP-Package-TopLevel~31bf3856ad364e35~x86~~7.3.7601.933.cat        
(w)    CBS Catalog Expired    0x800B0101    servicing\Packages\Microsoft-Windows-WinMan-WinIP-Package~31bf3856ad364e35~x86~en-US~7.3.7601.933.cat        
(w)    CBS Catalog Expired    0x800B0101    servicing\Packages\Microsoft-Windows-WinMan-WinIP-Package~31bf3856ad364e35~x86~~7.3.7601.933.cat        
[B](w)    CBS Catalog Expired    0x800B0101    servicing\Packages\Package_for_KB123456_client~31bf3856ad364e35~x86~en-US~7.3.7601.933.cat        
(w)    CBS Catalog Expired    0x800B0101    servicing\Packages\Package_for_KB123456_client~31bf3856ad364e35~x86~~7.3.7601.933.cat    [/B]    
(w)    CBS Catalog Expired    0x800B0101    servicing\Packages\WIN8IP-Microsoft-Windows-WMI-Package~31bf3856ad364e35~x86~en-US~7.3.7601.933.cat        
(w)    CBS Catalog Expired    0x800B0101    servicing\Packages\WIN8IP-Microsoft-Windows-WMI-Package~31bf3856ad364e35~x86~~7.3.7601.933.cat        
(w)    CBS Catalog Expired    0x800B0101    servicing\Packages\Windows-Management-Protocols-Package-Win7~31bf3856ad364e35~x86~en-US~7.3.7601.933.cat        
(w)    CBS Catalog Expired    0x800B0101    servicing\Packages\Windows-Management-Protocols-Package-Win7~31bf3856ad364e35~x86~~7.3.7601.933.cat

On a closer look, it may be the Windows Management Framework Production Preview package...

Windows Management Framework 5.0 Production Preview is now available | Windows PowerShell Blog

If that is listed in your list of installed programs, please try uninstalling it.

Read More:

RalphG · Aug 27, 2016

Hi, Kb123456 does not appear as an installed update,updates appear to start at kb212**** there appears to be the windows managment preview 5 installed kb 3066439 but if I try to uninstall it says certain items cannot be uninstalled and the later released version will not install Win7-KB3134760-x86.msu .
Regards

RalphG · Aug 28, 2016

Managed to uninstall kb3066439 by changing the date to 1 sep 2015 and it uninstalled changed date to today and ran surt log should be attached
Regards

zcomputerwiz · Aug 29, 2016

Code:

Checking Component Store
(w)	CSI Catalog Expired	0x800B0101	winsxs\Catalogs\e14f6d64ebc5847ec787136462e8c408c82910a8512953951aedb734c73fbbac.cat	win8ip-micr..anguagepack_31bf3856ad364e35_7.3.7601.933_33b2ae78d235ea88	
(f)	CSI Manifest Zero Length	0x00000000	winsxs\Manifests\x86_1ad5a19b387a83310adeff9dcf94da71_b77a5c561934e089_6.1.7601.18410_none_57a61dea1ca815ba.manifest	x86_1ad5a19b387a83310adeff9dcf94da71_b77a5c561934e089_6.1.7601.18410_none_57a61dea1ca815ba	
(w)	CSI Catalog Expired	0x800B0101	winsxs\Catalogs\3bbb06f313a98f46f75414918820d668ec138d1c5502d7239fb3509394ec6405.cat	web-service..anguagepack_31bf3856ad364e35_7.3.7601.933_725fc3345ea7cb41	
(w)	CSI Catalog Expired	0x800B0101	winsxs\Catalogs\b7254ded1ee44309cf1be919dd10222e4173c23bc72ca096a88edcf8fbe579b7.cat	microsoft-n..anguagepack_31bf3856ad364e35_7.3.7601.933_f1d8bc5dd17f682b	
(f)	CSI Manifest Zero Length	0x00000000	winsxs\Manifests\x86_94deee6ac5d61c823afa9633087ca95f_b03f5f7f11d50a3a_6.1.7601.22617_none_43ee5fdf927097ba.manifest	x86_94deee6ac5d61c823afa9633087ca95f_b03f5f7f11d50a3a_6.1.7601.22617_none_43ee5fdf927097ba	
(f)	CSI Manifest Missing	0x00000002	amd64_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_d58a6d64ab65b396.manifest	amd64_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_d58a6d64ab65b396	
(f)	CSI Manifest Missing	0x00000002	amd64_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_499a1b14d5902dfc.manifest	amd64_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_499a1b14d5902dfc	
(f)	CSI Manifest Missing	0x00000002	amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2.manifest	amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2	
(f)	CSI C Mark Deployment Missing	0x00000000	c!avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_0b20a8ff883c3a4a	x86_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_1d37a43bbfe1dc9c	
(f)	CSI C Mark Deployment Missing	0x00000000	c!avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_c373722873c01144	amd64_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_d58a6d64ab65b396	
(f)	CSI C Mark Deployment Missing	0x00000000	c!avast.vc140.mfc_fcc99ee6193ebbca_14.0.24210.0_49391d6d8244622b	x86_avast.vc140.mfc_fcc99ee6193ebbca_14.0.24210.0_none_a338d8ea2df29efb	
(f)	CSI C Mark Deployment Missing	0x00000000	c!policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_ef17e13d91c55d96	amd64_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_499a1b14d5902dfc	
(f)	CSI C Mark Deployment Missing	0x00000000	c!policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_36c51814a641869c	x86_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_914751ebea0c5702	
(f)	CSI C Mark Deployment Missing	0x00000000	c!avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_020285fe6d6e0580	amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2	
(f)	CSI C Mark Deployment Missing	0x00000000	c!policy.14.0.avast.vc140.mfc_fcc99ee6193ebbca_14.0.24210.0_364e78aca69bba41	x86_policy.14.0.avast.vc140.mfc_fcc99ee6193ebbca_14.0.24210.0_none_962753dde6e08635

Good job :)

Are you currently using Avast! antivirus or is it no longer installed?

RalphG · Aug 29, 2016

Hi, yes using the free Avast version 12.3.2280
Regards
Ralph

RalphG · Aug 29, 2016

uninstalled Avast and used removal tool, then reinstalled Avast 12.3.2280

RalphG · Aug 31, 2016

please find updated check sur log

BrianDrab · Sep 4, 2016

Hi RalphG -

I'm going to step in and assist. zcomputerwiz is not available at the moment. Please do the following.

1. Uninstall Avast
2. Perform the instructions from the following link. Make sure to use the instructions from the Manifest is missing (manifest is missing) section.
https://www.sysnative.com/forums/wi...avast-causing-corrupt-manifest-files-fix.html
3. Don't re-install Avast yet.
4. Run SURT again and provide the resulting CheckSUR.log.

RalphG · Sep 4, 2016

Hi, the instructions are for windows 10 I am currently running windows 7 ultimate 32 bit can you confirm to run this?

BrianDrab · Sep 4, 2016

Yes I can confirm. thanks.

RalphG · Sep 5, 2016

Uninstalled avast but script came up with error attached

[SOLVED] sfc has corruption cannot fix

Well-known member

Attachments

Well-known member

Windows Update Expert

Well-known member

Attachments

Well-known member

Attachments

Windows Update Expert

Well-known member

Windows Update Expert

Well-known member

Windows Update Expert

Well-known member

Well-known member

Attachments

Windows Update Expert

Well-known member

Well-known member

Well-known member

Attachments

Emeritus

Well-known member

Emeritus

Well-known member

Attachments