tjsepka
Contributor
I'm not sure what it means, but I noticed I got the same error as above creating a restore point. The event log said the restore point was successfully created.
Last edited:
[SOLVED] SFC found corrupt files that it can't fix
- Thread starter tjsepka
- Start date
zcomputerwiz
Windows Update Expert
Looks like the VSS System Writer is still missing.
At this point you may want to consider a repair installation (in-place upgrade) of Windows. Do you have Windows 7 SP1 installation media available?
At this point you may want to consider a repair installation (in-place upgrade) of Windows. Do you have Windows 7 SP1 installation media available?
tjsepka
Contributor
It's been a while since I last tried a repair installation (it wasn't successful), but I've made a lot of changes to the system since then. I do have installation media available and know how to do this. I'll probably try some other things I've found in researching this before I resort to doing a repair installation. I'll update this thread as I work forward with this.
The VSS problem is not critical since my backups are working, and I'm able to access shadow copies using ShadowExplorer (if I ever have a need to do it...). My biggest issue is not being able to run sfc /scannow from even a command prompt via the installation CD, let alone safe and normal modes. Some of the other issues I'm trying to clear up all point back to being able to run sfc. One issue is getting Windows media player to launch, but I do have other more important things needing repair (I can't recall them right now, because I'm in a rush right now - I need to keep a written list!).
Since starting down fixing things on my machine, I've accomplished:
1.) Completely repairing damaged sxs;
2.) Restored the capability to boot into safe mode (details in another forum's thread).
Thanks for your help so far, and if you run across anything, please let me know. As I said, I'll update this thread as I move forward.
The VSS problem is not critical since my backups are working, and I'm able to access shadow copies using ShadowExplorer (if I ever have a need to do it...). My biggest issue is not being able to run sfc /scannow from even a command prompt via the installation CD, let alone safe and normal modes. Some of the other issues I'm trying to clear up all point back to being able to run sfc. One issue is getting Windows media player to launch, but I do have other more important things needing repair (I can't recall them right now, because I'm in a rush right now - I need to keep a written list!).
Since starting down fixing things on my machine, I've accomplished:
1.) Completely repairing damaged sxs;
2.) Restored the capability to boot into safe mode (details in another forum's thread).
Thanks for your help so far, and if you run across anything, please let me know. As I said, I'll update this thread as I move forward.
zcomputerwiz
Windows Update Expert
The fact that SFC will not run from external media is troubling, and without a log being produced it will be difficult to determine an appropriate course of action.
I'd like to get more specific information about where the failure is occurring when running SFC in Windows, normal mode.
Please collect another process monitor trace without any filters. Start the trace before running SFC, stop the trace about a minute *after* SFC reports failure so we don't miss anything.
Zip the trace file and CBS.log, then upload to a file sharing site and include the link here.
I'd like to get more specific information about where the failure is occurring when running SFC in Windows, normal mode.
Please collect another process monitor trace without any filters. Start the trace before running SFC, stop the trace about a minute *after* SFC reports failure so we don't miss anything.
Zip the trace file and CBS.log, then upload to a file sharing site and include the link here.
tjsepka
Contributor
An unfiltered, normal mode procmon pml file can be found here since it's 10.5 MB compressed and can't be attached:
sfc logfile normal mode.zip - Google Drive
I'll experiment to see if I can get a safe mode version.
The cbs.log file is attached, but based on its time (13:05) & date (12/09/2016), doesn't appear to have been touched by the attempt at sfc (pml time was 17:44).
Tom
sfc logfile normal mode.zip - Google Drive
I'll experiment to see if I can get a safe mode version.
The cbs.log file is attached, but based on its time (13:05) & date (12/09/2016), doesn't appear to have been touched by the attempt at sfc (pml time was 17:44).
Tom
Last edited:
tjsepka
Contributor
Here's a link to a procmon capture with AVG temporarily disabled (same error message: Windows Resource Protection could not start the repair service.).
sfc logfile normal mode avg temporarily disabled.zip - Google Drive
sfc logfile normal mode avg temporarily disabled.zip - Google Drive
tjsepka
Contributor
I've attached a procmon pml file generated from trying to run sfc in safe mode. I tried twice so that's what the pml file contains.
When trying to run sfc from via a boot disk command prompt, I've been referring to this for reference:
Mike's Technology and Finance Blog: How to Perform an Offline System Integrity Verification
However, I've been using:
sfc /scannow /offbootdir=c:\ /offwindir=c:\windows
which is a little bit different than shown in the link above. It's run in the past saying it couldn't repair all of the problems it found. Not it says it can't run because of resource protection. My disk information is shown in the attached jpegs.
I wonder if part of running it via the boot dick in a command prompt window has something to do with system reserved partition not having a drive letter as used as shown in the link above?
Any thought would be appreciated!
When trying to run sfc from via a boot disk command prompt, I've been referring to this for reference:
Mike's Technology and Finance Blog: How to Perform an Offline System Integrity Verification
However, I've been using:
sfc /scannow /offbootdir=c:\ /offwindir=c:\windows
which is a little bit different than shown in the link above. It's run in the past saying it couldn't repair all of the problems it found. Not it says it can't run because of resource protection. My disk information is shown in the attached jpegs.
I wonder if part of running it via the boot dick in a command prompt window has something to do with system reserved partition not having a drive letter as used as shown in the link above?
Any thought would be appreciated!
Attachments
Last edited:
zcomputerwiz
Windows Update Expert
The drive letter may be different in the recovery environment. What shows up if you run:
bcdedit | find "osdevice"
in the recovery environment command prompt?
bcdedit | find "osdevice"
in the recovery environment command prompt?
tjsepka
Contributor
osdevice partition C:
Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=C:
path \bootmgr
description Windows Boot Manager
locale en-US
default {default}
resumeobject {bbda5bdc-5f7a-11e4-909d-806e6f6e6963}
displayorder {default}
timeout 30
displaybootmenu Yes
Windows Boot Loader
-------------------
identifier {default}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7 Home Premium
locale en-US
osdevice partition=C:
systemroot \Windows
resumeobject {bbda5bdc-5f7a-11e4-909d-806e6f6e6963}
bootlog Yes
Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=C:
path \bootmgr
description Windows Boot Manager
locale en-US
default {default}
resumeobject {bbda5bdc-5f7a-11e4-909d-806e6f6e6963}
displayorder {default}
timeout 30
displaybootmenu Yes
Windows Boot Loader
-------------------
identifier {default}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7 Home Premium
locale en-US
osdevice partition=C:
systemroot \Windows
resumeobject {bbda5bdc-5f7a-11e4-909d-806e6f6e6963}
bootlog Yes
tjsepka
Contributor
I reran Windows6.1-KB947821-v34-x86.msu (system update readiness tool) to see if anything changed. It ran cleanly the last time I ran it, but now it contains some errors. CheckSUR.log is attached.
tjsepka
Contributor
Attached is the output from SFCFix.exe.
zcomputerwiz
Windows Update Expert
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.
View attachment SFCFix.zip
Once complete, run SURT again and attach CheckSUR.log with your reply.
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.
- Download SFCFix.exe (by niemiro) and save this to your Desktop.
- Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
- Save any open documents and close all open windows.
- On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
- Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
- SFCFix will now process the script.
- Upon completion, a file should be created on your Desktop: SFCFix.txt.
- Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.
View attachment SFCFix.zip
Once complete, run SURT again and attach CheckSUR.log with your reply.
tjsepka
Contributor
Here's the SFCFix output (corresponding CheckSUR output is attached):
Code:
SFCFix version 3.0.0.0 by niemiro.
Start time: 2016-12-14 10:42:48.285
Microsoft Windows 7 Service Pack 1 - x86
Using .zip script file at C:\Users\tjs\Desktop\SFCFix.zip [0]
PowerCopy::
Successfully took permissions for file or folder C:\Windows\winsxs\x86_wcf-infocard_api_dll_31bf3856ad364e35_6.1.7601.18523_none_a5e27db60deb6bc8
Successfully took permissions for file or folder C:\Windows\winsxs\x86_netfx-netfxsbs10_exe_31bf3856ad364e35_6.1.7601.17514_none_3d9659600c3683e3
Successfully took permissions for file or folder C:\Windows\winsxs\x86_netfx-dw_b03f5f7f11d50a3a_6.1.7601.18523_none_a1f9e3b9d7db7cad
Successfully took permissions for file or folder C:\Windows\winsxs\x86_microsoft.windows.h..display-driverclass_31bf3856ad364e35_6.1.7600.16385_none_43670cedf1a9c429
Successfully took permissions for file or folder C:\Windows\winsxs\x86_microsoft-windows-tzutil_31bf3856ad364e35_6.1.7601.17514_none_364b3ec461692953
Successfully took permissions for file or folder C:\Windows\winsxs\x86_microsoft-windows-time-tool_31bf3856ad364e35_6.1.7601.17514_none_ef1085419a309311
Successfully took permissions for file or folder C:\Windows\winsxs\x86_microsoft-windows-t..dp-winstationdriver_31bf3856ad364e35_6.1.7601.18540_none_4d586a7f3360a97d
Successfully took permissions for file or folder C:\Windows\winsxs\x86_microsoft-windows-sonic-tables-2th1_31bf3856ad364e35_6.1.7600.16385_none_6f9196b4c105ea8d
Successfully took permissions for file or folder C:\Windows\winsxs\x86_microsoft-windows-setup-adm_31bf3856ad364e35_6.1.7600.16385_none_7ece2f48e3472311
Successfully took permissions for file or folder C:\Windows\winsxs\x86_microsoft-windows-s..sktopini-sendtouser_31bf3856ad364e35_6.1.7600.16385_none_081ae7a4f56c5467
Successfully took permissions for file or folder C:\Windows\winsxs\x86_microsoft-windows-s..opini-accessibility_31bf3856ad364e35_6.1.7600.16385_none_da41b324de9c3847
Successfully took permissions for file or folder C:\Windows\winsxs\x86_microsoft-windows-s..ktopini-systemtools_31bf3856ad364e35_6.1.7600.16385_none_7e4396bce8f78221
Successfully took permissions for file or folder C:\Windows\winsxs\x86_microsoft-windows-s..ktopini-maintenance_31bf3856ad364e35_6.1.7600.16385_none_5e708a1ffe7aa932
Successfully took permissions for file or folder C:\Windows\winsxs\x86_microsoft-windows-s..ktopini-accessories_31bf3856ad364e35_6.1.7600.16385_none_ebed72081abd7309
Successfully took permissions for file or folder C:\Windows\winsxs\x86_microsoft-windows-s..ini-systemtoolsuser_31bf3856ad364e35_6.1.7600.16385_none_208203e244db0d22
Successfully took permissions for file or folder C:\Windows\winsxs\x86_microsoft-windows-s..ini-maintenanceuser_31bf3856ad364e35_6.1.7600.16385_none_05ddf62fb732aa51
Successfully took permissions for file or folder C:\Windows\winsxs\x86_microsoft-windows-s..ini-accessoriesuser_31bf3856ad364e35_6.1.7600.16385_none_23da83d97579563a
Successfully took permissions for file or folder C:\Windows\winsxs\x86_microsoft-windows-s..i-accessibilityuser_31bf3856ad364e35_6.1.7600.16385_none_631ad0256a1095cc
Successfully took permissions for file or folder C:\Windows\winsxs\x86_microsoft-windows-s..-binaries.resources_31bf3856ad364e35_6.1.7601.17514_lt-lt_cd37305567da84e8
Successfully took permissions for file or folder C:\Windows\winsxs\x86_microsoft-windows-s..-binaries.resources_31bf3856ad364e35_6.1.7601.17514_el-gr_56d73702c6334f9e
Successfully took permissions for file or folder C:\Windows\winsxs\x86_microsoft-windows-mspaint_31bf3856ad364e35_6.1.7600.16385_none_8df3dcc84fe54e8b
Successfully took permissions for file or folder C:\Windows\winsxs\x86_microsoft-windows-iologgingdll.resources_31bf3856ad364e35_6.1.7601.22589_en-us_f7556e6951263ab9
Successfully took permissions for file or folder C:\Windows\winsxs\x86_microsoft-windows-ie-f12.resources_31bf3856ad364e35_11.2.9600.17041_en-us_f6a96f63b61c8b5f
Successfully took permissions for file or folder C:\Windows\winsxs\x86_microsoft-windows-energyefficiencywizard_31bf3856ad364e35_6.1.7600.16385_none_18a686bb98480f0f
Successfully took permissions for file or folder C:\Windows\winsxs\x86_microsoft-windows-ehome-reg-inf_31bf3856ad364e35_6.1.7601.17514_none_f733aa7021315a64
Successfully took permissions for file or folder C:\Windows\winsxs\x86_microsoft-windows-edition-transmogrifier_31bf3856ad364e35_6.1.7601.17514_none_17983cea99707d4c
Successfully took permissions for file or folder C:\Windows\winsxs\msil_system.runtime.seri..ion.formatters.soap_b03f5f7f11d50a3a_6.1.7601.22733_none_05a3bea3fa19258c
Successfully took permissions for file or folder C:\Windows\winsxs\msil_accessibility_b03f5f7f11d50a3a_6.1.7601.18523_none_2208500a4f9f1a4d
Successfully copied file C:\Users\tjs\AppData\Local\niemiro\Archive\winsxs\x86_wcf-infocard_api_dll_31bf3856ad364e35_6.1.7601.18523_none_a5e27db60deb6bc8\infocardapi.dll to C:\Windows\winsxs\x86_wcf-infocard_api_dll_31bf3856ad364e35_6.1.7601.18523_none_a5e27db60deb6bc8\infocardapi.dll.
Successfully copied file C:\Users\tjs\AppData\Local\niemiro\Archive\winsxs\x86_netfx-netfxsbs10_exe_31bf3856ad364e35_6.1.7601.17514_none_3d9659600c3683e3\NETFXSBS10.exe to C:\Windows\winsxs\x86_netfx-netfxsbs10_exe_31bf3856ad364e35_6.1.7601.17514_none_3d9659600c3683e3\NETFXSBS10.exe.
Successfully copied file C:\Users\tjs\AppData\Local\niemiro\Archive\winsxs\x86_netfx-dw_b03f5f7f11d50a3a_6.1.7601.18523_none_a1f9e3b9d7db7cad\dw20.exe to C:\Windows\winsxs\x86_netfx-dw_b03f5f7f11d50a3a_6.1.7601.18523_none_a1f9e3b9d7db7cad\dw20.exe.
Successfully copied file C:\Users\tjs\AppData\Local\niemiro\Archive\winsxs\x86_microsoft.windows.h..display-driverclass_31bf3856ad364e35_6.1.7600.16385_none_43670cedf1a9c429\dispci.dll to C:\Windows\winsxs\x86_microsoft.windows.h..display-driverclass_31bf3856ad364e35_6.1.7600.16385_none_43670cedf1a9c429\dispci.dll.
Successfully copied file C:\Users\tjs\AppData\Local\niemiro\Archive\winsxs\x86_microsoft-windows-tzutil_31bf3856ad364e35_6.1.7601.17514_none_364b3ec461692953\tzutil.exe to C:\Windows\winsxs\x86_microsoft-windows-tzutil_31bf3856ad364e35_6.1.7601.17514_none_364b3ec461692953\tzutil.exe.
Successfully copied file C:\Users\tjs\AppData\Local\niemiro\Archive\winsxs\x86_microsoft-windows-time-tool_31bf3856ad364e35_6.1.7601.17514_none_ef1085419a309311\w32tm.exe to C:\Windows\winsxs\x86_microsoft-windows-time-tool_31bf3856ad364e35_6.1.7601.17514_none_ef1085419a309311\w32tm.exe.
Successfully copied file C:\Users\tjs\AppData\Local\niemiro\Archive\winsxs\x86_microsoft-windows-t..dp-winstationdriver_31bf3856ad364e35_6.1.7601.18540_none_4d586a7f3360a97d\rdpwd.sys to C:\Windows\winsxs\x86_microsoft-windows-t..dp-winstationdriver_31bf3856ad364e35_6.1.7601.18540_none_4d586a7f3360a97d\rdpwd.sys.
Successfully copied file C:\Users\tjs\AppData\Local\niemiro\Archive\winsxs\x86_microsoft-windows-sonic-tables-2th1_31bf3856ad364e35_6.1.7600.16385_none_6f9196b4c105ea8d\2th1 to C:\Windows\winsxs\x86_microsoft-windows-sonic-tables-2th1_31bf3856ad364e35_6.1.7600.16385_none_6f9196b4c105ea8d\2th1.
Successfully copied file C:\Users\tjs\AppData\Local\niemiro\Archive\winsxs\x86_microsoft-windows-setup-adm_31bf3856ad364e35_6.1.7600.16385_none_7ece2f48e3472311\Setup.admx to C:\Windows\winsxs\x86_microsoft-windows-setup-adm_31bf3856ad364e35_6.1.7600.16385_none_7ece2f48e3472311\Setup.admx.
Successfully copied file C:\Users\tjs\AppData\Local\niemiro\Archive\winsxs\x86_microsoft-windows-s..sktopini-sendtouser_31bf3856ad364e35_6.1.7600.16385_none_081ae7a4f56c5467\Desktop.ini to C:\Windows\winsxs\x86_microsoft-windows-s..sktopini-sendtouser_31bf3856ad364e35_6.1.7600.16385_none_081ae7a4f56c5467\Desktop.ini.
Successfully copied file C:\Users\tjs\AppData\Local\niemiro\Archive\winsxs\x86_microsoft-windows-s..opini-accessibility_31bf3856ad364e35_6.1.7600.16385_none_da41b324de9c3847\Desktop.ini to C:\Windows\winsxs\x86_microsoft-windows-s..opini-accessibility_31bf3856ad364e35_6.1.7600.16385_none_da41b324de9c3847\Desktop.ini.
Successfully copied file C:\Users\tjs\AppData\Local\niemiro\Archive\winsxs\x86_microsoft-windows-s..ktopini-systemtools_31bf3856ad364e35_6.1.7600.16385_none_7e4396bce8f78221\Desktop.ini to C:\Windows\winsxs\x86_microsoft-windows-s..ktopini-systemtools_31bf3856ad364e35_6.1.7600.16385_none_7e4396bce8f78221\Desktop.ini.
Successfully copied file C:\Users\tjs\AppData\Local\niemiro\Archive\winsxs\x86_microsoft-windows-s..ktopini-maintenance_31bf3856ad364e35_6.1.7600.16385_none_5e708a1ffe7aa932\Desktop.ini to C:\Windows\winsxs\x86_microsoft-windows-s..ktopini-maintenance_31bf3856ad364e35_6.1.7600.16385_none_5e708a1ffe7aa932\Desktop.ini.
Successfully copied file C:\Users\tjs\AppData\Local\niemiro\Archive\winsxs\x86_microsoft-windows-s..ktopini-accessories_31bf3856ad364e35_6.1.7600.16385_none_ebed72081abd7309\Desktop.ini to C:\Windows\winsxs\x86_microsoft-windows-s..ktopini-accessories_31bf3856ad364e35_6.1.7600.16385_none_ebed72081abd7309\Desktop.ini.
Successfully copied file C:\Users\tjs\AppData\Local\niemiro\Archive\winsxs\x86_microsoft-windows-s..ini-systemtoolsuser_31bf3856ad364e35_6.1.7600.16385_none_208203e244db0d22\Desktop.ini to C:\Windows\winsxs\x86_microsoft-windows-s..ini-systemtoolsuser_31bf3856ad364e35_6.1.7600.16385_none_208203e244db0d22\Desktop.ini.
Successfully copied file C:\Users\tjs\AppData\Local\niemiro\Archive\winsxs\x86_microsoft-windows-s..ini-maintenanceuser_31bf3856ad364e35_6.1.7600.16385_none_05ddf62fb732aa51\Desktop.ini to C:\Windows\winsxs\x86_microsoft-windows-s..ini-maintenanceuser_31bf3856ad364e35_6.1.7600.16385_none_05ddf62fb732aa51\Desktop.ini.
Successfully copied file C:\Users\tjs\AppData\Local\niemiro\Archive\winsxs\x86_microsoft-windows-s..ini-accessoriesuser_31bf3856ad364e35_6.1.7600.16385_none_23da83d97579563a\Desktop.ini to C:\Windows\winsxs\x86_microsoft-windows-s..ini-accessoriesuser_31bf3856ad364e35_6.1.7600.16385_none_23da83d97579563a\Desktop.ini.
Successfully copied file C:\Users\tjs\AppData\Local\niemiro\Archive\winsxs\x86_microsoft-windows-s..i-accessibilityuser_31bf3856ad364e35_6.1.7600.16385_none_631ad0256a1095cc\Desktop.ini to C:\Windows\winsxs\x86_microsoft-windows-s..i-accessibilityuser_31bf3856ad364e35_6.1.7600.16385_none_631ad0256a1095cc\Desktop.ini.
Successfully copied file C:\Users\tjs\AppData\Local\niemiro\Archive\winsxs\x86_microsoft-windows-s..-binaries.resources_31bf3856ad364e35_6.1.7601.17514_lt-lt_cd37305567da84e8\lt-LT_BitLockerToGo.exe.mui to C:\Windows\winsxs\x86_microsoft-windows-s..-binaries.resources_31bf3856ad364e35_6.1.7601.17514_lt-lt_cd37305567da84e8\lt-LT_BitLockerToGo.exe.mui.
Successfully copied file C:\Users\tjs\AppData\Local\niemiro\Archive\winsxs\x86_microsoft-windows-s..-binaries.resources_31bf3856ad364e35_6.1.7601.17514_el-gr_56d73702c6334f9e\el-GR_BitLockerToGo.exe.mui to C:\Windows\winsxs\x86_microsoft-windows-s..-binaries.resources_31bf3856ad364e35_6.1.7601.17514_el-gr_56d73702c6334f9e\el-GR_BitLockerToGo.exe.mui.
Successfully copied file C:\Users\tjs\AppData\Local\niemiro\Archive\winsxs\x86_microsoft-windows-mspaint_31bf3856ad364e35_6.1.7600.16385_none_8df3dcc84fe54e8b\mspaint.exe to C:\Windows\winsxs\x86_microsoft-windows-mspaint_31bf3856ad364e35_6.1.7600.16385_none_8df3dcc84fe54e8b\mspaint.exe.
Successfully copied file C:\Users\tjs\AppData\Local\niemiro\Archive\winsxs\x86_microsoft-windows-iologgingdll.resources_31bf3856ad364e35_6.1.7601.22589_en-us_f7556e6951263ab9\iologmsg.dll.mui to C:\Windows\winsxs\x86_microsoft-windows-iologgingdll.resources_31bf3856ad364e35_6.1.7601.22589_en-us_f7556e6951263ab9\iologmsg.dll.mui.
Successfully copied file C:\Users\tjs\AppData\Local\niemiro\Archive\winsxs\x86_microsoft-windows-ie-f12.resources_31bf3856ad364e35_11.2.9600.17041_en-us_f6a96f63b61c8b5f\F12.dll.mui to C:\Windows\winsxs\x86_microsoft-windows-ie-f12.resources_31bf3856ad364e35_11.2.9600.17041_en-us_f6a96f63b61c8b5f\F12.dll.mui.
Successfully copied file C:\Users\tjs\AppData\Local\niemiro\Archive\winsxs\x86_microsoft-windows-energyefficiencywizard_31bf3856ad364e35_6.1.7600.16385_none_18a686bb98480f0f\energy.dll to C:\Windows\winsxs\x86_microsoft-windows-energyefficiencywizard_31bf3856ad364e35_6.1.7600.16385_none_18a686bb98480f0f\energy.dll.
Successfully copied file C:\Users\tjs\AppData\Local\niemiro\Archive\winsxs\x86_microsoft-windows-ehome-reg-inf_31bf3856ad364e35_6.1.7601.17514_none_f733aa7021315a64\desktop.ini to C:\Windows\winsxs\x86_microsoft-windows-ehome-reg-inf_31bf3856ad364e35_6.1.7601.17514_none_f733aa7021315a64\desktop.ini.
Successfully copied file C:\Users\tjs\AppData\Local\niemiro\Archive\winsxs\x86_microsoft-windows-edition-transmogrifier_31bf3856ad364e35_6.1.7601.17514_none_17983cea99707d4c\TransmogProvider.dll to C:\Windows\winsxs\x86_microsoft-windows-edition-transmogrifier_31bf3856ad364e35_6.1.7601.17514_none_17983cea99707d4c\TransmogProvider.dll.
Successfully copied file C:\Users\tjs\AppData\Local\niemiro\Archive\winsxs\msil_system.runtime.seri..ion.formatters.soap_b03f5f7f11d50a3a_6.1.7601.22733_none_05a3bea3fa19258c\System.Runtime.Serialization.Formatters.Soap.dll to C:\Windows\winsxs\msil_system.runtime.seri..ion.formatters.soap_b03f5f7f11d50a3a_6.1.7601.22733_none_05a3bea3fa19258c\System.Runtime.Serialization.Formatters.Soap.dll.
Successfully copied file C:\Users\tjs\AppData\Local\niemiro\Archive\winsxs\msil_accessibility_b03f5f7f11d50a3a_6.1.7601.18523_none_2208500a4f9f1a4d\Accessibility.dll to C:\Windows\winsxs\msil_accessibility_b03f5f7f11d50a3a_6.1.7601.18523_none_2208500a4f9f1a4d\Accessibility.dll.
Successfully restored ownership for C:\Windows\winsxs\x86_wcf-infocard_api_dll_31bf3856ad364e35_6.1.7601.18523_none_a5e27db60deb6bc8
Successfully restored permissions on C:\Windows\winsxs\x86_wcf-infocard_api_dll_31bf3856ad364e35_6.1.7601.18523_none_a5e27db60deb6bc8
Successfully restored ownership for C:\Windows\winsxs\x86_netfx-netfxsbs10_exe_31bf3856ad364e35_6.1.7601.17514_none_3d9659600c3683e3
Successfully restored permissions on C:\Windows\winsxs\x86_netfx-netfxsbs10_exe_31bf3856ad364e35_6.1.7601.17514_none_3d9659600c3683e3
Successfully restored ownership for C:\Windows\winsxs\x86_netfx-dw_b03f5f7f11d50a3a_6.1.7601.18523_none_a1f9e3b9d7db7cad
Successfully restored permissions on C:\Windows\winsxs\x86_netfx-dw_b03f5f7f11d50a3a_6.1.7601.18523_none_a1f9e3b9d7db7cad
Successfully restored ownership for C:\Windows\winsxs\x86_microsoft.windows.h..display-driverclass_31bf3856ad364e35_6.1.7600.16385_none_43670cedf1a9c429
Successfully restored permissions on C:\Windows\winsxs\x86_microsoft.windows.h..display-driverclass_31bf3856ad364e35_6.1.7600.16385_none_43670cedf1a9c429
Successfully restored ownership for C:\Windows\winsxs\x86_microsoft-windows-tzutil_31bf3856ad364e35_6.1.7601.17514_none_364b3ec461692953
Successfully restored permissions on C:\Windows\winsxs\x86_microsoft-windows-tzutil_31bf3856ad364e35_6.1.7601.17514_none_364b3ec461692953
Successfully restored ownership for C:\Windows\winsxs\x86_microsoft-windows-time-tool_31bf3856ad364e35_6.1.7601.17514_none_ef1085419a309311
Successfully restored permissions on C:\Windows\winsxs\x86_microsoft-windows-time-tool_31bf3856ad364e35_6.1.7601.17514_none_ef1085419a309311
Successfully restored ownership for C:\Windows\winsxs\x86_microsoft-windows-t..dp-winstationdriver_31bf3856ad364e35_6.1.7601.18540_none_4d586a7f3360a97d
Successfully restored permissions on C:\Windows\winsxs\x86_microsoft-windows-t..dp-winstationdriver_31bf3856ad364e35_6.1.7601.18540_none_4d586a7f3360a97d
Successfully restored ownership for C:\Windows\winsxs\x86_microsoft-windows-sonic-tables-2th1_31bf3856ad364e35_6.1.7600.16385_none_6f9196b4c105ea8d
Successfully restored permissions on C:\Windows\winsxs\x86_microsoft-windows-sonic-tables-2th1_31bf3856ad364e35_6.1.7600.16385_none_6f9196b4c105ea8d
Successfully restored ownership for C:\Windows\winsxs\x86_microsoft-windows-setup-adm_31bf3856ad364e35_6.1.7600.16385_none_7ece2f48e3472311
Successfully restored permissions on C:\Windows\winsxs\x86_microsoft-windows-setup-adm_31bf3856ad364e35_6.1.7600.16385_none_7ece2f48e3472311
Successfully restored ownership for C:\Windows\winsxs\x86_microsoft-windows-s..sktopini-sendtouser_31bf3856ad364e35_6.1.7600.16385_none_081ae7a4f56c5467
Successfully restored permissions on C:\Windows\winsxs\x86_microsoft-windows-s..sktopini-sendtouser_31bf3856ad364e35_6.1.7600.16385_none_081ae7a4f56c5467
Successfully restored ownership for C:\Windows\winsxs\x86_microsoft-windows-s..opini-accessibility_31bf3856ad364e35_6.1.7600.16385_none_da41b324de9c3847
Successfully restored permissions on C:\Windows\winsxs\x86_microsoft-windows-s..opini-accessibility_31bf3856ad364e35_6.1.7600.16385_none_da41b324de9c3847
Successfully restored ownership for C:\Windows\winsxs\x86_microsoft-windows-s..ktopini-systemtools_31bf3856ad364e35_6.1.7600.16385_none_7e4396bce8f78221
Successfully restored permissions on C:\Windows\winsxs\x86_microsoft-windows-s..ktopini-systemtools_31bf3856ad364e35_6.1.7600.16385_none_7e4396bce8f78221
Successfully restored ownership for C:\Windows\winsxs\x86_microsoft-windows-s..ktopini-maintenance_31bf3856ad364e35_6.1.7600.16385_none_5e708a1ffe7aa932
Successfully restored permissions on C:\Windows\winsxs\x86_microsoft-windows-s..ktopini-maintenance_31bf3856ad364e35_6.1.7600.16385_none_5e708a1ffe7aa932
Successfully restored ownership for C:\Windows\winsxs\x86_microsoft-windows-s..ktopini-accessories_31bf3856ad364e35_6.1.7600.16385_none_ebed72081abd7309
Successfully restored permissions on C:\Windows\winsxs\x86_microsoft-windows-s..ktopini-accessories_31bf3856ad364e35_6.1.7600.16385_none_ebed72081abd7309
Successfully restored ownership for C:\Windows\winsxs\x86_microsoft-windows-s..ini-systemtoolsuser_31bf3856ad364e35_6.1.7600.16385_none_208203e244db0d22
Successfully restored permissions on C:\Windows\winsxs\x86_microsoft-windows-s..ini-systemtoolsuser_31bf3856ad364e35_6.1.7600.16385_none_208203e244db0d22
Successfully restored ownership for C:\Windows\winsxs\x86_microsoft-windows-s..ini-maintenanceuser_31bf3856ad364e35_6.1.7600.16385_none_05ddf62fb732aa51
Successfully restored permissions on C:\Windows\winsxs\x86_microsoft-windows-s..ini-maintenanceuser_31bf3856ad364e35_6.1.7600.16385_none_05ddf62fb732aa51
Successfully restored ownership for C:\Windows\winsxs\x86_microsoft-windows-s..ini-accessoriesuser_31bf3856ad364e35_6.1.7600.16385_none_23da83d97579563a
Successfully restored permissions on C:\Windows\winsxs\x86_microsoft-windows-s..ini-accessoriesuser_31bf3856ad364e35_6.1.7600.16385_none_23da83d97579563a
Successfully restored ownership for C:\Windows\winsxs\x86_microsoft-windows-s..i-accessibilityuser_31bf3856ad364e35_6.1.7600.16385_none_631ad0256a1095cc
Successfully restored permissions on C:\Windows\winsxs\x86_microsoft-windows-s..i-accessibilityuser_31bf3856ad364e35_6.1.7600.16385_none_631ad0256a1095cc
Successfully restored ownership for C:\Windows\winsxs\x86_microsoft-windows-s..-binaries.resources_31bf3856ad364e35_6.1.7601.17514_lt-lt_cd37305567da84e8
Successfully restored permissions on C:\Windows\winsxs\x86_microsoft-windows-s..-binaries.resources_31bf3856ad364e35_6.1.7601.17514_lt-lt_cd37305567da84e8
Successfully restored ownership for C:\Windows\winsxs\x86_microsoft-windows-s..-binaries.resources_31bf3856ad364e35_6.1.7601.17514_el-gr_56d73702c6334f9e
Successfully restored permissions on C:\Windows\winsxs\x86_microsoft-windows-s..-binaries.resources_31bf3856ad364e35_6.1.7601.17514_el-gr_56d73702c6334f9e
Successfully restored ownership for C:\Windows\winsxs\x86_microsoft-windows-mspaint_31bf3856ad364e35_6.1.7600.16385_none_8df3dcc84fe54e8b
Successfully restored permissions on C:\Windows\winsxs\x86_microsoft-windows-mspaint_31bf3856ad364e35_6.1.7600.16385_none_8df3dcc84fe54e8b
Successfully restored ownership for C:\Windows\winsxs\x86_microsoft-windows-iologgingdll.resources_31bf3856ad364e35_6.1.7601.22589_en-us_f7556e6951263ab9
Successfully restored permissions on C:\Windows\winsxs\x86_microsoft-windows-iologgingdll.resources_31bf3856ad364e35_6.1.7601.22589_en-us_f7556e6951263ab9
Successfully restored ownership for C:\Windows\winsxs\x86_microsoft-windows-ie-f12.resources_31bf3856ad364e35_11.2.9600.17041_en-us_f6a96f63b61c8b5f
Successfully restored permissions on C:\Windows\winsxs\x86_microsoft-windows-ie-f12.resources_31bf3856ad364e35_11.2.9600.17041_en-us_f6a96f63b61c8b5f
Successfully restored ownership for C:\Windows\winsxs\x86_microsoft-windows-energyefficiencywizard_31bf3856ad364e35_6.1.7600.16385_none_18a686bb98480f0f
Successfully restored permissions on C:\Windows\winsxs\x86_microsoft-windows-energyefficiencywizard_31bf3856ad364e35_6.1.7600.16385_none_18a686bb98480f0f
Successfully restored ownership for C:\Windows\winsxs\x86_microsoft-windows-ehome-reg-inf_31bf3856ad364e35_6.1.7601.17514_none_f733aa7021315a64
Successfully restored permissions on C:\Windows\winsxs\x86_microsoft-windows-ehome-reg-inf_31bf3856ad364e35_6.1.7601.17514_none_f733aa7021315a64
Successfully restored ownership for C:\Windows\winsxs\x86_microsoft-windows-edition-transmogrifier_31bf3856ad364e35_6.1.7601.17514_none_17983cea99707d4c
Successfully restored permissions on C:\Windows\winsxs\x86_microsoft-windows-edition-transmogrifier_31bf3856ad364e35_6.1.7601.17514_none_17983cea99707d4c
Successfully restored ownership for C:\Windows\winsxs\msil_system.runtime.seri..ion.formatters.soap_b03f5f7f11d50a3a_6.1.7601.22733_none_05a3bea3fa19258c
Successfully restored permissions on C:\Windows\winsxs\msil_system.runtime.seri..ion.formatters.soap_b03f5f7f11d50a3a_6.1.7601.22733_none_05a3bea3fa19258c
Successfully restored ownership for C:\Windows\winsxs\msil_accessibility_b03f5f7f11d50a3a_6.1.7601.18523_none_2208500a4f9f1a4d
Successfully restored permissions on C:\Windows\winsxs\msil_accessibility_b03f5f7f11d50a3a_6.1.7601.18523_none_2208500a4f9f1a4d
PowerCopy:: directive completed successfully.
Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 228 datablocks.
Finish time: 2016-12-14 10:42:54.681
Script hash: NB6VCYD7PmEQs7JE1C8EeG7Dter5dwPHQjUqyvqRKNM=
----------------------EOF-----------------------tjsepka
Contributor
I suspect that the errors are not due to file corruptions, but due to software that I've installed after the clean run of SFCFix a number of months ago. My disks are now monitored more closely for errors using a disk SMART monitoring program and an event popup from system management if a disk error occurs.
zcomputerwiz
Windows Update Expert
Looks like there's only a few items left in the SURT log. Let's fix those and see how far we get with SFC.
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.
View attachment SFCFix.zip
Once SFCFix has completed, run SURT again and attach CheckSUR.log with your reply.
SFCFix Script
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.
- Download SFCFix.exe (by niemiro) and save this to your Desktop.
- Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
- Save any open documents and close all open windows.
- On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
- Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
- SFCFix will now process the script.
- Upon completion, a file should be created on your Desktop: SFCFix.txt.
- Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.
View attachment SFCFix.zip
Once SFCFix has completed, run SURT again and attach CheckSUR.log with your reply.
tjsepka
Contributor
I suspect that the errors are not due to file corruptions, but due to software that I've installed after the clean run of SFCFix a number of months ago. My disks are now monitored more closely for errors using a disk SMART monitoring program and an event popup from system management if a disk error occurs.
Here's the latest (I think we're good, but you tell me - CheckSUR.log is attached):
Now to see where sfc/scannow stands(?).....
Here's the latest (I think we're good, but you tell me - CheckSUR.log is attached):
Code:
SFCFix version 3.0.0.0 by niemiro.
Start time: 2016-12-14 13:09:21.407
Microsoft Windows 7 Service Pack 1 - x86
Using .zip script file at C:\Users\tjs\Desktop\SFCFix.zip [0]
RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_policy.14.0.avg.vc140.mfc_f92d94485545da78_14.0.24210.0_none_ce167c85fbed1945.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_avg.vc140.crt_f92d94485545da78_14.0.24210.0_none_b1a7386eee2cbfb4.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_policy.14.0.avg.vc140.crt_f92d94485545da78_14.0.24210.0_none_d595624ff71e9c62.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_avg.vc140.mfc_f92d94485545da78_14.0.24210.0_none_aa2852a4f2fb3c97.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_policy.14.0.avg.vc140.mfc_f92d94485545da78_14.0.24210.0_none_ce167c85fbed1945.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_avg.vc140.crt_f92d94485545da78_14.0.24210.0_none_b1a7386eee2cbfb4.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_policy.14.0.avg.vc140.crt_f92d94485545da78_14.0.24210.0_none_d595624ff71e9c62.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_avg.vc140.mfc_f92d94485545da78_14.0.24210.0_none_aa2852a4f2fb3c97.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_policy.14.0.avg.vc140.mfc_f92d94485545da78_14.0.24210.0_none_ce167c85fbed1945 with error code ERROR_FILE_NOT_FOUND.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_avg.vc140.crt_f92d94485545da78_14.0.24210.0_none_b1a7386eee2cbfb4 with error code ERROR_FILE_NOT_FOUND.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_policy.14.0.avg.vc140.crt_f92d94485545da78_14.0.24210.0_none_d595624ff71e9c62 with error code ERROR_FILE_NOT_FOUND.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_avg.vc140.mfc_f92d94485545da78_14.0.24210.0_none_aa2852a4f2fb3c97 with error code ERROR_FILE_NOT_FOUND.
RegistryScript:: directive failed to complete successfully.
Failed to process all directives successfully.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 232 datablocks.
Finish time: 2016-12-14 13:09:22.388
Script hash: P38F22ZCWmFpa8hKq1qdzrZiKIUmUHq90nIUerz0We4=
----------------------EOF-----------------------Now to see where sfc/scannow stands(?).....
zcomputerwiz
Windows Update Expert
Yes, looks good. Let's try SFC.
SFC Scan
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 zip and attach this to your next post.
tjsepka
Contributor
Seems the same as in earlier posts:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
Thu 12/15/2016 18:08:39.11 C:\Windows\system32>sfc /scannow
Windows Resource Protection could not start the repair service.
Thu 12/15/2016 21:49:01.59 C:\Windows\system32>
This was run in normal mode. I've attached a procmon capture of the attempt. To me, it looks pretty much the same as in my earlier posts. To the best of my recollection, the procmon event captures were pretty much the same between safe and normal modes.
Also attached are a procmon file summary and filtered list of unsuccessful results from the capture. I'm thinking along the line of either missing files, incorrect permissions, or maybe both. Any thoughts?
Tom
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
Thu 12/15/2016 18:08:39.11 C:\Windows\system32>sfc /scannow
Windows Resource Protection could not start the repair service.
Thu 12/15/2016 21:49:01.59 C:\Windows\system32>
This was run in normal mode. I've attached a procmon capture of the attempt. To me, it looks pretty much the same as in my earlier posts. To the best of my recollection, the procmon event captures were pretty much the same between safe and normal modes.
Also attached are a procmon file summary and filtered list of unsuccessful results from the capture. I'm thinking along the line of either missing files, incorrect permissions, or maybe both. Any thoughts?
Tom
zcomputerwiz
Windows Update Expert
In the recovery environment, please try running sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows
If this still fails, in the recovery environment please run diskpart and list the volumes, disks, and partitions. You may wish to use a camera (or camera phone) to capture the output and include it with your reply.
If this still fails, in the recovery environment please run diskpart and list the volumes, disks, and partitions. You may wish to use a camera (or camera phone) to capture the output and include it with your reply.
tjsepka
Contributor
It ran and it said:
"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."
No cbs.log was generated in either:
c:\windows\logs\cbs\
x:\windows\logs\cbs\
A cbs.log was generated after rebooting in normal made and is attached.
I also have procmon PML files in safe and normal modes captured from earlier today. Please let me know if you want me upload them.
"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."
No cbs.log was generated in either:
c:\windows\logs\cbs\
x:\windows\logs\cbs\
A cbs.log was generated after rebooting in normal made and is attached.
I also have procmon PML files in safe and normal modes captured from earlier today. Please let me know if you want me upload them.
Has Sysnative Forums helped you? Please consider donating to help us support the site!