[SOLVED] Only sfc scannow shows corrupted files

Clamarc

Clamarc

Member
Joined
Oct 16, 2018
Posts
20
Location
Brazil
Good Morning
I execute the following commands successfully:
Dism.exe /online /Cleanup-Image /StartComponentCleanup
Dism /Online /Cleanup-Image /RestoreHealth


However, the sfc / scannow command can not fix corrupted files


see attached logs


Thank's
Clamarc

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


SFCFix version 3.0.0.0 by niemiro.
Start time: 2018-10-16 10:14:25.771
Microsoft Windows 10 Build 17134 - amd64
Not using a script file.


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


Successfully processed all directives.


Failed to generate a complete zip file. Upload aborted.


SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2018-10-16 10:37:24.672
----------------------EOF-----------------------
 

Attachments

softwaremaniac said:
Hi! These Avast corruptions are benign and can safely be ignored.
Click to expand...

Hi softwaremaniac,


But do I stay with this message every time I run sfc / scannow? ... does not there exist a way to fix this so the sfc runs without showing this message in the future?


thank's
Clamarc
 
Sure, we can try!

Step#1 - FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download attached file and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
 

Attachments

Good Morning softwaremaniac,



I noticed that when I execute commands at the prompt as an administrator, I get access denied. Could you verify that access permissions have changed on my computer?
Why am I an admin user and do I have access to certain folders?


Thank's

Fix result of Farbar Recovery Scan Tool (x64) Version: 10.10.2018
Ran by Claudio (20-10-2018 06:53:13) Run:1
Running from C:\Users\Claudio\Desktop
Loaded Profiles: Claudio (Available Profiles: Claudio & Administrator)
Boot Mode: Normal
==============================================


fixlist content:
*****************
CreateRestorePoint:
cmd: reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS
[-HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.25325.0_none_586e9d411a1940c6]
[-HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.25325.0_none_a01bd4182e9569cc]
[-HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_avast.vc140.mfc_fcc99ee6193ebbca_14.0.25325.0_none_a4fbd60a2b6998ff]
[-HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.25325.0_none_4b5d1834d3072800]
[-HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.25325.0_none_930a4f0be7835106]
[-HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_policy.14.0.avast.vc140.mfc_fcc99ee6193ebbca_14.0.25325.0_none_97ea50fde4578039]
*****************


Restore point was successfully created.


========= reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS =========


A opera‡Æo foi conclu¡da com ˆxito.




========= End of CMD: =========


HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.25325.0_none_586e9d411a1940c6 => removed successfully
HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.25325.0_none_a01bd4182e9569cc => removed successfully
HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_avast.vc140.mfc_fcc99ee6193ebbca_14.0.25325.0_none_a4fbd60a2b6998ff => removed successfully
HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.25325.0_none_4b5d1834d3072800 => removed successfully
HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.25325.0_none_930a4f0be7835106 => removed successfully
HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_policy.14.0.avast.vc140.mfc_fcc99ee6193ebbca_14.0.25325.0_none_97ea50fde4578039 => removed successfully


==== End of Fixlog 06:54:11 ====
 
Good morning. Nothing we did would cause a change in permissions as I've simply deleted the Avast remnants. Would you please run SFC again to see what it says now and attach CBS.log.
 
softwaremaniac said:
Good morning. Nothing we did would cause a change in permissions as I've simply deleted the Avast remnants.
Click to expand...
I know


While waiting for his first response, I noticed two strange situations:
- The permissions settings on my computer are different from what it was before.
- The computer is also taking 3 minutes to start!


I have two questions:
1 - In the CBS log, can you see what is happening at the start of my computer that is causing the slowness?
2 - Do you have any command at the prompt that I can execute to return the Windows default access permissions?


follows log attached

Thank's
Clamarc
 

Attachments

1. No, but I can propose steps to check some things out.
2. What makes you think your permissions are different (please be very specific as I have to understand before I can assist).

SFC looks ok now.
 
Hi softwaremaniac,


softwaremaniac said:
1. No, but I can propose steps to check some things out.
Click to expand...
it would be interesting if you can check it out because it takes 3min to boot!

softwaremaniac said:
2. What makes you think your permissions are different (please be very specific as I have to understand before I can assist).
Click to expand...
Before going to your forum, I tried some alternatives to solve the problem and one of them asked to execute the net stop
msiserver command and got the access denied even while executing the prompt as admin? I am an admin user but it
seems that I do not have administrator permissions!


sfc is ok now, very thank's

Clamarc
 
GSmartControl
Follow the instructions below to test your hard drive health with GSmartControl:



  • Download GSmartControl and save it on your Desktop;
  • Execute gsmartcontrol.exe; Let the install complete and launch the programme.
  • Identify your drive in the list, and double-click on it to bring up it's window (usually you'll find your drive by it's size or it's brand name);
  • Go in the Perform Tests tab, then select Extended Self-test in the Test type drop-down list and click on Execute (this test can take a few hours to complete);
  • Once the test is over, the results will be displayed at the bottom of the window. Please copy and paste these results in your next reply;
  • Also, go in the Attributes tab and if you have any entries highlighted in red or pink, take a screenshot of the GSmartControl window and attach it in your next reply;
    info_failing.png
 
Good Morning softwaremaniac,

Result Test

Number of entries in self-test log: 3

[TABLE="width: 800"]
[TR]
[TD]Test #[/TD]
[TD]Type[/TD]
[TD]Status[/TD]
[TD]% Completed[/TD]
[TD]Lifetime hours[/TD]
[TD]LBA of the first error[/TD]
[/TR]
[TR]
[TD] 1[/TD]
[TD]Extended offline[/TD]
[TD]Completed without error[/TD]
[TD="align: center"] 100%[/TD]
[TD="align: center"] 38284[/TD]
[TD="align: center"] -[/TD]
[/TR]
[TR]
[TD] 2[/TD]
[TD]Conveyance offline[/TD]
[TD]Completed without error[/TD]
[TD="align: center"] 100%[/TD]
[TD="align: center"] 10806[/TD]
[TD="align: center"] -[/TD]
[/TR]
[TR]
[TD] 3[/TD]
[TD]Short offline[/TD]
[TD]Completed without error[/TD]
[TD="align: center"] 100%[/TD]
[TD="align: center"] 56[/TD]
[TD="align: center"] -[/TD]
[/TR]
[/TABLE]


OBS: The model of my HDD features an IntelliPark power reduction technology. Some specialized sites guide you to change
the idle value from 8s to 300s (5min) in order to increase the life of the HDD. Can this really improve the durability of
the HDD?

see also attached image

Thank's
Clamarc


 

Attachments

  • Image Test GSmartControl.jpg
    Image Test GSmartControl.jpg
    151.5 KB · Views: 3
Unfortunately, I was suspecting that this may be the cause. Your HDD is failing. Please urgently backup your data and replace the drive. That will fix your issues.
 
softwaremaniac said:
Unfortunately, I was suspecting that this may be the cause. Your HDD is failing.
Click to expand...

Good Morning softwaremaniac,

So can I consider the chkdsk command as unreliable? ... because it shows me
that there is no damaged sector on my disk! I ran the command on my four
partitions and it did not show any errors!?... or is the chkdsk check different
from the GSmartControl check?

See logs below:


chkdsk c: /r /f /v


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


A disk check has been scheduled.
Windows will now check the disk.


Stage 1: Examining basic file system structure ...
511744 file records processed.
File verification completed.
7861 large file records processed.
0 bad file records processed.


Stage 2: Examining file name linkage ...
1269 reparse records processed.
653518 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
1269 reparse records processed.


Stage 3: Examining security descriptors ...
Cleaning up 1202 unused index entries from index $SII of file 0x9.
Cleaning up 1202 unused index entries from index $SDH of file 0x9.
Cleaning up 1202 unused security descriptors.
Security descriptor verification completed.
70888 data files processed.
CHKDSK is verifying Usn Journal...
36212392 USN bytes processed.
Usn Journal verification completed.


Stage 4: Looking for bad clusters in user file data ...
511728 files processed.
File data verification completed.


Stage 5: Looking for bad, free clusters ...
16256524 free clusters processed.
Free space verification is complete.


Windows has scanned the file system and found no problems.
No further action is required.


157437951 KB total disk space.
91546968 KB in 430643 files.
241288 KB in 70889 indexes.
0 KB in bad sectors.
623595 KB in use by the system.
65536 KB occupied by the log file.
65026100 KB available on disk.


4096 bytes in each allocation unit.
39359487 total allocation units on disk.
16256525 allocation units available on disk.


Internal Info:
00 cf 07 00 24 a7 07 00 c9 cc 0d 00 00 00 00 00 ....$...........
55 04 00 00 a0 00 00 00 00 00 00 00 00 00 00 00 U...............


Windows has finished checking your disk.
Please wait while your computer restarts.

------

chkdsk d: /r /f /v


Stage 1: Examining the basic structure of the file system ...
27392 of processed file records.
File verification completed.
3 records of large files processed.
0 invalid file records processed.


Stage 2: Examining the filename link ...
296 records of new analyzes processed.
31126 of index entries processed.
Index check completed.
0 files not indexed checked.
0 unincorrected files recovered in lost and found.
296 records of new analyzes processed.


Stage 3: examining security descriptors ...
Excluding 27 unused index entries from $ SII index
of file 9.
Deleting 27 unused index entries from $ SDH index
of file 9.
Clearing 27 unused security descriptors.
Verification of completed security descriptors.
1868 processed data files.
CHKDSK is checking the USN diary ...
8817928 of USN bytes processed.
Completed USN Journal Check.


Stage 4: Looking for invalid clusters in user file data ...
27376 of processed files.
Checking the data of the completed file.


Stage 5: Looking for free invalid clusters ...
33249767 of free processed clusters.
Free space verification completed.


There are no problems with the file system.
No action required.


409585220 KB of total disk space.
276464520 KB in 21884 files.
7148 KB in 1869 indexes.
0 KB in bad sectors.
114484 KB in use by system.
65536 KB occupied by log file.
132999068 KB available on disk.


4096 bytes in each allocation unit.
Total of 102396305 disk allocation units.
33249767 allocation units available on disk.


------

chkdsk e: /r /f /v


Stage 1: Examining the basic structure of the file system ...
121504 of processed file records.
File verification completed.
30 records of large files processed.
0 invalid file records processed.


Stage 2: Examining the filename link ...
3439 records of new analyzes processed.
129790 of index entries processed.
Index check completed.
0 files not indexed checked.
0 unincorrected files recovered in lost and found.
3439 records of new analyzes processed.


Stage 3: examining security descriptors ...
Excluding 362 unused index entries from $ SII index
of file 9.
Deleting 362 Unused Index Entries from $ SDH Index
of file 9.
Clearing 362 unused security descriptors.
Verification of completed security descriptors.
4144 processed data files.
CHKDSK is checking the USN diary ...
36823568 of USN bytes processed.
Completed USN Journal Check.


Stage 4: Looking for invalid clusters in user file data ...
121488 of processed files.
Checking the data of the completed file.


Stage 5: Looking for free invalid clusters ...
30917397 of free processed clusters. .
Free space verification completed.


There are no problems with the file system.
No action required.


327845904 KB of total disk space.
203927608 KB in 21257 files.
15088 KB in 4145 indexes.
0 KB in bad sectors.
233620 KB in use by system.
65536 KB occupied by log file.
123669588 KB available on disk.


4096 bytes in each allocation unit.
Total of 81961476 allocation units on disk.
30917397 Available allocation units on disk

------

chkdsk g: /r /f /v


Stage 1: Examining the basic structure of the file system ...
256 of processed file records.
File verification completed.
0 records of large files processed.
0 invalid file records processed.


Stage 2: Examining the filename link ...
1 records of new analyzes processed.
286 of processed index entries.
Index check completed.
0 files not indexed checked.
0 unincorrected files recovered in lost and found.
1 records of new analyzes processed.


Stage 3: examining security descriptors ...
Excluding 10 unused index entries from $ SII index
of file 9.
Deleting 10 unused index entries from $ SDH index
of file 9.
Clearing 10 unused security descriptors.
Verification of completed security descriptors.
16 processed data files.
CHKDSK is checking the USN diary ...
10568 of USN bytes processed.
Completed USN Journal Check.


Stage 4: Looking for invalid clusters in user file data ...
240 of processed files.
Checking the data of the completed file.


Stage 5: Looking for free invalid clusters ...
20421908 of free processed clusters. ...
Free space verification completed.


There are no problems with the file system.
No action required.


81787900 KB of total disk space.
30968 KB in 13 files.
88 KB in 17 indexes.
0 KB in bad sectors.
69212 KB in use by system.
65536 KB occupied by log file.
81687632 KB available on disk.


4096 bytes in each allocation unit.
Total of 20446975 disk allocation units.
20421908 allocation units available on disk.

Thank's
Clamarc
 
Ok softwaremaniac... so, if nothing else can be done, you can consider the topic as closed.


appreciate your attention
Clamarc
 
You must log in or register to reply here.

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

Back
Top