When is a Reboot Not a Reboot?

Topic

New Reply

I saw a pop-up window this morning that I had to schedule a reboot, as MS had updated my Windows 10 machine from 1909 to 2004.  (I know that I no longer have control over when MS installs patches.)  So I scheduled a reboot for 11 PM tonight, knowing that I would reboot manually before then.  So, I shut down all of my applications and rebooted.  But that reboot did NOT install anything.  I had to go to Windows Update and reboot from there for the updates to be installed.  Why?

Reply | Quote

Replies

[PKCano]

Because you scheduled the time for the reboot/install to 11:00pm. What you did was just a regular reboot.

BTW, did you have Pause set and the time ran out? There seems to be a bug (or MS intention) to include the Feature Update with the monthly patches when Pause runs out.

• This reply was modified 4 years, 10 months ago by PKCano.

Reply | Quote

I had pause set and there was no update to 2004 – I currently get the 2004 download message – but I have set the TargetReleaseVersionInfo registry key set to 1903.

cheers, Paul

Reply | Quote

I believe I had a pause set.  I know that the 2004 update would have been installed sometime, so I do not care when the update installs, as long as it causes no problems (which I cannot guarantee).

Is Windows 10 smart enough to know that I have installed the update and that I do not need a reboot at 11 PM tonight?

I noticed that the Windows Update log was cleared, so the only entry is the 2004 update.

If I install a monthly update and then do a regular reboot, will that install the monthly update(s) I have just installed?  Or is Windows 10 reboot selective in what it installs?  Note that I have been running Win 10 “in production” on my desktop for only about two weeks.

 

Reply | Quote

OK, so 2004 is already installed.
Do you have June updates for 2004 in the Windows Update queue? I would guess it updated during the install. In the Taskbar search box type “winver” (without quotes. If it is Win10 v2004 Build is 10941.329, it is up to date.

Reply | Quote

I have not checked the update queue.  Winver says I am running 10941.329.  But I did get a pop-up window about scheduling a reboot.  The update queue says that NS had auto-installed

2020-05 Cumulative Update for .NET Framework 3.5 and 4.8 for Windows 10 Version 2004 for x64 (KB4552925)

2020-06 Security Update for Adobe Flash Player for Windows 10 Version 2004 for x64-based Systems(KB4561600)

and those are pending a reboot.

Reply | Quote

A regular reboot should go ahead and install those updates.
I would go through any settings you have made in the past anywhere in the system. MS is notorious for resetting them to their defaults. Default programs, file associations, privacy settings, etc.

Reply | Quote

To answer the topic/ thread title question;
I’d say it’s the difference between having fast-start enabled or disabled

Windows - commercial by definition and now function...

Reply | Quote

Microfix, I seem to recall that a requested restart is always a real reboot, regardless of fast boot settings. It’s the shutdown / startup that’s affected by that setting. But that’s a bit off topic.

To the original poster: You’re saying Microsoft updated your system from v1909 to v2004 against your wishes? Are you sure you had your system set to defer feature updates? Specifically:

-Noel

Reply | Quote

I guess that I am the original poster.  I have been running Win 10 in production for only a few weeks, and I have no idea what I had set for Windows Updates.  I tried to postpone the monthly updates as long as possible until AskWoody was below DEFCOM-2.  The only problem I have seen with 2004 is that after a reboot, my Samsung ML3312-ND printer is offline; I have to disconnect the USB cable and re-connect it to get the printer back online.  Not a big problem, but the cable is a bit inaccessible.  I will have to run a controlled test after my next reboot.

Reply | Quote