Windows 10: Run SFC Command in Windows 10

It's actually fine to not worry about it unless you are having issues with PowerShell.

If you are, then doing a repair install should sort it without losing anything.

Repair Install Windows 10 with an In-place Upgrade

 

Yes windows seems to be functioning just fine.I think I will just leave it be for now until I actually run into some trouble then I will do a refresh. I usually refresh any os I have had at least twice a year anyway. Thanks for shedding some light on it for me.I can't thank you enough for your time, you're a true gentlemen.

 

You're most welcome. *Smile

 

hey i also have the smme problem and i did option 5 and heres the file by the look of it theres around five corruptions plz reply help?!sfcdetails.txt

 

Hello xing he, and welcome to Ten Forums. *Smile

It looks like you have a bunch of shortcuts with has mismatches. If you haven't already, see if dong what's in the note box at the bottom of OPTION THREE may allow SFC to repair them afterwards.

 

umm the Dism or the reset and if its the reset will it delete anything

 

I have been using Windows 10 Pro since the RTM was released mid-July and apart from one system freeze (during a forced graphics driver update of all things!), it has been otherwise 100% stable and functional. I've encountered a few annoying bugs but those are to be expected in any new operating system. My PC is a games machine and everything works great. That is the main thing.

One minor issue I have encountered though is that when I run sfc /scannow in an elevated PowerShell window it will always find corrupted files that it cannot fix. An examination of the log file reveals that the unfixable files are actually shortcuts to things like Task Scheduler, etc, which all oddly work and do not report errors.

This is my SFC log file: https://dl.dropboxusercontent.com/u/...SFCDetails.txt

Unfortunately, running DISM does not work either as it returns error 0x800F081F after reaching 100% with a message about the source files not being found. If I try to link to the install.esd on my USB memory stick using the /source flag then it still returns the same error. DISM /scanhealth reports that the component store is repairable however.

Although this issue has not adversely affected Windows 10 in any way I have noticed, the obsessive compulsive in me (the one that cannot abide seeing error messages), finally decided that he would do an upgrade install of Windows from within Windows. This went well, in fact, I only had to upgrade my graphics driver post-install as everything else was exactly as it was before the upgrade. I ran sfc /scannow at this point and it found errors but fixed them this time! I also ran DISM /restorehealth and it passed 100% complete, no errors.

I then proceeded to check for Windows Updates because the upgrade meant they had to be redownloaded. Sadly, post Windows Update and restart sfc /scannow is back to reporting unfixable corruption and DISM returns the 0x800F081F error! Arggghhhhhhh!

After much reading around, I have come to the conclusion that Windows 10 Pro build 10240 must have a bug of some kind that prevents SFC and DISM from working properly...at least on my system anyway. If I had to take a guess then I would say that is because the component store is not being updated with the newer files from the Windows Update downloads but the database is so when it checks for corruption there is a mismatch on the file versions, something like that (I admit I am not expert). And the /source flag does not work with DISM because the image I have on my USB memory stick is of the original 10240 build not the updated version I am running post-Windows Update.

I am curious though to know if anyone running Windows 10 from an upgrade has NO errors when running sfc /scannow or DISM. Many people will not be aware of this issue because they would have no reason to run either unless they have a problem. I have read that doing a clean install fixes the issue but that is not an option for me due to the sheer number of programs, apps and games that I have installed.

 

Well not completely sure exactly what you mean, but I think I do, so here goes. I upgraded my OS from windows 7 Ultimate to Win10 Pro, have never done a fresh install. same reason as you too many registered programs to re-install. I have run both sfc scannow and Dism command: dism.exe /online /cleanup-image /restorehealth both ran fine, sfc found no errors, but everytime I've ran it in the past it always leaves files in my pending renames folder, that can be very hard to remove. Dism command runs fine also, telling me it has run successfully when its finished. So hoped this has helped you a little. My machine is NOT a gamming machine, far from it. Just an HP computer built in 2009 with a SSD primary partition.

 

You would start at the top of the list in the blue note box to see if SFC may be able to repair the files afterwards.

Reset and refresh would be a last resort since a reset is like a clean install, and a refresh would remove all installed apps.

If you are not having any issues from them, then it wouldn't be worth doing a refresh or reset.

 

In response to Daz1967,

I had exactly the same problem you had except that after upgrading win 10 within Windows 10 and ran the updates post upgrade, the infamous error 0x800f081f didn't come back in my case. For good measure, I ran sfc /scannow again just before this writing and everything is fine (no integrity violations). Now, my suggestions to you is to download a new media creation tool from Microsoft's site and burned the .iso file with Windows own integrated burning tool while you are still in the Media creation Tool window at the end of your download (Burn image now). Don't use a third-party image burning app.

After creating your .iso image on a DVD, try to run the upgrade again within Windows 10 , but make sure you have created a good system image backup before anything. I hope that will resolve your issue.

 

If you cant open your start menu and search doesn't work and you need to run elevated powershell go to
C:\Users\YOUR_NAME\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Windows PowerShell

https://www.tenforums.com/tutorials/2...dows-10-a.html

Change YOUR_NAME to your user account. Now right click on Windows PowerShell to Run as administrator.

Same thing for elevated cmd

C:\Users\YOUR_NAME\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\System Tools

Right click on Command Prompt to Run as administrator.

Your will notice other windows files to run from there.

 

Using the first method, how do I check if the system is whole because the SFC command does not create any CBS.log file?

Thanks

Bye

 

Hello Balubeto, *Smile

The only way to do so using OPTION ONE is by whatever it may tell you in the command prompt at that time.

 

I want to know if the partition is normally used to boot Windows 8.x/10.x or if it is used only by the SFC utility using the first method?

Thanks

Bye

 

You'll need to post a screenshot showing the full layout of your Disk Management (diskmgmt.msc) to determine that.

The Recovery Partition is usually used just for WinRE, but you don't want to delete it.