I keep getting fooled by these happening unknown to me. When they're in progress, some of Windows' functions just stop being available, but they don't let me know; they just hang.
Here's a typical example that's just occurred.
I ran DISM in CMD, preparatory to an SFC scan. It finished, I started the SFC, but it just hung there. Then I set about looking for the cause. It took some time to realise that a system update must be in progress.
Is there a way to have the updates inform me that one's in progress? I can't find one in Settings.
Ed
I keep getting fooled by these happening unknown to me. When they're in progress, some of Windows' functions just stop being available, but they don't let me know; they just hang.
Here's a typical example that's just occurred.
I ran DISM in CMD, preparatory to an SFC scan. It finished, I started
the SFC, but it just hung there. Then I set about looking for the cause.
It took some time to realise that a system update must be in progress.
Is there a way to have the updates inform me that one's in progress? I
can't find one in Settings.
Ed
I keep getting fooled by these happening unknown to me. When they're in progress, some of Windows' functions just stop being available, but they don't let me know; they just hang.
Here's a typical example that's just occurred.
I ran DISM in CMD, preparatory to an SFC scan. It finished, I started
the SFC, but it just hung there. Then I set about looking for the cause.
It took some time to realise that a system update must be in progress.
Is there a way to have the updates inform me that one's in progress? I
can't find one in Settings.
Ed
On 05/06/2026 17:16, Ed Cryer wrote:
I keep getting fooled by these happening unknown to me. When they're in
progress, some of Windows' functions just stop being available, but they
don't let me know; they just hang.
Here's a typical example that's just occurred.
I ran DISM in CMD, preparatory to an SFC scan. It finished, I started
the SFC, but it just hung there. Then I set about looking for the cause.
It took some time to realise that a system update must be in progress.
Is there a way to have the updates inform me that one's in progress? I
can't find one in Settings.
Ed
Why are you online while performing maintenance on your system? Common
sense would suggest doing such things offline when you are not busy with other important tasks. In my opinion, routine maintenance does not
constitute important work.
Also, most system-level maintenance requires elevated privileges, so
it's even more important to be offline.
On 06/05/2026 12:16 PM, Ed Cryer wrote:
I keep getting fooled by these happening unknown to me. When they're
in progress, some of Windows' functions just stop being available, but
they don't let me know; they just hang.
Here's a typical example that's just occurred.
I ran DISM in CMD, preparatory to an SFC scan. It finished, I started
the SFC, but it just hung there. Then I set about looking for the
cause. It took some time to realise that a system update must be in
progress.
Is there a way to have the updates inform me that one's in progress? I
can't find one in Settings.
Ed
Look in Windows Update prior to running DISM commands.
ÿAt least 3 separate DISM commands should be done prior to SFC [1]
[1] At this time on both Windows 11 and Windows 10 ESU, multiple types
of updates can be included in the monthly(2nd Tues) deployment
ÿ1. Monthly Security updates (Monthly updates, MSRT)
ÿ2. Monthly .NET updates
ÿ3. Windows Recovery Updates(inclusion started summer 2025)
ÿ4. Secure Boot update [2] (inclusion started last year, but for most devices more recent starting in April)
#1-3 are normal deployment(if available, deployed to almost all devices
that were previously 'update-current')
#4 are staged deployment(if available, not necessarily deployed to all devices)
[1]
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /AnalyzeComponentStore
If the first two report no component store issues or no corruption, run
the third.
If the third reports no reclaimable packages, then run SFC
If the first or second report component store or corruption issues, then
run the following prior to the third(AnalyzeComponentStore)
DISM /Online /Cleanup-Image /RestoreHealth
If the third(AnalyzeComponentStore) indicates reclaimable packages, run
the following.
DISM /Online /Cleanup-Image /StartComponentCleanup
Restart the device, then rerun the those three(CheckHealth, ScanHealth, Analyze) to validate no further issues, the run SFC.
[2] #4 can be unique, requiring 2 Restarts
ÿ- Simplified explanation - one to push the certs to the device, the
second to load newly signed cert and acceptance of the certs.
Note: SFC(just like Disk Cleanup) can appear to be in a 'limbo'
state(appear to not be responding, hanging)...best to not abort or interrupt(i.e. walk away for 15-20 min).
App updates being deployed via the MSFT Store and Security
Updates(Windows Security/Defender) do not impact DISM or SFC running.
[1]
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /AnalyzeComponentStore
In article <1100b9k$1kh9f$1@dont-email.me>, winstonmvp@gmail.com says...
[1]
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /AnalyzeComponentStore
If you're going to run /ScanHealth there is no need to run /CheckHealth
https://gemini.google.com/share/19a44499b2f7
Thanks for all the advice.
I do always look to see if there are any updates awaiting before doing system maintenance; and I did on this occasion too.
There were none. Moreover, my DISM ran without a hitch. So then, that update must have been pushed into my machine at some time between DISM and SFC; bare seconds.
I guess I could always pause updates before doing cleaning jobs. But then I'd probably forget to turn them back onÿ (:-
I've detected a tendency in Windows for years towards giving out less and less info on what's going on. Less user-friendliness.
MS probably resent all us still using Win10; why can't we move up to Win11? My answer; because it's inferior to Win10.
Ed
On Sat, 6/6/2026 6:36 AM, Ed Cryer wrote:
Thanks for all the advice.
I do always look to see if there are any updates awaiting before doing system maintenance; and I did on this occasion too.
There were none. Moreover, my DISM ran without a hitch. So then, that update must have been pushed into my machine at some time between DISM and SFC; bare seconds.
I guess I could always pause updates before doing cleaning jobs. But then I'd probably forget to turn them back onÿ (:-
I've detected a tendency in Windows for years towards giving out less and less info on what's going on. Less user-friendliness.
MS probably resent all us still using Win10; why can't we move up to Win11? My answer; because it's inferior to Win10.
Ed
The other four hundred and fifty million people are switching to Linux.
And me, I'm going to try Diet Pepsi. It tastes great and it is less filling.
"Windows 12, open Microsoft Word for me"
"I'm afraid I can't do that, Dave"
"Well, first of all, you idiot AI, my name is not Dave."
"And second of all..."
You won't have time, to worry about updates.
Paul
Philip Herlihy wrote:
In article <1100b9k$1kh9f$1@dont-email.me>, winstonmvp@gmail.com says...
[1]
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /AnalyzeComponentStore
If you're going to run /ScanHealth there is no need to run /CheckHealth
https://gemini.google.com/share/19a44499b2f7
And if you run "DISM /Online /Cleanup-Image /RestoreHealth" (as I've
always done), then that covers all takes.
Ed
| Sysop: | Jacob Catayoc |
|---|---|
| Location: | Pasay City, Metro Manila, Philippines |
| Users: | 4 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 494928:13:36 |
| Calls: | 162 |
| Files: | 568 |
| D/L today: |
14 files (349K bytes) |
| Messages: | 74,957 |