Are you seeing multiple reboots?

Topic

New Reply

For those running Windows – if you’ve gone ahead and installed the July updates, are you seeing more than one reboot? (Note I am not recommending that
[See the full post at: Are you seeing multiple reboots?]

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

Replies

No.
I use WUmgr and get the usual first reboot after update installation and second reboot after 30% updating to 100% and desktop

Reply | Quote

Susan Bradley wrote:

if you’ve gone ahead and installed the July updates, are you seeing more than one reboot?

Yes, I did.
I updated Wednesday 12 July about 03:30 WET (*), when my Windows 11 Pro 22H2 rebooted -surprisingly- 3 times.
But now I’m not unduly worried any more. All is quite well and no different than before. My computer still works fine, games and all.

(*) Western European Time and dry.

1 Desktop Win 11
1 Laptop Win 10
Both tweaked to look, behave and feel like Windows 95
(except for the marine blue desktop, rgb(0, 3, 98)

Reply | Quote

Absolutely! 7/11: Cumulative update for .NET Framework 3.5, 4.8 and 4.8.1 for Windows 10 version 22H2 for x64 (KB5027538); 7/13: Same update name (KB5028937); 7/15: 4.8.1 is supposed to be installed after a restart (KB5011048). This is disconcerting.

Reply | Quote

As I wrote before – at least 3 reboots, probably 4 (self -induced).  I got the update from the catalog.  I first used WUmgr, but it got the wrong KB number and failed to download.  I had to look up the correct KB number and install it myself. (185 instead of 182)

Mark

Windows 11 Pro 22H2

 

Reply | Quote

Mark wrote:

at least 3 reboots, probably 4 (self -induced)

I also did a 4th reboot, also voluntarily self-inflicted, just to make sure I did get all updates, patches and whatnot.

But that 4th reboot was superfluous, as Windows Update then told me Windows was Upsy-Daisy.

1 Desktop Win 11
1 Laptop Win 10
Both tweaked to look, behave and feel like Windows 95
(except for the marine blue desktop, rgb(0, 3, 98)

Reply | Quote

I had to self-reboot to get the other reboots started.  I had already installed the .Net, Malicious Software, etc. updates from WU, but I aborted the Windows 11 update because it was cumulative and HUGE.  It also was the wrong KB number as I found later.  I can’t remember if the other updates rebooted then or not , but I think that they did.

Mark

Windows 11 Pro 22H2

 

Reply | Quote

No reboots at this end after installing July updates via Windows Update except the usual restart/installation of updates. Windows 10 22H2 Pro.

Reply | Quote

Concering these multiple reboots when updating, are users experiencing this waiting for the updates to finish installing? (You can see this on the security page if you let windows do it.) If you click the reboot message, that seems to pop once per .Net update for instance you will have to reboot many times.

Tldr: Users clicking the popup before updates are installed or windows doing this by itself?

 

Reply | Quote

I remain in the Settings\Windows Update window until all updates have finished installing and there is no activity except the “Restart needed” notice.

July updates on x4 Win10 computers (two in VMs and two in hardware installs).
No updates were offered for the .NET Framework 3.5/4.8/4.8.1 on any of the installations, only updates for .NET 6 where applicable.
Reboot at 30% on all machines only, no multiples.

x3 Win11 installations (two Win11 ARM VMs, one Win 11 hardware install) that had OOB patches.
No updates were offered for .NET Framework 3.5/4.8.1 on any of the installations.
Reboot at 30% on all machines only, no multiples.

1 user thanked author for this post.

Coldheart9020

Reply | Quote

Jim wrote:

Tldr: Users clicking the popup before updates are installed or windows doing this by itself?

I have often wondered about this phenomenon.  I have never understood why MS allows a completed update to display a ‘reboot now’ notice while another update is installing.  I was reminded of this a couple of weeks ago when helping a friend setup a newly acquired Win10 machine.  I had to stop him from responding to the prompt, pointing out that another update was installing and several were queued.

Reply | Quote

Susan Bradley wrote:

For those running Windows – if you’ve gone ahead and installed the July updates, are you seeing more than one reboot?

I had three.  I always wait until all updates are downloaded and installed before I click on Restart now.

As for my NAS, I wait for the push on it, and that happens after Active hours, so I never see it.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We were all once "Average Users". We all have our own reasons for doing the things that we do with our systems, we don't need anyone's approval, and we don't all have to do the same things.

Computer Specs

Reply | Quote

I do the same as you (except I don’t have a NAS), waiting until all updates have finished and there is little or no cpu and disk activity before clicking on the restart now offer. My updates come from settings/windows update: a cumulative monthly update, a dot-net monthly update, a dot-net 6.0 runtime update for windows 11 pro, and the monthly MSRT update and a MSE virus definitions update. This time I had three restarts, at roughly 15% and 30% and near 100% after the initial reboot to begin the process. Windows 11 pro version 22H2 with no modifications to the registry. The Killer Intelligence Service always crashes during or after every monthly update, so I have changed how that service starts to “manual” in services.

 

Reply | Quote

All systems here had the OoB patch installed at the end of June.
No July .NET updates offered via WU (wumgr) for W10
Note: ALL systems are hardware installs, No VM’s; no emulation.

W10 Pro 22H2 x64 (2 devices) kb5028166
W10 Pro 22H2 x86 (1 device) kb5028166
MSRT blocked as well as MSFT drivers (prefer OEM drivers)
Sitting at winver 19045.3208
One reboot for all three devices post patching, no issues.

Downloaded via MSFT catalog
Win8.1 x64 (2 devices with Server 2012 R2 trick) kb5028232
MSRT blocked as well as MSFT drivers (use OEM drivers)
Only one reboot on both for the rock solid OS, no issues.

Usually install .NET updates before the CU (as a long-time preference) with a restart between and after and observe ‘Resmon’ (system resource monitor) whilst patching and let the relevant resources finish before invoking a restart. I prefer to close the ‘patching complete’ popup,once indicated that the patching is complete, wait until SSD activity has slowed down before closing ‘Resmon’ and restarting the system myself.

All of which, have had no file integrity violations before or after the events.

No problem can be solved from the same level of consciousness that created IT- AE

Reply | Quote

I experienced an extra reboot on this go-round, 3x Win 11 22H2 machines and one Win 10 22H2 via plain old Windows Update. As always lately, I wait for all the thrashing to finish and all offered patches to show as completed before giving permission to reboot.

Two minor thigs of note: I can’t remember which OS it was (sorry), but one of my machines was not offered the .NET update when I released the update deferment. It finally noticed it was needed hours/a day later, after not just the post update reboots, but some use and another shutdown/restart cycle.

I have also noticed that machines like some “resting time” to straighten their clothing and smooth out their hair on the login screen before I log back in, or I may be faced with the annoying but harmless “Let’s finish setting up your Windows device” screen that needs to be dismissed if I get ahead of the housekeeping. The slower machines needing more time of course.

Reply | Quote

Net framework optional updates it is not necessary

Reply | Quote

When the update was about 95% done, my machine went into a second reboot.  And it took about half an hour to finally present the reboot screen.

Reply | Quote

If Secure Boot is active and the KB5025885/CVE-2023-24932 SKUSiPolicy.p7b was not deployed manually, updating boot files will probably require second reboot

2 users thanked author for this post.

TechTango, PKCano

Reply | Quote

Just one reboot here on each of the four Windows 10 machines I’ve updated.  FWIW, I do wait until all updates have finished installing and there is no activity except the “Restart needed” notice.

Reply | Quote

And MSRT.

All updates were installed and waiting for a restart. One reboot at 30% then “cleaning things up”.   Process took around a minute. No observed issues.

Win 10 home - 22H2
Attitude is a choice...Choose wisely

Reply | Quote

Yes.

I have seen as many as three reboots (the first patch reboot, followed by one or sometimes two more) during Windows patching.  This has borne true for Windows 11 22H2, Server 2012 R2, and Server 2016.

We are SysAdmins.
We walk in the wiring closets no others will enter.
We stand on the bridge, and no malware may pass.
We engage in support, we do not retreat.
We live for the LAN.
We die for the LAN.

Reply | Quote

Yes, Multiple reboots with Windows 10 22H2

Reply | Quote

W10 22H2, yes as others have described, whenever I get a .NET update it wants a reboot before the cumulative update finish’s. I just wait and reboot after all have finished so I only reboot once. It only happens when there is a .NET update.

Don't take yourself so seriously, no one else does 🙂
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

Reply | Quote

2 of the 3 PCs updated last week.  Each took three re-boots.  I think the total update time wsas about 4 minutes.  My workstation does not get updated until the end of the month when all the dust settles.  W11 22H2

Reply | Quote