[SOLVED] Windows Server 2008 R2 error viewing features and roles

ammexico · Sep 22, 2016

I will reboot during maintenance window tonight and follow up with you tomorrow.

zcomputerwiz · Sep 22, 2016

Very good. Thanks :)

ammexico · Sep 23, 2016

There was one error while running the script

Code:

SFCFix version 3.0.0.0 by niemiro.
Start time: 2016-09-23 09:56:18.852
Microsoft Windows Server 2008 R2 Service Pack 1 - amd64
Using .zip script file at C:\Users\hbramont.CFMM\Desktop\SFCFix.zip [2]




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\1883f7df6db..53c2a527a41_31bf3856ad364e35_8.0.7601.17537_98c3cd12b345bd72.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\22d1e327a6b..8d2fa772562_6595b64144ccf1df_5.~~6.1.1.0.2296_4d07bb9b678f683.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\2e18f52dc38..07c4527b44e_31bf3856ad364e35_8.0.7601.17579_20db61f5937e4a1a.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\361df218835..597fb498b7a_31bf3856ad364e35_6.1.7601.17537_2a55c15d5d9e5f91.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\394446527dd..236cd488597_31bf3856ad364e35_6.1.7601.17571_6873a7882342cac2.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\5be0be1636f..c44015bda84_31bf3856ad364e35_6.1.7601.17609_b4f0df61f9083567.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\9c076e57253..e8b316bfeb7_31bf3856ad364e35_8.0.7601.17634_880aab4c1e04de45.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\c31879c945d..423bdb6cbfb_31bf3856ad364e35_6.1.7601.17537_9eaecc6a7fb5572d.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\daf566dfc6a..93b41bf170b_31bf3856ad364e35_8.0.7601.17562_993116c19c05cbf9.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\e09122b2d71..884aeffa348_31bf3856ad364e35_8.0.7601.17535_7d3f1774f65a6bf9.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.4053_d1c738ec43578ea1.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4148_5090ab56bcba71c2.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\wow64_microsoft-windows-iis-corewebengine_31bf3856ad364e35_6.1.7600.16385_none_35f3a420775685bf.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-activexcompat_31bf3856ad364e35_8.0.7601.17579_none_12cf71b9d8fec2d5.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.762_none_11ecb0ab9b2caf3c.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_policy.9.0.microsoft.vc90.mfcloc_1fc8b3b9a1e18e3b_9.0.30729.1_none_818f59bf601aa775.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\Components\CanonicalData\Deployments.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\1883f7df6db..53c2a527a41_31bf3856ad364e35_8.0.7601.17537_98c3cd12b345bd72.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\22d1e327a6b..8d2fa772562_6595b64144ccf1df_5.~~6.1.1.0.2296_4d07bb9b678f683.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\2e18f52dc38..07c4527b44e_31bf3856ad364e35_8.0.7601.17579_20db61f5937e4a1a.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\361df218835..597fb498b7a_31bf3856ad364e35_6.1.7601.17537_2a55c15d5d9e5f91.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\394446527dd..236cd488597_31bf3856ad364e35_6.1.7601.17571_6873a7882342cac2.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\5be0be1636f..c44015bda84_31bf3856ad364e35_6.1.7601.17609_b4f0df61f9083567.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\9c076e57253..e8b316bfeb7_31bf3856ad364e35_8.0.7601.17634_880aab4c1e04de45.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\c31879c945d..423bdb6cbfb_31bf3856ad364e35_6.1.7601.17537_9eaecc6a7fb5572d.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\daf566dfc6a..93b41bf170b_31bf3856ad364e35_8.0.7601.17562_993116c19c05cbf9.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\e09122b2d71..884aeffa348_31bf3856ad364e35_8.0.7601.17535_7d3f1774f65a6bf9.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\f02270b20fa..f77f97e60b6_31bf3856ad364e35_6.1.7600.20621_a3ebe8236e0f58a5.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.4053_d1c738ec43578ea1.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4148_5090ab56bcba71c2.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\wow64_microsoft-windows-iis-corewebengine_31bf3856ad364e35_6.1.7600.16385_none_35f3a420775685bf.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-activexcompat_31bf3856ad364e35_8.0.7601.17579_none_12cf71b9d8fec2d5.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.762_none_11ecb0ab9b2caf3c.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_policy.9.0.microsoft.vc90.mfcloc_1fc8b3b9a1e18e3b_9.0.30729.1_none_818f59bf601aa775.
Successfully imported registry key HKEY_LOCAL_MACHINE\Components\CanonicalData\Deployments\ed3d2bdde4c..a11ee4fa4e1_31bf3856ad364e35_6.1.7600.21136_963d948268a687c0.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\1883f7df6db..53c2a527a41_31bf3856ad364e35_8.0.7601.17537_98c3cd12b345bd72.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\22d1e327a6b..8d2fa772562_6595b64144ccf1df_5.~~6.1.1.0.2296_4d07bb9b678f683 with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\2e18f52dc38..07c4527b44e_31bf3856ad364e35_8.0.7601.17579_20db61f5937e4a1a.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\361df218835..597fb498b7a_31bf3856ad364e35_6.1.7601.17537_2a55c15d5d9e5f91.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\394446527dd..236cd488597_31bf3856ad364e35_6.1.7601.17571_6873a7882342cac2.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\5be0be1636f..c44015bda84_31bf3856ad364e35_6.1.7601.17609_b4f0df61f9083567.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\9c076e57253..e8b316bfeb7_31bf3856ad364e35_8.0.7601.17634_880aab4c1e04de45.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\c31879c945d..423bdb6cbfb_31bf3856ad364e35_6.1.7601.17537_9eaecc6a7fb5572d.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\daf566dfc6a..93b41bf170b_31bf3856ad364e35_8.0.7601.17562_993116c19c05cbf9.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\e09122b2d71..884aeffa348_31bf3856ad364e35_8.0.7601.17535_7d3f1774f65a6bf9.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\f02270b20fa..f77f97e60b6_31bf3856ad364e35_6.1.7600.20621_a3ebe8236e0f58a5.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.4053_d1c738ec43578ea1.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4148_5090ab56bcba71c2.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\wow64_microsoft-windows-iis-corewebengine_31bf3856ad364e35_6.1.7600.16385_none_35f3a420775685bf.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-activexcompat_31bf3856ad364e35_8.0.7601.17579_none_12cf71b9d8fec2d5.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.762_none_11ecb0ab9b2caf3c.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_policy.9.0.microsoft.vc90.mfcloc_1fc8b3b9a1e18e3b_9.0.30729.1_none_818f59bf601aa775.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\Components\CanonicalData\Deployments\ed3d2bdde4c..a11ee4fa4e1_31bf3856ad364e35_6.1.7600.21136_963d948268a687c0.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\Components\CanonicalData\Deployments.
RegistryScript:: directive failed to complete successfully.

attached is the checkSUR log generated

zcomputerwiz · Sep 23, 2016

I've found some errors in the hive that need manual editing. Be sure to turn automatic Windows Updates off on this machine first.

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.

ammexico · Sep 23, 2016

I'll need to reboot during maintenance window. I will follow up Monday. Thanks for all your help

zcomputerwiz · Sep 23, 2016

Very good. Thanks.

ammexico · Sep 26, 2016

Components file found at COMPONENTS1.zip - Google Drive

zcomputerwiz · Sep 26, 2016

Step 1 - Replace Components Hive Manually

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 COMPONENTS.ZIP and save to your desktop.
Right-click on it and select Extract all.... Make sure the "Show extracted files when complete" is checked and click Extract.
Now we have the COMPONENTS file that we will be using to replace your current one.
Navigate to C:\Windows\System32\config
Right-click on the current COMPONENTS file and select rename. Rename it to COMPONENTS.bad.
Note: If you get an error that the file is in use, reboot your computer and then try again.
Take the file from the Components folder on your desktop and paste it into C:\Windows\System32\config

View attachment 22715

When finished, run SURT again and attach CheckSUR.log

ammexico · Sep 27, 2016

attached is the checksur log generated.

zcomputerwiz · Sep 27, 2016

Something didn't go right on my end. Please try this hive instead:

Step 1 - Replace Components Hive Manually

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 COMPONENTS.ZIP and save to your desktop.
Right-click on it and select Extract all.... Make sure the "Show extracted files when complete" is checked and click Extract.
Now we have the COMPONENTS file that we will be using to replace your current one.
Navigate to C:\Windows\System32\config
Right-click on the current COMPONENTS file and select rename. Rename it to COMPONENTS.bad.
Note: If you get an error that the file is in use, reboot your computer and then try again.
Take the file from the Components folder on your desktop and paste it into C:\Windows\System32\config

View attachment 22724

As usual, when complete run SURT and attach CheckSUR.log

ammexico · Sep 27, 2016

Will do.

zcomputerwiz · Sep 28, 2016

Is this a physical server or a VM? Has the RAM in the host ever been tested or replaced?

ammexico · Sep 29, 2016

Sorry i was out yesterday, attached is the checksur log generated.

This is a VM and the host hasn't had any RAM issues/changes. Ive moved this vm to another host to see if it helps.

zcomputerwiz · Sep 29, 2016

Excellent. I think I've got them all now.

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

Once SFCFix has completed, run SURT again and attach CheckSUR.log with your reply.

ammexico · Sep 29, 2016

attached is the checksur log generated

zcomputerwiz · Sep 29, 2016

Looking good. We'll try some fixes for the expired catalogs after this.

Code:

(f)	CSI C Mark Deployment Missing	0x00000000	c!dot4.inf_31bf3856ad364e35_d364e35_6.1.7600.16385_10da47a1	amd64_dot4.inf_31bf3856ad364e35_6.1.7600.16385_none_3868f74cf5b51f17	
(f)	CSI C Mark Deployment Not Marked	0x00000000	c!policy.9.0...vc90.mfcloc_1fc8b3b9a1e18e3b_9.0.30729.1_818f59bf601aa775	x86_policy.9.0.microsoft.vc90.mfcloc_1fc8b3b9a1e18e3b_9.0.30729.1_none_818f59bf601aa775	
(f)	CSI C Mark Deployment Not Marked	0x00000000	c!microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.762_11ecb0ab9b2caf3c	x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.762_none_11ecb0ab9b2caf3c

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

Once complete, run SURT again and attach CheckSUR.log with your reply.

ammexico · Sep 29, 2016

attached is the checksur log generated.

zcomputerwiz · Sep 29, 2016

That's all of the missing keys :)

Now for the expired certificates:

Code:

Checking Package Manifests and Catalogs
(w)	CBS Catalog Expired	0x800B0101	servicing\Packages\Package_11_for_KB2729094~31bf3856ad364e35~amd64~~6.1.1.0.cat		
(w)	CBS Catalog Expired	0x800B0101	servicing\Packages\Package_13_for_KB2722913~31bf3856ad364e35~amd64~~6.1.1.0.cat		
(w)	CBS Catalog Expired	0x800B0101	servicing\Packages\Package_15_for_KB2722913~31bf3856ad364e35~amd64~~6.1.1.0.cat		
(w)	CBS Catalog Expired	0x800B0101	servicing\Packages\Package_2_for_KB2705219~31bf3856ad364e35~amd64~~6.1.1.1.cat		
(w)	CBS Catalog Expired	0x800B0101	servicing\Packages\Package_5_for_KB2647753~31bf3856ad364e35~amd64~~6.1.3.1.cat

Please try downloading and installing the following updates:
https://support.microsoft.com/en-us/kb/2749655
https://support.microsoft.com/en-us/kb/2729094
Download Security Update for Windows Server 2008 R2 x64 Edition (KB2705219) from Official Microsoft Download Center
Download Update for Windows Server 2008 R2 x64 Edition (KB2647753) from Official Microsoft Download Center

ammexico · Sep 29, 2016

2749655, 2729094, 2705219 all say they are already installed

2647753 says it does not apply.

zcomputerwiz · Sep 29, 2016

Are you able to view features and roles at this point?

[SOLVED] Windows Server 2008 R2 error viewing features and roles

Well-known member

Windows Update Expert

Well-known member

Attachments

Windows Update Expert

Well-known member

Windows Update Expert

Well-known member

Windows Update Expert

Well-known member

Attachments

Windows Update Expert

Well-known member

Windows Update Expert

Well-known member

Attachments

Windows Update Expert

Well-known member

Attachments

Windows Update Expert

Well-known member

Attachments

Windows Update Expert

Well-known member

Windows Update Expert