Windows 10: scannow and dism don't work right

I ran sfc/scannow (trying to diagnose a sleep problem) and it found irreparable files, and I ran it again in safe mode, and again, irreparable.
I ran dism and it couldn't access the source files. (Afterwards, I checked windows update, and it says that the computer is up to date, and the last check was at the time I ran dism!)
Is this behavior normal for windows 10 pro x64?

:)

 

SFC /scannow and DISM not working

Ok I will try that, but my computer prompted me to restart to repair it. Now I can't seem to get on because there is no 'Skip' option. I left it on overnight to see if chkdsk would finish, but in the morning it told me to restart because Windows couldn't
start properly. Which meant repeating the process. Any way I can stop it?

EDIT: I managed to get back onto it by unplugging all usb cables, do you think there might be an issue with my keyboard or something?

 

SFC /scannow and DISM not working

Major file system corruption. I would run it again to see if it has re-occurred and if so the HD may be failing

For the second test (which is more important) go to the HD maker>download>run

I cant tell you which opengl it is.

 

What do you mean they don't work right? Details!

Are you using an administrative command prompt (right click Start, select Command Prompt [Admin])?

 

yes, elevated command prompt.
my message indeed contains the errors I encountered.
scannow complains of irreparable files
dism complains that it couldn't access the source files

 

Sorry, dark on dark (dark theme), couldn't see the context of the message.

Have you tried running sfc /scannow Command at Boot?

 

I didn't try that one yet, too lazy... maybe I will give it a go.

 

You first need to run dism command to fix the component store then you can proceed to run sfc.
You also need the Windows 10 ISO from Windows 10 Download - Tech Bench. extract with Winrar or 7-zip

1- Create a folder on desktop: mount
2- Copy install.wim to desktop from the extracted ISO in the Sources folder.

Open Admin Command prompt, copy each line then run:

Dism /mount-wim /wimFile:%USERPROFILE%\Desktop\install.wim /index:1 /MountDir:%USERPROFILE%\Desktop\mount

Dism /Online /Cleanup-Image /CheckHealth

Dism /Online /Cleanup-Image /RestoreHealth /Source:%USERPROFILE%\Desktop\mount\windows /LimitAccess

Dism /unmount-wim /Mountdir:%USERPROFILE%\Desktop\mount /discard

After done with component store repair, run: sfc /scannow

NOTE: You might have to re-run sfc multiple times until you get a clean message.

 

thanks.
I made the mount folder on my desktop, and I mounted a ISO of windows 10, it is an ISO that I downloaded after the big november update.
I copied the install.wim file from it, and pasted it in the mount folder.
I ran admin cmd prompt, and entered the first command.
It returned the error pasted below, even though I can clearly see that the file is in the specified folder:

Error: 2


The system cannot find the file specified.


The DISM log file can be found at C:\windows\Logs\DISM\dism.log

 

I just now ran dism check health, and it shows no problems.
If no problems, then why did scannow say there were problems?
this is the message I got:
C:\windows\system32>Dism /Online /Cleanup-Image /CheckHealth


Deployment Image Servicing and Management tool
Version: 10.0.10586.0


Image Version: 10.0.10586.0


No component store corruption detected.
The operation completed successfully.

 

I saw this post on reddit.
It sounds like maybe windows.old is the source of the "corrupt and unrepairable" files.? If that is true, there really is no problem to begin with.
Windows 10 can't repair corrupt files! : Windows10

 

see link in sig below - program runs all the needed cmds.. to SFC and Restore health

 

You did wrong. From my post #6, copy install.wim onto desktop, not in the mount folder.
Read step #2 again.

 

thanks, my mistake.
but in any case, I ran the health check, and it came out good, so I don't really see the need to run repair dism.

and what about the unrepaired "corrupted files" report from scannow? could it be from windows.old?

this is from kyhi's readme file:
Note: SFC has been known to flag perfectly good files as corrupt, although this does not harm anything other,then the user now thinking the system is corrupt, and resulting in false positive confusion about the corruption

 

Sometimes sfc will refuse to fix the corrupted file(s) unless you first run:
dism /online /cleanup-image /restorehealth
and if this command fails then you'd use the procedure in step #6