[SOLVED] Win 8.1 Pro with Media Center "manifest is damaged"

Geek · Jun 11, 2016

Hi Sysnative!

We have a piece of 3rd party software (E p i c o r E a g l e 25.0 client) that crashes and we do not have media to re-install. I am trying to get the software from the vendor, but they are blaming Windows so I am trying to eliminate all errors in Windows.

Running the Windows SFC command, I found about 6 errors. Using dism and the RestoreHealth switch, I was able to fix 4 of the errors and another was introduced.

The remaining 3 errors are all tagged "manifest is damaged". Here they are:

2016-06-10 15:05:00, Info CSI 0000059d [SR] Cannot verify component files for NetFx-System, Version = 6.3.9600.20922, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:b03f5f7f11d50a3a}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)

2016-06-10 15:06:44, Info CSI 00000686 [SR] Cannot verify component files for System.Resources, Version = 6.3.9600.20922, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture = [l:10{5}]"en-us", VersionScope neutral, PublicKeyToken = {l:8 b:b77a5c561934e089}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)

2016-06-10 15:06:51, Info CSI 00000693 [SR] Cannot verify component files for System, Version = 6.3.9600.20922, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:b77a5c561934e089}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)

I was reading that I would have to do a Windows Repair, but seeing that I have Windows 8 Pro with Media Center, I've read about problems with activation keys and iso images not matching. The previous owner threw away all software and any keys, so I am left with trying to identify the current keys which I've read can be problematic with the Media Center add-on. Anyway...

So I saw this wonderful site that helps people fix errors found in SFC! I downloaded the SFCFix tool and ran it. Here are the results:

SFCFix version 3.0.0.0 by niemiro.

Start time: 2016-06-11 16:28:54.402

Microsoft Windows 8.1 Update 3 - amd64

Not using a script file.

AutoAnalysis::

SUMMARY: No corruptions were detected.

AutoAnalysis:: directive completed successfully.

Successfully processed all directives.

SFCFix version 3.0.0.0 by niemiro has completed.

Currently storing 0 datablocks.

Finish time: 2016-06-11 16:45:38.325

----------------------EOF-----------------------

I was a little surprised no errors were found, and now I'm wondering if I'm making a mountain out of a molehill... or if I'm really in deep.

I've zipped the CBS folder and will attach. UPDATE: It seems I'll have to use the dropbox script after creating this post.

Any advice you can give me would be greatly appreciated!

Thanks,
Geek

LogBot · Jun 11, 2016

Logfile submission from Geek

Logfile submission from Geek.

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

zcomputerwiz · Jun 14, 2016

The following manifests are reported corrupt:

Code:

amd64_netfx-system_b03f5f7f11d50a3a_6.3.9600.20922_none_ef0cfe5e1ee455fe.manifest
msil_system.resources_b77a5c561934e089_6.3.9600.20922_en-us_9735d86ab8517cbc.manifest
msil_system_b77a5c561934e089_6.3.9600.20922_none_dec9891839b02a29.manifest

Please manually upload the components hive by following these instructions:

Upload Components Hive

Navigate to C:\Windows\System32\config
Right-click on the current COMPONENTS file and select copy
Note: If you get an error that the file is in use, reboot your computer and then try again.
Right-click on your Desktop and select paste
Right-click on the COMPONENTS file on your Desktop and select Send To -> Compressed (zipped) Folder
Upload the zip from your Desktop to a file sharing service such as DropBox, OneDrive, SendSpace, etc. and include the link with your reply.

Geek · Jun 14, 2016

Thank you for helping me, zcomputerwiz!

https://dl.dropboxusercontent.com/u/16541214/COMPONENTS.zip

zcomputerwiz · Jun 15, 2016

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

Download SFCFix.exe (by niemiro) and save this to your Desktop.
Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
SFCFix will now process the script.
Upon completion, a file should be created on your Desktop: SFCFix.txt.
Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

View attachment SFCFix.zip

DISM /RestoreHealth Scan

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

Right-click on the Start

button and select Command Prompt (Admin)
When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter

Dism /Online /Cleanup-Image /RestoreHealth
When DISM finishes scanning your component store, zip up and attach your CBS log to your next post:

C:\Windows\Logs\CBS\CBS.log

If the zip file is larger than 8MB, please use a file sharing service such as OneDrive, DropBox, SendSpace, etc. and include the link with your reply.

Geek · Jun 16, 2016

Here is the SFCFix.txt. It looks good!

Code:

SFCFix version 3.0.0.0 by niemiro.
Start time: 2016-06-11 17:28:20.545
Microsoft Windows 8.1 Update 3 - amd64
Using .txt script file at C:\Users\debbiem\Desktop\SFCFixScript.txt [1]








Collect:: directive completed successfully.








Successfully processed all directives.
Using .zip script file at C:\Users\debbiem\Desktop\SFCFix.zip [0]








PowerCopy::
Successfully took permissions for file or folder C:\Windows\WinSxS\manifests\amd64_netfx-system_b03f5f7f11d50a3a_6.3.9600.20922_none_ef0cfe5e1ee455fe.manifest
Successfully took permissions for file or folder C:\Windows\WinSxS\manifests\msil_system.resources_b77a5c561934e089_6.3.9600.20922_en-us_9735d86ab8517cbc.manifest
Successfully took permissions for file or folder C:\Windows\WinSxS\manifests\msil_system_b77a5c561934e089_6.3.9600.20922_none_dec9891839b02a29.manifest


Successfully copied file C:\Users\debbiem\AppData\Local\niemiro\Archive\WinSxS\manifests\amd64_netfx-system_b03f5f7f11d50a3a_6.3.9600.20922_none_ef0cfe5e1ee455fe.manifest to C:\Windows\WinSxS\manifests\amd64_netfx-system_b03f5f7f11d50a3a_6.3.9600.20922_none_ef0cfe5e1ee455fe.manifest.
Successfully copied file C:\Users\debbiem\AppData\Local\niemiro\Archive\WinSxS\manifests\msil_system.resources_b77a5c561934e089_6.3.9600.20922_en-us_9735d86ab8517cbc.manifest to C:\Windows\WinSxS\manifests\msil_system.resources_b77a5c561934e089_6.3.9600.20922_en-us_9735d86ab8517cbc.manifest.
Successfully copied file C:\Users\debbiem\AppData\Local\niemiro\Archive\WinSxS\manifests\msil_system_b77a5c561934e089_6.3.9600.20922_none_dec9891839b02a29.manifest to C:\Windows\WinSxS\manifests\msil_system_b77a5c561934e089_6.3.9600.20922_none_dec9891839b02a29.manifest.


Successfully restored ownership for C:\Windows\WinSxS\manifests\amd64_netfx-system_b03f5f7f11d50a3a_6.3.9600.20922_none_ef0cfe5e1ee455fe.manifest
Successfully restored permissions on C:\Windows\WinSxS\manifests\amd64_netfx-system_b03f5f7f11d50a3a_6.3.9600.20922_none_ef0cfe5e1ee455fe.manifest
Successfully restored ownership for C:\Windows\WinSxS\manifests\msil_system.resources_b77a5c561934e089_6.3.9600.20922_en-us_9735d86ab8517cbc.manifest
Successfully restored permissions on C:\Windows\WinSxS\manifests\msil_system.resources_b77a5c561934e089_6.3.9600.20922_en-us_9735d86ab8517cbc.manifest
Successfully restored ownership for C:\Windows\WinSxS\manifests\msil_system_b77a5c561934e089_6.3.9600.20922_none_dec9891839b02a29.manifest
Successfully restored permissions on C:\Windows\WinSxS\manifests\msil_system_b77a5c561934e089_6.3.9600.20922_none_dec9891839b02a29.manifest
PowerCopy:: directive completed successfully.








Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 3 datablocks.
Finish time: 2016-06-16 11:25:58.028
Script hash: RVgi7te17t39BIaUP/4Qo2KxqNxcqvF9sSCO8gdERhY=
----------------------EOF-----------------------

I'll run DISM and post the CBS.log next...

Geek · Jun 16, 2016

Here is the CBS.log file zipped up:

zcomputerwiz · Jun 16, 2016

Code:

2016-06-16 11:45:23, Info                  CBS    
=================================
Checking System Update Readiness.


Summary:
Operation: Detect and Repair 
Operation result: 0x0
Last Successful Step: Entire operation completes.
Total Detected Corruption:	0
	CBS Manifest Corruption:	0
	CBS Metadata Corruption:	0
	CSI Manifest Corruption:	0
	CSI Metadata Corruption:	0
	CSI Payload Corruption:	0
Total Repaired Corruption:	0
	CBS Manifest Repaired:	0
	CSI Manifest Repaired:	0
	CSI Payload Repaired:	0
	CSI Store Metadata refreshed:	True

Total Operation Time: 932 seconds.

2016-06-16 11:45:23, Info                  CBS    SQM: CheckSur: hrStatus: 0x0 [S_OK], download Result: 0x0 [S_OK]

Looks good!

Run SFC again, and when it completes zip and attach CBS.log with your reply.

Geek · Jun 16, 2016

Thank you!
Thank you!
Thank you!

I will run SFC again and post the new CBS.log.

Can I ask, in your experience, have you found specific things that cause manifests to get damaged? It seemed odd to me that DISM can fix some but not others, especially since the fix seemed to be replacing the damaged ones with good copies.

I guess I'm just looking for some insight into how these things happen (and how to avoid), how often it happens, and what are the signs and potential problems of having damaged manifests?

Geek · Jun 16, 2016

Here's the latest CBS.log file zipped.

Thanks again!

View attachment CBS.zip

zcomputerwiz · Jun 16, 2016

I can only say that in my experience Windows Update servicing problems are sometimes associated with hardware problems (bad RAM, HDD) or unexpected power events (power outage, computer turned off while updating, etc.).

If manifests are damaged it will prevent SFC and DISM from verifying system files associated with those manifests, which may also prevent new updates from successfully installing.

If you would like to check the health of your disk, try this:

GSmartControl
Follow the instructions below to test your hard drive health with GSmartControl:

Download GSmartControl and save it on your Desktop;
Extract the content of the GSmartControl .zip archive and execute gsmartcontrol.exe; To extract you can right-click your mouse on the GSmartControl.zip file and select Extract.
Identify your drive in the list, and double-click on it to bring up it's window (usually you'll find your drive by it's size or it's brand name);
Go in the Perform Tests tab, then select Extended Self-test in the Test type drop-down list and click on Execute (this test can take a few hours to complete);
Once the test is over, the results will be displayed at the bottom of the window. Please copy and paste these results in your next reply;
Also, go in the Attributes tab and if you have any entries highlighted in red or pink, copy and paste their name in your next reply (or take a screenshot of the GSmartControl window and attach it in your next reply);

Geek · Jun 17, 2016

Thanks. The drive is clean:

This PC has had virus infections in the past. It's several years old. I wonder if that would cause corruption...

zcomputerwiz · Jun 17, 2016

That drive does look good :)

Virus infections may certainly interfere with Windows Updates, and could cause unexpected restarts etc. which may explain the corrupt manifests.

Is everything functioning as expected at this point?

Geek · Jun 17, 2016

Everything "Windows" is functioning, but the 3rd party software is still crashing. Even after a re-install. It seems to be a network issue perhaps. Thank you for your help!

zcomputerwiz · Jun 20, 2016

Glad to help!

I'll mark the thread solved. If you require further assistance, please post back and I will continue to assist you.

[SOLVED] Win 8.1 Pro with Media Center "manifest is damaged"

Geek

Member

LogBot

Well-known member

zcomputerwiz

Windows Update Expert

Geek

Member

zcomputerwiz

Windows Update Expert

Geek

Member

Geek

Member

Attachments

zcomputerwiz

Windows Update Expert

Geek

Member

Geek

Member

zcomputerwiz

Windows Update Expert

Geek

Member

zcomputerwiz

Windows Update Expert

Geek

Member

zcomputerwiz

Windows Update Expert