[SOLVED] Server 2012R2 Security Monthly Rollup failing not installing.
- Thread starter Vdub
- Start date
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.
- Download the file SFCFix.zip and save it on your desktop.
- Save any work you have open, and close all programs.
- Drag the SFCFix.zip file over the
SFCFix.exe executable and release it.
- SFCFix will launch, let it complete.
- Once done, a file will appear on your desktop, called SFCFix.txt.
- Attach that file to your next reply.
The log looks good.
Restart the machine.
Run the command
If it fails copy the file c:\Windows\Logs\CBS\cbs.log to your desktop.
Zip the copied file and attach the zipped cbs.log to your next reply.
Restart the machine.
Run the command
sfc /scannow in an elevated commandprompt and report the result.If it fails copy the file c:\Windows\Logs\CBS\cbs.log to your desktop.
Zip the copied file and attach the zipped cbs.log to your next reply.
It failed again.
C:\windows\system32>sfc /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 81% complete.
Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.
Log file attached.
C:\windows\system32>sfc /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 81% complete.
Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.
Log file attached.
Step 1:
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.
Step 2:
Restart the machine.
Run the command
If it fails copy the file c:\Windows\Logs\CBS\cbs.log to your desktop.
Zip the copied file and attach the zipped cbs.log to your next reply.
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.
- Download the attachment SFCFix.zip and save it on your desktop.
- Save any work you have open, and close all programs.
- Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
- SFCFix will launch, let it complete.
- Once done, a file will appear on your desktop, called SFCFix.txt.
- Open the file, then copy and paste its content in your next reply.
Step 2:
Restart the machine.
Run the command
sfc /scannow in an elevated commandprompt and report the result.If it fails copy the file c:\Windows\Logs\CBS\cbs.log to your desktop.
Zip the copied file and attach the zipped cbs.log to your next reply.
Step 2 done.
Failures still detected.
C:\windows\system32>sfc /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.
CBS.log attached.
Failures still detected.
C:\windows\system32>sfc /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.
CBS.log attached.
Step 1:
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.
Step 2:
Restart the machine.
Run the command
If it fails copy the file c:\Windows\Logs\CBS\cbs.log to your desktop.
Zip the copied file and attach the zipped cbs.log to your next reply.
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.
- Download the attachment SFCFix.zip and save it on your desktop.
- Save any work you have open, and close all programs.
- Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
- SFCFix will launch, let it complete.
- Once done, a file will appear on your desktop, called SFCFix.txt.
- Open the file, then copy and paste its content in your next reply.
Step 2:
Restart the machine.
Run the command
sfc /scannow in an elevated commandprompt and report the result.If it fails copy the file c:\Windows\Logs\CBS\cbs.log to your desktop.
Zip the copied file and attach the zipped cbs.log to your next reply.
Has Sysnative Forums helped you? Please consider donating to help us support the site!