Reply to thread

Message

<blockquote data-quote="plat" data-source="post: 919900" data-attributes="member: 74969">This is an interesting question.&nbsp; I run the sfc /scannow alone about 99% of the time when checking for system file corruption.If that comes up with corrupted files/able or unable to fix, then I run dism /online /cleanup-image /restorehealth.&nbsp; Then I run sfc again and almost always, it&#039;s clean afterward.I don&#039;t think an sfc scan showing file corruption has ever led to a complete Windows reinstallation on here.&nbsp; It&#039;s generally been hardware-involved issues instead, like bluescreens of death (BAD_SYSTEM_CONFIG_INFO) or a corrupted partition.&nbsp; Which reminds me, I better update my static image.&nbsp; <img class="smilie smilie--emoji" loading="lazy" alt="😬" title="Grimacing face&nbsp; &nbsp; :grimacing:" src="https://cdn.jsdelivr.net/joypixels/assets/6.6/png/unicode/64/1f62c.png" data-shortname=":grimacing:" />What do you all do?</blockquote>

[QUOTE="plat, post: 919900, member: 74969"] This is an interesting question. I run the sfc /scannow alone about 99% of the time when checking for system file corruption. If that comes up with corrupted files/able or unable to fix, then I run dism /online /cleanup-image /restorehealth. Then I run sfc again and almost always, it's clean afterward. I don't think an sfc scan showing file corruption has ever led to a complete Windows reinstallation on here. It's generally been hardware-involved issues instead, like bluescreens of death (BAD_SYSTEM_CONFIG_INFO) or a corrupted partition. Which reminds me, I better update my static image. 😬 What do you all do? [/QUOTE]

Verification