Author Topic: (SOLVED) Issues with SFC /Scannow... DISM not working (Read 19851 times)

layne81 · « **on:** July 30, 2015, 09:24:20 am »

Hello,

I recently just purchased your pro version. I love what you are doing and there definitely was a need for a program such as this.

Anyhow, I am having issues with some system freezing, instability...etc etc... I ran sfc /scannow and resulted in corrupted files... I then ran DISM restore heath (the actual command) inside CMD and it says it repaired....ran sfc again...corrupted files...this happens over and over again... no repair....

The issue is with the files utc.app.jason and telemetry (not the full name) but it cannot repair it for some reason. It is driving me nuts....

I have attached my CBS log.

I cannot install Windows 10 update either... it hangs at 32%... i have to power down and then start backup...it restores to prev win 8.1 pro os.

Here are my specs:
Case: Corsair Vengeance Series C70
Motherboard: Asus Rampage IV Black Edition
CPU: i7-4930k
CPU Cooler: Corsair H100i Water/Liquid Cooler
Ram: 16GB Corsair Vengeance Pro 1866 (CMY16GX3M2A1866C9R)
GPU: 2x EVGA GTX 780 Ti Classified (SLI)
PSU: Corsair AX1200i
HD: Samsung 840 Pro 256GB (OS)
2x WD Velociraptor 500GB (RAID)
OS: Windows 8.1 Pro (x64)
Fans: 6x Corsair AF120 Performance Edition Fans

Also, will your registry repair overwrite my registry tweaks such as menushowdelay, mousehover, etc. ?

Thanks in advance for the help,
Layne

Shane · « **Reply #1 on:** July 30, 2015, 12:09:33 pm »

If havent done so yet I want you to do a bad sector check on the drive with windows chkdsk

Open a cmd.exe window as administrator and put this in
chkdsk c: /r

It will say it cant while the drive is in use and would you like to schedule it for next boot. hit "Y" and then reboot the system. The scan should start before windows loads.

This scan will take a long time based on the size of your hard drive. There will be 5 stages and stage 4 and 5 are where it checks for bad sectors. Once the scan is done the results will be in the event viewer. Post the results for me

Shane

layne81 · « **Reply #2 on:** July 30, 2015, 01:45:54 pm »

Ok here is the results:

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 ...
1637632 file records processed. File verification completed.
8444 large file records processed. 0 bad file records processed.
Stage 2: Examining file name linkage ...
3141318 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered.
Stage 3: Examining security descriptors ...
Cleaning up 695 unused index entries from index $SII of file 0x9.
Cleaning up 695 unused index entries from index $SDH of file 0x9.
Cleaning up 695 unused security descriptors.
Security descriptor verification completed.
751844 data files processed. CHKDSK is verifying Usn Journal...
269291648 USN bytes processed. Usn Journal verification completed.

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

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

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

249518407 KB total disk space.
160581000 KB in 782537 files.
897204 KB in 751845 indexes.
0 KB in bad sectors.
1975243 KB in use by the system.
65536 KB occupied by the log file.
86064960 KB available on disk.

4096 bytes in each allocation unit.
62379601 total allocation units on disk.
21516240 allocation units available on disk.

Internal Info:
00 fd 18 00 7f 69 17 00 22 01 2a 00 00 00 00 00 .....i..".*.....
10 99 0a 00 49 00 00 00 00 00 00 00 00 00 00 00 ....I...........

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

layne81 · « **Reply #3 on:** July 30, 2015, 02:09:01 pm »

Ok I ran sfc /scannow in elevated command prompt and i am still showing corrupt files.

Shane · « **Reply #4 on:** July 30, 2015, 03:23:15 pm »

Have you ran all my repairs in the windows repair yet and in windows safe mode?

If you have I want you to do it a 2nd time. A lot of times if things dont repair right on the first run they will on a 2nd because the first one fixed something for the other repairs to work.

If you havent ran all the repairs yet I want you to do that, but do all of them and make sure you do it in windows safe mode. If any 3rd party program messes with the repairs, not only will it slow down the repairs but it could make things worse.

Oh and of course make sure my program does a registry backup first, that way if something doesnt go right you can restore the registry to before the repairs

Shane

layne81 · « **Reply #5 on:** July 31, 2015, 05:44:17 am »

Hello,

I ran the windows repair in safe mode last night twice and sfc /scannow is still returning corrupted files for utc.app.json and telemetry....

One thing I noticed is.... The CBS.log says that utc.app.json does not match utc.app.json.... So...looking into it.... I noticed that there is 2 copies of telemetry and utc.app.json.

One is copy is located in the Temp folder under Winsxs.... I believe this is what is causing the issues....

Would it mess anything up to clear out that Temp folder in Winsxs and see if that rectifies the issue?

Thanks again for the help,
Layne

Boggin · « **Reply #6 on:** July 31, 2015, 05:51:43 am »

Does the Telemetry error refer to KB3068708 ?

layne81 · « **Reply #7 on:** July 31, 2015, 05:57:01 am »

sfcdetails.txt attached.

layne81 · « **Reply #8 on:** July 31, 2015, 06:05:07 am »

I just uninstalled KB3068708 and ran SFC /SCANNOW again to see if it made a difference and the corrupt files still remain.

Boggin · « **Reply #9 on:** July 31, 2015, 06:08:06 am »

My eyes are crossing over reading that

- it's using wrap around.

Delete that post and then open a Command Prompt(Admin) and enter findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt

This will put an icon onto the Desktop which when double clicked will open the CBS Log in Notepad which you can then copy & paste into the reply box.

This lists just what it has and hasn't repaired.

You could also try SFCFix.exe to see if it will clean up any sfc anomalies http://thetechcookbook.com/automatic-sfc-corruption-repair-sfcfix-exe/

Just seen your latest post and as a chkdsk /f gives it a clean bill of health then the SFCFixe tool may have some effect.

layne81 · « **Reply #10 on:** July 31, 2015, 06:18:36 am »

ok I erased the CBSLOG paste and attached sfcdetails.txt in my previous post.

Boggin · « **Reply #11 on:** July 31, 2015, 06:24:06 am »

That makes it a lot easier to read - Thanks.

Give that SFCFix tool a go to see what that reports and then do another sfc /scannow to see it's still reporting corruption.

layne81 · « **Reply #12 on:** July 31, 2015, 06:25:39 am »

I actually tried that SFCtool before....

I will try again and see if it is able to fix this go round.

layne81 · « **Reply #13 on:** July 31, 2015, 06:30:20 am »

ok this is a different tool than i used before...

It is prompting to instert my Windows 8.1 disc which I cannot at the moment because I am in my office at work. I will try this solution once I am back home.

Thanks for link!

Boggin · « **Reply #14 on:** July 31, 2015, 06:39:43 am »

I've never known that to prompt for an install disk before - it has obviously found something that it needs to extract from the disk - a bit like a sfc /scannow used to do on XP, so I've read - but it does sound promising.

Rick · « **Reply #15 on:** July 31, 2015, 11:05:44 pm »

Quote from: Boggin on July 31, 2015, 06:08:06 am

My eyes are crossing over reading that - it's using wrap around.

Delete that post and then open a Command Prompt(Admin) and enter findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt

This will put an icon onto the Desktop which when double clicked will open the CBS Log in Notepad which you can then copy & paste into the reply box.

This lists just what it has and hasn't repaired.

You could also try SFCFix.exe to see if it will clean up any sfc anomalies http://thetechcookbook.com/automatic-sfc-corruption-repair-sfcfix-exe/

Just seen your latest post and as a chkdsk /f gives it a clean bill of health then the SFCFixe tool may have some effect.

Boggin, good post; seems it asks for install disk when errors found; but does it asks for search for? example, we do a install from the hard drive?
I did not check that

thank you

layne81 · « **Reply #16 on:** July 31, 2015, 11:25:45 pm »

This issue was rectified by a combination of the SFCFix.exe file that Boggin provided and updating to Windows 10 Pro.

Thanks again for your help,
Layne

Boggin · « **Reply #17 on:** August 01, 2015, 12:21:48 am »

SFCFix.exe has proven to be a handy tool in dealing with those KB generated errors and glad it helped to fix your problem.

It's a pity that sfc /scannow doesn't have its attributes.