corrupted and cant be fixed files
- Thread starter daour
- Start date
That extract is incomplete.
Please reboot, and post the full CBS.log file (You'll have to copy it to the desktop and then Zip it)
There are at least two files corrupted - one of which appears to have been fixed between the second and third(?) runs of SFC you did today.
Please reboot, and post the full CBS.log file (You'll have to copy it to the desktop and then Zip it)
There are at least two files corrupted - one of which appears to have been fixed between the second and third(?) runs of SFC you did today.
As I suspected, the scan did not complete successfully. - here's the stuff the extract didn't show...
It looks to me as if you have some registry corruption.
From what I can see, it may be limited to only that file/key
Please download and save the CheckSUR tool from System Update Readiness Tool fixes Windows Update errors in Windows 7, Windows Vista, Windows Server 2008 R2, and Windows Server 2008
(you'll need to look in the details for Windows 7, downloading from the Microsoft Download Center)
Run it - The tool can take anywhere from 5 mins to a couple of hours to run (or 'Install') depending on how much it has to do, and may exit silently - it may appear to freeze for most of that time, but be patient.
The result is logged in the C:\Windows\Logs\CBS\CheckSUR.log file - and an archive …\checksur.persist.log file
Then zip the CheckSUR.log and upload it to your reply.
Code:
2013-10-20 20:21:28, Info CSI 000000be [SR] Verifying 100 (0x0000000000000064) components
2013-10-20 20:21:28, Info CSI 000000bf [SR] Beginning Verify and Repair transaction
2013-10-20 20:21:30, Error CSI 000000c0 (F) STATUS_OBJECT_NAME_NOT_FOUND #1762316# from Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile(flags = (AllowSharingViolation), handle = {provider=NULL, handle=0}, da = (SYNCHRONIZE|FILE_READ_ATTRIBUTES), oa = @0xe2cdf0->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[122]"\??\C:\Windows\WinSxS\amd64_microsoft-windows-g..validatefntcache-06_31bf3856ad364e35_6.1.7601.17959_none_a6ad7859316056f1"; a:(OBJ_CASE_INSENSITIVE)}, iosb = @0xe2cdd0, as = (null), fa = 0, sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), cd = FILE_OPEN, co = (FILE_SYNCHRONOUS_IO_NONALERT|0x00004000), eab = NULL, eal = 0, disp = Invalid)
[gle=0xd0000034]
2013-10-20 20:21:30, Error CSI [EMAIL="000000c1@2013/10/20:17:21:30.637"]000000c1@2013/10/20:17:21:30.637[/EMAIL] (F) d:\win7sp1_gdr\base\wcp\sil\merged\ntu\ntsystem.cpp(2057): Error STATUS_OBJECT_NAME_NOT_FOUND originated in function Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile expression: (null)
[gle=0x80004005]
2013-10-20 20:21:30, Error CSI 000000c2 (F) STATUS_OBJECT_NAME_NOT_FOUND #1762315# from Windows::Rtl::SystemImplementation::CDirectory::OpenExistingDirectory(...)[gle=0xd0000034]
2013-10-20 20:21:30, Error CSI 000000c3 (F) STATUS_OBJECT_NAME_NOT_FOUND #1762314# from Windows::Rtl::SystemImplementation::CDirectory_IRtlDirectoryTearoff::OpenExistingDirectory(flags = 0, da = (SYNCHRONIZE), oa = @0xe2d6e8->SIL_OBJECT_ATTRIBUTES {s:40; on:"amd64_microsoft-windows-g..validatefntcache-06_31bf3856ad364e35_6.1.7601.17959_none_a6ad7859316056f1"; a:(OBJ_CASE_INSENSITIVE)}, sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), oo = (FILE_DIRECTORY_FILE|FILE_SYNCHRONOUS_IO_NONALERT|FILE_OPEN_FOR_BACKUP_INTENT), dir = NULL, disp = Invalid)
[gle=0xd0000034]
2013-10-20 20:31:31, Info CBS Reboot mark refs incremented to: 1It looks to me as if you have some registry corruption.
From what I can see, it may be limited to only that file/key
Please download and save the CheckSUR tool from System Update Readiness Tool fixes Windows Update errors in Windows 7, Windows Vista, Windows Server 2008 R2, and Windows Server 2008
(you'll need to look in the details for Windows 7, downloading from the Microsoft Download Center)
Run it - The tool can take anywhere from 5 mins to a couple of hours to run (or 'Install') depending on how much it has to do, and may exit silently - it may appear to freeze for most of that time, but be patient.
The result is logged in the C:\Windows\Logs\CBS\CheckSUR.log file - and an archive …\checksur.persist.log file
Then zip the CheckSUR.log and upload it to your reply.
The following problems show from the CheckSUR log
The remainder are 'normal' for aWin7 machine with IE10 installed.
The SFC scan shows the following problems now..
It's too late tonight for me to do anything - I'll try in the morning.
Code:
Checking Component Store
(f) CSI Manifest Missing 0x00000002 x86_microsoft-windows-ie-vgx_31bf3856ad364e35_9.4.8112.16464_none_058e7557031f04c0.manifest x86_microsoft-windows-ie-vgx_31bf3856ad364e35_9.4.8112.16464_none_058e7557031f04c0
(f) CSI Payload File Missing 0x00000000 invalidateFntcache.exe amd64_microsoft-windows-g..validatefntcache-06_31bf3856ad364e35_6.1.7601.17959_none_a6ad7859316056f1
Unavailable repair files:
winsxs\manifests\x86_microsoft-windows-ie-vgx_31bf3856ad364e35_9.4.8112.16464_none_058e7557031f04c0.manifestThe SFC scan shows the following problems now..
Code:
2013-10-21 19:22:27, Info CSI 00000312 [SR] Repairing 4 components
2013-10-21 19:22:27, Info CSI 00000313 [SR] Beginning Verify and Repair transaction
2013-10-21 19:22:35, Info CSI 00000314 [SR] Cannot repair member file [l:20{10}]"gb2312.uce" of Microsoft-Windows-charmap, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-10-21 19:22:35, Info CSI 00000315 [SR] Cannot repair member file [l:44{22}]"invalidateFntcache.exe" of Microsoft-Windows-GC-InvalidateFntcache-06, Version = 6.1.7601.17959, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2013-10-21 19:22:55, Info CSI 00000316 [SR] Cannot repair member file [l:20{10}]"CA-wp6.jpg" of Microsoft-Windows-MarketTheme-CA-Component, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-10-21 19:23:19, Info CSI 00000317 [SR] Cannot repair member file [l:20{10}]"user32.amx" of Microsoft-Windows-Application-Experience-API-Tracing-Infrastructure-Manifests, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatchIt's too late tonight for me to do anything - I'll try in the morning.
i keep getting this error when i start my pc and i have to shut it down and start it again:
windows explorer is not responding
if you restart or close the program you might information.
-restart
-close
-wait
i have noerton 360 the only thing that starts when my pc start.
windows explorer is not responding
if you restart or close the program you might information.
-restart
-close
-wait
i have noerton 360 the only thing that starts when my pc start.
I've uploaded a file - daour.zip - to my SkyDrive at Noel's SkyDrive
Please download and save it.
Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract
Close all windows (it would be a good idea to print these
instructions!)
Now reboot to the Repair Environment - as soon as the machine restarts, start
tapping F8 - this should bring up the Advanced Boot Menu, at the top of which
should be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.
Pick the option to use a Command Prompt
At the prompt type
DIR C:\daour
hit the enter key - if you get a 'Not Found' error try
DIR D:\daour
or
DIR E:\daour
The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...
XCOPY
<drive>:\daour <drive>:\windows\winsxs /y /i /s /v /h
(e.g. XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )
run the command (it should take almost no time)and when the prompt returns, type
EXIT
and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.
Now run SFC /SCANNOW in an Elevated Command Prompt
then reboot and upload the new CBS.log file to your reply
Please download and save it.
Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract
Close all windows (it would be a good idea to print these
instructions!)
Now reboot to the Repair Environment - as soon as the machine restarts, start
tapping F8 - this should bring up the Advanced Boot Menu, at the top of which
should be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.
Pick the option to use a Command Prompt
At the prompt type
DIR C:\daour
hit the enter key - if you get a 'Not Found' error try
DIR D:\daour
or
DIR E:\daour
The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...
XCOPY
<drive>:\daour <drive>:\windows\winsxs /y /i /s /v /h
(e.g. XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )
run the command (it should take almost no time)and when the prompt returns, type
EXIT
and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.
Now run SFC /SCANNOW in an Elevated Command Prompt
then reboot and upload the new CBS.log file to your reply
Please post the log files, - and there's still one more file to fix anyhow :)
The file I need is the C:\Windows\Logs\CBS\CBS.log file
One way to fix it, certainly - good luck with the new install!
Has Sysnative Forums helped you? Please consider donating to help us support the site!