SFC /Scannow

Topic

New Reply

Have run sfc /scannow and it shows that WRP found corrupt files but was unable
to fix some some of them. Do these need to be fixed and how?
Thanks
45614-SFC-2

Reply | Quote

Replies

From an elevated Command Prompt type

dism /online /cleanup-image /restorehealth

and hit Enter. It can take a while to run, but let it run until completion.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

Have run the DISM as you suggest and have attached the result.
Thanks
45615-DISM

Reply | Quote

Have run the dism, result attached.
Thanks

45615-DISM

Reply | Quote

RPC is an integral part of Windows and having it fail is not a good sign.
Can you post the DISM log?

cheers, Paul

Reply | Quote

Paul how would I post this file 552Kb?
Thanks
Dave

Reply | Quote

You could run another sfc /scannow and then SFCFix.exe straight after and that will produce a smaller log and may even fix what the sfc /scannow was unable to.

http://www.majorgeeks.com/files/details/sfcfix.html

Instead of uploading such a large file as the DISM CBS, after the sfc /scannow enter this cmd –

findstr /c:”[SR]” %windir%LogsCBSCBS.log >”%userprofile%Desktopsfcdetails.txt

This will put an icon onto the desktop which when double clicked will open in Notepad, but you can right click on the icon and .zip it to upload and as this file will only list what has and hasn’t been repaired, it will be much smaller than the DISM one.

Reply | Quote

Sudo, hope this is OK, was’nt too sure.
45625-sfcdetails

Reply | Quote

That attachment is fine.

Did these problems manifest after installing KB3189866 ?

Can you run another sfc /scannow now and then download/run SFCFix.exe from my link in Post#6 to see what that reports.

You need to run another sfc /scannow before the SFCFix.exe as the CBS log is volatile.

If SFCFix.exe reports irreparable files then uninstall KB3189866 or use your restore points if it won’t uninstall and then run another sfc /scannow to see if it still reports corruption.

As so much is being shown as corrupt in the store and if these steps don’t resolve, then create an up to date Win 10 bootable media from https://www.microsoft.com/en-gb/software-download/windows10 and then do a repair install or you could run the Update now and reinstall Win 10 which won’t affect your programs and files.

Do you use Fax or XPS Viewer which you could remove from Devices and Printers which should remove those errors and have you considered using an alternative free antivirus program to Windows Defender ?

Reply | Quote

Hi Sudo, I am not sure if these problems only manifested themselves after installing KB3189866. as
I never ran sfc/scannow after the initial update to Windows 10 from windows 7.
I do have Fax and Microsoft document writer on Devices and Printers.
I will try a different free antivirus.
Will give more info. just now.
Thanks so far.

Reply | Quote

Latest sfc /scannow.45629-sfcdetails

Is this ok Sudo, I’m getting a bit confused.

Reply | Quote

Sudo this is what happens when I ran SFCFIX.
I am not sure about the KB3189866 uninstall.

45630-SFCFIX

Reply | Quote

My eyes were starting to blur reading all of the corruption in your first sfc txt, but the latest one looks similar.

It’s not a good sign that SFCFix.exe has crashed, but I’ve recently upgraded a Win 7 machine to Win 10 and I don’t think I saw KB3189866 listed among the ensuing updates – although I could have been mistaken

That KB has been referenced in the sfc txt that it would seem to be related.

It’s up to you if you want to take your machine back to pre-KB3189866 but for that amount of corruption should it not be responsible, then I would say that you are looking at either a repair install or a re-run of Upgrade now which will do the same – but something has caused that level of corruption of system files.

Are there any repetitive errors in Event Viewer ?

Reply | Quote

Sudo have attached some of the errors from event viewer to have alook at.
Do I create the W10 bootable media after uninstalling KB3189866.
If I uninstall this KB will my PC revert to W10 V1511?

45635-Event-Viewer

Reply | Quote

No, that KB came after the AU.

Going back to before it was installed and running another sfc /scannow can eliminate it as the cause.

If it hasn’t been pulled then you should get it back through WUs.

The latest ISO or the Upgrade now button will have the latest version which should include any major updates such as KB3189866.

I get those DCOM 10016 errors every time I boot up and would seem to be endemic with Win 10 – I just ignore them as I haven’t noticed any real adverse problems.

The Print Service errors are probably related to the corruption reported in sfc.txt

The Device Setup Manager could be a result of RPC failing to start ? – but the CAPI2 Event ID 513 will interfere with any system images you try to create, but is easily fixed by copying the command in the following article then pasting it to the Command Prompt (Admin) and should return as in the article.

Just right click and drag your mouse over the whole of that cmd then right click and select Copy.

http://justworks.ca/blog/fix-event-513-capi2-errors-during-windows-backup

That Side by Side error – can you click on that to see if it relates to Photo Galley etc. ?

If it does then go Start – type appwiz.cpl and press enter.

Scroll down to Windows Live Essentials – right click on it then click on Change then check the Repair button and let it do its thing.

While you are doing that, I’ll have a look through the rest of the errors but if going pre-KB doesn’t resolve then I reckon the reinstall is the best option.

Reply | Quote

ESENT ID 472 you can ignore.

DNS Clents Events 1014 – I’ve come across that one before where this has resolved by going into Device Manager/View/Show hidden devices – expand Network adapters – right click on the Ethernet adapter – select Properties and under the Advanced tab, change Energy Efficient Ethernet to Disabled in the dropdown.

Can’t find a thing on that DbxSvc Event ID 270.

EDIT – Forgot to add – for the AppMode-Runtime 69 – see if Windows key + r – type wsreset.exe and press enter sorts that one.

That cmd resets the Store.

Reply | Quote

Hi Sudo, the attachment refers to the SFCFix.exe after crashing. Does this need to
be sent somewhere?

I have created the W10 bootable media disc.

I am not sure how to do the uninstall of KB3189866, if i uninstall the KB will my revert bact to Version 1511?
This is what I am confused about.
Many thanks for all your help so far, do appreciate it.

45641-SFCFIX-1

Reply | Quote

Sudo attached is the one for Side By Side

45638-sidebyside

Reply | Quote

Can you reinstall Easus as it may be a Visual C++ package problem.

Reply | Quote

I think the SFCFix.exe fail is down to corruption of your system and not on the part of the program.

If RPC is still failing to start then that can affect quite a few things.

That KB is after the AU and you would only be able to go back to 1511 from 1607 if you did it within 10 days of installing the AU – so no worries on that.

It may take you back from .187 but you’ll still have 1607 14393.#

To uninstall an update – Go Start – Settings – Update and Security – Update history – Uninstall updates.

Type KB3189866 into the top right search box and when it comes up, right click on it and select Uninstall.

It’s a hefty sized update so may take some time to uninstall and will require a restart to effect and then Windows will need to reconfigure updates.

Reply | Quote

I ran the AU Windows10Upgrade28084.exe on the 15th September, so uninstalling KB3189866 will be OK?
Thanks

Reply | Quote

The KB is separate to the AU just as the other updates that accompanied it after the AU.

I installed that update on the 13th Sept. so it’s possible that was the date I manually did the AU.

Hang on and I’ll uninstall the update on mine and then will be able to tell you what effects it will have.

I’ll be creating a restore point first, though.

Reply | Quote

It went pretty much as I expected but had a wobbly moment when it shutdown so far through reconfiguring the updates – got to the 30%, shutdown and came back up with just a black screen and the Win 10 logo.

That disappeared to just leave me with a black screen for longer than I would have cared for but eventually came back up and continued with the Working on updates and the % to progress to a full restart.

winver showed that I had gone from 14393.187 to 14393.0 so you should be safe.

Create your restore point by opening Windows Explorer – right click on This PC and select Properties then click on System Protection in the upper left pane.

It should show that it is On for C:

If it shows as Off then click on Configure and check the top radio button – OK and then click on Create – give it a name – OK and then go into Uninstall updates as previously described when it returns that the restore point had been successfully created.

Going to do a check for updates to reinstall it if it hasn’t already started downloading it, so will be shooting off for a while.

Reply | Quote

Just thought I’d pop back to let you know that a check for updates produced a Cumulative Update which was KB3193494 which seems to have replaced KB3189866 as winver shows I’m back up to 14393.187

It’s possible that MS has superseded it with this latest one as there were some install problems for some – it hung on 95% for a while for me.

This one downloaded and installed in a crack and the restart didn’t take long either.

Reply | Quote

Thanks Sudo. Will give it ago and see.

Reply | Quote

My uninstall and update ran the same as yours, back to 187.

Ran sfc /scannow, same results as before.

Reply | Quote

Did you run the sfc /scannow before installing the new update – which was the purpose of the exercise.

Reply | Quote

Sudo I apologise I some how forgot. This really messes things up.

Reply | Quote

Reply | Quote

It may have been a futile exercise anyway as you don’t know when the corruption occurred.

I’d just open Windows Explorer – click on This PC, stick the Win 10 ISO disk in and click on Setup.exe or you could hit the Update now button in https://www.microsoft.com/en-gb/software-download/windows10

This won’t affect any programs or personal stuff except kick out CCleaner if you have it and you may have to pin IE back onto your taskbar and unpin Edge if you don’t use it.

It may be prudent to create an external system image and system repair disk before you proceed with that.

Reply | Quote

What version of W10 will I end up with after this procedure?
Thanks
Dave

Reply | Quote

You should end up with the same version as you have now – only working.

I recently upgraded a Win 7 machine using the Assistive Technologies link and that gave me 1607 14393.187 which meant I didn’t have to go through the AU.

The ISO and the Upgrade now button will have been upgraded to the most recent version.

Have you run a chkdsk /f since you’ve had this problem – that will tell you if you have any KBs in bad sectors, but to see the log, you have to open Event Viewer.

When it opens, ensure that Event Viewer (Local) is highlighted in the upper left pane – if it isn’t then just click on it and wait for it to read the Data.

Expand Windows Logs – click on Application – Action/Find then type chkdsk or wininit into the Find box and press enter.

Cancel the Find box and read the report in the scrollable window.

To post its log, click on Copy/Copy details as text in the lower right pane – right click in the reply box and select Paste.

Reply | Quote

Did you receive the log details for the chkdsk?

Reply | Quote

I haven’t seen them.

Did you do it as I’d described ?

Reply | Quote

Sudo I think you should have it now. Sorry about that.:confused:

Reply | Quote

The last line of your post I was’nt too sure about. The reply box I right clicked on was on your post and
it created a mail which I sent. Was this the correct “reply box.”

Reply | Quote

No – you right click in your reply box.

It copies the log twice as you’ll see from a Preview of your post, but if you want, you can edit out the top one as the bottom one gives all of the info – or just leave it as is.

Reply | Quote

Where have you sent it ?

Go back into Event Viewer to view the chkdsk log – click on Copy/Copy details as text in the lower right pane – right click in a new reply box and select Paste and submit.

Reply | Quote

Log Name: Application
Source: Microsoft-Windows-Wininit
Date: 23-Sep-16 06:41:59 AM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: Dave-PC
Description:

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 …
467712 file records processed.

File verification completed.
8910 large file records processed.

0 bad file records processed.

Stage 2: Examining file name linkage …
584348 index entries processed.

Index verification completed.
0 unindexed files scanned.

0 unindexed files recovered to lost and found.

Stage 3: Examining security descriptors …
Cleaning up 5801 unused index entries from index $SII of file 0x9.
Cleaning up 5801 unused index entries from index $SDH of file 0x9.
Cleaning up 5801 unused security descriptors.
Security descriptor verification completed.
58319 data files processed.

CHKDSK is verifying Usn Journal…
171128776 USN bytes processed.

Usn Journal verification completed.
CHKDSK discovered free space marked as allocated in the volume bitmap.

Windows has made corrections to the file system.
No further action is required.

155724799 KB total disk space.
95295508 KB in 312204 files.
210060 KB in 58320 indexes.
0 KB in bad sectors.
712351 KB in use by the system.
65536 KB occupied by the log file.
59506880 KB available on disk.

4096 bytes in each allocation unit.
38931199 total allocation units on disk.
14876720 allocation units available on disk.

Internal Info:
00 23 07 00 8e a6 05 00 ea 57 0a 00 00 00 00 00 .#…….W……
2b 48 00 00 81 00 00 00 00 00 00 00 00 00 00 00 +H…………..

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

Event Xml:

1001
0
4
0
0
0x80000000000000

4979

Application
Dave-PC

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 …
467712 file records processed.

File verification completed.
8910 large file records processed.

0 bad file records processed.

Stage 2: Examining file name linkage …
584348 index entries processed.

Index verification completed.
0 unindexed files scanned.

0 unindexed files recovered to lost and found.

Stage 3: Examining security descriptors …
Cleaning up 5801 unused index entries from index $SII of file 0x9.
Cleaning up 5801 unused index entries from index $SDH of file 0x9.
Cleaning up 5801 unused security descriptors.
Security descriptor verification completed.
58319 data files processed.

CHKDSK is verifying Usn Journal…
171128776 USN bytes processed.

Usn Journal verification completed.
CHKDSK discovered free space marked as allocated in the volume bitmap.

Windows has made corrections to the file system.
No further action is required.

155724799 KB total disk space.
95295508 KB in 312204 files.
210060 KB in 58320 indexes.
0 KB in bad sectors.
712351 KB in use by the system.
65536 KB occupied by the log file.
59506880 KB available on disk.

4096 bytes in each allocation unit.
38931199 total allocation units on disk.
14876720 allocation units available on disk.

Internal Info:
00 23 07 00 8e a6 05 00 ea 57 0a 00 00 00 00 00 .#…….W……
2b 48 00 00 81 00 00 00 00 00 00 00 00 00 00 00 +H…………..

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

Reply | Quote

That’s fine – I was just worried that the corruption could have been as a result of bad sectors on the hard drive.

If you have created a system image onto external media and a system repair disk, then go ahead with the repair install by either method, although I would favour the Update now button and as a safeguard to any install problems, either fully disable or uninstall your antivirus program.

Reply | Quote

Would this include the Malwarebytes as well?

Reply | Quote

No – it only applies to an active antivirus program as it can block files by scanning them and not releasing them.

I had a hell of a job manually updating to the AU and again upgrading a Win 7 machine until I disabled all aspects of Norton Security in the first instance and uninstalling Avast Free in the second.

Reply | Quote

Thanks will do.

Reply | Quote

Sudo I pressed the update button, and ran the Windows10 upgrade, and it was over in a flash.

Is this correct?

Reply | Quote

I would have thought it would have taken longer than that – run another sfc /scannow and if it still reports corruption then use the disk.

I’ll create a system image of mine and give that button a try.

Be back in a while if you want to hang on, but run the sfc /scannow anyway.

Reply | Quote

Problems with SFC seem to be happening more frequently with Win10.
I got this message after it reached 19%.

I’m completely in the dark as to what it means.

Alex

Reply | Quote

Alex, I just run a sfc /scannow and it still shows corrupt files??

Reply | Quote

I didn’t get very far with that Update now button either – clicked on run and shortly after was thanked for updating to the latest version which is probably because I have the latest version as you have.

Is that what you got ?

I’d go for using the disk as that will perform a repair install.

@ Alex – If you have the latest version of 1607 14393.187 and sfc /scannow is reporting corruption, then you have corruption.

I’ve just run a sfc /scannow and it came back clean.

You can follow what Dave has done so far but if you need specific help then you will need to open your own thread – but I’d start with a chkdsk /f to see if you have any bad sectors – although I think you are looking at a repair install as well.

Reply | Quote

Yes Sudo, I also got thanked for updating to the latest version

I then used the disk, and then ran a sfc /scannow with results attached. Clean, fantastic.
This was really a marathon effort from your side and at times you showed great patience.
I really appreciate your efforts, never giving up on me.
Running the disk was also quite a marathon, but has paid off.

45650-Sfc-23

Reply | Quote

That’s great news.

When I take a job on, I’ll stay with it until it’s fixed or in some cases, the member gives up – but if I’m unable to take it further because of a lack of expertise on my part then I’ll say so and ask someone else to take a look.

If you are happy then you can use the Thread Tools dropdown to Mark thread as Solved – which will close it from any further comment, except by a Mod or you can re-open it.

And it’s been a pleasure to help and to see a successful conclusion.

BTW – Have you reinstated your AV program ?

Reply | Quote

Yes Sudo my AV up and running.

Once again many thanks.

Reply | Quote