DISM.exe fails with error (manifestfile contaisn one or more syntax errors)

martenvelen · Apr 4, 2016

I tried to fix a virtual machine where the Windows Updates fails with error code 800f0831

chdsk /r and sfc /scannow did not solve the problem

Attached is the logfile of DISM

How can we fix this?

zcomputerwiz · Apr 7, 2016

Hello and Welcome!

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.

martenvelen · Apr 8, 2016

zcomputerwiz said:
Hello and Welcome!

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.

didn't I already do this in my initial post? The logfile is already attached

zcomputerwiz · Apr 8, 2016

I'll need the other log file, C:\Windows\Logs\CBS\CBS.log :smile9:

martenvelen · Apr 11, 2016

Did a new run, here are the files

zcomputerwiz · Apr 11, 2016

Code:

2016-04-11 10:49:33, Info                  CBS    
=================================
Checking System Update Readiness.

(w)	CBS Watchlist Package Missing	0x80070490	Microsoft-Windows-ServerCore-FullServer-ExtraFoundation-Package-shell~31bf3856ad364e35~amd64~hr-HR~0.0.0.0	Package_for_KR2876415~31bf3856ad364e35~amd64~~6.2.1.1	
(w)	CBS Watchlist Package Missing	0x80070490	WinPE-NetFx4-Package~31bf3856ad364e35~amd64~ar-SA~0.0.0.0	Packawe_for_KB2737084~31bf3856ad364e35~amd64~~6.2.1.0	

Summary:
Operation: Detect and Repair 
Operation result: 0x800736b5
Last Successful Step: CBS store detection completes.
Total Detected Corruption:	2
	CBS Manifest Corruption:	0
	CBS Metadata Corruption:	2
	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:	False

Total Operation Time: 1572 seconds.

2016-04-11 10:49:33, Info                  CBS    SQM: CheckSur: hrStatus: 0x800736b5 [ERROR_SXS_MANIFEST_PARSE_ERROR], download Result: 0x0 [S_OK]

Notice the missing packages:
Package_for_KR2876415~31bf3856ad364e35~amd64~~6.2.1.1
Packawe_for_KB2737084~31bf3856ad364e35~amd64~~6.2.1.0

This suggests registry corruption, which may be caused by bad RAM.
Has this VM been moved to another host?

Please follow the instructions here to test the RAM in your physical host machine: https://www.sysnative.com/forums/hardware-tutorials/3909-test-ram-memtest86.html

Let me know the results.

martenvelen · Apr 12, 2016

Yes, I noticed these weird typos. But the RAM was already changed and completely new RAM modules were installed.

No, the host is still the same but the RAM was changed after one module caused BSOD but these don't occur anymore.

Should we replace the whole RAM again? How can we fix these issues with the registry? We can not run Memtest86+ on this machine as we have to access the VMs running on the host and work with them on a daily basis.

If it is the RAM, should't the messages / errors be different each time? Because it is always the same with these 2 as it seems.

zcomputerwiz · Apr 13, 2016

Since you have already diagnosed and replaced the bad RAM no further testing is required.

Let's take a look at the CBS branch of the Software hive:

Export Component Based Servicing

Click on the Start button and in the search box, type regedit
When you see regedit on the list, right-click on it and select Run as administrator
When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\
Once selected, click File > Export....
Change the Save as type: to Registry Hive Files (*.*)
Name this file ComponentBasedServicing (with no file extension) and save it to your Desktop.
Right Click on the ComponentBasedServicing file on your Desktop and choose Send To -> Compressed (Zipped) Folder.

Once done please upload ComponentBasedServicing.zip via DropBox OneDrive or SendSpace and include the link with your reply.

martenvelen · Apr 18, 2016

View attachment 20307

15MB unzipped, 2MB zipped

zcomputerwiz · Apr 18, 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.

martenvelen · Apr 20, 2016

zcomputerwiz said:
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 20312

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.

attached both files

zcomputerwiz · Apr 20, 2016

Code:

2016-04-20 10:28:56, Info                  CBS    
=================================
Checking System Update Readiness.


Summary:
Operation: Detect and Repair 
Operation result: 0x800736b5
Last Successful Step: CBS store detection 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:	False

Total Operation Time: 2171 seconds.

2016-04-20 10:28:56, Info                  CBS    SQM: CheckSur: hrStatus: 0x800736b5 [ERROR_SXS_MANIFEST_PARSE_ERROR], download Result: 0x0 [S_OK]

Looks like that worked.

Let's see if SFC can find out which manifest it can't parse.

Step 2 - SFC Scan

Swipe in from the right edge of the screen, and then tap Search.
(If you're using a mouse, point to the upper-right corner of the screen, move the mouse pointer down, and then click Search.)
Type cmd in the search box, and then right-click or press and hold on Command Prompt.
Tap or click Run as administrator.
When command prompt opens, copy and paste the following commands into it, press enter after each

sfc /scannow

Wait for this to finish before you continue

copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt
This will create a file, cbs.txt on your Desktop. Please attach this to your next post.

martenvelen · Apr 21, 2016

here is the file

zcomputerwiz · Apr 21, 2016

Code:

  (3)  Stage (1): flags: 8 app: [Microsoft-Windows-WindowsUpdateClient-ActiveX, Version = 7.8.9200.16924, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral]) comp: (null) man: @0x94b27b9708
2016-04-21 16:15:15, Error                 CSI    00000725@2016/4/21:14:15:15.101 (F) base\wcp\componentstore\versionedindex.cpp(3434): Store corruption detected in function ComponentStore::CRawStoreLayout::CheckFamilyIndexForDeadWinnerComponent expression: (null)
  MissingWinningComponentKey on resource [100]"amd64_microsoft-windows-w..pdateclient-activex_31bf3856ad364e35_7.8.9200.16733_none_3a8661a53058494c"[gle=0x80004005]

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.

martenvelen · Apr 22, 2016

Code:

SFCFix version 3.0.0.0 by niemiro.
Start time: 2016-04-22 08:48:47.424
Microsoft Windows Server 2012  - amd64
Using .zip script file at C:\Users\Admin\Desktop\Fix\SFCFix (2).zip [0]








RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-w..pdateclient-activex_31bf3856ad364e35_7.8.9200.16733_none_3a8661a53058494c.


Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-w..pdateclient-activex_31bf3856ad364e35_7.8.9200.16733_none_3a8661a53058494c.


Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-w..pdateclient-activex_31bf3856ad364e35_7.8.9200.16733_none_3a8661a53058494c.
RegistryScript:: directive completed successfully.








Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 3 datablocks.
Finish time: 2016-04-22 08:48:51.417
Script hash: /Fk/jqRSMlbH4zh1fmN9905WgpNTB3IY3XkCXOPeC8c=
----------------------EOF-----------------------

zcomputerwiz · Apr 22, 2016

Code:

2016-04-22 09:30:43, Info                  CBS    Applicability(ComponentAnalyzerEvaluateSelfUpdate): Component: amd64_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.2.9200.20683_sl-si_c415d7d56b623d0c, elevate: 2, applicable(true/false): 0
2016-04-22 09:30:43, Info                  CBS    Failed to enumerate store versions on component: amd64_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.2.9200.20683_sr-..-cs_639f5467e4baa054 [HRESULT = 0x80070057 - E_INVALIDARG]
2016-04-22 09:30:43, Info                  CBS    Failed to enumerate related component versions on component: amd64_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.2.9200.20683_sr-..-cs_639f5467e4baa054 [HRESULT = 0x80070057 - E_INVALIDARG]

Looks like the fix worked and we have another error to look at.

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.

martenvelen · Apr 25, 2016

Here is the zipped COMPONENTS file

Download COMPONENTS.zip from Sendspace.com - send big files the easy way

zcomputerwiz · Apr 27, 2016

I don't see that particular key, so please try checking for Windows Updates and install any that are offered.

If the updates fail to install, zip and attach CBS.log with your reply.

zcomputerwiz · Apr 27, 2016

Never mind, found it.
It's another bitflip in this value:

Code:

"Package_11_for_KB2836988~31bf3856ad364e35~amd64~~6.2.1.0.Trigger_1"="6.2.9200.206း3@@2"

It should look like this:

Code:

"Package_11_for_KB2836988~31bf3856ad364e35~amd64~~6.2.1.0.Trigger_1"="6.2.9200.20683@@2"

Let's fix it.
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

martenvelen · Apr 28, 2016

done

Code:

SFCFix version 3.0.0.0 by niemiro.
Start time: 2016-04-28 09:10:53.825
Microsoft Windows Server 2012  - amd64
Using .zip script file at C:\Users\Admin\Desktop\Fix\SFCFix.zip [0]








RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-i..timezones.resources_31bf3856ad364e35_0.0.0.0_sr-..-cs_8a459de7425f9708.


WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-i..timezones.resources_31bf3856ad364e35_0.0.0.0_sr-..-cs_8a459de7425f9708.


Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-i..timezones.resources_31bf3856ad364e35_0.0.0.0_sr-..-cs_8a459de7425f9708.


Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-i..timezones.resources_31bf3856ad364e35_0.0.0.0_sr-..-cs_8a459de7425f9708.
RegistryScript:: directive completed successfully.








Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 4 datablocks.
Finish time: 2016-04-28 09:10:56.757
Script hash: jJwv57vu1xhOMXMGrYrpf6vqCA5Kgp02Gk/4GgfRUgI=
----------------------EOF-----------------------

DISM.exe fails with error (manifestfile contaisn one or more syntax errors)

Member

Attachments

Windows Update Expert

Member

Windows Update Expert

Member

Attachments

Windows Update Expert

Member

Windows Update Expert

Member

Windows Update Expert

Member

Attachments

Windows Update Expert

Member

Attachments

Windows Update Expert

Member

Attachments

Windows Update Expert

Member

Windows Update Expert

Windows Update Expert

Member