Problems With SFC Scannow

No still the same.

I did a in house upgrade from the disk and still getting the same results. I think at this stage I'll give up on it as the O/S is running fine.

200motels said:

I did a in house upgrade from the disk and still getting the same results. I think at this stage I'll give up on it as the O/S is running fine.

This is my thinking of what I did too. Everything I do, need, or have, works the way it should. Can't be major if nothing is broken on the outside. All other system checks come out clean.

200motels said:

I did a in house upgrade from the disk and still getting the same results. I think at this stage I'll give up on it as the O/S is running fine.

After I did the inhouse upgrade I did a sfc /scannow and it was negative as posted above, I shut down PC and 10 mins ago I ran sfc /scannow again just to be sure and bingo it all came back clean.

lx07 said:

Don't give up. This is how it works....

sfc /scannow will take whatever is in the component store and reapply it if it can. This only copies files which are on your local disk anyway.
dsim /online (online means your current windows image) /whatever /cleanupimage /restorehealth this means download from MS servers anything that is not correct. Basically if the hash of some .dll or .exe is diferent in the component store it will download the correct version from MS. You need internet connection for this (unless you want to grab files from another known source which probably you don't)

So run DSIM (with whatever parameters you want but /restorehealth would be good), reboot, then run sfc.

On a clean install it should be OK. I did a clean install of 10 yesterday and sfc says no issues.

hi
may i know which is the command line ?
dsim /online /whatever /cleanupimage /restorehealth
in /whatever what should i add ?
thanks

drugo said:

hi
may i know which is the command line ?
dsim /online /whatever /cleanupimage /restorehealth
in /whatever what should i add ?
thanks

Hi drugo

I followed this solution from the Microsoft support site:

https://support.microsoft.com/en-gb/kb/947821

This should fix issues automatically after being loaded via Windows Update. I ran SFC /scannow afterwards and now everything is fine.

Regards
UKMedia

UKMedia said:

Hi drugo

I followed this solution from the Microsoft support site:

https://support.microsoft.com/en-gb/kb/947821

This should fix issues automatically after being loaded via Windows Update. I ran SFC /scannow afterwards and now everything is fine.

Regards
UKMedia

Hi UkMedia SFC /scannow or SFC /verifyonly doesn't report any violation or errors
but opening CBS.log i find many warning Overlap: Duplicate ownership
like

Info CSI 000007bb Error - Overlap: Duplicate ownership for directory [l:84]"\??\C:\WINDOWS\SystemApps\Microsoft.Windows.AssignedAccessLockApp_cw5n1h2txyewy\pris" in component Microsoft-Windows-AssignedAccessLockApp.AppxMain.Resources, version 10.0.10586.0, arch amd64, culture [l:5]"en-US", nonSxS, pkt {l:8 b:31bf3856ad364e35}

Hi

I have always ignored the warning (rightly or wrongly!)

Regards

UKMedia said:

Hi

I have always ignored the warning (rightly or wrongly!)
Regards

hi me too
don't know if it's a warning or an error what i posted above
but i guess SFC /verifyonly should find every error
cheers

200motels said:

SFC Scannow is throwing up a problem Windows Resource Protection found corrupt files but was unable to fix some of them. Now I've tried to fix them with SFC Fix application but no joy. DISMfile attached.

I had the same issue but got it working, thought it might help you (I know this is a little late). New users would say 'Signing Out...' as soon as they were signing in, variations of DISM did not fix.

Turns out the 'Default' user in C:\Users had incorrect permissions. I fixed it by changing the permissions (Credit goes to here: http://answers.microsoft.com/en-us/w...c-68b599b31bf5)

- Navigate to C:\Users
- Right-click on 'Default' (you'll need to view hidden files to do this) and go to 'Properties'
- Go to the 'Security' Tab
- Mine only had one user setup, but need to make sure you have:
-- 'Everyone' to have read access
-- 'SYSTEM' to have full access
-- 'Administrators' to have full access

I created and applied those settings, created a new user, and it worked perfectly. That worked for me, I hope it works for you.