Hi there fellow forumers,
First of all let me say that i have read a topic on this subject, posted on this forum(https://www.sevenforums.com/tutoria...eadiness-tool-checksur-log-file-analyzis.html) 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 !
First of all let me say that i have read a topic on this subject, posted on this forum(https://www.sevenforums.com/tutoria...eadiness-tool-checksur-log-file-analyzis.html) 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 !
My Computer
- Computer type
- PC/Desktop
- OS
- 2008R2 64 bit
