Error in SBS2011 Server Manager. System Update Readiness Tool problems

Hi there fellow forumers,

First of all let me say that i have read a topic on this subject, posted on this forum(System Update Readiness Tool - CheckSur.log File Analyzis) and went through the suggested methods of fixing this type of problem before posting here.

The description of the problem would be that in SBS2011, which is a variant of 2008R2, if i open server manager i cannot view roles and features. As suggested, i have downloaded the System Update Readiness Tool (KB947821) and ran it, without any effect on the problem. I then proceeded to analyse the CheckSur.log as described in the above link, but also in the windows advanced guidelines for servicing corruption.
The CheckSur.log reports the following problem at the bottom of the page:

Unavailable repair files:
winsxs\manifests\amd64_microsoft-hyper-v-deployment_31bf3856d364e35_6.1.7600.16385_none_8883d99c0907d5dc.manifest
winsxs\manifests\amd64_microsoft-windows-lsa-msprivs.resources_31bf3856ad364e35_6.1.7600.16385_sv-se_a86f224d5acff0fÙ.manifest

As these are manifests, i attempted to copy the files to %Windir%\Temp\CheckSUR\winsxs\manifests\ by mounting a Windows SBS 2011 Standard disk and extracting the files. I was only able to find the following manifest files in the mounted disk:

amd64_microsoft-hyper-v-deployment_31bf3856ad364e35_6.1.7600.16385_none_8883d99c0907d5dc.manifest

and

amd64_microsoft-windows-lsa-msprivs.resources_31bf3856ad364e35_6.1.7600.16385_sv-se_a86f224d5acff0f9.manifest

If you look carefully, you will see that the first manifest file has an illegal character in its name when displayed in the CheckSUR log, 31bf3856d364e35, in the public key, as well as in the second manifest file name, the last character of the file name is Ù, while i retrieved the same manifest file but with a 9 instead. I copied these retrieved files to C:\Windows\Temp\CheckSUR\winsxs\Manifests\ and ran the Readiness tool again. No change.

I then proceeded to analyze the COMPONENTS hive in the registry, in order to locate the string with the same name in CanonicalData\Deployments as in subkey in Catalogs, which would point to the Windows Update from where i can extract it. Unfortunately, there is no string pointing to a windows KB update, so that would mean it's native component and the only files are the ones that i retrieved from the installation disk.

I am wondering if it's because the two manifest files are misspelled in the CheckSUR log, that the readiness tool cannot find them and use them in the winsxs location where i have placed them. Renaming the manifests as they appear in the CheckSUR log is only doable for the second manifest, as the first one contains an illegal character for filenames.

In any case, i am stuck and don't know how to fix this from here.
Your help is much appreciated !

Hi Alex,

IF they are CORE component entries, then i would suggest a repair install, as you have a copy of SBS2011.

follow-up coming about finding those entries in the mean time please download Farbar (FRST)
Download Farbar Recovery Scan Tool


Roy

Hi Roy,

Thank you very much for your reply and sorry for my late response, as we are on different timezones.
I guess we could try a repair of the SBS, which reminds me that i haven't mentioned that this is a virtual machine. I never run a repair install so i am a bit worried that all the software installed on the server will need to be installed again and reconfigured, as i am assuming that the registry will be completely reset even though the hard drive is not formatted.

In the mean time i have downloaded the tool that you suggested and ran a scan. I am attaching the two log files that came as a result.
Also here are the subkeys from CanonicalData\Deployments of the two manifest files:
p!CBS_microsoft-hyper-v-package~31bf3856ad364e35~amd64~~6.1.7600.1_20a41360ac60bded
p!CBS_microsoft-windows-foundation-package~31bf3856ad364e35~amd64~_669c8c63b48c8ee1
p!CBS_microsoft-windows-foundation-package~31bf3856ad364e35~amd64~_56a20b8cc2231cf7

There are three of them as the second manifest had 2 subkeys, one for version 6.1.7600 and the other for 6.1.7601. Please see attached pictures of the registry as well for further confirmation. The tool's log files are named FRST and Addition.

Thanks again for your help with this!
Alex

Hi Alex,

A repair install -
will preserve your user accounts, data, programs, and system drivers.

as for FRST
did you notice the registry search option, input the corrupted data value if its coming from an update it will list it
(based on those 3 lines you posted im gonna plump for NO)

Hyper V is an optional feature - you could try unticking/reticking via WU>> turn features on/off
(in the smaller window that appears)
REBOOT

Can you post the CBS log,
im hoping it will include something like


C:\Windows\logs\CBS\Checksur.log. You should see the following errors: Checking Package Manifests and Catalogs
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\Package_for_KB978601~31bf3856ad364e35~amd64~~6.0.1.0.mum Expected file name Package_for_KB978601_server~31bf3856ad364e35~amd64~~6.0.1.0.mum does not match the actual file name
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\Package_for_KB979309~31bf3856ad364e35~amd64~~6.0.1.0.mum Expected file name Package_for_KB979309_server~31bf3856ad364e35~amd64~~6.0.1.0.mum does not match the actual file name
Or
(f) CBS MUM Corrupt 0x800B0100 servicing\Packages\Package_for_KB978601~31bf3856ad364e35~amd64~~6.0.1.0.mum servicing\Packages\Package_for_KB978601~31bf3856ad364e35~amd64~~6.0.1.0.cat Package manifest cannot be validated by the corresponding catalog
(f) CBS MUM Corrupt 0x800B0100 servicing\Packages\Package_for_KB979309~31bf3856ad364e35~amd64~~6.0.1.0.mum servicing\Packages\Package_for_KB979309~31bf3856ad364e35~amd64~~6.0.1.0.cat Package manifest cannot be validated by the corresponding catalog
Or
(f) CBS MUM Missing 0x00000002 servicing\packages\Package_114_for_KB955839~31bf3856ad364e35~amd64~~6.0.1.0.mum
(f) CBS MUM Missing 0x00000002 servicing\packages\Package_83_for_KB955839~31bf3856ad364e35~amd64~~6.0.1.0.mum




Roy

Note things could get slow Xmas time - family comes first

Hi Roy,

I greatly appreciate your help! As you said, it's Christmas period so i am also off work. I will post the CBS log in the next few days, and also have look at that option that you mentioned in the FRST.

Merry Christmas!
Alex

Hi again Roy,

Here is the CheckSUR log, for when you have time to have a look:



Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f) CSI Corrupt Component Keyform 0x00000000 identity x86_microsoft-windows-security-licensing-slc_31bf3856ad364e35_6.1.7t00.16385_none_4e4dd39d5ad99039 identity and keyform do not match; keyform is wrong.
(f) CSI Missing Deployment Key 0x00000000 prnlx007.in..anguagepack_31bf3856ad364e35_6.1.7600.16385_9d91e7a16f3abada HKLM\Components\CanonicalData\Deployments
(f) CSI Missing Deployment Key 0x00000000 prnlx008.in..anguagepack_31bf3856ad364e35_6.1.7600.16385_9ee620b83ad51d31 HKLM\Components\CanonicalData\Deployments
(f) CSI Missing Deployment Key 0x00000000 prnlx009.in..anguagepack_31bf3856ad364e35_6.1.7600.16385_a03b4078066f7f88 HKLM\Components\CanonicalData\Deployments
(f) CSI Corrupt Identity 0xC0150017 Microsoft-Hyper-V-Deployment, Culture=neutral, Version=6.1.7600.16385, PublicKeyToken=31bf3856ad364e35,%ProcessorArchitecture=amd64, versionScope=NonSxS amd64_microsoft-hyper-v-deployment_31bf3856d364e35_6.1.7600.16385_none_8883d99c0907d5dc Bad identity
(f) CSI Could Not Open file 0x0000007B winsxs\Manifests\amd64_microsoft-hyper-v-deployment_31bf3856d364e35_6.1.7600.16385_none_8883d99c0907d5dc.manifest amd64_microsoft-hyper-v-deployment_31bf3856d364e35_6.1.7600.16385_none_8883d99c0907d5dc
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-hyper-v-deployment_31bf3856d364e35_6.1.7600.16385_none_8883d99c0907d5dc.manifest amd64_microsoft-hyper-v-deployment_31bf3856d364e35_6.1.7600.16385_none_8883d99c0907d5dc
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-hyper-v-deployment_31bf3856d364e35_6.1.7600.16385_none_8883d99c0907d5dc.manifest amd64_microsoft-hyper-v-deployment_31bf3856d364e35_6.1.7600.16385_none_8883d99c0907d5dc
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-hyper-v-deployment_31bf3856d364e35_6.1.7600.16385_none_8883d99c0907d5dc.manifest amd64_microsoft-hyper-v-deployment_31bf3856d364e35_6.1.7600.16385_none_8883d99c0907d5dc
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-hyper-v-deployment_31bf3856d364e35_6.1.7600.16385_none_8883d99c0907d5dc.manifest amd64_microsoft-hyper-v-deployment_31bf3856d364e35_6.1.7600.16385_none_8883d99c0907d5dc
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-hyper-v-deployment_31bf3856d364e35_6.1.7600.16385_none_8883d99c0907d5dc.manifest amd64_microsoft-hyper-v-deployment_31bf3856d364e35_6.1.7600.16385_none_8883d99c0907d5dc
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-hyper-v-deployment_31bf3856d364e35_6.1.7600.16385_none_8883d99c0907d5dc.manifest amd64_microsoft-hyper-v-deployment_31bf3856d364e35_6.1.7600.16385_none_8883d99c0907d5dc
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-hyper-v-deployment_31bf3856d364e35_6.1.7600.16385_none_8883d99c0907d5dc.manifest amd64_microsoft-hyper-v-deployment_31bf3856d364e35_6.1.7600.16385_none_8883d99c0907d5dc
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-hyper-v-deployment_31bf3856d364e35_6.1.7600.16385_none_8883d99c0907d5dc.manifest amd64_microsoft-hyper-v-deployment_31bf3856d364e35_6.1.7600.16385_none_8883d99c0907d5dc
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-hyper-v-deployment_31bf3856d364e35_6.1.7600.16385_none_8883d99c0907d5dc.manifest amd64_microsoft-hyper-v-deployment_31bf3856d364e35_6.1.7600.16385_none_8883d99c0907d5dc
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-hyper-v-deployment_31bf3856d364e35_6.1.7600.16385_none_8883d99c0907d5dc.manifest amd64_microsoft-hyper-v-deployment_31bf3856d364e35_6.1.7600.16385_none_8883d99c0907d5dc
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-hyper-v-deployment_31bf3856d364e35_6.1.7600.16385_none_8883d99c0907d5dc.manifest amd64_microsoft-hyper-v-deployment_31bf3856d364e35_6.1.7600.16385_none_8883d99c0907d5dc
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-hyper-v-deployment_31bf3856d364e35_6.1.7600.16385_none_8883d99c0907d5dc.manifest amd64_microsoft-hyper-v-deployment_31bf3856d364e35_6.1.7600.16385_none_8883d99c0907d5dc
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-hyper-v-deployment_31bf3856d364e35_6.1.7600.16385_none_8883d99c0907d5dc.manifest amd64_microsoft-hyper-v-deployment_31bf3856d364e35_6.1.7600.16385_none_8883d99c0907d5dc
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-hyper-v-deployment_31bf3856d364e35_6.1.7600.16385_none_8883d99c0907d5dc.manifest amd64_microsoft-hyper-v-deployment_31bf3856d364e35_6.1.7600.16385_none_8883d99c0907d5dc
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-hyper-v-deployment_31bf3856d364e35_6.1.7600.16385_none_8883d99c0907d5dc.manifest amd64_microsoft-hyper-v-deployment_31bf3856d364e35_6.1.7600.16385_none_8883d99c0907d5dc
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-hyper-v-deployment_31bf3856d364e35_6.1.7600.16385_none_8883d99c0907d5dc.manifest amd64_microsoft-hyper-v-deployment_31bf3856d364e35_6.1.7600.16385_none_8883d99c0907d5dc
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-hyper-v-deployment_31bf3856d364e35_6.1.7600.16385_none_8883d99c0907d5dc.manifest amd64_microsoft-hyper-v-deployment_31bf3856d364e35_6.1.7600.16385_none_8883d99c0907d5dc
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-hyper-v-deployment_31bf3856d364e35_6.1.7600.16385_none_8883d99c0907d5dc.manifest amd64_microsoft-hyper-v-deployment_31bf3856d364e35_6.1.7600.16385_none_8883d99c0907d5dc
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-hyper-v-deployment_31bf3856d364e35_6.1.7600.16385_none_8883d99c0907d5dc.manifest amd64_microsoft-hyper-v-deployment_31bf3856d364e35_6.1.7600.16385_none_8883d99c0907d5dc
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-hyper-v-deployment_31bf3856d364e35_6.1.7600.16385_none_8883d99c0907d5dc.manifest amd64_microsoft-hyper-v-deployment_31bf3856d364e35_6.1.7600.16385_none_8883d99c0907d5dc
(f) CSI Missing Deployment Key 0x00000000 prnlx00b.in..anguagepack_31bf3856ad364e35_6.1.7600.16385_d6c24e61a2293f77 HKLM\Components\CanonicalData\Deployments
(f) CSI Corrupt Identity 0xC0000161 (not UTF8) amd64_microsoft-windows-lsa-msprivs.resources_31bf3856ad364e35_6.1.7600.16385_sv-se_a86f224d5acff0fÙ Bad identity
(f) CSI Manifest Missing 0x00000002 amd64_microsoft-windows-lsa-msprivs.resources_31bf3856ad364e35_6.1.7600.16385_sv-se_a86f224d5acff0fÙ.manifest amd64_microsoft-windows-lsa-msprivs.resources_31bf3856ad364e35_6.1.7600.16385_sv-se_a86f224d5acff0fÙ
(f) CSI Missing Deployment Key 0x00000000 prnlx006.in..anguagepack_31bf3856ad364e35_6.1.7600.16385_9c3dae8aa3a05883 HKLM\Components\CanonicalData\Deployments
(f) CSI Corrupt Component Keyform 0x00000000 identity amd64_microsoft-windows-t..xtservice-migration_31bf3856ad364e35_6.1.7600.16385_none_32b4588 5b10854m identity and keyform do not match; keyform is wrong.
(f) CSI C Mark Deployment Not Marked 0x00000000 c!microsoft-w..-deployment_31bf3856ad364e35_6.1.7600.16385_4b13adff2a2573ee amd64_microsoft-windows-d..er-tools-deployment_31bf3856ad364e35_6.1.7600.16385_none_4b13adff2a2573ee
(f) CSI C Mark Deployment Not Marked 0x00000000 c!nvraid.inf_31bf3856ad364e35_6.1.7600.20712_96a205e1f19732b1 amd64_nvraid.inf_31bf3856ad364e35_6.1.7600.20712_none_96a205e1f19732b1
(f) CSI C Mark Deployment Not Marked 0x00000000 c!microsoft-w..-deployment_31bf3856ad364e35_6.1.7600.16385_4b13adff2a2573ee amd64_microsoft-windows-dfsn-tools-dfscmd_31bf3856ad364e35_6.1.7600.16385_none_49d9a0605686e042
(f) CSI C Mark Deployment Not Marked 0x00000000 c!microsoft-w..-deployment_31bf3856ad364e35_6.1.7600.16385_4b13adff2a2573ee amd64_microsoft-windows-dfsn-tools-dfsdiag_31bf3856ad364e35_6.1.7600.16385_none_993d97e2bd7cb4a7
(f) CSI C Mark Deployment Not Marked 0x00000000 c!microsoft-w..-deployment_31bf3856ad364e35_6.1.7600.16385_4b13adff2a2573ee amd64_microsoft-windows-dfsn-tools-dfsutil_31bf3856ad364e35_6.1.7600.16385_none_a0583334b8f67fd6

Summary:
Seconds executed: 603
Found 16 errors
CSI Could Not Open file Total count: 1
CSI Manifest Missing Total count: 1
CSI Missing Deployment Key Total count: 5
CSI Corrupt Component Keyform Total count: 2
CSI Corrupt Identity Total count: 2
CSI C Mark Deployment Not Marked Total count: 5
CSI Replacement File: CreateFile Failed Total count: 20

Unavailable repair files:
winsxs\manifests\amd64_microsoft-hyper-v-deployment_31bf3856d364e35_6.1.7600.16385_none_8883d99c0907d5dc.manifest
winsxs\manifests\amd64_microsoft-windows-lsa-msprivs.resources_31bf3856ad364e35_6.1.7600.16385_sv-se_a86f224d5acff0fÙ.manifest


I also did used the search option from the tool that i downloaded and found the string with the corrupt data, but i still can't tell if it's coming from an update, here are the search results:

================== Search Registry: "31bf3856d364e35_6.1.7600.16385" ===========

[HKEY_LOCAL_MACHINE\Corp COMPONENTS\DerivedData\Components\amd64_microsoft-hyper-v-deployment_31bf3856d364e35_6.1.7600.16385_none_8883d99c0907d5dc]

====== End of Search ======


================== Search Registry: "sv-se_a86f224d5acff0fÙ" ===========

[HKEY_LOCAL_MACHINE\Corp COMPONENTS\DerivedData\Components\amd64_microsoft-windows-lsa-msprivs.resources_31bf3856ad364e35_6.1.7600.16385_sv-se_a86f224d5acff0fÙ]

====== End of Search ======


Thanks again and enjoy you Christmas holidays with you family!
Alex

Hi Alex,

bad news

Unfortunately i do not have some of the required files to send you - HyperV
also the corruption for this also appears in the components hive
Which is not my area

GOOD news

Try the Sysnative Forum, they have a far more extensive library of manifests/files etc than me
Please run thier fix tool, and post the latest cbs log
http://www.sysnative.com/niemiro/apps/SFCFix.exe


The illegal character Ù should be a 9, a bit flip error

i could supply a partial fix but its better to keep it under one hat.

Roy

Thank you for all your effort you put on to help me Roy, i will give it a try on the Sysnative Forum.

Have a happy new year!
Alex