SFC /scannow reports multiple DIRSD OWNER WARNINGs - Win 8.1

Whilst waiting for assistance, I had a read of some other threads with similar titles and learned that DIRSD OWNER WARNING may not be serious. However, on running sfc /scannow again today, it reports 4 instances of "cannot repair..."

I have attached an up-to-date copy of CBS.log, which I saved as .txt, in accordance with instructions that I found in another thread. I hope that was the right thing to do.

Peter
 

Attachments

Hi PeterPan. :welcome:

FWIK, that message should be normal.
About the "cannot repair", you are getting the usual windows 8/8.1 error never fixed by Microsoft (that file keeps to corrupt itself even if you repair it).
You can find more informations in GUIDE: CNBJ2530.DPB and prncacla.inf Corruptions - Windows 8/8.1 (click).
There you'll find you should run the command dism /online /cleanup-image /restorehealth (from an elevated command prompt, i.e. a command prompt with administrator powers), then, after the first command completed, re-check if the file was repaired with sfc /scannow.
Each one of those two commands should last about 15-60 minutes.

Hope this helps! :wave:
 
Hi @xilolee,
Thanks for the advice; I've tried to follow it.

I followed the link to the GUIDE in your posting. That instructed me to download and run SFCFix.exe, which I did. The result is shown in 2016-06-17_SFCFix.txt, which I have attached. That says it has fixed a problem, which sounds promising. However, that is the same result as I received when I ran SFCFix.exe a few days ago, before I posted here, so I am not celebrating yet.

This morning I ran sfc /scannow again, which resulted in the CBS log file 2016-06-18 CBS.txt. The file is 136MB, so I have tried to share it via OneDrive here;

https://1drv.ms/t/s!ArnaXjIix1kkyQbOxTFqs3ddFPzr.

Please tell me if I have made a mess of sharing it.

Then, I followed your advice and ran the command dism /online /cleanup-image /restorehealth (from an elevated command prompt). That returned a failure message at the command line, (Error: 0x80240021 DISM failed. No operation was performed). The resulting DISM log is also attached as 2016-06-18_DISM_Log.txt

Please advise what I should do next.

Peter
 

Attachments

Sfcfix says it's fixed.
Sfc /scannow probably said the same (did you check the final message on the command prompt?).
No problem for the DISM command, given that sfcfix used it.
 
So are you saying that I can just ignore the error message from DISM, "Error: 0x80240021 DISM failed."?


 
OH, OK then.

Thanks for your assistance. Without your reassurance, I would have worried when I saw a HUGE log file with over 120 instances of "failed to..." :eek:

Peter
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top