2008 R2 - won't update, SFC fails, probably eats babies too.

That one went through without problems:

SFCFix version 2.4.9.2 by niemiro.
Start time: 2016-02-01 16:08:05.335
Microsoft Windows Server 2008 R2 Service Pack 1 - amd64
Using .txt script file at \\CIP-DC\RedirectedFolders\certifiedremote\Desktop\SFCScript.txt [0]




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\wow64_microsoft-windows-ie-feeds-platform_31bf3856ad364e35_8.0.7600.17051_none_e106bf9eff758eba.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\wow64_microsoft-windows-ie-feeds-platform_31bf3856ad364e35_8.0.7600.17051_none_e106bf9eff758eba.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\wow64_microsoft-windows-ie-feeds-platform_31bf3856ad364e35_8.0.7600.17051_none_e106bf9eff758eba.
RegistryScript:: directive completed successfully.




Successfully processed all directives.
SFCFix version 2.4.9.2 by niemiro has completed.
Currently storing 10 datablocks.
Finish time: 2016-02-01 16:08:05.692
Script hash: vLinnKEk0utYG5AoG+Jqr3Yb74a6sLV+7GVP3dt+fn4=
----------------------EOF-----------------------
 
Great. Please do the following again.

System Update Readiness Tool (SUR)
 1. Download and run the following file. Or use the one you already downloaded.
2. When it asks you if you wish to install, please answer yes. Note: It could take 15 minutes or more to run. Please don't cancel.
3. You will get an Installation Complete screen when it's done running.
4. Please attach the log from the following location. C:\Windows\Logs\CBS\CheckSUR.log
Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
 
Good. Please download and attempt to install the following update.

Download Update for Windows Server 2008 R2 x64 Edition (KB2749655) from Official Microsoft Download Cente

Hopefully this will resolve the following errors.

Code: 
Checking Package Manifests and Catalogs
(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_3_for_KB2705219~31bf3856ad364e35~amd64~~6.1.1.1.cat  
(w) CBS Catalog Expired 0x800B0101 servicing\Packages\Package_5_for_KB2722913~31bf3856ad364e35~amd64~~6.1.1.0.cat  
(w) CBS Catalog Expired 0x800B0101 servicing\Packages\Package_6_for_KB2705219~31bf3856ad364e35~amd64~~6.1.1.1.cat  
(w) CBS Catalog Expired 0x800B0101 servicing\Packages\Package_for_KB2731847_SP1~31bf3856ad364e35~amd64~~6.1.1.2.cat
 
No dice! The update claims that it's "not applicable to your computer". CBS.log has these entries:

Code: 
2016-02-01 17:05:34, Error                 CSI    0000003c (F) STATUS_OBJECT_NAME_NOT_FOUND #777565# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = (AllowAccessDenied), key = {provider=NULL, handle=0}, da = (KEY_READ|DELETE|KEY_WOW64_64KEY), oa = @0xe3ce10->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[217]"\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.17592 (win7sp1_gdr.110408-1631)\ComponentFamilies\amd64_microsoft-windows-i..l-keyboard-0001080c_31bf3856ad364e35_none_1036028c71d2d28b\f256!kbdbene.dll"; a:(OBJ_CASE_INSENSITIVE)}, disp = Unmapped disposition: 14929328 (0x00e3cdb0))[gle=0xd0000034]
2016-02-01 17:05:34, Error                 CSI    0000003d@2016/2/1:22:05:34.572 (F) d:\win7sp1_gdr\base\wcp\sil\merged\ntu\ntsystem.cpp(3676): Error STATUS_OBJECT_NAME_NOT_FOUND originated in function Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey expression: (null)
[gle=0x80004005]
2016-02-01 17:05:34, Error                 CSI    0000003e (F) STATUS_OBJECT_NAME_NOT_FOUND #777564# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = 0, key = {provider=NULL, handle=0}, da = (KEY_READ|DELETE|KEY_WOW64_64KEY), oa = @0xe3ce10->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[217]"\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.17592 (win7sp1_gdr.110408-1631)\ComponentFamilies\amd64_microsoft-windows-i..l-keyboard-0001080c_31bf3856ad364e35_none_1036028c71d2d28b\f256!kbdbene.dll"; a:(OBJ_CASE_INSENSITIVE)}, disp = Unmapped disposition: 14930392 (0x00e3d1d8))[gle=0xd0000034]
2016-02-01 17:05:34, Error                 CSI    0000003f@2016/2/1:22:05:34.604 (F) d:\win7sp1_gdr\base\wcp\sil\merged\ntu\ntsystem.cpp(3676): Error STATUS_OBJECT_NAME_NOT_FOUND originated in function Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey expression: (null)
[gle=0x80004005]
2016-02-01 17:05:34, Error                 CSI    00000040 (F) STATUS_OBJECT_NAME_NOT_FOUND #777563# from Windows::Rtl::SystemImplementation::CKey::OpenExistingKey(f = 2, da = (KEY_READ|DELETE), oa = @0xe3d270, key = NULL, disp = (null))[gle=0xd0000034]
2016-02-01 17:05:34, Error                 CSI    00000041 (F) STATUS_OBJECT_NAME_NOT_FOUND #777558# from Windows::Rtl::SystemImplementation::CKey::DeleteRecursively(...)[gle=0xd0000034]
2016-02-01 17:05:34, Error                 CSI    00000042 (F) STATUS_OBJECT_NAME_NOT_FOUND #701008# from Windows::Rtl::SystemImplementation::CKey::DeleteRecursively(...)[gle=0xd0000034]
2016-02-01 17:05:34, Info                  CBS    Failed to get CSI store. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2016-02-01 17:05:34, Error                 CBS    Failed to initialize store parameters with boot drive:  and windows directory:  [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

I think I'm picking up enough about how this is working to guess that "\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.17592 (win7sp1_gdr.110408-1631)\ComponentFamilies\amd64_microsoft-windows-i..l-keyboard-0001080c_31bf3856ad364e35_none_1036028c71d2d28b\f256!kbdbene.dll" is also damaged.
 
I think I'm picking up enough about how this is working to guess that "\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.17592 (win7sp1_gdr.110408-1631)\ComponentFamilies\amd64_microsoft-windows-i..l-keyboard-0001080c_31bf3856ad364e35_none_1036028c71d2d28b\f256!kbdbene.dll" is also damaged.
Click to expand...

I thought so and was the very first item I attempted to fix. Not exactly sure what is going on yet but wanted to finish cleaning up the SURT errors first. So let's fix the following one.
Code: 
(f) CSI Corrupt Identity 0xC0150019 584be9cd03d80ef7a394edcc1db0e023, Culture=neutral, Versiol=6.1.7620.20830. PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS 584be9cd01d..dcc1fb0e023_31bf3856ad366e35_6.1,7600.20830_9c2af780f77d:518 Bad identity

Step#1 - 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.
  1. Download SFCFix.exe (by niemiro) and save this to your Desktop. If you still have this on your desktop from downloading previously, you don't need to re-download.
  2. Download the file below, SFCScript.txt, and save this to your Desktop.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCScript.txt.
  5. Drag the file SFCScript.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please
 

Attachments

Here's the result:

SFCFix version 2.4.9.2 by niemiro.
Start time: 2016-02-01 20:04:43.486
Microsoft Windows Server 2008 R2 Service Pack 1 - amd64
Using .txt script file at \\CIP-DC\RedirectedFolders\certifiedremote\Desktop\SFCScript.txt [0]




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.

Failed to delete registry key HKEY_LOCAL_MACHINE\18658\CanonicalData\Deployments\584be9cd01d..dcc1fb0e023_31bf3856ad366e35_6.1,7600.20830_9c2af780f77d:518. A root key cannot be created under this hive.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\584be9cd01d..dcc1fb0e023_31bf3856ad364e35_6.1.7600.20830_9c2ad780f77d8518.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\584be9cd01d..dcc1fb0e023_31bf3856ad364e35_6.1.7600.20830_9c2ad780f77d8518.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
RegistryScript:: directive failed to complete successfully.




Failed to process all directives successfully.
SFCFix version 2.4.9.2 by niemiro has completed.
Currently storing 11 datablocks.
Finish time: 2016-02-01 20:04:43.530
Script hash: wZqdt5UUHfvG4mNlL+DJlUgs8HqJ0VIQ5VmWgqr5WCw=
----------------------EOF-----------------------
 
Arghh...I had an error in my script. Please re-do with the following.

Step#1 - 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.

  1. Download SFCFix.exe (by niemiro) and save this to your Desktop. If you still have this on your desktop from downloading previously, you don't need to re-download.
  2. Download the file below, SFCScript.txt, and save this to your Desktop.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCScript.txt.
  5. Drag the file SFCScript.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please
 

Attachments

Okay, done!

SFCFix version 2.4.9.2 by niemiro.
Start time: 2016-02-01 22:36:47.271
Microsoft Windows Server 2008 R2 Service Pack 1 - amd64
Using .txt script file at \\CIP-DC\RedirectedFolders\certifiedremote\Desktop\SFCScript.txt [0]




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\584be9cd01d..dcc1fb0e023_31bf3856ad366e35_6.1,7600.20830_9c2af780f77d:518.

WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\584be9cd01d..dcc1fb0e023_31bf3856ad366e35_6.1,7600.20830_9c2af780f77d:518.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\584be9cd01d..dcc1fb0e023_31bf3856ad366e35_6.1,7600.20830_9c2af780f77d:518.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\584be9cd01d..dcc1fb0e023_31bf3856ad366e35_6.1,7600.20830_9c2af780f77d:518.
RegistryScript:: directive completed successfully.




Successfully processed all directives.
SFCFix version 2.4.9.2 by niemiro has completed.
Currently storing 12 datablocks.
Finish time: 2016-02-01 22:36:47.656
Script hash: 7/5bc2nMRJ2e5fT5g8sXaN3Hm4c7b/NCbR9TSsyp43U=
----------------------EOF-----------------------
 
This should fix all but the expired errors.

Step#1 - 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.


  1. Download SFCFix.exe (by niemiro) and save this to your Desktop. If you still have this on your desktop from downloading previously, you don't need to re-download.
  2. Download the file below, SFCScript.txt, and save this to your Desktop.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCScript.txt.
  5. Drag the file SFCScript.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please
 

Attachments

Yes, all successes:

SFCFix version 2.4.9.2 by niemiro.
Start time: 2016-02-02 13:35:36.836
Microsoft Windows Server 2008 R2 Service Pack 1 - amd64
Using .txt script file at \\CIP-DC\RedirectedFolders\certifiedremote\Desktop\SFCScript.txt [0]




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-p..unterinfrastructure_31bf3856ad364e35_6.1.7600.16385_none_cd7aeeff1897d018.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_policy.8.0.microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4927_none_09bd9a47facfb1f8.
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\prnbr00a.inf_31bf3856ad364e35_6.1.7600.16385_62f3926260bd65e5.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\prnca00b.inf_31bf3856ad364e35_6.1.7600.16385_dd3ee736dd6ff736.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\prnca003.inf_31bf3856ad364e35_6.1.7600.16385_c4148f7740e2dfef.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\prnbr009.inf_31bf3856ad364e35_6.1.7600.16385_4d88ba167403f57d.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\prnca00c.inf_31bf3856ad364e35_6.1.7600.16385_ddc7f96bf68e339f.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\prnca00a.inf_31bf3856ad364e35_6.1.7600.16385_dcb5d501c451bacd.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\prnbr008.inf_31bf3856ad364e35_6.1.7600.16385_4cffa7e15ae5b914.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\prnca00f.inf_31bf3856ad364e35_6.1.7600.16385_df63300b41e8e8da.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\prnca00d.inf_31bf3856ad364e35_6.1.7600.16385_de510ba10fac7008.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-p..unterinfrastructure_31bf3856ad364e35_6.1.7600.16385_none_cd7aeeff1897d018.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_policy.8.0.microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4927_none_09bd9a47facfb1f8.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\19055a21d67..b91024fdd2c_31bf3856ad364e35_6.1.7600.16699_3b703ba747883cad.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\prnbr00a.inf_31bf3856ad364e35_6.1.7600.16385_62f3926260bd65e5.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\prnca00b.inf_31bf3856ad364e35_6.1.7600.16385_dd3ee736dd6ff736.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\prnca003.inf_31bf3856ad364e35_6.1.7600.16385_c4148f7740e2dfef.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\prnbr009.inf_31bf3856ad364e35_6.1.7600.16385_4d88ba167403f57d.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\prnca00c.inf_31bf3856ad364e35_6.1.7600.16385_ddc7f96bf68e339f.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\prnca00a.inf_31bf3856ad364e35_6.1.7600.16385_dcb5d501c451bacd.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\prnbr008.inf_31bf3856ad364e35_6.1.7600.16385_4cffa7e15ae5b914.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\prnca00f.inf_31bf3856ad364e35_6.1.7600.16385_df63300b41e8e8da.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\prnca00d.inf_31bf3856ad364e35_6.1.7600.16385_de510ba10fac7008.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-p..unterinfrastructure_31bf3856ad364e35_6.1.7600.16385_none_cd7aeeff1897d018.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_policy.8.0.microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4927_none_09bd9a47facfb1f8.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\19055a21d67..b91024fdd2c_31bf3856ad364e35_6.1.7600.16699_3b703ba747883cad.
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\prnbr00a.inf_31bf3856ad364e35_6.1.7600.16385_62f3926260bd65e5.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\prnca00b.inf_31bf3856ad364e35_6.1.7600.16385_dd3ee736dd6ff736.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\prnca003.inf_31bf3856ad364e35_6.1.7600.16385_c4148f7740e2dfef.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\prnbr009.inf_31bf3856ad364e35_6.1.7600.16385_4d88ba167403f57d.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\prnca00c.inf_31bf3856ad364e35_6.1.7600.16385_ddc7f96bf68e339f.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\prnca00a.inf_31bf3856ad364e35_6.1.7600.16385_dcb5d501c451bacd.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\prnbr008.inf_31bf3856ad364e35_6.1.7600.16385_4cffa7e15ae5b914.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\prnca00f.inf_31bf3856ad364e35_6.1.7600.16385_df63300b41e8e8da.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\prnca00d.inf_31bf3856ad364e35_6.1.7600.16385_de510ba10fac7008.
RegistryScript:: directive completed successfully.




Successfully processed all directives.
SFCFix version 2.4.9.2 by niemiro has completed.
Currently storing 24 datablocks.
Finish time: 2016-02-02 13:35:37.652
Script hash: BsdheZaUfUopbjgzRVbXQDobvMC2Ivi6owSlPJGZ1eg=
----------------------EOF-----------------------
 
Let's verify what is left.

System Update Readiness Tool (SUR)
 1. Download and run the following file. Or use the one you already downloaded.
2. When it asks you if you wish to install, please answer yes. Note: It could take 15 minutes or more to run. Please don't cancel.
3. You will get an Installation Complete screen when it's done running.
4. Please attach the log from the following location. C:\Windows\Logs\CBS\CheckSUR.log
Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
 
Good. Please try the following.

Remove Update Manually
 1. Click on the Start button and in the search box, type Command Prompt
2. When you see Command Prompt on the list, right-click on it and select Run as administrator
3. When command prompt opens, copy and paste the following command into it, press enter
wusa /uninstall /KB:2722913

4. Let me know if it says it was successful or if there are any errors.
 
Please re-do with the following.

Step#1 - 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.


  1. Download SFCFix.exe (by niemiro) and save this to your Desktop. If you still have this on your desktop from downloading previously, you don't need to re-download.
  2. Download the file below, SFCScript.txt, and save this to your Desktop.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCScript.txt.
  5. Drag the file SFCScript.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please
 

Attachments

SFCFix gave this result:

SFCFix version 2.4.9.2 by niemiro.
Start time: 2016-02-02 16:02:11.059
Microsoft Windows Server 2008 R2 Service Pack 1 - amd64
Using .txt script file at \\CIP-DC\RedirectedFolders\certifiedremote\Desktop\SFCScript.txt [0]




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\584be9cd01d..dcc1fb0e023_31bf3856ad366e35_6.1,7600.20830_9c2af780f77d:518.

WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\584be9cd01d..dcc1fb0e023_31bf3856ad366e35_6.1,7600.20830_9c2af780f77d:518.

Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\584be9cd01d..dcc1fb0e023_31bf3856ad366e35_6.1,7600.20830_9c2af780f77d:518.

Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\584be9cd01d..dcc1fb0e023_31bf3856ad366e35_6.1,7600.20830_9c2af780f77d:518 with error code ERROR_FILE_NOT_FOUND.
RegistryScript:: directive failed to complete successfully.




Failed to process all directives successfully.
SFCFix version 2.4.9.2 by niemiro has completed.
Currently storing 24 datablocks.
Finish time: 2016-02-02 16:02:11.185
Script hash: DLdoIf3Dp/Noo0AeT1CaSEgUisnejVE1C9y7se+EMQY=
----------------------EOF-----------------------

Using WUSA afterwards gave the same error.
 
OK. Let's run this a final time. If all looks good (except for the expired certs) then we'll turn our attention to the SFC error.

System Update Readiness Tool (SUR)
 1. Download and run the following file. Or use the one you already downloaded.
2. When it asks you if you wish to install, please answer yes. Note: It could take 15 minutes or more to run. Please don't cancel.
3. You will get an Installation Complete screen when it's done running.
4. Please attach the log from the following location. C:\Windows\Logs\CBS\CheckSUR.log
Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
 
Good. Let's focus on the SFC errors now. Please do the following.

SFC Scan
  1. Click on the Start button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. 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
  4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.


Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top