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

Kalrath · Jan 27, 2016

We've got a system here that fails on updates with 80070002. SFC won't run. CheckSUR identified an update with a problem, but providing a fresh copy of the update to CheckSUR just results in errors that the replacement is invalid. No updates are visible in the control panel to be uninstalled that way, and using wusa /uninstall on the update just pops up a fatal error 8000ffff. I'd like to take it out back with a baseball bat at this point, but it's the company DC, so replacing it poses some significant problems.

Here's SFCfix.txt:

SFCFix version 2.4.8.0 by niemiro.
Start time: 2016-01-27 19:54:03.515
Microsoft Windows Server 2008 R2 Service Pack 1 - amd64
Not using a script file.

AutoAnalysis::
FIXED: Successfully repaired missing store directory C:\Windows\winsxs\amd64_microsoft-windows-efs-lsa-extension_31bf3856ad364e35_6.1.7600.14385_nong_252f55d1cea824ae.
FIXED: Successfully repaired missing store directory C:\Windows\winsxs\amd64_microsoft-windows-p..ting-tools-printbrm_31bf3856ad364e35_6.1.7600.16385_none_dfaf1a1b5d059a71.
FAILED: Could not repair missing store directory C:\Windows\winsxs\x86_mkcrosoft-windows/d..ime-eashared/imepad_31bf3856cd364e35]6.1.7600.16385_none_3a62984e00869735 with error code ERROR_INVALID_NAME.

SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 3
CBS & SFC total unimportant corruption count: 0
CBS & SFC total fixed corruption count: 3
SURT total detected corruption count: 26
SURT total unimportant corruption count: 0
SURT total fixed corruption count: 0
AutoAnalysis:: directive completed successfully.

Successfully processed all directives.
SFCFix version 2.4.8.0 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2016-01-27 19:55:30.907
----------------------EOF-----------------------

Any advice is appreciated, this's been driving me mildly crazy!

BrianDrab · Jan 30, 2016

Hi and welcome to Sysnative. Let's see if we can get you fixed up. I need a copy of your COMPONENTS hive. Please do the following.

Retrieve Components Hive

Please download the Freeware RegBak from here: Acelogix Software - Download products
You will find it at the bottom of the page that the link brings you to.
Go ahead and install this program and accept all the defaults. After the last install screen the program should open.
Click the New Backup button. Accept the defaults and simply click Start.
When it says Finished successfully, click the Close button.
This will bring you back to the main screen of the program. You will see one entry in this list with the date that you did it. Right-click on this line-item and select Explore Backup...
This will bring you into the folder where the backup was made. You should see a Users folder and a Windows folder along with a couple other files. Double-click on the Windows folder to open it. Then open the System32 folder and then config folder. You should see around 6 files in here, one of which is named COMPONENTS.
Copy the COMPONENTS file to your Desktop. If the COMPONENTS file does not exist, please fetch it instead from C:\Windows\System32\config\COMPONENTS.
Now right click on the COMPONENTS file that is on your desktop and select Send to > Compressed (zipped) folder.
Then please upload the zip file (COMPONENTS.zip) to your favourite file sharing website (it will be too big to upload here). Examples of services to upload to are Dropbox or One Drive or SendSpace and then just provide the link in your reply.
You can close any open windows you have as well as the RegBack program now.

Kalrath · Jan 30, 2016

Hi Brian! Here's the file: Dropbox - components.zi

Thanks for taking a look.

BrianDrab said:
Hi and welcome to Sysnative. Let's see if we can get you fixed up. I need a copy of your COMPONENTS hive. Please do the following.

Retrieve Components Hive

Please download the Freeware RegBak from here: Acelogix Software - Download products
You will find it at the bottom of the page that the link brings you to.

Go ahead and install this program and accept all the defaults. After the last install screen the program should open.

Click the New Backup button. Accept the defaults and simply click Start.

When it says Finished successfully, click the Close button.

This will bring you back to the main screen of the program. You will see one entry in this list with the date that you did it. Right-click on this line-item and select Explore Backup...

This will bring you into the folder where the backup was made. You should see a Users folder and a Windows folder along with a couple other files. Double-click on the Windows folder to open it. Then open the System32 folder and then config folder. You should see around 6 files in here, one of which is named COMPONENTS.

Copy the COMPONENTS file to your Desktop. If the COMPONENTS file does not exist, please fetch it instead from C:\Windows\System32\config\COMPONENTS.

Now right click on the COMPONENTS file that is on your desktop and select Send to > Compressed (zipped) folder.

Then please upload the zip file (COMPONENTS.zip) to your favourite file sharing website (it will be too big to upload here). Examples of services to upload to are Dropbox or One Drive or SendSpace and then just provide the link in your reply.

You can close any open windows you have as well as the RegBack program now.

BrianDrab · Jan 30, 2016

Thanks. Please do the following.

Code:

2016-01-27 20:04:53, Error                 CSI    00000037 (F) STATUS_OBJECT_NAME_NOT_FOUND #689951# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = 0, key = {provider=NULL, handle=0}, da = (KEY_READ|DELETE|KEY_WOW64_64KEY), oa = @0x290eb60->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: 43052840 (0x0290ef28))[gle=0xd0000034]
2016-01-27 20:04:53, Error                 CSI    00000038@2016/1/28:01:04:53.120 (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-01-27 20:04:53, Error                 CSI    00000039 (F) STATUS_OBJECT_NAME_NOT_FOUND #689950# from Windows::Rtl::SystemImplementation::CKey::OpenExistingKey(f = 2, da = (KEY_READ|DELETE), oa = @0x290efc0, key = NULL, disp = (null))[gle=0xd0000034]
2016-01-27 20:04:53, Error                 CSI    0000003a (F) STATUS_OBJECT_NAME_NOT_FOUND #689945# from Windows::Rtl::SystemImplementation::CKey::DeleteRecursively(...)[gle=0xd0000034]
2016-01-27 20:04:53, Error                 CSI    0000003b (F) STATUS_OBJECT_NAME_NOT_FOUND #613395# from Windows::Rtl::SystemImplementation::CKey::DeleteRecursively(...)[gle=0xd0000034]

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.

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.
Download the file below, SFCScript.txt, and save this to your Desktop.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCScript.txt.
Drag the file SFCScript.txt 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

Kalrath · Jan 30, 2016

Here is the output:

SFCFix version 2.4.9.1 by niemiro.
Start time: 2016-01-30 13:43:40.692
Microsoft Windows Server 2008 R2 Service Pack 1 - amd64
Using .txt script file at \\CIP-DC\RedirectedFolders\certifiedremote\Desktop\SFCScript.txt [0]

FileScan::
[0: 2] C:\Windows\winsxs\amd64_microsoft-windows-i..l-keyboard-0001080c_31bf3856ad364e35_6.1.7600.16385_none_fc85c21f62352524\KBDBENE.DLL
Expected: vCGBxLztgzM6JWWBjU1CiBYyOIqS27WGjtJ2HWvm3Cg=
Expected: 6.1.7600.16385
Failed to trace component amd64_microsoft-windows-i..l-keyboard-0001080c_31bf3856ad364e35_6.1.7600.16385_none_fc85c21f62352524 with return code -2.

[C:\Windows\System32\KBDBENE.DLL]

[1: 2] C:\Windows\winsxs\wow64_microsoft-windows-i..l-keyboard-0001080c_31bf3856ad364e35_6.1.7600.16385_none_06da6c719695e71f\KBDBENE.DLL
Expected: zd+VFDnKSUO+JDkNlTrqri3OwWZl6hvJMGTcoZBroa4=
Expected: 6.1.7600.16385
Failed to trace component wow64_microsoft-windows-i..l-keyboard-0001080c_31bf3856ad364e35_6.1.7600.16385_none_06da6c719695e71f with return code -2.

[C:\Windows\SysWOW64\KBDBENE.DLL]
FileScan:: directive completed successfully.

Successfully processed all directives.
SFCFix version 2.4.9.1 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2016-01-30 13:43:50.208
Script hash: WY+sEELcRiRRYO5Z9fqIOfwNNCMHEa0nHoIb6d3qgRI=
----------------------EOF-----------------------

BrianDrab · Jan 30, 2016

Thanks. Please do 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.

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.
Download the file below, SFCScript.txt, and save this to your Desktop.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCScript.txt.
Drag the file SFCScript.txt 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

Kalrath · Jan 30, 2016

SFCFix version 2.4.9.1 by niemiro.
Start time: 2016-01-30 14:22:31.867
Microsoft Windows Server 2008 R2 Service Pack 1 - amd64
Using .txt script file at \\CIP-DC\RedirectedFolders\certifiedremote\Desktop\SFCScript(1).txt [0]

RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.17592 (win7sp1_gdr.110408-1631)\ComponentFamilies\amd64_microsoft-windows-i..l-keyboard-0001080c_31bf3856ad364e35_none_1036028c71d2d28b.

WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.17592 (win7sp1_gdr.110408-1631)\ComponentFamilies\amd64_microsoft-windows-i..l-keyboard-0001080c_31bf3856ad364e35_none_1036028c71d2d28b.

Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.17592 (win7sp1_gdr.110408-1631)\ComponentFamilies\amd64_microsoft-windows-i..l-keyboard-0001080c_31bf3856ad364e35_none_1036028c71d2d28b.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.17592 (win7sp1_gdr.110408-1631)\ComponentFamilies\amd64_microsoft-windows-i..l-keyboard-0001080c_31bf3856ad364e35_none_1036028c71d2d28b.
RegistryScript:: directive completed successfully.

Successfully processed all directives.
SFCFix version 2.4.9.1 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2016-01-30 14:22:32.246
Script hash: AHq1B2mmUbpgZz5SKbpPxm4jpVhbneiMCcsLR07+9VE=
----------------------EOF-----------------------

BrianDrab · Jan 30, 2016

Excellent. Now do 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.

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.
Download the file below, SFCScript.txt, and save this to your Desktop.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCScript.txt.
Drag the file SFCScript.txt 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

Step#2 - SFC Scan

Click on the Start

button and in the search box, type Command Prompt
When you see Command Prompt on the list, right-click on it and select 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.

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.

Items for your next post
1. SFCFix.txt
2. CBS.txt

Kalrath · Jan 30, 2016

Here's the output:
SFCFix version 2.4.9.1 by niemiro.
Start time: 2016-01-30 15:36:21.190
Microsoft Windows Server 2008 R2 Service Pack 1 - amd64
Using .txt script file at \\CIP-DC\RedirectedFolders\certifiedremote\Desktop\SFCScript(2).txt [0]

RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.17592 (win7sp1_gdr.110408-1631)\ComponentFamilies\amd64_microsoft-windows-i..l-keyboard-0001080c_31bf3856ad364e35_none_1036028c71d2d28b.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.17592 (win7sp1_gdr.110408-1631)\ComponentFamilies\amd64_microsoft-windows-i..l-keyboard-0001080c_31bf3856ad364e35_none_1036028c71d2d28b.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.17592 (win7sp1_gdr.110408-1631)\ComponentFamilies\amd64_microsoft-windows-i..l-keyboard-0001080c_31bf3856ad364e35_none_1036028c71d2d28b.

WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.17592 (win7sp1_gdr.110408-1631)\ComponentFamilies\amd64_microsoft-windows-i..l-keyboard-0001080c_31bf3856ad364e35_none_1036028c71d2d28b.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.17592 (win7sp1_gdr.110408-1631)\ComponentFamilies\amd64_microsoft-windows-i..l-keyboard-0001080c_31bf3856ad364e35_none_1036028c71d2d28b.
Successfully imported registry key HKEY_LOCAL_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.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.17592 (win7sp1_gdr.110408-1631)\ComponentFamilies\amd64_microsoft-windows-i..l-keyboard-0001080c_31bf3856ad364e35_none_1036028c71d2d28b\v!6.1.7600.16385.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.17592 (win7sp1_gdr.110408-1631)\ComponentFamilies\amd64_microsoft-windows-i..l-keyboard-0001080c_31bf3856ad364e35_none_1036028c71d2d28b.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_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.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.17592 (win7sp1_gdr.110408-1631)\ComponentFamilies\amd64_microsoft-windows-i..l-keyboard-0001080c_31bf3856ad364e35_none_1036028c71d2d28b.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.17592 (win7sp1_gdr.110408-1631)\ComponentFamilies\amd64_microsoft-windows-i..l-keyboard-0001080c_31bf3856ad364e35_none_1036028c71d2d28b\v!6.1.7600.16385.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.17592 (win7sp1_gdr.110408-1631)\ComponentFamilies\amd64_microsoft-windows-i..l-keyboard-0001080c_31bf3856ad364e35_none_1036028c71d2d28b.
RegistryScript:: directive completed successfully.

Successfully processed all directives.
SFCFix version 2.4.9.1 by niemiro has completed.
Currently storing 4 datablocks.
Finish time: 2016-01-30 15:36:21.265
Script hash: 0Y5EfyIBoLsqWK1j+30rM3gQZfii6OaTW58zdl8eW2I=
----------------------EOF-----------------------

And the cbs.txt: Dropbox - cbs.tx

BrianDrab · Jan 30, 2016

Thanks. We need to rule out disk corruption. Let's do a quick check.

Step#1 - ChkDsk Scan
1. Click your Start Button in the lower left of your computer and type cmd in the search box.
2. Once the cmd program is found, right-click on it with your mouse and select Run as administrator.
3. Answer Yes when asked to allow.
4. You should now have a black window open that you can type in to.
5. Please type chkdsk and then press enter.
6. Chkdsk will start to run. Please allow it to finish. You will know it is running when you see text as follows.

7. Download ListChkdskResult.exe by SleepyDude and save it on your desktop. If it's already downloaded to your desktop, just skip this step.
8. Right-click this file and select Run as administrator (Allow if prompted)and a text file will open (and also be saved on the desktop as ListChkdskResult.txt).
Please copy the contents of this file and paste into your next post.

Kalrath · Jan 31, 2016

ListChkdskResult by SleepyDude v0.1.7 Beta | 21-09-2013

------< Log generate on 1/30/2016 11:58:14 PM >------
Category: 0
Computer Name: CIP-DC.ciprichmond.local
Event Code: 26212
Record Number: 2124407
Source Name: Chkdsk
Time Written: 01-31-2016 @ 04:55:29
Event Type: Information
User:
Message: Chkdsk was executed in read-only mode on a volume snapshot.

Checking file system on C:
The type of the file system is NTFS.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
398080 file records processed.

File verification completed.
2005 large file records processed.

0 bad file records processed.

0 EA records processed.

251 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 3)...
468462 index entries processed.

Index verification completed.
0 unindexed files scanned.

0 unindexed files recovered.

CHKDSK is verifying security descriptors (stage 3 of 3)...
398080 file SDs/SIDs processed.

Cleaning up 298 unused index entries from index $SII of file 0x9.
Cleaning up 298 unused index entries from index $SDH of file 0x9.
Cleaning up 298 unused security descriptors.
Security descriptor verification completed.
35192 data files processed.

CHKDSK is verifying Usn Journal...
540392600 USN bytes processed.

Usn Journal verification completed.
Windows has checked the file system and found no problems.

976657403 KB total disk space.
473784144 KB in 360597 files.
130828 KB in 35193 indexes.
0 KB in bad sectors.
1023735 KB in use by the system.
65536 KB occupied by the log file.
501718696 KB available on disk.

4096 bytes in each allocation unit.
244164350 total allocation units on disk.
125429674 allocation units available on disk.

-----------------------------------------------------------------------

BrianDrab · Jan 31, 2016

Thanks. Please do the following to correct a corrupt key.

Code:

FAILED: Could not repair missing store directory C:\Windows\winsxs\x86_mkcrosoft-windows/d..ime-eashared/imepad_31bf3856cd364e35]6.1.7600.16385_none_3a62984e00869735 with error code ERROR_INVALID_NAME.

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.

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.
Download the file below, SFCScript.txt, and save this to your Desktop.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCScript.txt.
Drag the file SFCScript.txt 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

Kalrath · Jan 31, 2016

Done, here's the output:

SFCFix version 2.4.9.2 by niemiro.
Start time: 2016-01-31 13:04:04.459
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.

Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_mkcrosoft-windows\d..ime-eashared\imepad_31bf3856cd364e35]6.1.7600.16385_none_3a62984e00869735.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
RegistryScript:: directive completed successfully.

Successfully processed all directives.
SFCFix version 2.4.9.2 by niemiro has completed.
Currently storing 5 datablocks.
Finish time: 2016-01-31 13:04:04.929
Script hash: OAfOSZTlM+4lIUsW5hNNHeo8wl0lU4wXqaEPcfGln5Q=
----------------------EOF-----------------------

BrianDrab · Jan 31, 2016

Thanks. 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.

Kalrath · Jan 31, 2016

Here's the log:View attachment CheckSUR.log

BrianDrab · Jan 31, 2016

Thanks. Please do the following to fix a corruption.

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.

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.
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

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

Items for your next post
1. SFCFix.txt
2. CheckSUR.log

Kalrath · Jan 31, 2016

Here's SFCFix:

SFCFix version 2.4.9.2 by niemiro.
Start time: 2016-01-31 22:03:20.724
Microsoft Windows Server 2008 R2 Service Pack 1 - amd64
Using .zip script file at \\CIP-DC\RedirectedFolders\certifiedremote\Desktop\SFCFix.zip [0]

PowerCopy::
Successfully took permissions for file or folder C:\Windows\Temp\CheckSur\Winsxs\Manifests\wow64_microsoft-windows-ie-feeds-platform_31bf3856ad364e35_8.0.7600.17051_none_e106bf9eff758eba.manifest

Successfully copied file C:\Users\certifiedremote.CIPRICHMOND\AppData\Local\niemiro\Archive\Manifests\wow64_microsoft-windows-ie-feeds-platform_31bf3856ad364e35_8.0.7600.17051_none_e106bf9eff758eba.manifest to C:\Windows\Temp\CheckSur\Winsxs\Manifests\wow64_microsoft-windows-ie-feeds-platform_31bf3856ad364e35_8.0.7600.17051_none_e106bf9eff758eba.manifest.

Successfully restored ownership for C:\Windows\Temp\CheckSur\Winsxs\Manifests\wow64_microsoft-windows-ie-feeds-platform_31bf3856ad364e35_8.0.7600.17051_none_e106bf9eff758eba.manifest
Successfully restored permissions on C:\Windows\Temp\CheckSur\Winsxs\Manifests\wow64_microsoft-windows-ie-feeds-platform_31bf3856ad364e35_8.0.7600.17051_none_e106bf9eff758eba.manifest
PowerCopy:: directive completed successfully.

Successfully processed all directives.
SFCFix version 2.4.9.2 by niemiro has completed.
Currently storing 6 datablocks.
Finish time: 2016-01-31 22:03:21.049
Script hash: yLuE+x1qYPemXje9OHg/4pwiX7BBBN3G08a1hnZhmX4=
----------------------EOF-----------------------

But checkSUR is still complaining about that same manifest: View attachment CheckSUR.log

BrianDrab · Feb 1, 2016

You have corruption consistant with a potential hardware issue. Have you ever run a memory test on the machine? For example, the following key (which we'll fix) has a bunch of corruption in it.

Code:

[HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\2da657a18a4..5884a405f7b_31bf3856ad364e35_6.1,7600.16499_28ca18660c5948c3]

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.

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.
Download the file below, SFCScript.txt, and save this to your Desktop.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCScript.txt.
Drag the file SFCScript.txt 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

Kalrath · Feb 1, 2016

I'll run memtest once I can get some exclusive access to the server without anyone gnashing teeth about me booting them off! Here's sfcfix:

SFCFix version 2.4.9.2 by niemiro.
Start time: 2016-02-01 11:46:37.482
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\2da657a18a4..5884a405f7b_31bf3856ad364e35_6.1,7600.16499_28ca18660c5948c3.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.

Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\2da657a18a4..5884a405f7b_31bf3856ad364e35_6.1,7600.16499_28ca18660c5948c3.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\2da657a18a4..5884a405f7b_31bf3856ad364e35_6.1.7600.16699_28ca38660c5968c3.

Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\2da657a18a4..5884a405f7b_31bf3856ad364e35_6.1,7600.16499_28ca18660c5948c3 with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\2da657a18a4..5884a405f7b_31bf3856ad364e35_6.1.7600.16699_28ca38660c5968c3.
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 9 datablocks.
Finish time: 2016-02-01 11:46:37.870
Script hash: cxuKaxsRwxkeke2n2LrYRPY2hpyv/iDChDOnvxW8gD8=
----------------------EOF-----------------------

BrianDrab · Feb 1, 2016

Thanks. Let's fix another corruption.

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.

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.
Download the file below, SFCScript.txt, and save this to your Desktop.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCScript.txt.
Drag the file SFCScript.txt 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

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

Active member

Emeritus

Active member

Emeritus

Attachments

Active member

Emeritus

Attachments

Active member

Emeritus

Attachments

Active member

Emeritus

Active member

Emeritus

Attachments

Active member

Emeritus

Active member

Emeritus

Attachments

Active member

Emeritus

Attachments

Active member

Emeritus

Attachments