New
#21
IMHO it's worth a reinstall.
If it fixes it, fine.
If it doesn't, at least you know that sfc should work and you have deeper unknown problems.
IMHO it's worth a reinstall.
If it fixes it, fine.
If it doesn't, at least you know that sfc should work and you have deeper unknown problems.
Is a repair in-place upgrade from my previous post already considered/performed?
I would recommend to test your hard drive using a few tools
Please fill in your system specs
Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums
NoteDo not run SeaTools on an SSD as the results will be invalid.
Run HDTune to
- scan for errors, no quick scan but full scan
- check the health,
- benchmark.
It may take some time, but please take the time you need to perform it properly.
Let me know what the results are
- of the error scan,
- make a screenshot of the health of every hard drive and post the screenshots,
- post screenshots with the benchmark of the
- transfer rate,
- access time,
- burst rate,
- cpu usage.
Please follow this tutorial and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely including PSU, cooling system and other used stuff. PSU, cooling system and other used stuff are not in the tool from the tutorial, you need to get those details yourself.How to fill in your system specs:
I've check the disk health several times and that doesn't seem to be the problem. I'll do a repair install.
Not that one but CristalDisk, chkdsk several times, WD Disk Tool FULL SCAN (my HDD is WD) so up to this point I doubt is a HDD issue.
I ended up resolving it myself manually. I looked deeper in CBS.log and found a corrupt file being the cause of the sudden stop of the SFC at 1%. This file:
C:\Windows\WinSxS\amd64_custommarshalers_b03f5f7f11d50a3a_10.0.10586.0_none_d9afb0da2979817a\CustomM arshalers.dll
I replaced it with the file from another PC I have and again SFC stopped at 1%. Checked the log again and now this is the problematic file:
C:\Windows\Microsoft.NET\Framework64\v2.0.50727\CustomMarshalers.dll
Replaced again and now SFC gets to 54% then stops.
I'll keep looking and get back to you.
The corrupted files are a lot more than I espected, so after replacing several of them, I got tired and decided to make a repair install. But it failed with code 0x8007002c 0x2000D during SAFE_OS operation. So now I'm back to replacing files.
Any ideas so far?
Did you uninstall/disable any 3rd party AVs during the repair install?
Yep, I disabled ESET.
I finally replaced all the files, now SFC and DISM are working again. But I have some warning and error about wrong owners and duplicate permission on some system folders, any way of fix that?