Sfc windows server 2008

3. Verifying
System Files with the SFC Utility

The System File Scan
(SFC) utility can help you keep viruses at bay by ensuring you have the
correct version of the system files on your system. Viruses often
replace system files with patched versions that contain the virus code.
Hitchhiking on an existing system file makes it less likely that someone
will remove the virus and ensures the virus gets a chance to run, so
virus writers are motivated to use system files whenever they think they
can. This utility uses the following syntax:

SFC [/SCANNOW] [/VERIFYONLY] [/SCANFILE=<file>] [/VERIFYFILE=<file>]
[/OFFWINDIR=<offline windows directory>
/OFFBOOTDIR=<offline boot directory>]


NOTE

The syntax of the SFC
utility presented in this article is specific to Vista, Windows Server
2008 Full version, and Server Core. The syntax is completely different
from older versions of SFC that you find in products such as Windows XP.
The older windows products use a command line that looks like this: SFC [/SCANNOW] [/SCANONCE] [/SCANBOOT] [/REVERT]
[/PURGECACHE] [/CACHESIZE=x]. If you need
this and other older versions of the command line for Windows
administrative, get Windows
Administration at the Command Line (Sybex, 2007).

The following list
describes each of the command line arguments.


/SCANNOW

Scans all
of the protected system files immediately and repairs any damage it
finds. The utility normally relies on the content of the \WINDOWS\system32\dllcache folder to make repairs to the system files.
However, it can also use the Server Core DVD, the content of service
pack folders, or even online sources when necessary. In many cases,
you’ll want to verify the files using the /VERIFYONLY command line switch before you do a repair using this
command line switch.


/VERIFYONLY

Verifies all
of the protected system files immediately and works much the same as the
/SCANNOW option. However, this option
doesn’t perform any repairs. Even so, it provides you with a report of
system file reliability. To use this option, type SFC /VERIFYONLY and press Enter. You’ll see the utility work in
stages as shown in Figure 1.

Figure 1.
Verify that your system files are reliable and repair them only as
needed.

Картинка с сайта: tutorial.wmlcloud.com 




/SCANFILE=

File

Scans the specified
file and repairs any damage. You must provide the full path to the
file.


/VERIFYFILE=

File

Verifies the
specified file, but doesn’t repair any damage. You must provide the full
path to the file.


/OFFBOOTDIR=

Directory

Performs
offline repair of the specified boot directory.


/OFFWINDIR=

Directory

Performs
offline repair of the specified Windows directory.

Источник

Sysnative Forums

Картинка с сайта: www.sysnative.com

  • Microsoft Support & Malware Removal

  • Windows Update

You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.

[SOLVED] Windows server 2008 Standard SFC fail SFCFIX Fail. Please help

  • Thread starter
    Thread starter

    fortisq

  • Start date
    Start date

Joined
Sep 30, 2015
Posts
16




  • #1

I found this tool SFCFIX.exe and ran it but it didn’t seem to fix anything, It directed me here for more help.

Can the kind people here direct me towards a solution?

Pasted from SFCFIX
====
SFCFix version 2.4.5.0 by niemiro.
Start time: 2015-09-30 15:46:04.325
Microsoft Windows Server 2008 Service Pack 2 — x86
Not using a script file.

AutoAnalysis::
CORRUPT: C:\windows\winsxs\x86_microsoft-windows-s..onfiguration-wizard_31bf3856ad364e35_6.0.6002.18005_none_3ddae0a5485c3169\scwvariables.xml
CORRUPT: C:\windows\winsxs\x86_microsoft-windows-t..alservices-allroles_31bf3856ad364e35_6.0.6001.18000_none_63a86f6f23c7c11b\TerminalServices.Events.xml

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

Successfully processed all directives.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2015-09-30 15:46:26.794
———————-EOF————————

Joined
Jan 10, 2015
Posts
5,184
Location

USA




  • #2

Hello and Welcome!

Please zip up and attach C:\Windows\Logs\CBS\CBS.log and C:\Windows\Logs\CBS\CheckSUR.log
If the files are smaller than 8MB you can attach them with your reply, otherwise upload the files to a file sharing service like DropBox, OneDrive, SendSpace, etc. and include the link in your reply.

Joined
Sep 30, 2015
Posts
16


Joined
Jan 10, 2015
Posts
5,184
Location

USA




  • #4

Windows Update Package Replacement

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. Please download the attached file, Packs.zip and save this to your Desktop.
  2. Right-click on the file and select Extract All…
  3. Tick the box labelled Show extracted files when complete then click Extract
  4. A window will open showing two folders, Manifests and Packages
  5. Open the Manifests folder and copy the files into the following folder

    C:\Windows\Temp\CheckSur\Winsxs\Manifests

  6. Open the Packages folder and copy the files into the following folder

    C:\Windows\Temp\CheckSur\Servicing\Packages

  7. Run the System Update Readiness Tool (SURT) again.
  8. When the SURT finishes installing, copy (Ctrl + C) and paste (Ctrl + V) the contents of the SURT log into your next post please:

    C:\Windows\Logs\CBS\CheckSUR.log

View attachment Packs.zip

Joined
Sep 30, 2015
Posts
16




  • #5

=================================
Checking System Update Readiness.
Binary Version 6.0.6002.23186
Package Version 25.0
2015-10-02 13:10

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages
(f) CBS MUM Missing 0x00000002 servicing\Packages\Package_2_for_KB2467659~31bf3856ad364e35~x86~~6.0.1.1.mum
(fix) CBS MUM Missing CBS File Replaced Package_2_for_KB2467659~31bf3856ad364e35~x86~~6.0.1.1.mum from Cabinet: C:\windows\CheckSur\v1.0\windows6.0-6001-server-wave0.cab.
(fix) CBS Paired File CBS File also Replaced Package_2_for_KB2467659~31bf3856ad364e35~x86~~6.0.1.1.cat from Cabinet: C:\windows\CheckSur\v1.0\windows6.0-6001-server-wave0.cab.
(f) CBS MUM Missing 0x00000002 servicing\Packages\Package_4_for_KB2467659~31bf3856ad364e35~x86~~6.0.1.1.mum
(fix) CBS MUM Missing CBS File Replaced Package_4_for_KB2467659~31bf3856ad364e35~x86~~6.0.1.1.mum from Cabinet: C:\windows\CheckSur\v1.0\windows6.0-6001-server-wave0.cab.
(fix) CBS Paired File CBS File also Replaced Package_4_for_KB2467659~31bf3856ad364e35~x86~~6.0.1.1.cat from Cabinet: C:\windows\CheckSur\v1.0\windows6.0-6001-server-wave0.cab.
(f) CBS MUM Missing 0x00000002 servicing\Packages\Package_for_KB2467659_server_0~31bf3856ad364e35~x86~~6.0.1.1.mum
(fix) CBS MUM Missing CBS File Replaced Package_for_KB2467659_server_0~31bf3856ad364e35~x86~~6.0.1.1.mum from Cabinet: C:\windows\CheckSur\v1.0\windows6.0-6001-server-wave0.cab.
(fix) CBS Paired File CBS File also Replaced Package_for_KB2467659_server_0~31bf3856ad364e35~x86~~6.0.1.1.cat from Cabinet: C:\windows\CheckSur\v1.0\windows6.0-6001-server-wave0.cab.
(f) CBS MUM Missing 0x00000002 servicing\Packages\Package_for_KB2467659_server_1~31bf3856ad364e35~x86~~6.0.1.1.mum
(fix) CBS MUM Missing CBS File Replaced Package_for_KB2467659_server_1~31bf3856ad364e35~x86~~6.0.1.1.mum from Cabinet: C:\windows\CheckSur\v1.0\windows6.0-6001-server-wave0.cab.
(fix) CBS Paired File CBS File also Replaced Package_for_KB2467659_server_1~31bf3856ad364e35~x86~~6.0.1.1.cat from Cabinet: C:\windows\CheckSur\v1.0\windows6.0-6001-server-wave0.cab.
(f) CBS MUM Missing 0x00000002 servicing\Packages\Package_for_KB2467659_server~31bf3856ad364e35~x86~~6.0.1.1.mum
(fix) CBS MUM Missing CBS File Replaced Package_for_KB2467659_server~31bf3856ad364e35~x86~~6.0.1.1.mum from Cabinet: C:\windows\CheckSur\v1.0\windows6.0-6001-server-wave0.cab.
(fix) CBS Paired File CBS File also Replaced Package_for_KB2467659_server~31bf3856ad364e35~x86~~6.0.1.1.cat from Cabinet: C:\windows\CheckSur\v1.0\windows6.0-6001-server-wave0.cab.
(f) CBS MUM Missing 0x00000002 servicing\Packages\Package_for_KB2467659~31bf3856ad364e35~x86~~6.0.1.1.mum
(fix) CBS MUM Missing CBS File Replaced Package_for_KB2467659~31bf3856ad364e35~x86~~6.0.1.1.mum from Cabinet: C:\windows\CheckSur\v1.0\windows6.0-6001-server-wave0.cab.
(fix) CBS Paired File CBS File also Replaced Package_for_KB2467659~31bf3856ad364e35~x86~~6.0.1.1.cat from Cabinet: C:\windows\CheckSur\v1.0\windows6.0-6001-server-wave0.cab.

Checking Component Store
(f) CSI Manifest Missing 0x00000002 x86_3328765907efeda1f1b84fd870a8d97b_31bf3856ad364e35_6.0.6002.22541_none_23e10462e5e9c8d6.manifest x86_3328765907efeda1f1b84fd870a8d97b_31bf3856ad364e35_6.0.6002.22541_none_23e10462e5e9c8d6
(fix) CSI Manifest Missing CSI File Replaced File: x86_3328765907efeda1f1b84fd870a8d97b_31bf3856ad364e35_6.0.6002.22541_none_23e10462e5e9c8d6.manifest From: C:\windows\CheckSur\v1.0\windows6.0-6001-server-wave0.cab
(f) CSI Manifest Missing 0x00000002 x86_microsoft-windows-jolly-roger_31bf3856ad364e35_6.0.6002.22541_none_bc0eb0c39235c458.manifest x86_microsoft-windows-jolly-roger_31bf3856ad364e35_6.0.6002.22541_none_bc0eb0c39235c458
(fix) CSI Manifest Missing CSI File Replaced File: x86_microsoft-windows-jolly-roger_31bf3856ad364e35_6.0.6002.22541_none_bc0eb0c39235c458.manifest From: C:\windows\CheckSur\v1.0\windows6.0-6001-server-wave0.cab
(f) CSI Manifest Missing 0x00000002 amd64_policy.9.0.microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.1_none_3da38fdebd0e6822.manifest amd64_policy.9.0.microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.1_none_3da38fdebd0e6822
(f) CSI Manifest Missing 0x00000002 x86_14165530121d75c15400d055cdf4a391_31bf3856ad364e35_6.0.6001.18555_none_88f276b7745f9d43.manifest x86_14165530121d75c15400d055cdf4a391_31bf3856ad364e35_6.0.6001.18555_none_88f276b7745f9d43
(fix) CSI Manifest Missing CSI File Replaced File: x86_14165530121d75c15400d055cdf4a391_31bf3856ad364e35_6.0.6001.18555_none_88f276b7745f9d43.manifest From: C:\windows\CheckSur\v1.0\windows6.0-6001-server-wave0.cab
(f) CSI Manifest Missing 0x00000002 x86_microsoft-windows-jolly-roger_31bf3856ad364e35_6.0.6001.18555_none_b997cf807bf65669.manifest x86_microsoft-windows-jolly-roger_31bf3856ad364e35_6.0.6001.18555_none_b997cf807bf65669
(fix) CSI Manifest Missing CSI File Replaced File: x86_microsoft-windows-jolly-roger_31bf3856ad364e35_6.0.6001.18555_none_b997cf807bf65669.manifest From: C:\windows\CheckSur\v1.0\windows6.0-6001-server-wave0.cab
(f) CSI Manifest Missing 0x00000002 amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.1_none_99b61f5e8371c1d4.manifest amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.1_none_99b61f5e8371c1d4
(f) CSI Manifest Missing 0x00000002 x86_policy.9.0.microsoft.vc90.atl_1fc8b3b9a1e18e3b_9.0.21022.8_none_5d1777c2e857a23b.manifest x86_policy.9.0.microsoft.vc90.atl_1fc8b3b9a1e18e3b_9.0.21022.8_none_5d1777c2e857a23b
(f) CSI Manifest Missing 0x00000002 x86_microsoft.vc90.atl_1fc8b3b9a1e18e3b_9.0.21022.8_none_bdf22a22ab9e15d5.manifest x86_microsoft.vc90.atl_1fc8b3b9a1e18e3b_9.0.21022.8_none_bdf22a22ab9e15d5
(f) CSI Manifest Missing 0x00000002 x86_3214910dda2cdae14271d8dce138534f_31bf3856ad364e35_6.0.6002.18347_none_67e6d897050064ad.manifest x86_3214910dda2cdae14271d8dce138534f_31bf3856ad364e35_6.0.6002.18347_none_67e6d897050064ad
(fix) CSI Manifest Missing CSI File Replaced File: x86_3214910dda2cdae14271d8dce138534f_31bf3856ad364e35_6.0.6002.18347_none_67e6d897050064ad.manifest From: C:\windows\CheckSur\v1.0\windows6.0-6001-server-wave0.cab
(f) CSI Manifest Missing 0x00000002 x86_microsoft-windows-jolly-roger_31bf3856ad364e35_6.0.6002.18347_none_bb8b13ce7912bf71.manifest x86_microsoft-windows-jolly-roger_31bf3856ad364e35_6.0.6002.18347_none_bb8b13ce7912bf71
(fix) CSI Manifest Missing CSI File Replaced File: x86_microsoft-windows-jolly-roger_31bf3856ad364e35_6.0.6002.18347_none_bb8b13ce7912bf71.manifest From: C:\windows\CheckSur\v1.0\windows6.0-6001-server-wave0.cab
(f) CSI Manifest Missing 0x00000002 x86_0c2829fc3a4fd4f697f7392242a7dc21_31bf3856ad364e35_6.0.6001.22805_none_61b3ccbd5b9592e5.manifest x86_0c2829fc3a4fd4f697f7392242a7dc21_31bf3856ad364e35_6.0.6001.22805_none_61b3ccbd5b9592e5
(fix) CSI Manifest Missing CSI File Replaced File: x86_0c2829fc3a4fd4f697f7392242a7dc21_31bf3856ad364e35_6.0.6001.22805_none_61b3ccbd5b9592e5.manifest From: C:\windows\CheckSur\v1.0\windows6.0-6001-server-wave0.cab
(f) CSI Manifest Missing 0x00000002 x86_microsoft-windows-jolly-roger_31bf3856ad364e35_6.0.6001.22805_none_ba577fb394eb64cc.manifest x86_microsoft-windows-jolly-roger_31bf3856ad364e35_6.0.6001.22805_none_ba577fb394eb64cc
(fix) CSI Manifest Missing CSI File Replaced File: x86_microsoft-windows-jolly-roger_31bf3856ad364e35_6.0.6001.22805_none_ba577fb394eb64cc.manifest From: C:\windows\CheckSur\v1.0\windows6.0-6001-server-wave0.cab

Summary:
Seconds executed: 486
Found 18 errors
Fixed 14 errors
CSI Manifest Missing Total count: 12
Fixed: CSI Manifest Missing. Total count: 8
CBS MUM Missing Total count: 6
Fixed: CBS MUM Missing. Total count: 6
Fixed: CBS Paired File. Total count: 6

Unavailable repair files:
winsxs\manifests\amd64_policy.9.0.microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.1_none_3da38fdebd0e6822.manifest
winsxs\manifests\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.1_none_99b61f5e8371c1d4.manifest
winsxs\manifests\x86_policy.9.0.microsoft.vc90.atl_1fc8b3b9a1e18e3b_9.0.21022.8_none_5d1777c2e857a23b.manifest
winsxs\manifests\x86_microsoft.vc90.atl_1fc8b3b9a1e18e3b_9.0.21022.8_none_bdf22a22ab9e15d5.manifest

Checking CoreOS key for repairing corruptions.
Winner version: 6.0.6002.18971.
Processor architecture: x86.
Check key to be repaired: wcm://Microsoft-Windows-CoreOS?version=6.0.6002.18971&language=neutral&processorArchitecture=x86&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers\metadata\elements\ComputerName
Recreated value: @_type.
Recreated value: @dataOnly.
Recreated value: @default.
Recreated value: @description.
Recreated value: @displayName.
Recreated value: @handler.
Recreated value: @legacyName.
Recreated value: @legacyType.
Recreated value: @migrate.
Recreated value: @scope.
Recreated value: @xsd:type.
(w) Unable to get system disk properties 0x0000045D IOCTL_STORAGE_QUERY_PROPERTY Disk Cache

Joined
Jan 10, 2015
Posts
5,184
Location

USA




  • #6

I’d like some more details about the remaining files.

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.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip — do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip 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 — put [CODE][/CODE] tags around the log to break up the text.

View attachment SFCFix.zip

Joined
Sep 30, 2015
Posts
16




  • #7

SFCFix version 2.4.5.0 by niemiro.
Start time: 2015-10-02 14:04:30.065
Microsoft Windows Server 2008 Service Pack 2 - x86
Using .zip script file at C:\Users\dbressers\Desktop\SFCFix.zip [0]




Trace::
Failed to trace component amd64_policy.9.0.microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.1_none_3da38fdebd0e6822 with return code -3.

Failed to trace component amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.1_none_99b61f5e8371c1d4 with return code -3.

Failed to trace component x86_policy.9.0.microsoft.vc90.atl_1fc8b3b9a1e18e3b_9.0.21022.8_none_5d1777c2e857a23b with return code -3.

Failed to trace component x86_microsoft.vc90.atl_1fc8b3b9a1e18e3b_9.0.21022.8_none_bdf22a22ab9e15d5 with return code -3.
Trace:: directive completed successfully.




Successfully processed all directives.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2015-10-02 14:04:30.643
Script hash: +Tw0FfiCcuItzw5U3f3lSmri06IERUx+n5sgdIOo31c=
----------------------EOF-----------------------

Joined
Jan 10, 2015
Posts
5,184
Location

USA




  • #8

Let’s check for corrupt files.

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. Right click on cbs.txt and choose Send To -> Compressed (zipped) Folder. Attach cbs.zip from your Desktop to your next post.

Joined
Sep 30, 2015
Posts
16




  • #9

Let’s check for corrupt files.

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. Right click on cbs.txt and choose Send To -> Compressed (zipped) Folder. Attach cbs.zip from your Desktop to your next post.

Thank you!

View attachment CBS.zip

Joined
Jan 10, 2015
Posts
5,184
Location

USA




  • #10

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.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip — do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip 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 — put [CODE][/CODE] tags around the log to break up the text.

View attachment SFCFix.zip

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 zip and attach this to your next post.

Joined
Sep 30, 2015
Posts
16




  • #11

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.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip — do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip 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 — put [CODE][/CODE] tags around the log to break up the text.

View attachment 16770

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 zip and attach this to your next post.

Thank you

View attachment cbs.zip

Joined
Jan 10, 2015
Posts
5,184
Location

USA




  • #12

That looks good.

Please check for Windows Updates and install any that are offered.

If an update fails to install, zip up and attach C:\Windows\Logs\CBS\CBS.log with your reply.

Joined
Sep 30, 2015
Posts
16




  • #13

That looks good.

Please check for Windows Updates and install any that are offered.

If an update fails to install, zip up and attach C:\Windows\Logs\CBS\CBS.log with your reply.

Yes it updates not but SFC still fails?

Joined
Jan 10, 2015
Posts
5,184
Location

USA




  • #14

SFC is stating it found corrupt files and couldn’t fix them?

Go ahead and run SFC again, and then zip and attach C:\Windows\Logs\CBS\CBS.log

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 zip and attach this to your next post.

Joined
Sep 30, 2015
Posts
16




  • #15

SFC is stating it found corrupt files and couldn’t fix them?

Go ahead and run SFC again, and then zip and attach C:\Windows\Logs\CBS\CBS.log

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 zip and attach this to your next post.

View attachment cbs.zip

Joined
Jan 10, 2015
Posts
5,184
Location

USA




  • #16

Windows Update Package Replacement

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. Please download the attached file, Manifests.zip and save this to your Desktop.
  2. Right-click on the file and select Extract All…
  3. Tick the box labelled Show extracted files when complete then click Extract
  4. A window will open showing the folder Manifests
  5. Open the Manifests folder and copy the files into the following folder

    C:\Windows\Temp\CheckSur\Winsxs\Manifests

  6. Run the System Update Readiness Tool (SURT) again.
  7. When the SURT finishes installing, copy (Ctrl + C) and paste (Ctrl + V) the contents of the SURT log into your next post please:

    C:\Windows\Logs\CBS\CheckSUR.log

View attachment Manifests.zip

Joined
Sep 30, 2015
Posts
16




  • #17

Windows Update Package Replacement

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. Please download the attached file, Manifests.zip and save this to your Desktop.
  2. Right-click on the file and select Extract All…
  3. Tick the box labelled Show extracted files when complete then click Extract
  4. A window will open showing the folder Manifests
  5. Open the Manifests folder and copy the files into the following folder

    C:\Windows\Temp\CheckSur\Winsxs\Manifests

  6. Run the System Update Readiness Tool (SURT) again.
  7. When the SURT finishes installing, copy (Ctrl + C) and paste (Ctrl + V) the contents of the SURT log into your next post please:

    C:\Windows\Logs\CBS\CheckSUR.log

View attachment 16999 

=================================
Checking System Update Readiness.
Binary Version 6.0.6002.23186
Package Version 25.0
2015-10-19 12:06

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f)    CSI Manifest Missing    0x00000002    amd64_policy.9.0.microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.1_none_3da38fdebd0e6822.manifest    amd64_policy.9.0.microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.1_none_3da38fdebd0e6822    
(fix)    CSI Manifest Missing    CSI File Replaced    File: amd64_policy.9.0.microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.1_none_3da38fdebd0e6822.manifest From: C:\windows\CheckSur\v1.0\windows6.0-6001-server-wave0.cab
(f)    CSI Manifest Missing    0x00000002    amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.1_none_99b61f5e8371c1d4.manifest    amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.1_none_99b61f5e8371c1d4    
(fix)    CSI Manifest Missing    CSI File Replaced    File: amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.1_none_99b61f5e8371c1d4.manifest From: C:\windows\CheckSur\v1.0\windows6.0-6001-server-wave0.cab
(f)    CSI Payload File Missing    0x00000000    msvcr90.dll    amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.1_none_99b61f5e8371c1d4    
(f)    CSI Payload File Missing    0x00000000    msvcp90.dll    amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.1_none_99b61f5e8371c1d4    
(f)    CSI Payload File Missing    0x00000000    msvcm90.dll    amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.1_none_99b61f5e8371c1d4    
(f)    CSI Manifest Missing    0x00000002    x86_policy.9.0.microsoft.vc90.atl_1fc8b3b9a1e18e3b_9.0.21022.8_none_5d1777c2e857a23b.manifest    x86_policy.9.0.microsoft.vc90.atl_1fc8b3b9a1e18e3b_9.0.21022.8_none_5d1777c2e857a23b    
(fix)    CSI Manifest Missing    CSI File Replaced    File: x86_policy.9.0.microsoft.vc90.atl_1fc8b3b9a1e18e3b_9.0.21022.8_none_5d1777c2e857a23b.manifest From: C:\windows\CheckSur\v1.0\windows6.0-6001-server-wave0.cab
(f)    CSI Manifest Missing    0x00000002    x86_microsoft.vc90.atl_1fc8b3b9a1e18e3b_9.0.21022.8_none_bdf22a22ab9e15d5.manifest    x86_microsoft.vc90.atl_1fc8b3b9a1e18e3b_9.0.21022.8_none_bdf22a22ab9e15d5    
(fix)    CSI Manifest Missing    CSI File Replaced    File: x86_microsoft.vc90.atl_1fc8b3b9a1e18e3b_9.0.21022.8_none_bdf22a22ab9e15d5.manifest From: C:\windows\CheckSur\v1.0\windows6.0-6001-server-wave0.cab
(f)    CSI Payload File Missing    0x00000000    ATL90.dll    x86_microsoft.vc90.atl_1fc8b3b9a1e18e3b_9.0.21022.8_none_bdf22a22ab9e15d5    

Summary:
Seconds executed: 473
 Found 8 errors
 Fixed 4 errors
  CSI Manifest Missing Total count: 4
  Fixed: CSI Manifest Missing.  Total count: 4
  CSI Payload File Missing Total count: 4

Checking CoreOS key for repairing corruptions.
Winner version: 6.0.6002.18971.
Processor architecture: x86.
Check key to be repaired: wcm://Microsoft-Windows-CoreOS?version=6.0.6002.18971&language=neutral&processorArchitecture=x86&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers\metadata\elements\ComputerName
Recreated value: @_type.
Recreated value: @dataOnly.
Recreated value: @default.
Recreated value: @description.
Recreated value: @displayName.
Recreated value: @handler.
Recreated value: @legacyName.
Recreated value: @legacyType.
Recreated value: @migrate.
Recreated value: @scope.
Recreated value: @xsd:type.
(w)    Unable to get system disk properties    0x0000045D    IOCTL_STORAGE_QUERY_PROPERTY    Disk Cache

Joined
Jan 10, 2015
Posts
5,184
Location

USA




  • #18

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.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip — do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip 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 — put [CODE][/CODE] tags around the log to break up the text.

View attachment SFCFix.zip

Once SFCFix has completed, run the System Update Readiness Tool again.
When SURT has finished, attach C:\Windows\Logs\CBS\CheckSUR.log with your reply.

Joined
Sep 30, 2015
Posts
16




  • #19

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.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip — do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip 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 — put [CODE][/CODE] tags around the log to break up the text.

View attachment 17001

Once SFCFix has completed, run the System Update Readiness Tool again.
When SURT has finished, attach C:\Windows\Logs\CBS\CheckSUR.log with your reply. 

SFCFix version 2.4.5.0 by niemiro.
Start time: 2015-10-19 12:34:06.967
Microsoft Windows Server 2008 Service Pack 2 - x86
Using .zip script file at C:\Users\dbressers\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\windows\WinSxS\x86_microsoft.vc90.atl_1fc8b3b9a1e18e3b_9.0.21022.8_none_bdf22a22ab9e15d5
Successfully took permissions for file or folder C:\windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.1_none_99b61f5e8371c1d4

Successfully copied file C:\Users\dbressers\AppData\Local\niemiro\Archive\WinSxS\x86_microsoft.vc90.atl_1fc8b3b9a1e18e3b_9.0.21022.8_none_bdf22a22ab9e15d5\ATL90.dll to C:\windows\WinSxS\x86_microsoft.vc90.atl_1fc8b3b9a1e18e3b_9.0.21022.8_none_bdf22a22ab9e15d5\ATL90.dll.
Successfully copied file C:\Users\dbressers\AppData\Local\niemiro\Archive\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.1_none_99b61f5e8371c1d4\msvcm90.dll to C:\windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.1_none_99b61f5e8371c1d4\msvcm90.dll.
Successfully copied file C:\Users\dbressers\AppData\Local\niemiro\Archive\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.1_none_99b61f5e8371c1d4\msvcp90.dll to C:\windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.1_none_99b61f5e8371c1d4\msvcp90.dll.
Successfully copied file C:\Users\dbressers\AppData\Local\niemiro\Archive\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.1_none_99b61f5e8371c1d4\msvcr90.dll to C:\windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.1_none_99b61f5e8371c1d4\msvcr90.dll.

Successfully restored ownership for C:\windows\WinSxS\x86_microsoft.vc90.atl_1fc8b3b9a1e18e3b_9.0.21022.8_none_bdf22a22ab9e15d5
Successfully restored permissions on C:\windows\WinSxS\x86_microsoft.vc90.atl_1fc8b3b9a1e18e3b_9.0.21022.8_none_bdf22a22ab9e15d5
Successfully restored ownership for C:\windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.1_none_99b61f5e8371c1d4
Successfully restored permissions on C:\windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.1_none_99b61f5e8371c1d4
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 5 datablocks.
Finish time: 2015-10-19 12:34:07.904
Script hash: 91LST0Gf8XON5FH5jHyDD0Fj7r/n/GWpk6oYxqJfHts=
----------------------EOF-----------------------

=================================
Checking System Update Readiness.
Binary Version 6.0.6002.23186
Package Version 25.0
2015-10-19 12:36

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store

Summary:
Seconds executed: 447
 No errors detected

Checking CoreOS key for repairing corruptions.
Winner version: 6.0.6002.18971.
Processor architecture: x86.
Check key to be repaired: wcm://Microsoft-Windows-CoreOS?version=6.0.6002.18971&language=neutral&processorArchitecture=x86&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers\metadata\elements\ComputerName
Recreated value: @_type.
Recreated value: @dataOnly.
Recreated value: @default.
Recreated value: @description.
Recreated value: @displayName.
Recreated value: @handler.
Recreated value: @legacyName.
Recreated value: @legacyType.
Recreated value: @migrate.
Recreated value: @scope.
Recreated value: @xsd:type.
(w)    Unable to get system disk properties    0x0000045D    IOCTL_STORAGE_QUERY_PROPERTY    Disk Cache

Joined
Jan 10, 2015
Posts
5,184
Location

USA




  • #20

Very good, looks like that was it.

If you would like, run SFC again to verify if it reports no corrupt files.

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

  • Microsoft Support & Malware Removal

  • Windows Update

Источник

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Sign up

Источник

From Wikipedia, the free encyclopedia

sfc

Developer(s) Microsoft
Initial release June 25, 1998; 26 years ago
Operating system Microsoft Windows
Type System utility
License Proprietary commercial software
Website docs.microsoft.com/en-us/windows-server/administration/windows-commands/sfc

System File Checker (SFC[1]) is a utility in Microsoft Windows that allows users to scan for and restore corrupted Windows system files.[2]

Microsoft ships this utility with Windows 98, Windows 2000 and all subsequent versions of the Windows NT family of operating systems. In Windows Vista, Windows 7 and Windows 10, System File Checker is integrated with Windows Resource Protection (WRP), which protects registry keys and folders as well as critical system files. Under Windows Vista, sfc.exe can be used to check specific folder paths, including the Windows folder and the boot folder.

Windows File Protection (WFP) works by registering for notification of file changes in Winlogon. If any changes are detected to a protected system file, the modified file is restored from a cached copy located in a compressed folder at %WinDir%\System32\dllcache.

Windows Resource Protection (WRP) works by setting discretionary access-control lists (DACLs) and access control lists (ACLs) defined for protected resources. If any changes are detected to a protected system file, the modified file is restored from a cached copy located in a folder at %WinDir%\WinSxS\Backup.[3] Permission for full access to modify WRP-protected resources is restricted to the processes using the Windows Modules Installer service (TrustedInstaller.exe). Administrators no longer have full rights to system files.

Due to problems with Windows applications being able to overwrite system files in Windows 95, Microsoft has since implemented a number of security measures to protect system files from malicious attacks, corruptions, or problems such as DLL Hell.

System File Checker was first introduced on Windows 98 as a GUI utility. It offered scanning and restoration of corrupted system files by matching the version number against a database containing the original version number of the files in a fresh Windows 98 installation. This method of file protection was basic. It determined system files by file extension and file path. It was able to restore files from the installation media or a source specified by the user. Windows 98 did not offer real-time system file protection beyond file attributes; therefore, no preventive or reactive measure was available.

All Windows NT-based operating systems since Windows 2000 introduced real-time file protection, called Windows File Protection (WFP).[4]

In addition, the System File Checker utility (sfc.exe) was reimplemented as a more robust command-line utility that integrated with WFP. Unlike the Windows 98 SFC utility, the new utility forces a scan of protected system files using Windows File Protection and allows the immediate silent restoration of system files from the DLLCache folder or installation media.

SFC did not appear on Windows Me,[5] as it was replaced with System File Protection (SFP).[6] Similar to WFP, SFP offered real-time protection.

The System File Checker component included with versions of Windows 2000 earlier than Service Pack 4 overrode patches distributed by Microsoft;[7] this was rectified in Windows 2000 Service Pack 4.

In Windows NT-based operating systems, System File Checker can be invoked via Windows Command Prompt (with Admin privilege[8]), with the following command:

  • sfc /scannow (to repair problems)
  • or sfc /verifyonly (no repair)

If it finds a problem, it will attempt to replace the problematic files from the DLL Cache (%WinDir%\System32\dllcache). If the file is not in the DLL Cache or the DLL Cache is corrupted, the user will be prompted to insert the Windows installation media or provide the network installation path. System File Checker determines the Windows installation source path from the registry values SourcePath and ServicePackSourcePath.[9] It may keep prompting for the installation media even if the user supplies it if these values are not correctly set.[10]

In Windows Vista and onwards, files are protected using access control lists (ACLs), and if it finds a problem, it will attempt to replace the problematic files from the Windows Side-by-side Backup (%WinDir%\WinSxS\Backup).[3] However, the above command has not changed.

System File Checker in Windows Vista and later Windows operating systems can scan specified files. Also, scans can be performed against an offline Windows installation folder to replace corrupt files, in case the Windows installation is not bootable. For performing offline scans, System File Checker must be run from another working installation of Windows Vista or a later operating system or from the Windows setup DVD[11] or a recovery drive which gives access to the Windows Recovery Environment.

In cases where the component store is corrupted, the «System Update Readiness tool» (CheckSUR) can be installed on Windows 7, Windows Vista, Windows Server 2008 R2 or Windows Server 2008, replaced by «Deployment Image Service and Management Tool» (DISM) for Windows 10, Windows 8.1, Windows 8, Windows Server 2012 R2 or Windows Server 2012. This tool checks the store against its own payload and repairs the corruptions that it detects by downloading required files through Windows update.[12]

  1. ^
    Boswell, William (2003). «Using the System File Checker, SFC». Inside Windows Server 2003. Inside Series. p. 860. ISBN 9780735711587. Retrieved 2017-07-23. You do not need to hack the Registry to change the WFP settings. A command-line utility comes with Windows Server 2003 to set these values. Called the System File Checker, or SFC, the utility can also rebuild the D11Cache directory files if files are accidentally deleted.
  2. ^ «MS-DOS and Windows command line SFC command».
  3. ^ a b stevewhims (2021-01-07). «Protected Resource List — Win32 apps». learn.microsoft.com. Retrieved 2024-03-15.
  4. ^ «Description of the Windows File Protection Feature». Support. Microsoft. December 15, 2003. Archived from the original on October 20, 2004. Retrieved August 28, 2006.
  5. ^ Spector, Lincoln (February 14, 2001). «Answer Line: Windows 98 Utilities Missing in Windows Me?». PC World. IDG. Archived from the original on June 5, 2011. Retrieved December 26, 2011.
  6. ^ «System File Protection and Windows Me». Microsoft. December 4, 2011. Archived from the original on June 22, 2004. Retrieved August 28, 2006.
  7. ^
    «The SFC /SCANNOW Command May Overwrite Hotfix Files». Support. Microsoft. October 30, 2006. Archived from the original on November 16, 2006. Retrieved February 1, 2010.
  8. ^ «SFC — System File CheckerWindows CMD». SS64.com. Retrieved 2023-09-12.
  9. ^ «System File Checker does not accept a network location that contains the installer CD when you use the scannow switch in Windows XP SP2 or in Windows Server 2003». Support. Microsoft. January 13, 2005. Archived from the original on January 16, 2007.
  10. ^ «You are prompted to insert a Windows XP SP2 CD when you try to run the System File Checker tool on a Windows XP SP2-based computer». Support. Microsoft. July 5, 2005. Archived from the original on February 7, 2007.
  11. ^ kumar, Rohit (26 July 2016). «Run System File Checker Tool to Repair Windows 10/8/7 files». Craxworld. Self Published. Archived from the original on September 11, 2016.
  12. ^ «Fix Windows Update errors by using the DISM or System Update Readiness tool». Support. Microsoft. January 22, 2017. Retrieved February 11, 2017.
  • Frisch, Æleen (2001). Windows 2000 Commands Pocket Reference. O’Reilly. ISBN 978-0-596-00148-3.
  • John Paul Mueller (2007). Windows Administration at the Command Line for Windows Vista, Windows 2003, Windows XP, and Windows 2000. John Wiley & Sons. ISBN 978-0470165799.
  • sfc | Microsoft Docs
  • Use the System File Checker tool to repair missing or corrupted system files
  • Description of Windows XP and Windows Server 2003 System File Checker (Sfc.exe)

Источник

Понравилась статья? Поделить с друзьями:
0 0 голоса
Рейтинг статьи
Подписаться
Уведомить о
guest

0 комментариев
Старые
Новые Популярные
Межтекстовые Отзывы
Посмотреть все комментарии
  • Что означает windows problem reporting
  • Умный дом программа на windows
  • Параметры windows 7 приложения как открыть
  • Код события 10010 windows 10 как исправить
  • Опера грузит процессор на 100 что делать windows 10