If SFC gets stuck...

[Philip Herlihy]

Bizarre thing. Working remotely on a friend's PC, I wanted to give the thing a
"service". Weeded system files (took ages on a slow machine). Filesystem
check. DISM to scan the componenent store in preparation for an SFC /Scannow

Crawled its way to 29% in about an hour. We agreed to leave it overnight.

Morning: still 29%. Looked in Google: several people suggested maxmimising
the window in which it was running, then reducing it again.

It worked! 30%... 31% (etc).

How weird is that?

[Jeff Gaines]

On 23/09/2024 in message

Post by Philip Herlihy
Bizarre thing. Working remotely on a friend's PC, I wanted to give the thing a
"service". Weeded system files (took ages on a slow machine). Filesystem
check. DISM to scan the componenent store in preparation for an SFC /Scannow
Crawled its way to 29% in about an hour. We agreed to leave it overnight.
Morning: still 29%. Looked in Google: several people suggested maxmimising
the window in which it was running, then reducing it again.
It worked! 30%... 31% (etc).
How weird is that?

Probably took 25 Microsoft programmers six months to come up with that
feature :-)

[Andy Burns]

Post by Philip Herlihy
Crawled its way to 29% in about an hour. We agreed to leave it overnight.
Morning: still 29%. Looked in Google: several people suggested maxmimising
the window in which it was running, then reducing it again.
It worked! 30%... 31% (etc).
How weird is that?

Perhaps an accidental click to start a drag/select, which has the
side-effect of pausing wha's running in the window?

[Philip Herlihy]

Post by Andy Burns

Post by Philip Herlihy
Crawled its way to 29% in about an hour. We agreed to leave it overnight.
Morning: still 29%. Looked in Google: several people suggested maxmimising
the window in which it was running, then reducing it again.
It worked! 30%... 31% (etc).
How weird is that?

Perhaps an accidental click to start a drag/select, which has the
side-effect of pausing wha's running in the window?

Do we know it would do that? But a click is momentary, and as soon as the
mouse button was lifted it should surely restart, if paused at all.

[Andy Burns]

Andy Burns wrote...

Post by Andy Burns
Perhaps an accidental click to start a drag/select, which has the
side-effect of pausing wha's running in the window?

Do we know it would do that? But a click is momentary, and as soon as the
mouse button was lifted it should surely restart, if paused at all.

The new multi-tab command window seems to have changed behaviour, you
used to be able to leave selection in a state where the title read
"select blah" and I/O was blocked until yu hit enter ... not any longer.

<Loading Image...>

[Philip Herlihy]

Post by Andy Burns

Andy Burns wrote...

Post by Andy Burns
Perhaps an accidental click to start a drag/select, which has the
side-effect of pausing wha's running in the window?

Do we know it would do that? But a click is momentary, and as soon as the
mouse button was lifted it should surely restart, if paused at all.

The new multi-tab command window seems to have changed behaviour, you
used to be able to leave selection in a state where the title read
"select blah" and I/O was blocked until yu hit enter ... not any longer.
<https://i.sstatic.net/B6MCF.jpg>

That's interesting to know. I wasn't using the multi-tab version. I've
(still...) never got my head around PowerShell, so my start menu (right-click)
offers an admin/vanilla Command Prompt window, so that's what I used (admin).