Try opening an admin-level cmd-prompt and running "sfc /scannow" (it may be an issue of a dependent Windows DLL not being present or damaged).

引用自 Yujah：

Try opening an admin-level cmd-prompt and running "sfc /scannow" (it may be an issue of a dependent Windows DLL not being present or damaged).

Thank you very much. It worked. But it seems "DISM.exe /Online /Cleanup-image /Restorehealth" should be entered before "sfc /scannow"

Okay, Thanks for specifying the additional first step, and glad it did something.

not helping bro

none of this worked.

引用自 Promitheos：

none of this worked.

Interesting that we are here at the same timeframe. Your comment is 9 hours ago. Maybe some updated ♥♥♥♥♥♥ us over? I remember my windows updating last night.

So, those commands don't work?

引用自 The fentinator：

So, those commands don't work?

If you have the problem, try it; it does nothing detrimental at least.

But do otherwise notice that is a year+ old thread; I vaguely remember giving the original advise due to back then in fact running into a report that it was a likely issue with some specific dependent Windows DLL, but that may be otherwise now, even if the symptom is the same.

The comment before you says it's likely in essence similar now, but that a Windows update may now have not as a matter of "damage" but by design changed something. Probably Windows 11? Windows 11 is a pile of ♥♥♥♥♥♥♥♥ that routinely breaks compatibility all over the place.

引用自 Yujah：

...

As much as you hate Windows 11 if a Win11 system had the same damage to it the same command would work the same.

Yes, whence I advised to try it. My point explicitly was that it's likely not "damage" of the kind that the SFC would fix but a Windows 11 update again willy-nilly breaking ♥♥♥♥.

Hey guys, I'm running Windows 10 and just updated my PC. I'm now experiencing the same issue! I tried reinstalling Steam, but it didn't help. I also tried running "DISM.exe /Online /Cleanup-image /Restorehealth", but it has stalled for a very long time now at 62.3%.

Mmm. Kay. Maybe not Windows 11 then (it's still a pile of ♥♥♥♥♥♥♥♥ though!).

"62.3" seems well-known: https://www.reddit.com/r/techsupport/comments/11lf83v/dism_restore_health_stuck_on_623/

For anyone wondering: waiting is the fix.

Being stuck at 62.3% just means windows update is downloading a big ass file/update that will help restore your install.

Good thing I've kept it running then! Will update when done.

Update: So, thirty minutes later and I got A BSOD. Not sure what to do from here other than wait for an update or see if the issue is with my PC itself.

引用自 Trevelyan：

Update: So, thirty minutes later and I got A BSOD. Not sure what to do from here other than wait for an update or see if the issue is with my PC itself.

Well yes, little that can be said generally then; certainly the DISM shouldn't be bombing, and although that likely has nothing to do with the original issue. I'd probably be checking memory stability.

https://www.techrepublic.com/article/how-to-detect-bad-ram-with-the-windows-memory-diagnostic-tool/

or https://www.memtest86.com/download.htm

I ran the windows diagnostic tool and it found no issues.